Cause & Origin
The AI Cause & Origin section Estimatics writes into reports on insurance-claim jobs: which reports carry it, what it reads, how to change it, and what it does not claim. CERTIFY.
4 min read
In a disputed claim, cause is often the whole argument. On CERTIFY, Estimatics reads the job's findings and the context of the loss and writes a Cause & Origin section into your reports: a structured starting point for the part of the file that gets the closest look.
Where you see it
Cause & Origin is a report section, not a button you press. It's written when a report is composed:
| Report type | Includes Cause & Origin |
|---|---|
| "Damage Report" | ✓ |
| "Analysis" | ✓ |
| "Complete Report" | ✓ |
| "Custom Report" | ✓ if you pick it |
| "Findings" · "Geometry Report" · "Estimate" | — |
It also appears in the report Estimatics composes automatically when you mark a job Completed: on SCOPE and CERTIFY that report is a "Complete Report", and the section is in it on CERTIFY insurance-claim jobs. That report is finalized when it is composed, so to change it, compose a new one.
Two conditions decide whether the section is written:
- The account is on CERTIFY. The free trial counts as CERTIFY. On FIELD and SCOPE, those same reports compose without it. Nothing errors; the section simply isn't there. In a "Custom Report", it's listed but disabled, marked "Requires CERTIFY".
- The job is an insurance claim. It's written only on insurance-claim jobs (the "Insurance Claim" workflow types). Other workflow types, such as "Work Order", skip it.
→ Report types and sections · Building a custom report
What it's written from
Not from raw photos. Estimatics gives the AI the job as it stands when you compose the report:
- The findings recorded on the job, grouped by area, each marked as confirmed or still proposed
- Job details: address, date of loss, job type, damage type and cause of damage
- Inspector notes, notes on photos and walkthrough sessions
- Summaries of uploaded documents, the estimate and the inspection narrative, if they exist
- Building-code context for the job's ZIP code and damage type, and industry standards (IICRC)
Findings you deleted aren't included. Findings still waiting for review are, marked as unconfirmed, which is why it pays to review and approve your areas first.
→ Areas and approval · Building-code context
What it produces
Three to five sentences assessing the most likely cause and origin of the damage, stating uncertainty where the evidence is insufficient to reach a conclusion.
That last part is deliberate. An assessment that always sounds certain doesn't hold up when someone questions it. This one is written to say when the evidence doesn't support the conclusion.
Changing it
You can't type into the PDF. To change the wording, open the report in Reports and ask Esti in the report viewer, for example "Shorten the Cause & Origin section" or "Say that the source of the leak was not confirmed." Each change creates a new version of the report.
Once you "Finalize" a report, it can't be edited any more. To change it after that, compose a new one.
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 photos, measurements and findings are the evidence.
- It isn't automatic in the background. It's written when a report is composed, not while you capture.
Read it, have Esti correct what's off, and stand behind the version you send. Your professional judgment governs the claim.
Getting a useful assessment
The output is only as good as the record it reads:
- Review your findings and approve your areas before you compose the report.
- Capture the context, not just the damage. Where the water came in 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 stay silent about.
- Read it against the file. If it goes further than your evidence does, that's the sentence to change.
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: October 2026 · Questions? Email support@aiestimatics.com
Last updated: October 2026 · Feedback on this article