Cause & Origin

In a disputed claim, cause is usually the whole argument. On the CERTIFY plan, Estimatics reads your confirmed findings and the context of the loss and writes a Cause & Origin assessment — a structured starting point for the part of the file that gets scrutinized hardest.

Where you actually see it

Cause & Origin is a report section, not a button you press. It composes into the report when you generate one:

Report type	Includes Cause & Origin
Damage	✓
Analysis	✓
Complete	✓
Custom	✓ if you pick it
Findings · Geometry · Estimate	—

It only composes for a CERTIFY seat. On FIELD and SCOPE, those same report types compose without the section — you get the report, minus this part. Nothing errors; the section simply isn't there.

→ Report types and sections · Building a custom report

What it's written from

Not from raw photos. Estimatics gathers the findings already recorded on the job — the AI proposals you confirmed, plus any you added by hand — together with the job's context: property, loss type, dates, areas, and the evidence attached to each finding.

That ordering matters. The assessment is downstream of your review, so what it reasons about is the record you stood behind, not an unreviewed first pass.

What it produces

Three to five sentences assessing the most likely cause and origin of the damage, stating uncertainty explicitly where the evidence is insufficient to reach a conclusion.

That last part is deliberate. An assessment that always sounds certain is worthless in an adversarial setting — the first cross-examination question is how it handles a thin file. This one is written to say when the evidence doesn't carry the conclusion.

What it does not do

It is not an expert opinion. It doesn't assign liability, and it isn't a substitute for a licensed cause-and-origin investigator where one is required.
It doesn't decide coverage. Estimatics doesn't interpret policy language or make coverage determinations.
It isn't evidence of itself. It's an analysis of your evidence. The photographs, measurements, and findings are the evidence.
It isn't automatic. It composes when you generate a report, not in the background as you capture.

Read it, correct it, and stand behind the version you send. Your professional judgment — and your license — govern the claim.

Getting a useful assessment

The quality of the output tracks the quality of the record it reads:

Confirm your findings before generating. Unreviewed proposals make for a weaker assessment.
Capture the context, not just the damage. Where water entered matters as much as where it ended up.
Fill the gaps the evidence check flags. An area with no photos is an area the assessment has to be silent about.
Read it against the file. If it reaches further than your evidence does, that's the sentence to rewrite.

Damage findings

How findings are proposed and confirmed — the input this reads.

Evidence coverage

Catch a thin file before it's the reason an assessment says "insufficient".

Report types

Which reports carry this section, and what else they contain.

AI disclosure

How Estimatics uses AI, and the limits we hold ourselves to.

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