A guest broke your house rules — your options, in order

The threads all start mid-disaster. A neighbor texts a photo of cars down the block. The Ring cam shows eight people walking in for a two-guest booking. The cleaner calls from turnover: the whole unit smells like smoke. By the time a host posts to r/airbnb_hosts, the guest broke house rules hours or days ago, and the question is never "how do I prevent this." It's "what do I do now." This post is for that moment.

There's a real sequence here, and the order matters more than people expect. Do the steps out of order and you weaken your own case. So here's the playbook, in order, plus the one upstream step that quietly decides how well every later step goes.

When a guest broke house rules: document first, then message through the platform

Before you say a word to the guest, document.

Photograph everything, with timestamps. Smoke damage, the extra cars, the trash from a party, the pet bed that wasn't supposed to be there. Get the cleaner's photos too, with the date the file was taken. If you have a noise sensor or an exterior camera pointed at common areas, pull those readings now, while they still exist. Cameras get overwritten; memories get fuzzy. The record you build in the first hour is the one you'll be living with for the next two weeks.

Only then, message the guest, and message them through the platform. Not a text, not a phone call you'll later have to paraphrase. Airbnb's messaging thread is timestamped and retained. A calm, specific message ("We've noticed evidence of smoking in the unit, which our house rules list with a $500 remediation fee. Can you tell us what happened?") does two jobs at once. It opens the conversation, and it creates a dated record that you raised the issue promptly and gave the guest a chance to respond. That second job is the one hosts forget, and it's the one a Resolution Center agent actually reads.

Keep the tone factual. You're not winning an argument here. You're building a file.

The escalation ladder, and what each rung needs

When a guest violated house rules and money is now involved, there's a fixed ladder. You climb it one rung at a time, and skipping rungs tends to hurt you.

Rung one is the in-thread message you already sent. Many cases end here: a guest who knows they had four extra people and saw the fee in writing will often just pay.

Rung two is the Resolution Center, where you formally request funds. This is where your documentation gets weighed. The agent is looking at whether the rule existed, whether the guest knew about it, and whether your evidence is clean. (Airbnb changes these flows; read the current Help Center version yourself before you rely on any specific step.)

Rung three is AirCover or host damage protection, which generally comes into play for damage when the guest won't pay. Here the deadline bites: Airbnb's terms ask you to submit documentation within a set window after the loss, and that window is shorter than it feels. Assemble the file early, not on the last day.

The thing every rung has in common: each one asks, in some form, did the guest know, and can you prove it. Which is where cases split into two very different piles.

The fork: a signed acknowledgment vs "it's in my listing"

Here is where two hosts with identical incidents get different outcomes.

Host one, asked "did the guest know about the fee," answers: it's in my listing. The rule is published. Anyone could read it. But there's no record this particular guest ever saw that particular line, agreed to it, and did so before they arrived. That's disclosure without acknowledgment: the gap that sinks a large share of otherwise-decent claims. We wrote the long version of why that gap is fatal in why AirCover claims get denied, so we won't re-tread it here.

Host two, asked the same question, attaches a signed acknowledgment: this guest, by name, confirmed the no-smoking rule and the $500 fee individually, on a timestamped record dated before check-in, with a trail showing when and how they did it. That's not the host talking. That's the guest talking back.

Both hosts have the same photos. The difference is entirely in what each can put next to the photos. One file says "the rule existed." The other says "the guest agreed to this exact rule, on this date, before they had the keys." A reviewer can act on the second in a way they usually can't on the first.

To be exact about what this changes: the signed acknowledgment is evidence, not a verdict. It doesn't make the case automatic and it doesn't guarantee a payout — that call always belongs to the platform, the adjuster, or a clerk. What it does is move your file from the weaker pile to the stronger one. That's the whole game on the documentation side.

Prevention for next time: write rules that can actually be enforced

Once you've worked a case, the prevention angle stops feeling like overhead. Two things make the next incident easier to handle.

First, write enforceable rules. A rule like "no parties" is hard to act on; "no more than [X] total guests at any time, no events or gatherings, $[amount] fee for violation" is specific, has a number attached, and can be pointed at line by line. The common cases (extra guests, smoking, an unauthorized party, pets, late checkout) each deserve their own line with its own fee, not a vague paragraph. A house rules template gives you the structure so nothing load-bearing gets left out, and a rules generator helps you phrase each one tightly enough to enforce.

Second, separate the rule from the fee in your own head. The rule tells the guest what not to do. The fee is what you'll charge if they do it anyway — and a fee you've never written down with a number next to it is a fee you'll have trouble collecting. Itemize them.

This is the disclosure half of the file. It's necessary, and on its own it's still not enough, which brings us to the step that ties the whole sequence together.

Why the signature has to come before check-in

Everything above gets easier or harder based on one upstream decision: whether you collected the guest's agreement before they arrived.

You cannot manufacture acknowledgment after an incident. There's no honest way to get a guest to sign something dated before a check-in that already happened. So the moment the rule gets broken, the question of whether you have that signature is already settled, by a choice you made days earlier, or didn't.

Getting the signature before check-in also changes the dynamic on the guest's side, before anything goes wrong. A guest who individually confirmed "no smoking, $500 fee" and "no extra guests, $150 each" two days before arrival behaves differently than one who skimmed a listing. The rules stop being fine print and become something they personally agreed to. Some of the incidents simply don't happen, because the guest knew the line was real and that you'd be able to show they crossed it. That's the quiet value: the best version of this playbook is the one where you never have to run it.

This is the boundary worth being honest about. A signed acknowledgment is not a contract that decides the dispute, and it's not a guarantee you'll be paid. It's a stronger file — the difference between "the rule existed" and "the guest agreed to it, before they had the keys." If you want the reasoning in full, it's on why PreArrive exists. And if you want to stop running this playbook from behind, the move is to set the rules up so the next guest signs before they ever walk in. You can start drafting them with the additional rules generator.