What your STR insurer wants to see in a damage claim.

A short-term-rental damage claim succeeds or fails on the file behind it. Below is a plain account of the documentation an adjuster expects, the one gap that quietly sinks most host claims, and how a signed acknowledgment fits into a file a carrier can actually act on.

The documentation an adjuster expects.

Short-term-rental coverage varies — a dedicated STR policy, a landlord policy with an STR endorsement, or a platform protection program like AirCover sitting alongside it. The wording differs, but the file an adjuster reads is broadly the same. These are the items a carrier generally looks for in a guest-caused damage claim.

01

Proof of ownership or insurable interest in the property

The policy declarations page, a deed, or a management agreement that shows you have a stake in the property the claim covers. This is rarely the sticking point, but a missing declarations page slows a file down before it is even read.

02

A dated incident description — what happened, and when

A short, factual account: the date of the stay, the date the damage was found, and what was found. Adjusters work from timelines. A description that places the loss inside a specific reservation is far easier to act on than "a guest damaged the place."

03

Photographic evidence of the damage, ideally before-and-after

Turnover photos from before the stay and damage photos after it. Photos establish the loss. They are necessary — but on their own they only show that something is broken, not who is responsible for it.

04

Repair or replacement cost — estimates, invoices, receipts

A contractor estimate, a repair invoice, or receipts for replacement items. The number claimed should be supported by a document, not asserted. Vague or round figures invite a lower settlement.

05

Evidence the guest was responsible — and on notice

This is the item most short-term-rental claims are thin on. The adjuster wants to connect the damage to the guest, and to see that the guest was on notice about the rule or the condition involved. A house rule the guest never engaged with is weak on the second half.

06

Documentation submitted inside the policy or claim window

Most policies and platform protections set a deadline for supporting documentation after a loss. A file assembled in a rush on the last eligible day is a worse file. The strongest claims are the ones where the evidence already existed before the loss.

This is general operating guidance, not coverage advice. Your policy wording controls — read it, and confirm specifics with your broker or carrier.

Disclosure without acknowledgment.

Walk through declined or reduced short-term-rental claims and a pattern shows up. The host usually has the damage half of the file — turnover photos, a cleaner's account, a repair invoice. What the file is missing is the link between the damage and the guest's responsibility for it.

A house rule sitting in your listing or a PDF you emailed is disclosure: it shows the rule existed and was made available. It does not show the guest read that specific rule or accepted it. When an adjuster has strong damage evidence and nothing tying the guest to the rule, the gap they see is exactly that — and a claim that asks a carrier to assign responsibility on disclosure alone is a hard claim to pay in full. The host reads the outcome as "they didn't believe me." It is closer to "the file couldn't support the responsibility."

Why timing is the whole problem

You cannot manufacture an acknowledgment after a stay — you cannot get a guest to sign something dated before a check-in that already happened. The acknowledgment has to be collected before the stay, which means it is either already in the file when a loss occurs or it never will be. After the incident, it is too late to create the part that matters.

What carriers ask for — and where a signature fits.

A signed acknowledgment does not replace the rest of the claim file. You still need photos, estimates, and a clear incident description. What it does is close the responsibility gap — and it happens to answer several of the things an adjuster asks for in a form a carrier finds legible.

What an adjuster looks for

  • The guest was on notice about the rule or condition
  • A timeline that places the loss inside a specific stay
  • A record that cannot be quietly edited after the fact
  • Itemized amounts tied to something the guest saw

What a signed acknowledgment provides

  • On notice. The guest taps each rule and each fee individually before check-in — not one blanket checkbox — so the record shows that specific item was seen.
  • A timeline. A two-event audit trail — the email-link click and the signed action — each with a timestamp and IP, both dated before the stay.
  • An unedited record. A SHA-256 content hash over the packet text. A one-character change produces a different hash, so the version submitted is provably the version signed.
  • Itemized amounts. Each fee carries a label, an amount, and a unit — exactly as the guest acknowledged it — so a claimed number maps to a disclosed and accepted figure.

See what that evidence looks like

Evidence, not a guarantee.

A signed acknowledgment is evidence, not a verdict. It does not decide a claim, it does not override a policy exclusion, and whether any given adjuster is persuaded is their call. What it does is put you on the same documentary footing as any party that did its paperwork in advance, and remove the single most common reason these claims come up short — a disclosed rule that was never acknowledged.

It is also worth keeping the rest of the file in good order regardless: date your photos, keep your invoices, and submit inside the window. A signed acknowledgment makes a strong file stronger. It does not rescue a thin one on its own.

Build the part of the file you can't add later.

Collect a signed acknowledgment before every check-in, so the evidence already exists if a loss occurs. Free covers one property, no credit card.

Related, if you're going deeper.