A packet format for fast host claim review
Damage claims can become messy because photos, cleaner notes, estimates, guest messages, and platform deadlines live in different places. A good packet keeps the reviewer oriented without overstating the claim.
Recommended sections
- Claim summary: platform, reservation, claim type, amount, and deadline.
- Timeline: checkout, discovery, cleaning/repair steps, next guest check-in, and submission target.
- Evidence inventory: filenames, source, date captured, and what each file proves.
- Amount support: estimates, receipts, invoices, replacement links, and ownership proof.
- Guest/platform context: relevant messages, house rules, and prior disclosure.
- Open gaps: missing photos, missing receipts, uncertain cause, or unsupported amount items.
Best-fit claims
- Damage, missing-item, extra-cleaning, smoke odor, and pet damage claims with proof you can provide.
- Hosts or cohosts who want evidence organization before submission, not platform access.
- Claims where you can provide contemporaneous photos, notes, estimates, and messages.
Not a fit
- Fabricated, AI-generated, doctored, falsified, unverifiable, or synthetic evidence.
- Requests to log in, submit claims, contact guests, or provide legal, tax, insurance, or platform-policy advice.
- Any promise that a platform, insurer, guest, or payment method will reimburse the claim.
Do not send passwords, verification codes, guest payment details, platform login access, API keys, or private keys.