What is Certified Evidence — and why does it matter in appraisal and litigation?

Every property professional has said some version of this in a carrier dispute: "I have photos." It is the most common defense when an estimate is challenged, and it is also the weakest.

Having photos is not the same as having evidence. Evidence requires provenance — a verifiable answer to three questions: When was this captured? Where was it captured? Has it been altered since capture?

Most field documentation cannot answer any of these questions at all. This is about closing part of that gap — and being exact about the part that stays open.

The problem with "I have photos"

A photograph stored on a phone, uploaded to a cloud service, downloaded to a laptop, and attached to an email has passed through at least four systems. Each of those systems may have compressed the image, stripped its EXIF metadata, or modified its file properties. By the time it reaches the carrier's desk, the photo is just a JPEG — a file with no verifiable provenance.

A desk adjuster or appraisal panel looking at that photo has no way to confirm it was taken at the claimed property, on the claimed date, by the claimed inspector. They have to take the submitter's word for it. And in disputed claims — the claims where documentation matters most — taking someone's word is not enough.

This is not a hypothetical problem. It is the reason photographic evidence can be set aside with a single sentence: "The submitted documentation does not sufficiently establish the scope of loss." That is not a statement that the damage does not exist. It is a statement that the damage has not been proven.

What per-file integrity hashing is

The concept is simpler than it sounds, and the best analogy is an old one: a wax seal.

You write a letter, fold it, and press a seal over the fold. Anyone who receives it can check whether the seal is intact. If it's broken, everyone knows the letter may have been opened.

A cryptographic hash works the same way. A hash is a fixed-length string derived from every byte of a file. Change one pixel and the hash changes completely. Compare the hash you have now against the one recorded earlier, and any alteration between those two moments is detectable.

The part that matters is who computes the hash. A record made entirely of the uploader's own claims can't corroborate anything about the uploader — if the device reports the time, the location, and the file's own hash, then a device that lies about one is trusted about all three.

So Estimatics splits the record in two. The device declares a hash. Then the server re-reads the bytes it actually received and computes its own, independently. Both are kept. Only the server's is used to verify the device's.

That comparison lands in one of five states: Match (the two agree — the strongest state), Mismatch (the file that arrived is not the file the device said it sent), Unverifiable (the server hashed it, but the device declared nothing to compare against), Unreadable, or Pending while the check runs.

Unverifiable is not the same as Match, and refusing to blur that distinction is the point of the whole design.

What Estimatics records

Alongside the two hashes, the server records what it can observe about how the file arrived:

Clock offset. The gap between the device's clock and the server's at upload. Not a guaranteed capture time — evidence about the timestamp.

Location permission state. Whether GPS was granted, denied, or unavailable when the file was captured, recorded honestly either way.

Device provenance. Device identifier, model, OS and version, device time zone, and the app version that produced the file.

Capture origin. Whether it came from a team member or from a FIELD Lite invitation sent to someone outside the team.

The authenticated account that uploaded it.

The event log holding all of this is append-only — entries are added, never edited or removed.

None of this is a paid tier. It runs on every account, on every plan, including FIELD.

What it means in appraisal and litigation

In an appraisal proceeding, the party with the more credible, more verifiable documentation is usually in the stronger position. The useful shift isn't that your photographs become unimpeachable — it's that you can state something specific and checkable about them instead of asking anyone to take your word.

The claim Estimatics supports is narrow and defensible: the file in the record is byte-for-byte the file the server received, and here is everything the server could independently observe about how it got there.

That is a real thing to be able to say. It is not the same as saying the photograph is proven authentic, and the difference matters more, not less, in front of a panel or a court. A narrow claim you can substantiate is worth more than a broad one that invites cross-examination.

What it does not do

Being precise here is the whole value of the feature, so this list is deliberately long.

It does not prove the damage is real, or that the loss caused it. Integrity is about the file, not the interpretation of what's in it.

It does not prove anyone was physically present. It records whether the device reported a location and whether permission was granted. A device can be wrong, and permission can be denied.

It does not prove the moment of capture. It records the device's timestamp and how far that device's clock sat from the server's.

It does not cover the gap between capture and upload. The server hashes what it receives. It cannot speak to what happened to a file before it arrived.

It does not make a photograph admissible. Admissibility is decided by a court under its own rules, and no vendor feature changes that.

It is not a digital signature and not a notarization. No third party attests to anything.

It does not assign liability or determine coverage.

A hashed photograph of a water stain establishes that the file in the record is the file the server received, with a documented provenance chain around it. It does not establish that the stain came from a covered plumbing failure rather than deferred maintenance. That determination still requires professional expertise, and it always will.

What the record does is move the argument. Less time spent on whether the documentation can be trusted, more on whether the assessment is right. That's a better place to be arguing from — which is a more modest claim than "beyond reproach," and it's the one that survives contact with opposing counsel.

Who needs this

This matters most in the cases where documentation is most likely to be challenged: large-loss claims, disputed scopes, appraisal proceedings, and litigation.

Public adjusters who regularly negotiate with carriers on behalf of policyholders benefit from evidence that withstands procedural scrutiny. When every photograph carries verifiable provenance, the negotiation centers on scope and pricing rather than documentation adequacy.

Restoration contractors who need to justify their work scope to carriers or property owners benefit from an integrity-verified record of conditions as found, work performed, and results achieved.

Property attorneys who represent policyholders in coverage disputes or bad faith litigation benefit from a documented provenance chain they can describe accurately, rather than a stack of files with nothing behind them.

Independent adjusters working on behalf of carriers benefit from documentation that protects them professionally — evidence that proves their inspection was thorough, timely, and accurately reported.

The standard for property claims documentation is rising. Being able to say exactly what your file establishes — and exactly what it doesn't — is how you meet it.