Evidence is not photos. Evidence is documentation a reviewer can verify without trusting the host. This guide explains what separates claims that get paid from claims that get denied, and how to build the evidence record before damage occurs.
Most hosts use the word "evidence" to mean photos. Reviewers use it to mean documentation they can independently verify. These are not the same thing, and the gap between them is where most claims fail.
A photo on a host’s phone is documentation. It records that something existed at some point. A reviewer looking at it cannot confirm when it was taken, where it was taken, or whether it was edited. They can only see the image. That means they must decide whether to trust the host. Discretion enters. Trust gets applied conservatively. Claims get reduced or denied.
Evidence that a reviewer can verify independently removes the trust question. A photo with a server-verified timestamp, GPS coordinates tied to the property address, and a public verification URL tells the reviewer exactly when and where the photo was taken, without the host having to assert anything. The reviewer confirms it. The claim moves forward.
The practical implication: the question to ask about any piece of documentation is not "does this show the damage?" It is "can a reviewer verify this without taking my word for it?" If the answer is no, it is documentation. If the answer is yes, it is evidence.
Evidence quality is not binary. It exists on a spectrum across four dimensions. Understanding each dimension tells you where your current documentation is weak and what to fix before filing.
Can the reviewer confirm the evidence is what you say it is, without trusting you? This covers server-verified timestamps, GPS coordinates, chain of custody, and tamper-evidence. Evidence that cannot be authenticated is assertion, not proof.
Does the evidence cover everything a reviewer needs to decide? A before record, an after record, documentation of the specific damage, and corroboration of the dollar amount. Missing any one forces discretionary judgment.
Was the evidence captured at the right moments and is the filing still within the window? Post-stay inspection completed same day, claim filed early in the 14-day window, 72-hour guest contact period observed before escalation.
Is the claim written to signal a credible host filing a factual report? Specific and neutral language, itemised amounts with documentation, professional submission format. The smallest dimension, but the fastest to improve before filing.
For a scored assessment across all four dimensions, the free Airbnb Evidence Checklist Generator identifies the specific gaps most likely to reduce or deny your claim before AirCover reviews it.
The most common evidence failure is not bad photos. It is no before record. Hosts who only produce post-stay documentation after damage occurs cannot prove the damage was not pre-existing. The guest’s defence is always the same: "it was already like that." Without a pre-stay inspection showing the area undamaged from the same booking, that argument cannot be closed.
Reviewers processing hundreds of claims per week apply a fast triage. When a host cannot produce evidence that the property was undamaged before the guest arrived, the reviewer has no defensible basis for approving the claim. Denial is the lower-risk outcome. That is the outcome the process produces.
The before record cannot be created after damage is discovered. It must exist before the guest arrives. A pre-stay inspection completed before every guest, automatically, as part of the turnover workflow, is the only reliable way to ensure the before record exists when it is needed. Hosts who start building this record only after a bad guest have already lost the claim that would have made them start.
Practically: the before record for the current claim was the after record from the previous turnover. Hosts who run consistent pre-stay and post-stay inspections at every checkout build this record automatically, for every booking, without needing to think about it during a dispute.
A host who builds their evidence system reactively, after damage occurs, is already too late for the most important part. The evidence system that wins claims is operational, not reactive. It runs before every checkout, regardless of whether anything looks wrong.
Timestamped walkthrough of every guest-accessible area, captured with software that records GPS coordinates and timestamp server-side. This is the before record for the current booking and the after record for the previous one. It takes five to ten minutes.
Same walkthrough, same rooms, same order, completed before any cleaning begins. Once a cleaner has entered, the legal boundary between guest and cleaner responsibility is compromised. The inspection must happen first, every time.
Every inspection must produce a page anyone can open in a browser without logging in. Confirm the link works before you close the turnover. An inspection that did not produce a verification URL did not produce evidence.
Additional close-up photos, a contractor quote on company letterhead, and saved guest messages. These supplement the routine record. They do not replace the before record, which must already exist.
Confirm the 14-day window is open, check that the before record covers the damaged area, verify that the claimed amount is itemised and documented, and review the claim description for neutral factual language. This takes 30 minutes and changes the outcome.
AirCover reviewers do not run a formal scoring rubric on each submission. They run a triage. Can I verify the timeline? Can I verify the evidence? Does this look like a credible claim? What does the dollar amount tell me about the host’s expectations?
High-quality evidence allows that triage to complete in under a minute. The reviewer opens the verification URL, sees timestamped before-and-after pairs, confirms the GPS coordinates match the property, reads a neutral two-sentence damage description, and sees a specific itemised amount with a contractor quote. The decision is straightforward.
Low-quality evidence forces more time and more judgment. When the metadata is unverifiable, the reviewer must decide whether to trust the host. When the before record is missing, the reviewer must decide whether the damage could be pre-existing. When the amount is a round number with no documentation, the reviewer must decide whether it is accurate. Every discretionary decision is applied conservatively. Denials and reductions are the safe outcome for reviewers who cannot verify.
The practical implication: hosts with weak evidence are not submitting a claim so much as making a request. Whether it is granted depends on factors outside their control. Hosts with strong evidence are submitting a claim the reviewer can verify. The decision follows the evidence, not the reviewer’s discretion.
The guest can claim damage was pre-existing. The reviewer cannot close that argument. Denial is the safest outcome.
Photos sent through WhatsApp, downloaded from iCloud, or shared via messaging apps lose timestamps and GPS. The reviewer sees undated, unlocated photos.
A claimed amount of $500 or $1,000 with no quote or receipt signals estimation. Reviewers reduce or deny amounts they cannot verify against documentation.
Once the cleaner has entered, the legal boundary between guest and cleaner responsibility dissolves. Damage documented after cleaning cannot be reliably attributed to the guest.
Pre-stay and post-stay inspections paired automatically at every checkout. GPS-verified, server-timestamped. Public report URL the reviewer opens without a login. The before record that wins claims exists by default, before you need it.
The questions hosts ask most often about Airbnb evidence, with direct answers.
Evidence in an AirCover claim is any documentation a reviewer can independently verify without relying on the host's word. This includes photos with intact server-verified timestamps and GPS coordinates, a pre-stay inspection showing the damaged area undamaged, a post-stay inspection taken immediately after departure, a contractor quote or repair receipt, and saved guest messages. Photos on a device that the host controls, without verifiable metadata, are documentation, not evidence.
Quality matters more than quantity. Eight photos with verifiable timestamps, GPS coordinates, and a clear before-and-after structure outperform forty photos without any of those properties. The photos that matter most are: a before record of the damaged area from the pre-stay inspection, the same area in the post-stay inspection, and three or more close-up angles of the specific damage. Supplementary photos of the same item add marginal value after the third angle.
A pre-stay inspection is a timestamped walkthrough of the property completed before each guest arrives, documented with photos covering every guest-accessible area. It is the before record that proves the property was undamaged at the start of the stay. Without a pre-stay inspection, any damage found after checkout can be attributed to a previous guest, the cleaning crew, or pre-existing wear. The pre-stay inspection is the single most important piece of evidence in a damage claim, and the one most hosts skip.
Airbnb accepts them, but reviewers treat them with skepticism. Phone EXIF metadata records the device clock time, which any host can change. Photos sent through WhatsApp, downloaded from iCloud, or processed by any image editor lose their metadata entirely. When a reviewer cannot independently verify the timestamp or location, they must decide whether to trust the host. That is a discretionary decision, not an evidence-based one. Software that records metadata server-side at capture removes the trust question entirely.
Documentation is a record the host created. Evidence is a record a reviewer can verify. A photo on your phone is documentation. A photo with a server-verified timestamp, GPS coordinates tied to the property, and a public verification URL is evidence. The practical difference is what happens when the guest disputes the claim. Documentation that cannot be verified becomes a word-against-word dispute. Evidence that can be independently confirmed is a closed question.
Missing the before record. Hosts who only produce post-stay photos cannot prove the damage was not pre-existing. The guest's defence is always "it was already like that." Without a pre-stay inspection showing the area undamaged from the same booking, that argument cannot be closed. Reviewers who cannot establish that the damage was caused by the guest in question default to denial.
A contractor quote converts a round-number estimate into a verifiable amount. A host claiming $800 in damage with no documentation is asserting a number. A host claiming $820 with a quote on company letterhead from a named contractor is providing corroboration. Reviewers who can verify the dollar amount approve faster and at the claimed amount. Round numbers without documentation are frequently reduced or used as grounds to question the overall claim credibility.
High-quality evidence produces outcomes the host can predict. Low-quality evidence produces discretionary outcomes. A host with strong evidence, including verifiable timestamps, a before record, a post-stay inspection, and a contractor quote, gives the reviewer nothing to push back against. The amount paid reflects the documented cost. A host with weak evidence leaves every element of the payout to the reviewer's judgment, and that judgment is applied conservatively.
You can improve what you add at the incident stage: additional close-up photos, a contractor quote, saved guest messages. You cannot retroactively produce a pre-stay inspection. The before record must exist before the guest arrives. Hosts who discover damage and then attempt to build the evidence record face the fundamental gap of having no proof the damage was not already there. The routine evidence record must be built before it is needed.
Hosts must file AirCover claims within 14 days of guest checkout, or before the next guest checks in, whichever comes first. The window determines urgency, not quality. A timely claim with adequate evidence outperforms a late claim with excellent evidence. If you are approaching the deadline, file with the evidence you have and note that supporting documentation is being gathered. A claim filed on day 14 with mediocre evidence is recoverable. A claim filed on day 15 with excellent evidence is not.
No. The Evidence Checklist Generator scores your documentation across four quality dimensions before you file, identifies the specific gaps most likely to reduce or deny the claim, and returns a score you can act on before AirCover sees it. It does not interact with Airbnb or file anything on your behalf. It is an assessment tool that tells you where you stand before the decision is made, not after.
Every checkout inspection you run builds the before-and-after record that decides every future claim. Hosts who treat documentation as routine win disputes that others never see coming.
Free plan, no credit card. Ready in 2 minutes.