Sprinkler system inspection software
Capture sprinkler system inspections on an iPad that keeps working with no signal, then produce the sprinkler test report from your own Word template — with the prose drafted against your own standards library.
Built for fire contractors running teams of roughly 3–50 inspectors.
The loop you are running today
The assessment and audit side of fire safety is report work — a BAL assessment, a penetration survey, an evidence pack behind an annual statement. It is separated here from routine servicing on purpose: servicing produces signed records, and SurveyThanks has no signature field.
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 sprinkler test report out the door.
How the sprinkler test report gets built
Capture it once, offline
Your firm builds the sprinkler system 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, fire compartments and rated elements
Enter buildings, fire compartments and rated elements once, as a register. Every one of your penetrations, defects and rectification items then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The sprinkler test 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 fire safety firm typically loads
- AS 3959 for bushfire attack level assessment
- AS 1851 where you are auditing rather than signing service records
- NCC fire safety provisions and the relevant AS 1670 and AS 2419 parts
- State fire safety statement and certification requirements
- Your own assessment methodology and evidence standards
The sprinkler test report gets reviewed before it leaves
You write the review framework: a checklist of what a sprinkler test 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 fire safety framework usually carries
- Every rated element assessed carries a defect status, not just a description
- A BAL determination shows the inputs it was derived from
- Non-conformances cite the clause of the standard they fail
- Rectification items are specific enough for a contractor to price
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 sprinkler coverage is throughout; the form records the warehouse only.
That is a contradiction between the report and the field data — invisible to anything reading the sprinkler test 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, fire compartments and rated elements 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.
Every penetration points at the rated wall it breaches, so the register and the report body are the same data — and a compartment renamed during the survey stays consistent across both.
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 sprinkler test 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 fire safety work we cover
- Smoke detector testingDetector test register
- Asset protection zone inspectionsAPZ compliance report
- Bushfire attack level assessmentsBAL report
- Bushfire hazard reduction auditsHazard reduction report
- Evacuation diagram auditsDiagram compliance report
- Evacuation drill recordsDrill observation report
- Fire damper testingDamper test report
- Fire hydrant testingHydrant flow test report
Other disciplines
Rebuild your sprinkler test 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.