Hail damage roof inspection software
Capture hail damage roof inspections on an iPad that keeps working with no signal, then produce the hail damage report from your own Word template — with the prose drafted against your own standards library.
Built for loss adjusters running teams of roughly 3–50 inspectors.
The loop you are running today
Assessors and adjusters are measured on cycle time, and the bottleneck is never the site visit — it is the evening spent turning photos and notes into a report the insurer will accept without a query. The scope, the causation narrative and the policy response all have to agree with each other, every time.
The tell is simple: you are running a forms app plus Word plus a spreadsheet plus email, and re-typing the same findings into all four to get one hail damage report out the door.
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.
Drafted against your standards, not a generic model
You upload your own reference library — PDF, Word, Excel, CSV — and it is indexed for retrieval. A {{ai: …}} marker placed inside your Word template runs Claude at render time and drops the drafted prose into that exact spot, and {{ai:@space …}} narrows that one paragraph to one named tier of your library.
Where two sources conflict, the retrieved passages are labelled with their authority and the model is instructed to follow the higher one and state what it overrode. A document you mark superseded is excluded outright.
What a insurance firm typically loads
- Insurer scopes of work and reporting templates
- Policy wordings and general conditions for the schemes you service
- IICRC S500 and S520 for water and mould claims
- Your own causation and scoping methodology
- Panel service level agreements and reporting deadlines
The hail damage report gets 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 on its own every time that template renders.
Each finding comes back with a severity — info, minor or major — the sentence at fault, and the evidence that contradicts it. A person accepts or dismisses every one, and that decision is kept against the report rather than lost in a reply-all.
The framework can also be grounded in a named tier of your standards library, so a finding can be raised against your methodology rather than against a general sense of what a good report looks like.
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
The check a document-AI tool cannot run
Every tool in this space reads the finished document. We also hold the structured submission the document was generated from, so 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.
That is a contradiction between the report and the field data — invisible to anything reading the hail damage report on its own, and the class of error that comes back from a client.
The same screen reviews documents produced anywhere else — a subcontractor’s report, a draft from your old system — uploaded as PDF, Word, HTML or text. On that path there is no submission to compare against, so it is your checklist and your standards only.
Enter your buildings and rooms once
Every field app can do repeating sections. Almost none can do links between repeating rows — many-to-many, with stable row identity, on a device with no signal.
A single scope line can cover three rooms and a single room can carry damage from two perils, so the report can say "Main Warehouse — cause, extent, scope, reserve" as a coherent chapter instead of the same paragraph pasted four times.
It is also what makes the work answerable afterwards. Once the relationships are stored rather than described in prose, a question across every job you have ever done is a query against a spreadsheet-style grid, not a re-read of forty hail damage reports.
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.
- iOS only. There is no Android app.
- 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.