Generating a Damage Report

The Damage report is the deliverable most jobs end at. It takes the findings you confirmed, the photographs behind them, and the property and claim record, and renders them as one document you can hand to a carrier, an adjuster, or a homeowner.

Available on every plan, including FIELD — though what composes into it depends on your seat.

What it contains

Six sections, in this order:

Cover — property, claim, and inspection details, with your organization's branding
Executive Summary — an AI-written overview of the inspection and its key findings
Findings — the table of damage findings, confirmed and inferred
Damage Findings — the AI narrative describing each finding in detail (SCOPE)
Evidence — the grid of photographs linked to those findings
Cause & Origin — the AI cause-and-origin analysis (CERTIFY, insurance-claim jobs only)

What changes with your seat

Your seat	What composes
FIELD	Cover · Executive Summary · Findings · Evidence
SCOPE	The above, plus the Damage Findings narrative
CERTIFY	All six, including Cause & Origin

Sections above your tier are dropped without an error. The report renders; it's just shorter.

Cause & Origin also requires an insurance-claim job. On a Work Order or a Quick Quote it doesn't compose even on CERTIFY — the analysis doesn't apply to that kind of work.

How to generate one

Open the job and go to the Reports tab
Choose Damage as the report type
Compose

Composition and rendering run in the background. A live checklist shows which sections are planned for your tier and this job while it works, then the version moves through Pending → Rendering → Rendered. If something goes wrong it lands on Failed with the reason.

When it's rendered, download the PDF.

Sections that drop for lack of data

Beyond tier, a section is skipped when the job can't support it. On a Damage report that means:

Findings is skipped if the job has no findings
Evidence is skipped if no photos are linked to findings

Which is the practical reason to run and review the analysis first. Compose before you've analyzed and you get a cover, a summary, and very little else.

Versions

Every compose creates a new version rather than overwriting the last. Confirm three more findings, compose again, and you have two versions — the one you sent last week and the current one. Edits create versions too.

Before you send it

Analysis run and reviewed. Findings still sitting as inferred say so in the table
Severity checked against what was actually seen on site
Photo scores checked — a high-severity finding resting on a low-scoring photograph is the weak point in the file
The claim block complete — carrier, policy, deductible, date of loss
The policy uploaded, if you have it. Coverage context is what makes the coverage notes worth reading
The PDF opened and read, front to back. It's your name on the cover

Report types and composition

All seven types, the nine sections, and the rules that gate them.

How findings work

What goes into the findings table before it reaches a report.

Building a custom report

When a preset isn't the shape you need.

Document Intelligence

Getting coverage detail onto the job before you compose.

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