Smoke detector test register software
A large building can carry hundreds of detectors, and the deliverable is a register: every device, its zone and location, the date it was tested and whether it raised an alarm at the panel. The work is repetitive and the failure mode is a missed device, not a wrong judgement. SurveyThanks records each detector as a row inside its zone, so the report can state coverage zone by zone instead of leaving it to a spreadsheet tally.
Built for fire technicians running teams of roughly 3–50 inspectors.
Sample Detector test register
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Detector test register
Detector register — Zone 3, Level 2 office
- Site
- Fictional House, 25 Sample Avenue
- Panel
- FIP in ground-floor foyer
- Visit
- Annual detector test, 3 June 2026
| Device | Location | Result |
|---|---|---|
| Z3-D01 photoelectric | Corridor outside lift lobby | Result: Pass |
| Z3-D02 photoelectric | Meeting room 2.04 | Result: Pass |
| Z3-D03 thermal | Kitchenette | Result: No alarm at FIP |
| Z3-D04 photoelectric | Store room — ceiling obstructed by shelving | Result: Not accessed |
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 detector test register where your template puts it.
Per detector
- Device ID and type
- Zone and loop
- Location description
- Tested (yes / not accessed)
- Alarm received at panel
- Reason not accessed
Per zone
- Zone description
- Devices in zone (count)
- Devices tested (count)
Panel
- Panel faults on arrival
- Brigade isolation times
- Panel restored to normal
Standards the report works to
- AS 1670.1Fire detection, warning, control and intercom systems — System design, installation and commissioning — Fire
- Defines the installed system, including the detector spacing and clearances an obstruction can breach.
- AS 1851-2012Routine service of fire protection systems and equipment
- Sets the test routine and frequency for detection and alarm systems.
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 detector test register gets built
Capture it once, offline
Your firm builds the smoke detector testing 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 detector test register 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 detector test register 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 sprinkler coverage is throughout; the form records the warehouse only.
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
Questions
- How does a building with hundreds of detectors stay manageable?
- Detector rows sit as a repeatable group under each zone, so a large building is one submission with every device in its zone rather than a pile of separate test sheets.
- Can a technician scan the device label?
- Yes. A barcode field reads the device tag, which is faster and less error-prone than typing an ID while standing on a ladder.
- How does the report show devices we could not reach?
- Not accessed is its own answer with a required reason, and a calculated field counts tested against installed per zone, so the summary states coverage plainly.
- Does testing work in a basement with no signal?
- Yes. Results, photos and notes are captured offline and sync once the device is back online.
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 fire safety work we cover
- 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
- Fire safety statement auditsAFSS evidence pack
- Fire trail condition auditsTrail condition report
Other disciplines
Rebuild your detector test register 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.