Hail damage roof inspection app
A hail claim lives on the roof. The assessor has to tell fresh hail strikes from older wear, record what the roof is made of, count impacts on a test area of each roof face, and decide whether the cladding is functionally damaged or only marked. After a large storm, the same decision is being made on hundreds of roofs and the insurer wants it made the same way on every one.
Built for loss adjusters running teams of roughly 3–50 inspectors.
Sample Hail damage report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Hail damage report
Roof elevation summary (fictional)
- Claim
- HL-70883 (fictional)
- Roof
- Pre-painted corrugated steel, 22° pitch
- Inspected
- 11 November 2026
| Roof face | Impacts per test square | Finding |
|---|---|---|
| North | 14 dents, paint fractured at 3 | Finding: Replace |
| West | 9 dents, coating intact | Finding: Cosmetic |
| Box gutter, rear | Split seam, water entry to ceiling | Finding: Replace |
| Skylight dome | Cracked, consistent with hail | Finding: Replace |
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 hail damage report where your template puts it.
Roof
- Cladding type and profile
- Pitch and approximate age
- Access method (ladder, drone, internal)
Per roof face
- Impacts counted in test area
- Coating fractured (yes / no)
- Pre-existing corrosion or wear
- Photos with chalk-marked strikes
Other elements
- Gutters and downpipes
- Skylights and vents
- Solar panels
- Internal water entry
Standards the report works to
- AS 1562.1Design and installation of sheet roof and wall cladding — Metal
- Referenced when the scope specifies how replacement metal sheeting is fixed and lapped.
- AS 2050Design and installation of terracotta and concrete roof tiles
- Referenced for tiled roofs, where cracked tiles are replaced rather than whole faces.
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 hail damage report gets built
Capture it once, offline
Your firm builds the hail damage roof inspection 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 hail 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 hail 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 each roof face be its own row in the report?
- Yes. A roof face is a repeatable group with its own impact count, photos and finding, and the report lays them out as a table or a section per face.
- Can we keep the cosmetic-versus-functional call consistent between assessors?
- Build the decision into the form: required questions about coating fracture and water entry, with each answer carrying fixed report wording, so assessors make the same call in the same words.
- Can drone photos be used?
- Photos from any source can be attached to the job and placed into the report alongside the ones taken on the device.
- How do we handle a catastrophe surge of hail claims?
- Every assessor uses the same form and template, and the report draft exists as soon as the inspection is submitted, so reviewers spend their time checking rather than writing.
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
- Workers comp workplace visitsWorkplace visit report
- 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
- Flood inundation assessmentsInundation level report
- Heavy motor assessmentsTruck assessment report
Other disciplines
Rebuild your hail 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.