Damage Claims With Photos, Timestamps and a Paper Trail

A claim usually fails on documentation, not on the damage. Four artefacts, captured in the right order, decide most of these conversations.

Last updated: October 21, 2026

You find the burn mark on the counter after the cleaner has wiped it down. The damage is real, the guest is gone, and all that's left to argue with is a photo taken an hour too late. Most claims don't fail because the damage was minor. They fail on the file.

Key Takeaways

• The file decides, not the damage. A clear scratch with no baseline photo is a story. A blurry one with a dated record is a claim.
• Four artefacts, in order. Scale photo, timestamp, written record, unbroken thread with the guest.
• Photograph before you clean. A wiped surface removes the thing you needed to show.
• Notify the same day. A message sent a week later reads as an afterthought.
• Ask for replacement cost, not a feeling. A number tied to a receipt is easier to answer than one tied to annoyance.

Why claims fail

A claim fails in one of four ways, and none of them is about how bad the damage looks.

The first is timing. The host finds the damage after the turnover, and the turnover is what destroys the evidence. A cleaner doing the job properly removes the spill, the mark and the debris that made the problem legible. By the time anyone photographs it, the frame shows a clean counter and a story.

The second is scale. A photo of a stain on a white surface tells a reviewer nothing about size. Without a coin, a ruler or a hand in frame, the same photo can describe a scuff or a hole.

The third is attribution. Which booking, which night, and was the damage there before? A host with no baseline record can't answer, and a claim that can't name the booking is one the other side can treat as generic.

The fourth is tone. Hosts write when they're angry, and anger forces the other side to answer it rather than the damage. The thread becomes an argument about politeness, and the photos stop mattering.

Each of these is fixable before the guest arrives. That's the useful part: none of it needs hindsight, and all of it is cheap.

The four artefacts

Four things, and each answers a question the other side will ask.

A photograph with scale. Two frames, not one: a wide shot showing where in the room the damage sits, then a close shot with something for reference — a coin, a card, a tape measure. The wide shot proves location, the close shot proves size.

A timestamp you can defend. Not the file name and not your memory: the capture time on the image, plus the booking it belongs to, written in the record. If the file's timestamp gets stripped in transit, the record is the backup.

A written condition record. One page per unit, checked at the start and end of every stay. It needs to be consistent, dated, and specific enough to say "the mark was not there on the twelfth" rather than "the unit was fine".

An unbroken message chain. Everything in writing, in one place, in order. Once a conversation moves to a phone call, the chain breaks. Keep the call if you like, but put the outcome back in writing the same day.

None of the four is expensive. What makes them work is that they corroborate each other: the photo shows the damage, the timestamp places it, the record establishes the baseline, the thread shows you raised it promptly.

The order they have to be captured in

The sequence isn't a formality. Get it wrong and the artefacts stop supporting each other.

Before the guest arrives. The baseline. Photograph the rooms the way you'd photograph them for a listing, plus close-ups of the surfaces that take damage: worktops, dining table, sofa, bathroom fittings, television. Date the set and file it against the booking. This is the step most hosts skip, and it's the one that makes the other three usable.

At the moment of discovery. Stop. Don't clean, don't move the object, don't ask the cleaner to deal with it. Wide shot first, then close with scale, then a note in the record with the time and who found it. Two minutes here is worth more than an hour of explanation later.

After the unit is secured. Write the record entry while the detail is fresh: room, surface, what it is, approximate size, and what you believe caused it. Write what you saw, not what you concluded. "A circular burn, about the width of a coaster, on the left of the counter" survives scrutiny. "Guest burned the counter" invites an argument about intent.

The same day, not the same week. Message the guest through the channel the booking came through, so the thread stays attached to the reservation. Say what you found, attach the photos, name the amount and its basis, and give a date for a reply. Leave it there. A follow-up after three days is reasonable; four messages in an evening is not.

Before any repair. Photograph the damaged item in place, then the replacement or the receipt. Once the repair is done, the before-state is gone, and a claim that can only show an after-state has a hole in it.

One practical note on the record. Keep it in one place per unit and one format. A log split between a notebook, a photo album and a messaging app is one nobody can assemble under time pressure. Key it to the booking reference so the two can be joined later without guesswork.

That reference is the part software can hold for you. On localsbnb.com, read-only questions return the booking, the nights and the charges, so the record has a fixed point to attach to.

Writing the message that closes it

The message does more work than the photos, because it's the part a person reads first and remembers.

Open with the facts and no adjectives. What, where, when. Then the photos, attached rather than described. Then the number: replacement cost from a receipt or a quote, or cleaning cost from an invoice. If you don't have it yet, say when you will rather than guessing high.

Then the ask, stated once. A specific amount, a date for an answer, and what happens next if there isn't one. Keep the last part neutral. "If I don't hear back by Friday, I'll take this to the platform's resolution process" is a sentence, not a threat, and it gives the guest a choice.

Two things to leave out. Don't characterise the guest, and don't describe the stay. A message about "the state your group left the flat in" invites a reply about the group rather than the burn. And don't offer a discount in the same breath as the claim; it tells the other side the number was never firm.

Then keep the thread clean. Every reply gets an answer within a day, even if the answer is that you're waiting on a quote. Silence reads as either weakness or indifference, and both cost you.

What this method buys you is a file that stands on its own. If the guest pays, it's because the file made paying the easier option. If the platform reviews it, the reviewer gets four artefacts that agree with each other instead of a paragraph of frustration. It doesn't guarantee a payment, and no honest guide can promise one. It does mean the outcome turns on the damage rather than on your documentation.

FAQ

Can I take the photos after the cleaner has been in?

You can, but the claim is much weaker. The cleaner removes the spill, the debris and often the mark itself, leaving a clean surface with your description attached. If the turnover has happened, photograph what remains, write down what was removed and when, and say so plainly rather than presenting the photo as the moment of discovery.

Does a timestamp on the photo file count as proof?

It helps, and it isn't enough on its own. File timestamps can be edited and are sometimes stripped when an image is sent through a messaging app. Put the time in the written record next to the booking reference, and send the original file through the booking thread so the platform holds its own copy.

What if the guest disputes it?

Answer the specific point they raise with the artefact that addresses it. If they say the damage was already there, the baseline answers. If they say it's smaller than claimed, the scaled close-up answers. If they stop replying, send one short follow-up and then use whatever process the channel provides.

None of this needs new software, and most of it takes about ten minutes per checkout. What it needs is a habit that starts before the guest arrives. If the calendar is already where your bookings live, localsbnb.com is the place to keep the reference you'll be writing into the record at eleven at night.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. What a deposit can cover, how long you have to raise a claim, and what a platform's resolution process will accept differ by jurisdiction and by channel. Confirm the current rules with the competent authority and the current terms of each platform you use before you rely on a claim.