—AirCover claim denied
Most denied claims fail for the same reason — and it usually isn't the damage. Below is a practical checklist of what AirCover and the Resolution Center ask for, with each item mapped to the field that answers it on a signed certificate.
01The common denial pattern
Walk through the denials and a pattern shows up. The host almost always has the evidence of damage — photos from turnover, a cleaner's account, receipts for the repair. What the file is missing is evidence the guest agreed to the rule or fee being charged.
A rule sitting in your listing is disclosure: it proves the rule existed. It does not prove the guest saw that specific rule or accepted it. When a Resolution Center agent looks at a file with strong damage evidence and no acknowledgment, the gap they see is exactly that — and charging a guest's card on disclosure alone is hard for the platform to defend. So the claim closes with no money moved. The host reads it as "they didn't believe me." It's closer to "the file couldn't support a charge."
You can't manufacture an acknowledgment after a stay — you can't get a guest to sign something dated before a check-in that already happened. The acknowledgment has to be collected before the stay. After the incident, it's too late to create the part that matters.
02The checklist
Each row is something the Resolution Center or an adjuster looks for, why it matters, and the field on a PreArrive certificate that answers it. Use it to audit your own claim file before you submit — or to see what a complete file contains.
Proof the rule or fee was disclosed before check-in
A rule that surfaces only after the incident does not support a charge. The disclosure has to pre-date the guest taking possession of the property.
On a PreArrive certificateDisclosure delivered, with a send timestamp earlier than the check-in date.
Proof the guest acknowledged that specific rule or fee
Disclosure shows the rule existed; it does not show the guest agreed. A bulk "I agree to house rules" checkbox is weak — staff want to see the individual item confirmed.
On a PreArrive certificateLine-by-line acknowledgments — each rule and each fee tapped individually, never one blanket checkbox.
A record of when, and from where, the guest engaged
A claim is easier to act on when there are timestamps and IPs an adjuster can lean on, not just a host’s account of events.
On a PreArrive certificateA two-event audit trail: the email click and the signature, each with its own timestamp and IP.
Evidence the document was not edited after the fact
If the text could have been changed after the guest agreed, the acknowledgment loses weight. The adjuster needs to know the version submitted is the version signed.
On a PreArrive certificateA SHA-256 content hash over the packet text. A one-character edit produces a different hash.
The guest’s actual signature, not a typed-name proxy
A drawn signature is a deliberate, effortful act. It reads differently from a checkbox or an autofilled name field.
On a PreArrive certificateA drawn signature image, embedded inline on the certificate.
Itemized damage or fees, tied to disclosed amounts
Vague "additional fees may apply" language is hard to charge against. The amount claimed should map to a fee that was named and acknowledged.
On a PreArrive certificateEach fee with a label, amount, and unit — exactly as the guest saw and acknowledged it.
Documentation submitted inside the claim window
Airbnb’s host damage protection terms ask for supporting documentation within 14 days of the damage or loss. A claim assembled in a panic on day 13 is a worse claim.
On a PreArrive certificateThe certificate already exists before the stay — when the clock starts, you attach a document instead of building one.
03What a complete file looks like
A PreArrive certificate is the file the checklist above describes — built before the stay, not after the incident. The guest taps each rule and each fee, draws a signature, and you keep a single PDF: disclosure dated before check-in, line-by-line acknowledgment, a two-event audit trail with IPs and timestamps, and a content hash. It doesn't decide the dispute — it makes your case legible to whoever does.
Hosts who use PreArrive most are the ones whose previous claim was denied. The pattern of what's missing repeats — once you've lost one, the gap is obvious. The certificate doesn't promise the next claim gets paid; it just keeps the same gap from being the reason.
Open a clearly-marked sample certificate, then start free — Free covers one property, no credit card.
04Keep reading