How to File an AirCover Claim That Actually Gets Paid

Checkout minus two hours. The cleaning crew sends photos: a cracked bathroom mirror, a stained duvet, a broken dresser handle. You file an AirCover claim. Six days later: denied. Reason given — “insufficient evidence to confirm guest-caused damage.”

The damage was real. The denial was also technically correct — because the documentation package didn't meet AirCover's evidentiary standard. Those are two different problems, and only one of them is recoverable before checkout.

What AirCover Actually Requires

AirCover's Resolution Center has a specific evidentiary standard for approving claims. The published policy says “photos and documentation of damage.” The operational standard is stricter:

• Pre-damage baseline. Evidence that the item was undamaged before the booking. Photos from a prior check-in or professional cleaning report work. A listing photo showing the mirror intact works. No baseline = no claim.
• Post-damage evidence during the booking window. Photos timestamped within the reservation period. The moment of discovery matters — photos taken after the next guest's checkout are inadmissible.
• Causal link to guest action. Not “damage occurred.” “Damage was caused by a specific guest's action during a specific confirmed stay.” Weather events, appliance failures, and wear do not qualify — they have different insurance paths.
• Repair or replacement estimate. A professional quote, not a self-assessed value. Claims without third-party estimates are routinely reduced or denied.

The Evidence Package Structure

Every AirCover claim should be filed as a structured evidence package, not a photo dump. The structure:

1. Pre-stay baseline documentation. 3–5 photos of the affected item or area from the most recent pre-booking service. Labeled with date and reservation preceding the damage claim.
2. Post-checkout discovery documentation. Photos taken within 24 hours of checkout, timestamped. Same angles as the baseline. Labeled with the date and the reservation in question.
3. Written damage description. One paragraph per item: what it is, where it was, what condition it was in before the stay, what condition it's in now. No emotional language. Factual description.
4. Third-party cost estimate. Screenshot or PDF of a contractor or retailer quote. For item replacement, a current retail link showing replacement cost.
5. Timeline. Check-in timestamp → checkout timestamp → discovery timestamp → cleaning report timestamp. Gaps in the timeline create denial surface. Cover every gap.

The 72-Hour Filing Window

AirCover claims must be filed within 72 hours of checkout or before the next guest checks in — whichever is earlier. This is an absolute cutoff. No exceptions.

This means the evidence package must be assembled before the 72-hour window closes, not after. For hosts who have back-to-back bookings with less than 24 hours between checkouts, the effective filing window can be under 6 hours after discovery.

The operational implication: the cleaning protocol must include a condition documentation step at every checkout. Not optional. Not on request. Every turnover.

Common Denial Reasons and Recovery Paths

AirCover denials cluster around three patterns:

• No pre-damage baseline. Recovery: only possible if you can produce prior-stay documentation retroactively — a listing photo, a prior cleaning report, or a prior guest communication referencing the item. If no baseline exists, the claim is unrecoverable. Prevention is the only fix.
• Damage type outside AirCover scope. Appliance failure, weather events, and wear are not AirCover events. Recovery: none within AirCover — these route to your STR insurance policy. Prevention: know your coverage layers before you need them.
• Insufficient cost documentation. Recovery: add a professional estimate and appeal. AirCover allows one appeal per denied claim. The appeal with added documentation overturns insufficient-evidence denials at a meaningful rate.

The Documentation Infrastructure Behind Claims

A single successful AirCover claim is a documentation problem. Consistent AirCover outcomes across multiple properties are an infrastructure problem.

Hosts who resolve the infrastructure problem — systematic checkout documentation on every turnover, pre-stay and post-stay photos filed in a retrievable system — rarely face the denial pattern. Their claims arrive pre-packaged with the evidence AirCover requires, because that evidence was generated as a matter of operational routine.

Hosts who manage documentation reactively — only when damage occurs — generate claims that match the denial pattern reliably. They have the damage, but not the baseline.

For claims AirCover does deny after proper documentation, the appeal protocol covers the next step.