Tamper-evident evidence

A standard phone photo carries metadata that the owner can change, delete, or strip. The file can be edited in seconds and re-saved with a new date. Because the reviewer has no way to detect this, they cannot give the photo full weight, no matter how clearly it shows the damage.

This is the quiet reason careful hosts still lose claims. The problem is not the quality of the picture. It is that nothing stops the picture from having been altered, so the reviewer treats it as a claim, not a proof.

Tamper-evident evidence binds the content to a record that lives outside the host’s control. In practice that means three things: the capture time is fixed by a system the host cannot rewind, the location is verified at capture, and the finished report is published at a permanent link that would visibly change if the file were edited.

With those properties in place, any later edit breaks the match between the file and its record. The reviewer does not have to trust the host. They can check.

Most damage disputes collapse into one word against another. Tamper-evident evidence removes that symmetry. The host has a record a third party can verify, and the guest has an assertion. Reviewers resolve that imbalance in favour of the verifiable side almost every time.

This is also why tamper-evident documentation matters most at check-in. A verifiable baseline plus a verifiable check-out is a closed loop that a guest cannot argue their way out of.