Evidence Integrity & Chain of Custody

What Estimatics records about every file the moment it arrives — SHA-256 verified against the bytes received, capture provenance, and an append-only event log — where CERTIFY lets you see it, and what it does not prove.

8 min read


Every file that reaches Estimatics is stamped, hashed, and logged by the server at the moment it arrives. This page describes exactly what that means, who can see it, and what it does not prove. It is deliberately precise about the limits, because in appraisal and litigation an overstated claim is worse than no claim.

Recording applies to every account, on every plan. It isn't a module to switch on.

Seeing the record is a CERTIFY feature. On a CERTIFY account (the 14-day free trial counts as CERTIFY), the History tab, each file's Evidence log, and the Evidence integrity card show you what was recorded. On FIELD and SCOPE the record is still kept, but those screens are not shown.


The problem it solves

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: what the device reports, and what the server can observe independently. Both are kept. Only the second one is used to verify the first.


What is recorded on arrival

RecordedWhat it means
Server-side SHA-256The hash the server computes by re-reading the bytes it actually received, not the value the uploader sent
Client-declared SHA-256What the device said the file's hash was. Preserved, never trusted on its own
Verification statusThe comparison between the two (see below)
Clock offsetThe gap between the device's clock and the server's at the moment of upload
Location permissionWhether GPS was granted, denied, or unavailable when the file was captured
Capture originWhether it came from a team member or a FIELD Lite invitation
Device provenanceDevice identifier, model, OS and version, device time zone, and the app version that produced the file

Hash verification runs as a background job rather than inline. A video is hundreds of megabytes, and making an upload wait on a full re-read would be the first safeguard dropped under pressure. So it's queued, and retried if it fails.


The five verification states

The words below are the same on every CERTIFY screen: the file viewer, the Evidence log, History, Overview, and the iPhone app. The gallery marks only Changed in transit and Couldn't check.

You seeMeaning
VerifyingReceived; Estimatics hasn't finished re-reading it yet. It takes a few seconds
VerifiedThe server's hash equals the one the device declared: "This is exactly the file the device captured." The strongest state
Changed in transitThey differ. The file that arrived is not the file the device said it sent. Capture it again
Not verifiedThe server hashed the file, but the device declared nothing to compare against. Documents uploaded from the web are the common case
Couldn't checkEstimatics could not re-read the stored file to check it

Not verified is not the same as Verified, and the distinction is the point. The server's own hash is the one that counts, because it's the only one that doesn't depend on the word of whoever uploaded. But without a declaration from the device, the other half is missing. Which of the two is enough is a judgment for whoever is reading the file.


Device signature on iPhone captures

Photos, videos and scan files captured in the Estimatics iPhone app also carry a device signature. At capture, the app signs a statement about the file with a key held in the iPhone's Secure Enclave (Apple's App Attest). The origin line on a file's History entry (and on iPhone, under Information) tells you which case a file is:

  • "Signed on a genuine iPhone by the Estimatics app at capture."
  • "Uploaded from the web — no device signature."
  • "Captured on a device that can't sign."
  • "The device signature didn't verify."

A signature never blocks a capture. If a device can't sign, the photo is saved anyway and says so.


Where to see the record (CERTIFY)

  • History tab. A timeline of everything that happened on the job. On CERTIFY it adds the Evidence view, the Evidence integrity summary ("All N files in this job are verified"), and Copy full log for a carrier, which puts the whole evidence log on your clipboard as plain text.
  • Evidence log, per file. Open a photo, video or document and use Evidence log in the Evidence Metadata panel. You get that file's events, oldest first, plus the events of its annotated or trimmed copies. The same panel shows both SHA-256 values, the verification state, and Retained until when it applies.
  • Overview. A compact Evidence integrity card, with View history to jump to the Evidence view.
  • iPhone. The same states appear under Information on a photo or video, and the Evidence integrity card and History are on Job Overview.

Evidence events are recorded append-only: entries are added, never edited or removed. The log is what lets you show the sequence: when a file arrived, what was stamped on it, and what verification concluded.

Full walkthrough: History and Evidence.


Removing a file does not erase the original

On a paid CERTIFY account, deleting a photo retires it: it leaves the job and the reports, and its findings are removed, but the original file is kept in Estimatics' evidence storage for its retention period. If the job is under legal hold, files can't be retired until the hold is released. On other plans, and during the trial, deleting a photo is permanent.


What this does not prove

Being precise here is the whole value of the feature.

  • It does not prove the damage is real, or that it was caused by the loss. Integrity is about the file, not the interpretation.
  • It does not prove someone 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 the device's clock sat from the server's. That is evidence about the timestamp, not proof of it.
  • It does not make a photograph admissible. Admissibility is decided by a court under its own rules.
  • It is not a notarization. No third party attests to anything today. Report PDFs are not digitally signed, and the independent daily timestamp seal is not turned on.
  • It does not assign liability or determine coverage.

What it does support is a narrower and more defensible claim: 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.


Not available today

  • A dedicated "Certified Evidence" report type. It is not in the New report menu.
  • Downloadable evidence packages and public verification pages.
  • Digitally signed or sealed report PDFs.

Getting the most out of it

  1. Leave location permission on. A denied permission is recorded honestly, and an honestly recorded absence is still a gap in the file.
  2. Capture in the iPhone app where you can. Files uploaded from the web carry no device signature.
  3. Keep the app updated. The app version is part of the provenance record.
  4. Watch for Changed in transit. It's rare, and it means the upload didn't deliver what the device had. Recapture rather than explain it later, and contact support@aiestimatics.com with the job if it keeps happening.


Last updated: October 2026 · Questions? Email support@aiestimatics.com

Last updated: October 2026 · Feedback on this article