The evidence build sheet

Airbnb raised the bar on proof.
Here is how to clear it.

Legitimate and Verifiable Evidence is not a slogan, it is a specification. This guide is the build sheet: the six parts of a compliant evidence file, the mistakes that fail it, and how to capture proof that meets the 2026 standard every time.

By Checkout ShieldLast updated 2026-07-1912 min read
Quick answer

What you need to know in 60 seconds

To meet Airbnb's 2026 Legitimate and Verifiable Evidence standard, a file needs six things: original unedited files, a verifiable capture time, a verifiable location, an unbroken chain of custody, a before-and-after pairing, and no AI-generated or altered images.

Phone EXIF metadata is not enough, because it is easily stripped by messaging apps and easily faked, so it cannot carry a claim on its own.

The standard rewards proof a reviewer can check without trusting you. It comes from Airbnb's April 2026 Terms of Service, and the rest of this guide turns it into a build sheet you can follow on every stay.

Originals

Unedited files, never reconstructed

Time + GPS

When and where, independently checkable

Sealed

A hash proves nothing changed since capture

Verifiable

A public link a reviewer can check

Section 1

From a rule to a build sheet

The 2026 rule changes explain what Airbnb decided; this page explains what to do about it. The phrase Legitimate and Verifiable Evidence sounds abstract until you turn it into a specification, a list of concrete properties your documentation either has or does not.

Done that way, compliance stops being a worry and becomes a checklist. A file either has the six properties below or it has a gap, and the gap is exactly where a reviewer discounts it or a guest disputes it. The underlying principles are in the evidence guide; this is the 2026 build. Treat what follows as a specification you can hand to a cleaner or a co-host, not a philosophy you have to internalise.

Section 2

The anatomy of a compliant file

Six requirements, each with a plain meaning and a concrete way to meet it. This is the whole standard on one page:

RequirementWhat it meansHow to meet it
Original filesUnedited, not cropped, enhanced, or reconstructedCapture in place and submit the original
Verifiable timeWhen the photo was taken can be confirmedA server-verified timestamp, not just file metadata
Verifiable locationWhere it was taken can be confirmedGPS recorded at the moment of capture
Chain of custodyProvably unchanged since it was capturedA tamper-evident hash on each original
Before and afterA baseline to compare the damage againstPaired check-in and checkout records
No AI or editingNo generated or altered imagesNever enhance, filter, or recreate a photo

The chain-of-custody and location requirements map to tamper-evident evidence and a GPS-verified report, and the before-and-after pairing is the whole point of a check-in inspection.

Section 3

Why each requirement is there

None of the six is bureaucratic. Each one closes a specific way a claim gets discounted or disputed. Understanding why makes them stick:

01
Original filesA reviewer can only trust what has not been touched. The moment an image is cropped or enhanced, they cannot tell your honest edit from a dishonest one, so the safe assumption becomes suspicion.
02
Verifiable timeDamage claims live and die on when. A verifiable timestamp proves the damage was documented during your window, not reconstructed later, which is the single fact a wear-and-tear defence attacks.
03
Verifiable locationLocation ties the damage to your property. Without it, a reviewer cannot rule out that a photo was taken somewhere, or something, else, and an unanchored image is easy to dispute.
04
Chain of custodyIt is not enough that a file is unedited; you have to prove it. A tamper-evident seal turns "trust me, I did not change it" into "check for yourself," which is the difference the 2026 standard rewards.
05
Before and afterThe claim is about a difference between two states, not a single sad photo. A dated baseline is what converts "there is damage" into "this guest caused this damage during this stay."
06
No AI or editingThis is now an explicit rule, not just good practice. A generated or altered image can sink an entire claim, and the risk is often accidental, from an app that enhances by default.

Read together, the six describe one idea: evidence a reviewer can trust without trusting you. That is the shift the 2026 standard formalised, and it is why the how-to-meet-it column keeps pointing at capture that happens outside your own control.

Section 4

Why phone metadata is not enough

The most common evidence package is a folder of phone photos, and hosts assume the date and location baked into each file will carry the claim. Under the 2026 standard, it usually will not, for reasons that have nothing to do with your honesty:

  • EXIF is editable. The timestamp and GPS a phone writes into a photo can be changed in seconds with free software, so a reviewer cannot treat them as proof.
  • Messaging apps strip it. Send a photo through a chat app and the metadata is often removed in transit, leaving an image with no verifiable origin at all.
  • It is self-controlled. The data lives on your device, under your control, which means it fails the core test of independent verifiability.

The fix is not to abandon your phone; it is to capture through something that records the time, location, and integrity independently. That is the difference between EXIF metadata you assert and a record a reviewer can confirm.

Section 5

Server-verified vs self-verified capture

The whole standard reduces to one distinction. Evidence is either self-verified, where you vouch for it, or server-verified, where an independent system does. The 2026 rules are built to prefer the second.

Self-verified

A phone photo whose time and location come from the file itself. The reviewer has to trust the host, and the host controls everything, so an accusation of tampering is hard to disprove.

Server-verified

