Damage Claims and Your Policy: Assembling the Evidence Pack

A claim fails on documentation far more often than it fails on merit. The pack has to be assembled before the guest checks out, not after.

Last updated: September 26, 2026

Most claims that fail were arguable on the facts and hopeless on the file. The damage was real, the guest was plainly responsible, and the case still went nowhere because the photographs came late or the report never existed. The work that decides a claim happens during the stay, not after it.

Key Takeaways

• Claims fail on the file. Documentation decides far more outcomes than the merits do.
• The pack is built, not found. Nothing in it can be created once the guest has left.
• Timing beats detail. A dated photograph from the right moment outranks a better one from the wrong moment.
• One report, one shape. The same template every stay leaves no argument about what you normally do.
• Raise the finding first. The claim and the conversation are two separate jobs, and the order matters.

What a channel needs before it will even look at a claim

A channel's claim process is a filter, and it screens on structure before it screens on merit. Whatever a platform's rules say — and they differ, so check that platform's current terms — the opening questions tend to have the same shape. What happened. When it was discovered. How it was reported. What the guest was told. And what you can show.

The order matters, because a claim arriving without a date and a description usually gets sent back rather than examined. A claim arriving complete gets assessed on its facts.

What counts as complete is set by the platform, and platforms don't agree with each other. Some expect the guest to be approached first. Some define a reporting window of their own. Some require photographs taken before the guest checked out. Because those requirements differ and change, treat any list you find, including this one, as a template, and confirm the current terms of the channel you're claiming on.

Two structural points carry across every channel. The claim belongs to a booking, so the evidence has to be attached to that booking rather than to a folder on your phone. And the report has to be dated, because everything downstream depends on the timeline.

The evidence pack, item by item

The pack is a small set of items, and each one answers a question the channel will ask.

The check-in condition record. Photographs or a short video of the unit as the guest receives it, with the date attached. This is your baseline, and without it you can't show that anything changed.

The damage photographs. Close, well lit, and showing scale, so a coin or a hand beside the mark communicates size without a caption. Several angles, taken in one sitting rather than across a week.

The condition report at checkout, written before the guest leaves. Not a repair estimate — a description of what changed, with the date and the areas covered.

The booking record. Dates, guest count, and whatever the guest agreed to: house rules, deposit terms, the pet clause if there is one. This is what connects the damage to an obligation the guest actually accepted.

The conversation record. Messages where the issue was raised, what the guest replied, and what they were told. Screenshots with the date visible, saved with the booking rather than in a chat app that will eventually rotate them away.

The cost evidence. What it genuinely takes to put the item right: an invoice, a quote, a replacement price. A figure you invented isn't evidence, and it's the item most often assembled from memory.

What's missing from the pack is worth naming too. There's no place for an opinion about the guest, no place for a speculative total, and no place for a photograph taken after a repair has already begun.

Timing: what has to be captured inside the stay window

Every item in the pack is perishable, and the window that matters is the stay itself. Not the days after checkout, when the guest is gone and the unit has already been cleaned.

The baseline photographs have to exist before the guest settles in, which in practice means between the last clean and the guest's arrival. If you clean the unit and photograph it in the same pass, the two sit close enough together to be credible.

The damage has to be found and photographed while the guest is still on site. This is the step most often missed, because hosts discover damage during the turnover clean, when the guest has already left and can no longer be asked about it.

The report at checkout has to be written before the guest leaves, even when it says nothing happened. A "nothing to report" entry costs a minute and establishes that you check every time. A file containing reports only for the stays where something broke tells its own story.

Then the claim itself. How long you have to raise it is set by the platform, and those windows differ and get revised, so read the current terms rather than working from habit. The safer discipline is to raise the claim as soon as the pack is complete rather than as soon as you find the time.

One habit makes the whole timeline easier: keep the booking and its evidence in the same place, so the stay you're describing is one you can date and find again rather than one you reconstruct from a camera roll. Where bookings from Airbnb, Booking.com, Agoda and Trip.com sit on one calendar at localsbnb.com, an arrival and a departure are two points you can read off directly. That's exactly what a dated pack needs.

Raising a claim without burning the guest relationship

A claim is a request for money from someone you may want to host again, and those two goals pull against each other. Doing both is possible, and it comes down to the order of the conversations.

Raise the finding before you raise the claim. A message describing what you found and asking what happened reads differently from a demand. Often the guest offers to cover it, and the claim never needs to be filed at all.

Keep the two subjects apart. One conversation is about the guest and the stay, another is about the money. Mixing them means a guest who feels accused defends their reputation instead of discussing the damage.

Send the detail, not the conclusion. Photographs with dates and one line of description do more work than a paragraph of complaint. A guest who can see exactly what you're describing is far likelier to accept it.

Assume good faith once. Most damage isn't deliberate, and a message that starts from that assumption keeps your options open. If it turns out not to be good faith, you've lost nothing and the pack is unchanged.

And keep the tone out of the claim itself. The pack is what the platform reads. Anything emotional belongs in the conversation with the guest, and ideally nowhere at all.

FAQ

What if I only notice the damage after the guest has left?

Then you build the pack from whatever exists: the baseline photographs, the checkout report if you wrote one, and the message where you raise it. What you've lost is the chance to ask the guest about it while they were still there, which is usually the most useful single step. Photograph the unit at every turnover so the next claim has a baseline to work from.

Do I need a professional estimate before raising a claim?

Only if you want the claim to survive contact with the process. What it actually costs to put the item right is what gets assessed, and a figure you can't support weakens an otherwise sound claim. A quote or an invoice is stronger than an estimate you wrote yourself, and it takes about the same time to obtain.

Should the guest know a claim is coming?

Yes, and before it's filed. A guest who learns about a claim from the platform rather than from you is a guest who will dispute it on principle. Telling them first also gives them the chance to settle it directly, which is faster and cheaper than any process.

A claim is won during the stay or not at all. Photograph the unit before and after, write the report before the guest leaves, keep the cost evidence real, and raise the finding before you raise the demand. When a season of stays and their evidence live in one place, the file for any single stay is something you can assemble in an afternoon rather than rebuild from memory. That one place is where the channels you sell on sit, at localsbnb.com.

---

This article is general guidance for hosts and isn't legal or platform policy advice; claim requirements, evidence standards and reporting windows are set by each platform's current terms and by local law, and those prevail.