A damage request may require a reviewer to assess visible condition, timing, responsibility, ownership, coverage, and the amount requested. A condition record can support those questions, but it does not answer them by itself.
A few photos taken after damage is discovered may not show prior condition or when a change appeared. Platforms and insurers apply their own terms, deadlines, exclusions, and documentation requirements.
This guide explains documentation that may support a damage request and the limits of each record. No documentation system guarantees approval or payment.
Why Documentation Gaps Matter
When a platform or insurer evaluates a damage claim, they are asking three fundamental questions:
- What was the documented condition before the stay? A current baseline may provide comparison context, but it does not independently attribute a later change to a guest.
- Was the request made within the applicable deadline? Platforms and policies set their own notice and filing windows. Missing one may affect eligibility.
- Does the material address the requested facts? A reviewer may need room context, prior condition, discovery timing, responsibility information, ownership records, and cost support.
A photo of damage may show the present condition without showing whether it changed during a particular stay. A documented baseline and routine comparison record can add context, while the reviewer still decides causation and coverage.
Documents a Reviewer May Request
Requirements vary by platform, policy, and claim. Review the current terms that govern your request. A reviewer may ask for:
- Dated photographs or video showing the damage clearly, with enough context to identify the location and severity.
- Description of the damage including what was damaged, where it is located, and what caused it (if known).
- Prior-condition documentation showing the item or area before the reported change, subject to the record's scope and timing limits.
- Timeline documentation showing when the damage was discovered relative to the guest's checkout.
- Repair or replacement cost estimates from a qualified professional or retailer.
A later photo cannot reconstruct earlier visible condition. If prior-condition context matters, create and preserve that record before the condition changes.
Airbnb's August 1, 2026 Evidence Terms
Airbnb’s Host Damage Protection Terms, last updated August 1, 2026, require legitimate and verifiable evidence that is true, accurate, and not doctored or falsified, including through artificial intelligence. The terms also require timely filing, responsibility and cause information, ownership, loss amounts, and supporting documents. Airbnb decides eligibility and outcomes.
TurnAudit preserves the uploaded original, computes its SHA-256 digest from stored bytes, and requests an RFC-3161 timestamp. When granted, the token verifies the uploaded digest existed no later than the timestamp time. These controls do not establish recording time, location, operator, cause, completeness, coverage, or approval. See the integrity explainer.
This guide is general information, not legal or insurance advice. Platforms and insurers decide claims under their own terms.
Claim Windows Are Short: Know Yours
Platforms and policies set their own reporting windows. Airbnb’s Host Damage Protection Terms, last updated August 1, 2026, describe an applicable 14-day notice period and a separate applicable 30-day payment-request period. Other requirements and exclusions also apply. Follow the current terms governing your request.
The practical challenge is the same regardless of the exact number: you need to discover the damage, document it properly, and start the process while the window is open. If your cleaner doesn’t notice a stain until they start cleaning, and back-to-back bookings mean the scene changes that afternoon, the real deadline is much tighter than the paper one.
A pre-clean walkthrough can document visible condition after guest checkout and before cleaning changes the scene. After upload, TurnAudit records file-integrity and timestamp status. The walkthrough does not independently establish when it was recorded, how the guest left every area, or who caused a condition.
Prior-condition documentation cannot be recreated after the condition changes. Build the routine before an issue arises.
Building the Evidence Chain
A review package may organize four layers of documentation:
Layer 1: The Baseline
The baseline is a room-by-room reference showing visible condition in the camera's path. It may help a reviewer compare later records, but it does not guarantee coverage of every surface or item.
A walkthrough can preserve sequence and room context that isolated photos may miss. Its value depends on recency, camera coverage, image quality, and accurate property context. Update the baseline when furniture, decor, fixtures, or finishes change.
TurnAudit's baseline recording feature creates a visual comparison reference for later pre-clean and post-clean walkthroughs.
Layer 2: Pre-Clean Documentation
After guest checkout and before cleaning, record visible condition in each listed room. This preserves context before cleaning may change the scene, without deciding responsibility.
If cleaning starts before documentation, the scene may change before a stain, scratch, or misplaced item is recorded. A pre-clean walkthrough can preserve comparison context but cannot answer causation by itself.
Layer 3: Post-Clean Documentation
After cleaning, record the listed rooms again. The post-clean walkthrough supports turnover review and comparison with visible pre-clean condition. A human still decides what changed and what needs follow-up.
If a stain was visible in the pre-clean walkthrough and is still visible after cleaning, that is important information: it may represent damage that cannot be cleaned and needs repair or replacement. If it is gone after cleaning, it was likely a surface-level mess rather than permanent damage.
Layer 4: The Claim Package
When you need to file a claim, you assemble your evidence from the previous three layers into a complete package:
- Baseline recording of prior visible condition in the recorded area
- Pre-clean recording after checkout and before cleaning
- Post-clean recording for comparison after cleaning
- Upload integrity records and timestamp status, with their stated limits
- Repair or replacement estimates
This four-layer chain organizes condition, timing, and cost support for review. Platforms and insurers still apply their own requirements and decide what the materials establish.
How Video Adds Context
Video and photos document different scopes. A walkthrough can add sequence and room context, subject to what the operator records.
Video follows the camera path. A walkthrough may include areas that selected photos omit, but it still captures only what enters the frame and does not guarantee complete coverage.
Video can provide spatial context. A close-up photo may not show a mark’s location or scale. A walkthrough can show surrounding room context, limited to what the operator recorded and what the camera captured. It does not independently establish cause.
The uploaded file can carry integrity records. TurnAudit hashes the stored upload and requests an RFC-3161 timestamp. When granted, the token applies to the uploaded file’s digest as a whole. It does not separately timestamp each frame or establish recording circumstances.
A continuous walkthrough preserves sequence. It can provide room context that isolated photos may miss. It does not independently establish when, where, or by whom the scene was recorded, and it cannot show areas outside the camera view.
Timestamps: Useful, With Defined Limits
When granted, an RFC-3161 token attests that an uploaded file digest existed no later than the timestamp time. Reviewers may use that fact with other records, but it does not determine responsibility, recording time, location, or claim validity.
An RFC-3161 token alone does not establish:
- That your baseline was recorded before the guest's stay
- That your pre-clean walkthrough was recorded after the guest checked out
- That you discovered the damage within the required notification window
- That the damage was not present during a previous turnover
TurnAudit requests the RFC-3161 timestamp after upload. When granted, it applies to the uploaded file digest and establishes only that the digest existed no later than the timestamp time.
Organizing a Review Package
Having the evidence is one thing. Presenting it in a format that a claims reviewer can easily understand is another. When you file a damage claim, you do not want to send raw video files and expect the reviewer to figure out what they are looking at.
A well-formatted damage claim report includes:
- A summary of the damage with location and description
- Side-by-side comparison of baseline condition vs. current condition
- Timestamp status and verification material for uploaded originals
- Clearly labeled advisory frames, if included, kept separate from Tier 1 originals
- Property and guest stay details for reference
TurnAudit organizes a three-tier export: Tier 1 uploaded originals and verification material, Tier 2 advisory AI material labeled not evidence, and Tier 3 optional host-supplied support. Reviewers still apply their own requirements.
Documenting Conditions During Pre-Clean
Routine pre-clean documentation may help a host notice and record visible conditions before cleaning changes the scene.
If a cabinet handle appears broken during the pre-clean walkthrough, the cleaner can record it and the host can review the original promptly. Other records and the applicable reviewer still determine timing, responsibility, coverage, and outcome.
Routine records do not prevent damage or establish who caused it. Their value is preserving visible context for comparison with other documentation.
Building Your Documentation System
If you do not currently have a documentation system in place, here is how to get started:
- Record a baseline. Walk through each listed room in its intended state. Remember that coverage is limited to the camera path and image quality.
- Make pre-clean walkthroughs routine. Record after guest checkout and before cleaning starts. Use a consistent room-by-room checkout inspection checklist.
- Record post-clean walkthroughs. After cleaning, record the listed rooms again for comparison and human review.
- Preserve originals and verification material. TurnAudit hashes stored upload bytes, seals the uploaded original, and requests an RFC-3161 timestamp.
- Know your notification deadlines. Review the current platform and policy terms. Missing a deadline may affect eligibility.
Routine documentation takes operating time and may help preserve useful context for a later review. Its value depends on your portfolio, risk, platform terms, and whether the captured record addresses the issue in question.