Water damage scope report app for escape-of-liquid claims
An escape-of-liquid claim needs two answers before anyone talks about money: where the water came from, and how far it travelled. Restorers and assessors record the source, the water category, moisture readings on a grid across each affected room and the materials that cannot be dried. The insurer then reads a scope that separates drying and strip-out from the reinstatement that follows.
Built for restorers running teams of roughly 3–50 inspectors.
Sample Water damage scope
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Water damage scope
Room 2 — Kitchen (source room)
- Claim
- WD-24817 (fictional)
- Source
- Failed flexi hose under kitchen sink
- Attended
- 9 April 2026, 07:40
| Location | Moisture reading | Result |
|---|---|---|
| Kitchen base cabinet floor | 38% (WME), particleboard swollen | Result: Replace |
| Floor tiles, grid point K3 | 24% at subfloor, drying | Result: Dry |
| Hall skirting, 1.2 m from door | 11%, within dry standard | Result: Dry |
| Laundry wall (shared) | No elevated reading | Result: Unaffected |
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 water damage scope where your template puts it.
Source and event
- Source of water
- Date of event and date isolated
- Water category (1, 2 or 3)
- Ongoing leak or one-off failure
Per room
- Room name and floor finish
- Moisture readings by grid point
- Affected materials (keep / dry / remove)
- Photos of source and extent
Scope
- Emergency drying equipment and days
- Strip-out items
- Reinstatement line items
- Excluded wear, tear or gradual damage
Standards the report works to
- IICRC S500Standard for Professional Water Damage Restoration
- Water categories, drying goals and the language a restorer’s scope is checked against.
- AS 3740Waterproofing of domestic wet areas
- Cited when the leak is a failed shower or bathroom membrane rather than a sudden pipe failure.
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 water damage scope gets built
Capture it once, offline
Your firm builds the burst pipe water damage scope 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 water damage scope 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 water damage scope 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 record moisture readings on return visits against the same points?
- Yes. Each reading point is a row the next visit’s form can refer back to, so the drying log shows day one, day three and sign-off figures side by side.
- How do we separate a sudden escape from a slow leak?
- Put the causation questions on the form — corrosion, staining, rot, how long the occupant noticed it — and use conditional sections so a gradual-damage finding prompts the evidence the insurer needs.
- Can the drying scope and the building scope go out as one report?
- They can render as separate sections of one Word document, or as two documents from the same inspection if the insurer wants them split.
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
- Fire damage assessmentsFire damage 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
- Liability scene investigationsScene investigation report
- Machinery breakdown assessmentsBreakdown cause report
Other disciplines
Rebuild your water damage scope 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.