Flood inundation assessment software
After a flood event, assessors work a street at a time and the single most useful number is how high the water reached inside each building. That level, measured from the floor and backed by water lines in photos, decides which linings, joinery and appliances are lost. Recorded consistently across hundreds of claims, it also lets an insurer see the event as a whole rather than as separate files.
Built for hydrologists running teams of roughly 3–50 inspectors.
Sample Inundation level report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Inundation level report
Inundation record — ground floor (fictional)
- Claim
- FL-11206 (fictional)
- Event
- Riverine flood, March 2026 (fictional)
- Inspected
- 27 March 2026
| Location | Water line above floor | Result |
|---|---|---|
| Living room | 640 mm, tide mark on plasterboard | Result: Strip linings |
| Kitchen | 610 mm, base cabinets submerged | Result: Replace |
| Garage slab | 820 mm, silt deposit | Result: Clean |
| Electrical switchboard | Above water line, not affected | Result: Check by electrician |
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 inundation level report where your template puts it.
Property
- Floor level relative to ground
- Construction type (slab, raised timber)
- Number of levels affected
Per room
- Water line height above floor
- Duration of inundation (if known)
- Silt or contamination present
- Photos of water line with scale
Cause
- Source (riverine, overland flow, storm surge, stormwater)
- Neighbouring properties affected
- Policy flood cover noted
Standards the report works to
- General Insurance Code of Practice 2020Insurance Council of Australia — General Insurance Code of Practice
- Includes commitments for handling claims after a declared catastrophe, which shape how quickly assessments are expected.
- IICRC S500Standard for Professional Water Damage Restoration
- Floodwater is category 3 under this standard, which drives what is removed rather than dried.
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 inundation level report gets built
Capture it once, offline
Your firm builds the flood inundation 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 inundation level 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 inundation level 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 load a whole street of flood jobs before we lose coverage?
- Yes. The “load today’s jobs” download puts the day’s jobs, forms and map tiles on the iPad so the inspections can be done offline and sync later.
- Can we report water heights across every claim from one event?
- Water line heights are stored as numbers on each submission, so they can be filtered and exported across every job for the event from the submissions grid.
- Does the report have to distinguish flood from storm water?
- Put the source of water on the form as a required question; the report then states it explicitly and conditional sections can follow the answer.
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
- Burst pipe water damage scopesWater damage scope
- Business interruption verificationsBI verification report
- Contents claim inventoriesContents schedule report
- Fine art condition reportsArtwork condition report
- Fire damage assessmentsFire damage report
- Hail damage roof inspectionsHail damage report
- Heavy motor assessmentsTruck assessment report
- Home claim assessmentsClaim assessment report
Other disciplines
Rebuild your inundation level 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.