The Public Adjuster's Guide to Estimatics

Why the file wins the claim

Carrier disputes reduce to a small number of questions: is this damage real, is it from the loss, and is the documentation what it claims to be? Most PA files answer the first with a photograph, the second with an assertion, and the third not at all.

Estimatics is built to make each of those answerable — and to be precise about which ones it can't answer, because in appraisal an overstated claim is worse than no claim.

The workflow

1. Capture — walk the property with the iOS app, photos assigned to areas, syncing to the dashboard while you're still on site. Works with no signal.
2. Analyze — you trigger the AI on a photo or a whole area, and it proposes findings: damage type, severity, material, location, an evidence note, and a 0–100 score on the photograph's own quality. You confirm, correct, or delete each one.
3. Check coverage — the evidence completeness signal shows, area by area, whether the file is green, amber, or red. Fix the reds before you submit, not after a re-inspection request.
4. Scope — flag findings with +Scope and the AI builds the line-item estimate, priced against the property's ZIP code with its sources shown.
5. Deliver — compose a report, or export ESX into Xactimate at $10 per export.

What evidence integrity actually gives you

On every plan, including FIELD. The moment a file arrives, the server re-reads the bytes it received and computes its own SHA-256 — not the value the device claimed. It records the device's declared hash separately, the gap between the device clock and the server clock, whether location permission was granted or denied, the device model, OS, timezone, and app version, and whether the capture came from your team or a FIELD Lite invitation.

Verification lands in one of five states, and Unverifiable is not Match — the distinction is the point.

What it does not prove: that the damage is real, that someone was physically present, that the timestamp is accurate, or that a photograph is admissible. What it supports is narrower and more 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 arrived.

→ Evidence integrity in full

What CERTIFY adds

Cause & Origin — an AI cause-and-origin assessment written from your confirmed findings, three to five sentences, stating uncertainty explicitly where the evidence doesn't carry a conclusion. It composes into the Damage, Analysis, and Complete reports for a CERTIFY seat only.

Plus 5 ESX exports per user each month, included.

Which plan

The plan rate is per Estimator seat. Field inspectors are $39 and office staff $24 whatever your estimators are on.

SCOPE for active PAs — the report is your product, and SCOPE is where it's written and branded. CERTIFY when cause is part of the argument.

Getting started

1. Install the iOS app
2. Create a job and walk the property
3. Run the analysis, confirm the findings, check the coverage signal
4. Build the scope and compose the report

Request a demo to see a real inspection end to end.

Related in the Help Center

• How findings work
• Evidence coverage
• Evidence integrity and chain of custody
• Cause & Origin