Why AirCover claims get denied — the pattern behind the rejection

We started PreArrive after reading a few hundred host forum threads that all ended the same way. A guest does something — smokes inside, brings four extra people, leaves at 3 PM on a same-day turnover — the host files with AirCover or opens a Resolution Center case, and weeks later the case closes with no money moved. The host has photos. The host has receipts. The host has the rule, right there in the listing. And the claim still gets denied.

After enough of these, the denials stop looking like bad luck and start looking like a pattern. The damage is rarely the problem. What fails is the file — the evidence package the host hands over. And it fails in a small number of predictable ways.

Disclosure is not acknowledgment

This is the one that catches almost everyone, so it's worth being precise about.

Disclosure is you stating a rule or a fee. It lives in your listing description, your house manual, your check-in message. "No smoking anywhere on the property." "$500 smoking remediation fee." You wrote it down, it's published, anyone can read it.

Acknowledgment is the guest confirming they saw that specific rule and agreed to it — ideally with a timestamp, ideally before they checked in.

These are two different things, and a claim needs both. Disclosure alone establishes that the rule existed. It does not establish that the guest ever agreed to it. When an adjuster or a Resolution Center agent looks at a file with strong disclosure and no acknowledgment, the gap they see is: the host published a rule, and there's no proof the guest accepted it. From the platform's side, charging a guest's card on that basis is hard to defend. So they don't.

The host reads the denial as "they didn't believe me." It's closer to "the file didn't contain the half that lets us act." A rule in a listing is the host talking. An acknowledgment is the guest talking back. Only the second half moves money.

What counts as acknowledgment — and what doesn't

Hosts often do have something they think is acknowledgment. It usually isn't, quite.

A chat message — "sounds good, see you Friday" — is not acknowledgment of a specific fee. It's a pleasantry that happens to be near the rules. Nobody reading it later can tell which rule, if any, the guest was responding to.

A checkbox at booking that says "I agree to the house rules" is weak. It's one bulk action covering everything at once, with no record of which rules were shown or whether the guest read past the first line. Resolution Center staff have seen ten thousand of those; they don't carry much weight.

A signature on a paper form left on the kitchen counter is acknowledgment, but undated and impossible to tie to a moment before check-in.

What a claims reviewer is actually looking for is narrower: the guest, individually, confirming each rule and each fee, on a record that captures when they did it and that the when was before they took possession of the property. Line by line, not one blanket "I agree." A timestamp that pre-dates check-in. Some trace of how it happened — an email click, an IP, a signature they drew themselves.

That's a higher bar than most hosts realize they need to clear. It's also completely achievable before the guest ever arrives. The problem is purely one of timing: almost nobody collects it in advance, because in the moment everything is fine and there's no dispute to motivate the paperwork.

The 14-day window

The second pattern is quieter and costs hosts who actually have a decent case.

Airbnb's host damage protection terms ask you to submit your documentation within 14 days of the damage or loss. (Airbnb publishes this in their Help Center under host damage protection — worth reading the current version yourself.) Two weeks sounds generous until you're inside it.

Here's how the window gets eaten. The guest checks out. You don't find the damage until turnover, maybe a day later. The cleaner photographs it; you start a back-and-forth with the guest, because that's the decent thing to do and because the platform wants to see you tried. The guest goes quiet, or denies it, or counter-claims. You wait. You escalate. By the time you've accepted the guest isn't going to pay and you formally open the case, ten days are gone — and you're now assembling evidence, hunting for the chat where you "mentioned" the fee, screenshotting your listing, under a deadline.

A claim assembled in a panic on day 13 is a worse claim. Things get missed. And the single thing most likely to be missing is the acknowledgment — because it never existed, and there's no way to manufacture it after the fact. You cannot go back and get a guest to sign something dated before a check-in that already happened.

The fix isn't to move faster after the incident. It's to have the acknowledgment already on file before the stay, so that when the clock starts you're attaching a document, not building one.

What the file is usually missing

If you lined up the denied claims and the paid ones, the paid files tend to have four things the denied files don't:

1. A disclosure dated before check-in. Not just "the rule existed" — the rule was delivered to this guest, on a date, and that date is earlier than their arrival.
2. Per-item acknowledgment. The guest confirmed each rule and each fee individually. An adjuster can point at the exact line and say: they saw this one, specifically.
3. An audit trail. Two events, ideally — the guest opening the disclosure and the guest signing it — each with a timestamp and an IP. This is the spine that makes the record hard to wave away.
4. Something tamper-evident. A content hash, or any mechanism showing the text the guest agreed to is the same text you're now submitting. It closes the "you edited this afterward" objection before anyone raises it.

None of this is exotic. It's the kind of record a claims reviewer is trained to look for — disclosure, acknowledgment, timestamps, a way to tell whether the text was edited later. It just has to exist before the incident, because after the incident it's too late to create the part that matters.

A sober note on what this is

We build a tool that produces exactly that file — a signed, timestamped acknowledgment the guest completes in about ninety seconds before check-in, and a PDF certificate you can attach to a claim. But it's worth being clear about what such a certificate is and isn't.

It is not a verdict. It does not decide the dispute, and it does not guarantee a payout. Whether any given Airbnb agent, insurer, or small-claims clerk is persuaded is their call, and it always will be.

What it is, is evidence — and evidence is the thing most denied claims are short of. A certificate doesn't make your case unbeatable. It makes your case legible: it puts you on the same documentary footing as any party that did its paperwork in advance. That's not a small thing. Most of the time, the denial wasn't a judgment that the host was wrong. It was a judgment that the file couldn't support a charge. Fix the file, before the stay, and you've removed the most common reason these claims fail.

If you want the longer argument for why a signed acknowledgment changes the outcome, we lay it out on why PreArrive exists. And if you'd like to see what the evidence actually looks like on paper, there's a sample certificate — clearly marked as a specimen — you can open and read end to end.