Capture where the time, location, and integrity are recorded on a system the host does not control. The reviewer checks the record rather than trusting the host, which is exactly what the standard asks for.

This is why the answer to almost every requirement in the table points the same way. A dated baseline, a verifiable timestamp, an integrity hash: each is strongest when it is produced somewhere you cannot quietly change it. Independence is the feature, not a nice-to-have.

Section 6

The mistakes that fail it

Most non-compliant files fail on the same handful of avoidable mistakes: photos taken days later with no verifiable time, images forwarded through a chat app that strips their data, a genuine photo run through an enhancer until it looks altered, or damage shots with no baseline to compare against.

The safest habit in 2026 is the simplest: capture the original, do not touch it, and submit the original. Every gap in a claim traces back to a photo that could not prove when it was taken, where, or that it had not been changed.

If a guest ever turns the standard against you and claims your evidence was fabricated, verifiable originals are the answer, as covered in accused of faking evidence.

Section 7

The pre-file checklist

Before you submit a claim, run the file against the standard one last time. If every answer is yes, it is difficult to discount and difficult to dispute:

  • Are these the original files, untouched since capture?
  • Can the capture time be verified independently, not just read off the file?
  • Is the location tied to the property?
  • Is there a before shot from check-in to pair with the after?
  • Can you show nothing changed since capture?
  • Is anything edited, enhanced, or generated? If so, remove it.
This is what Checkout Shield does

A file that meets the 2026 standard by construction.

Checkout Shield captures originals in place, records a server-verified time and location, seals each photo with a tamper-evident hash, and pairs check-in with checkout, so every one of the six requirements is met without you thinking about it.

  • Original captures, never edited
  • Server-verified GPS and timestamps at capture
  • Tamper-evident hash on every original photo
  • Paired check-in and checkout for a true baseline
  • Public verification link a reviewer can check
  • Free plan for one property
Section 8

The standard in a real dispute

Put two hosts side by side with identical damage, a cracked bathroom tile a guest denies causing, and the 2026 standard decides between them before either says a word.

Host A: built the file

A check-in capture shows the tile intact, server-verified time and location. A checkout capture shows it cracked, same day, sealed with a hash. The guest's denial has nothing to attach to. The reviewer opens one link and the comparison is decided.

Host B: improvised

Two checkout phone photos, taken a day late, no baseline, forwarded through a chat app that stripped the metadata. Real damage, honest host, but nothing a reviewer can independently verify. The guest's pre-existing-damage defence cannot be ruled out, and the claim is discounted.

The damage was the same. The honesty was the same. The only difference was whether the evidence met the standard, and that difference is the entire outcome. This is why the specification is worth building into your routine before you ever need it: the file is the argument, and it has to exist before the dispute starts. The damage claim guide walks the same logic through the full claim.

FAQ

Got a question? Here are the answers.

The questions hosts ask about the 2026 evidence standard, answered plainly.

01

What is the 2026 evidence standard on Airbnb?

It is Legitimate and Verifiable Evidence: the standard Airbnb applies to damage-claim documentation since its April 2026 Terms of Service update. In practice it means original, unedited files whose time and location can be independently verified, with no AI-generated or altered images. It rewards proof that is captured properly and penalises anything reconstructed.

02

What makes an evidence file compliant?

Six things: the files are originals, the capture time is verifiable, the location is verifiable, there is an unbroken chain of custody proving nothing changed, there is a before-and-after pairing to establish a baseline, and nothing is AI-generated or edited. A file with all six is difficult for a reviewer to discount and difficult for a guest to dispute.

03

Does phone photo metadata meet the standard?

Not reliably. The date and location a phone writes into a photo, its EXIF metadata, is easily stripped by messaging apps and easily faked, so it cannot carry a claim on its own. The standard is better met by server-verified capture, where the time and location are recorded independently rather than trusted from the file.

04

What is the difference between server-verified and self-verified evidence?

Self-verified evidence relies on data the host controls, like a phone photo's own metadata, which a reviewer has to take on trust. Server-verified evidence records the time, location, and integrity on a system the host does not control, so it can be checked independently. The 2026 standard is built to favour the second, because it removes the need to trust the host.

05

How do I avoid failing the standard by accident?

The most common accidental failure is editing a genuine photo, running it through an app that enhances or upscales it can make real evidence look altered. Capture the original, do not touch it, keep the chain of custody intact, and submit the original rather than a screenshot or a re-saved copy.

06

Is meeting the 2026 standard worth the effort?

Yes, because it is the difference between a claim that pays and one that is discounted. It also future-proofs you: as fabricated evidence gets easier to make, verifiable originals get more valuable, and a guest accusing you of faking photos has nothing to stand on when your evidence is provably real.

Shape what we build next

Help us to improve

Was this guide helpful? Rate it and tell us what to build next. We read every single response.

Tap a star to rate
Would your file clear the bar?

Test it against the 2026 standard.

The free Damage Documentation Score audits your workflow against Legitimate and Verifiable Evidence, and shows exactly which part of a compliant file you are missing.

Free plan, no credit card. Ready in 2 minutes.