User Guide · Property Attorney
The Property Attorney's Guide to Estimatics
What Estimatics records about every piece of evidence, what a CERTIFY account shows on screen, what that supports in appraisal and litigation, and, stated plainly, what it does not prove.
7 min read
The questions that get asked
In appraisal and litigation, digital evidence draws scrutiny that a claim file rarely anticipates. Was this the condition at the time? Has this file changed since it was captured? Who produced it, and on what?
A folder of photographs and a scope in Xactimate can't answer any of those. This page describes exactly what Estimatics can, and is deliberate about the limits, because an overstated evidentiary claim is worse than no claim at all.
What the server records, on every plan
Estimatics splits the record in two: what the device reports, and what the server can observe on its own. Both are kept; only the second is used to check the first. This is recorded on every account, whatever the plan.
| Recorded | What it means |
|---|---|
| Server-side SHA-256 | The fingerprint the server computes from the bytes it actually received, not the value the uploader sent |
| Device-declared SHA-256 | The fingerprint the iPhone computed at capture. Kept, never trusted alone |
| Verification result | The comparison between the two |
| Clock offset | The gap between the device clock and the server clock at upload |
| Location permission | Whether location was granted, denied or unavailable at capture |
| Capture origin | Your team, or an outside FIELD Lite invitation |
| Device details | Device model, OS version, timezone, and the app version that produced the file |
| Device signature | iPhone captures are signed at capture with a key held in the phone's secure hardware (Apple App Attest). If the phone can't sign, the capture is saved unsigned. Files uploaded from the web have no device signature |
Evidence events are append-only: added, never edited or removed.
The verification results
"Verifying" · "Verified" · "Changed in transit" · "Not verified" · "Couldn't check"
"Not verified" is not "Verified", and the difference carries weight. "Not verified" means the device that sent the file gave no fingerprint to compare against. That's typical of documents uploaded from an office computer. The server's own fingerprint still doesn't depend on the uploader's word, but without a device fingerprint you can't detect a corrupted upload or a device misreporting what it sent. Which result is sufficient is a judgment for whoever reads the file. The record keeps one of these results for every file; a CERTIFY account sees them on screen, as described below.
What a CERTIFY account shows
The record above exists on every account. On a CERTIFY account, everyone on the team can see it:
- "Evidence integrity": a summary on the job's Overview and History tabs, such as "All 42 files in this job are verified" or "40 of 42 files in this job are verified", with how many are still being checked, how many weren't verified, and whether any changed in transit. Copies made in Estimatics (annotated or trimmed photos) are counted separately, and their originals are kept unchanged.
- "History": a timeline of the job by day, filtered by "Evidence" or "Job activity". Uploads, verifications, annotations and removals all appear here.
- "Evidence log": open any photo, video or document and the viewer shows "SHA-256 (device)", "SHA-256 (server)", "Verification" and "Verified at". The "Evidence log" button lists every event for that file and its copies, oldest first.
- "Copy full log for a carrier": copies the job's whole evidence log as plain text, ready to paste into an email. Estimatics doesn't send it anywhere on its own, and there is no PDF export of the history.
On FIELD and SCOPE, the viewer shows only the file's SHA-256.
Removing files, and legal hold
- On a paid CERTIFY account, removing a photo hides it from the job and its reports, but the original is kept in Estimatics' evidence storage. Its evidence log marks it "File no longer available".
- On other plans and during the free trial, deleting a photo is permanent.
- On every plan, removing a photo also removes the findings that came from it.
- Legal hold: while a job is on legal hold, its files can't be removed. Holds are placed and released by Estimatics support, not from the web app.
What this does not prove
- Not that the damage is real, or caused by the loss. Integrity is about the file, not the interpretation.
- Not that anyone was physically present. It records whether the device reported a location and whether permission was granted. A device can be wrong; permission can be denied.
- Not the moment of capture. It records the device's timestamp and how far that device's clock sat from the server's. That is evidence about the timestamp, not proof of it.
- Not admissibility. A court decides that under its own rules.
- Not a signed or sealed report. Report PDFs aren't digitally signed today, no independent timestamp seal is applied, and no third party notarizes the record.
- Not liability or coverage.
What it supports is narrower and easier to defend: the file in the record is byte-for-byte the file the server received, and here is everything the server could observe about how it got there.
ℹ Note
Estimatics does not produce a downloadable evidence package, a certified evidence report or a public verification link today. On CERTIFY, the evidence log comes from "Copy full log for a carrier" and from each file's "Evidence log".
Completeness, separately from integrity
Whether a file is intact and whether it is complete are different questions. Each area of the job carries a checklist marked "Complete", "Partial", "Missing" or "Not evaluated". Findings show the photo they came from, and the AI proposes findings while a person confirms them. In the estimate, every line built from findings links back to its finding and photo, and "What's missing" lists the facts the scope is still presuming. It's the pass to run before a file faces adversarial review.
Cause & Origin, on CERTIFY
On CERTIFY accounts, reports can include a Cause & Origin section, written by the AI from the job's evidence: three to five sentences on the most likely cause and origin, stating uncertainty where the evidence doesn't support a conclusion. It goes into the Damage, Analysis and Complete reports, on insurance-claim jobs only.
It is an analytical aid, not expert testimony, and it does not assign liability. The PDF can't be edited by hand: changes are requested from Esti in the report viewer, and each one creates a new version.
→ What Cause & Origin claims, and what it refuses to
What you receive from a client's file
- The report PDF. "Finalize" freezes the delivered version so it can no longer be edited. A finalized report can still be deleted from the job by the account's Super Admin or Estimator, so keep the copy you were sent.
- A photo share link. "Share" creates a link that works for 24 hours, with no login. The page shows every photo in the job with its notes, voice transcripts, GPS location and AI analysis, and "Download All" downloads all of them. It shows no custody data, and videos, scans and documents aren't included.
- The evidence log, on CERTIFY, as plain text from "Copy full log for a carrier".
How firms use it
Most property attorneys receive the file from a PA or contractor working in Estimatics. Firms that run their own field inspections can sign up directly: the iPhone app needs iOS 18.4 or later, and only Field Inspectors and Super Admins sign in on the iPhone.
Request a demo to discuss how this fits your litigation workflow.
Related in the Help Center
Already a customer? Visit the Help Center →
