Fire damage assessment and scope software
A fire claim is a building where the damage is graded by distance from the seat of the fire: charred structure near the origin, heat damage further out, and smoke and soot through rooms that never saw a flame. The loss adjuster has to record the origin as reported by fire services, grade each area, flag anything hazardous in the debris and scope demolition, cleaning and rebuild in a way the insurer can reserve against.
Built for loss adjusters running teams of roughly 3–50 inspectors.
Sample Fire damage report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Fire damage report
Area summary — single-storey dwelling (fictional)
- Claim
- FD-30941 (fictional)
- Origin (per fire service)
- Garage, near workbench
- Inspected
- 18 June 2026
| Area | Damage grade | Recommendation |
|---|---|---|
| Garage | Structural — roof framing charred | Recommendation: Demolish |
| Laundry (adjoining) | Heat — linings blistered, ceiling sagging | Recommendation: Strip out |
| Kitchen and living | Smoke — soot to ceilings and joinery | Recommendation: Clean |
| Bedrooms 1–3 | Light odour only | Recommendation: Deodorise |
Fields captured on site
Your firm builds the form in-app, so these are a starting point rather than a fixed schema. Every field is captured on the device, with or without signal, and lands in the fire damage report where your template puts it.
Event
- Fire service incident number
- Reported origin and cause
- Date and time of fire
- Occupancy at the time
Per area
- Damage grade (structural, heat, smoke, odour)
- Elements affected
- Hazards noted (suspected asbestos, unsafe structure)
- Photos
Scope
- Make-safe and security
- Demolition and debris removal
- Cleaning and deodorising
- Rebuild line items
Standards the report works to
- Code of PracticeSafe Work Australia — How to manage and control asbestos in the workplace
- Applies when fire-damaged material in an older building may contain asbestos and has to be assessed before demolition.
Load the standards you hold into your reference library and the drafted prose is written against them rather than against a general model.
How the fire damage report gets built
Capture it once, offline
Your firm builds the fire damage assessment form in-app — 25 field types, nesting repeatable groups, compound AND/OR visibility rules, reusable modules and calculated fields. Field capture works with no signal: jobs, forms, photos, notes and audio all queue in an idempotent outbox that only clears once the server confirms receipt.
Link it to your buildings and rooms
Enter buildings and rooms once, as a register. Every one of your damage observations and scope lines then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The fire damage report renders into the Word template you already use — your letterhead, your section order, your clause library — with conditionals, loops over repeats, composable sub-templates and photo grids.
Reviewed before it leaves
You write the review framework: a checklist of what a fire damage report must contain, plus the prose standards you would mark a junior against. Link it to a report template and it runs every time that template renders. Each finding comes back graded info, minor or major, quoting the sentence at fault, and a person accepts or dismisses every one.
Because the structured submission behind the report is held too, the review is a comparison rather than a proofread: The report says the escape of water was confined to the ground floor; the scope carries three first-floor rooms.
Checks a insurance framework usually carries
- Cause, extent and policy response agree with one another
- Every scope line traces back to a damage that was actually observed
- The reserve is supported by the scope rather than asserted
- Every section the insurer’s template requires is present and populated
Questions
- Can we grade every room without writing the same paragraph each time?
- Grades are options on the form with their own report wording, so selecting “smoke” for a room drops the agreed sentence into the report and the narrative only covers what is unusual.
- Where does the cause of the fire go if we did not determine it?
- Record the reported origin and its source — fire service, police or a forensic investigator — as separate fields, so the report attributes the cause rather than asserting it.
- Can we flag possible asbestos without holding up the scope?
- A hazard flag on an area can make a testing recommendation appear in the report while the rest of the scope is issued.
What this is not
Worth knowing before you book a demo, so neither of us wastes the half hour.
- Not field-service dispatch. No timesheets, no parts, no inventory. Scheduling exists to get an inspector to a site.
- No signature capture. If your deliverable has to carry a signed sign-off on the artefact itself, this is not the tool yet.
- Field capture is what works offline — jobs, forms, photos, notes and audio. Reports, chat, scheduling and the inbox need a connection.
- No client portal. Reports go out as a file or a password-protected link.
Other insurance work we cover
- Business interruption verificationsBI verification report
- Contents claim inventoriesContents schedule report
- Fine art condition reportsArtwork condition report
- Flood inundation assessmentsInundation level report
- Hail damage roof inspectionsHail damage report
- Heavy motor assessmentsTruck assessment report
- Home claim assessmentsClaim assessment report
- Impact damage assessmentsImpact damage report
Other disciplines
Rebuild your fire damage report in SurveyThanks
Bring the Word template you already send clients. If you are coming off another field-forms tool, a filled report can be uploaded, read field by field, and re-rendered into your template.