If you have ever submitted an AirCover damage claim and watched it die in review, you probably assumed the photos were the problem. They usually are not. The way the claim is written is what gets most denials — the same evidence, reorganised by an experienced host, regularly turns a rejection into a payout. That is because the AirCover specialist on the other end of your submission has roughly four minutes to triage it. If your narrative is disorganised, speculative, or emotional, the specialist treats the file as weak regardless of what is attached.
This guide walks through the exact anatomy of a winning AirCover claim — the structure, the language, the timing, the final review. It is built from hundreds of approved and denied claims shared across host forums in 2025 and 2026, plus the patterns Airbnb’s own Resolution Center coaches use internally.
The one thing every winning claim has: plausibility
Before you write a single word, understand the lens AirCover uses. The specialist is not asking “did damage happen?” They are asking: “is this host’s story plausible enough that approving it will not get flagged in audit?” That framing is everything.
Plausibility means three things in combination:
- A clear timeline — when the property was good, when the guest was there, when the damage was found. No gaps, no contradictions.
- Before/after evidence with matching angles, timestamps, and file integrity.
- A proportionate ask — the amount you claim matches what the damage actually costs to fix or replace.
Miss any of those and the default decision is denial, not because the specialist is hostile, but because approving a non-plausible claim puts their decision on the audit list.
The plausibility heuristic
AirCover specialists are not judges — they are risk-gatekeepers. Your job is to hand them a file so tightly organised that approving it is the low-risk option. Make denying harder than approving.
The 5-section claim structure that wins
Every claim that gets paid follows the same rough skeleton. It does not matter if the damage is a €80 stain or a €2,400 appliance — the structure scales. Do not submit a wall of text. Use the section headers below as literal paragraph breaks in your message.
1. One-line summary
Open with a single sentence that names the guest, the booking dates, and the damage category.
“Guest Priya K., reservation HMFXXXX, stayed 11–14 April 2026. Queen mattress and mattress protector damaged by an unsealed liquid.”
No emotion, no adjectives, no backstory. The specialist needs to know within five seconds what file they are looking at.
2. The timeline
Three timestamps, in order:
- Last confirmed good state — photo or inspection before check-in.
- Guest’s check-out — the official timestamp from Airbnb, not “when they left.”
- Damage discovery — when you or your cleaner found it, with the inspection photo timestamp.
3. The evidence packet
List what you are attaching, numbered, one line each. Example:
- Pre-check-in mattress photo, 11 Apr 2026 09:14 CEST
- Post-check-out mattress photo, 14 Apr 2026 12:40 CEST
- Cleaner statement with signature, 14 Apr 2026
- Replacement quote from Matratzenhaus GmbH, €480 incl. VAT
4. The ask
One sentence: “I am requesting €480 for full mattress replacement, matching the attached quote.” That is it. No hedging, no “I hope this is reasonable.”
5. What you did to resolve it
Mention that you contacted the guest through the Resolution Center first, give the timestamp, and state whether they responded or declined. AirCover requires this step before they will even look at a claim — proving you did it up front shortcuts an entire round of back-and-forth.
Language that gets paid vs language that gets denied
The vocabulary in a claim matters more than most hosts realise. These are real phrases from real denied claims:
Phrases that trigger denial
"I think the guest might have..." — speculation, not fact. Rewrite as observed damage.
"It was clearly a party." — inference without evidence. State what you saw (empty bottles counted, footage timestamp).
"The guest was rude/dishonest/a nightmare." — character attack. Removed from the file; your credibility drops.
"I am sure the damage is worth about €500." — unsupported valuation. Attach a quote.
Replace those patterns with observed → documented → quoted. You saw damage, you documented it with a photo, the repair has a number attached. Everything else is noise.
The evidence burden: what AirCover actually verifies
AirCover’s review team has internal tooling that does three things with your attached photos:
- EXIF timestamp check — reads the capture time from the file metadata. If your photo was taken three days after checkout, they see it.
- File integrity — detects whether the image was re-saved, edited, or re-compressed (WhatsApp strips this; native camera preserves it).
- Angle comparison — they eyeball whether your before/after pair shows the same object from a comparable position.
This is why hosts who shoot on WhatsApp lose claims they should win — the metadata is gone, and the file looks like it could be from anywhere. Always upload native-camera files, not screenshots, not WhatsApp exports.
Timing: when to submit (not immediately, not late)
Counterintuitive but important. Submitting within the first 30 minutes of discovering damage feels responsible, but it usually costs you money. Here is why:
- You have not yet contacted the guest via Resolution Center → the claim will bounce back.
- You have not yet gotten a written repair quote → the claim will sit while AirCover waits.
- You have not yet received your cleaner’s full report → the timeline will be thin.
The sweet spot is 24–72 hours after discovery: enough time to gather the attached pieces, not so much that you look disorganised. And you still have eleven days of buffer before the hard 14-day deadline — do not burn it on one message you will have to re-send.
The 60-second pre-submit review
Before you hit the submit button, run this checklist:
Pre-submit audit
✓ Timeline has three timestamps and no gaps
✓ At least one before-photo and one after-photo with matching angles
✓ EXIF data intact on every photo (no WhatsApp, no screenshots)
✓ A written quote or receipt for the amount claimed
✓ Resolution Center message sent to guest with timestamp logged
✓ No emotional language, no speculation, no character attacks
✓ Ask is proportionate — would a stranger call €480 fair for a ruined mattress?
If any row fails, stop. Fix it. Resubmit once. You get effectively one clean shot per claim — revisions read as “the host keeps changing their story” and that is the fastest way to a denial.
Bottom line
A winning AirCover claim is not the one with the most evidence. It is the one a tired specialist can triage in four minutes and feel safe approving. Structure, language, and timing do more work than the attached photos — the photos are just the backup for a case the narrative already made.
If you have not yet set up the documentation workflow that makes all of this possible, that is the actual prerequisite — no amount of good writing saves a claim built on missing evidence. HostProof handles the evidence side so you only have to think about the narrative. Every inspection becomes a before-state, every checkout becomes an after-state, every photo keeps its metadata, every claim writes itself from the audit trail.
Sources & further reading
- AirCover for Hosts — Airbnb official
- AirCover for Hosts · Terms & coverage details
- Host community discussion on r/AirBnBHosts, r/AirBnB, and the BiggerPockets STR forum
Last updated: 2026-04-21. Percentages and patterns in this article reflect Airbnb’s publicly documented policies plus aggregated host-community reports. Where figures are not directly attributable to an official Airbnb statistic, they should be read as community-observed patterns rather than official data.