Fire door inspection app with a door-by-door register
A fire door only works if every part of it does: the leaf and frame are undamaged, the gaps are within tolerance, the closer brings it shut and latched from any angle, the seals are intact and nobody has wedged it open or drilled a hole for a new lock. Fire contractors inspect each door on a building’s register and the building owner gets a register back, door by door, with the defects that need fixing.
Built for fire contractors running teams of roughly 3–50 inspectors.
Sample Fire door register
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Fire door register
Fire door register — Stair 2
- Building
- Fictional Apartments, 45 Sample Avenue
- Doors inspected
- 28 of 28
- Inspected
- 5 November 2026
| Door | Finding | Result |
|---|---|---|
| FD-S2-03 (L3 landing) | Closes and latches; tag legible | Result: Pass |
| FD-S2-05 (L5 landing) | Does not latch from 30°; closer needs adjustment | Result: Defect |
| FD-S2-07 (L7 landing) | Leaf-to-frame gap 6 mm at head | Result: Defect |
| FD-S2-08 (L8 landing) | Unapproved hole for access reader cable | Result: Defect |
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 fire door register where your template puts it.
Per door
- Door ID (barcode scan)
- Location
- Door type and FRL
- Compliance tag present and legible
- Closes and latches
- Gaps within tolerance
- Seals intact
- Hardware and penetrations
- Photos
Defects
- Door
- Defect
- Fixed on the day
- Recommended repair
Standards the report works to
- AS 1851-2012Routine service of fire protection systems and equipment
- Includes the routine inspection of fire and smoke doors the register reports.
- AS 1905.1Components for the protection of openings in fire-resistant walls — Fire-resistant doorsets
- The standard a doorset’s construction, tag and permitted modifications are judged against.
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 fire door register gets built
Capture it once, offline
Your firm builds the fire door 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, levels and tenancies
Enter buildings, levels and tenancies once, as a register. Every one of your elements, defects and cost 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 fire door 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 fire door 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 narrative calls the roof "fair"; the element register grades it C with a twelve-month cost line against it.
Checks a commercial property framework usually carries
- Every graded defect carries a cost band and a priority
- The make-good schedule and the narrative describe the same condition
- Access and DDA non-compliances cite the clause they fail
- Every photo referenced in the text exists and is captioned
Questions
- Can we scan the door’s tag or barcode to find it on the register?
- Yes. The form has a barcode field, so a door ID label can be scanned rather than picked from a list of hundreds.
- Can the register carry forward from one inspection to the next?
- Doors are stored once per building, and each inspection records its own result against them, so the register is the same door list every time with a new column of results.
- Can the report show only failed doors to the client?
- Your template can loop over every door, or filter to failures for a defects summary, and both can sit in the same report.
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 commercial property work we cover
- Replacement cost assessmentsInsurance valuation report
- Roof condition surveysRoof survey report
- Signage condition auditsSignage register
- Sinking fund forecast inspectionsMaintenance forecast report
- Water efficiency auditsWater audit report
- Accessibility DDA auditsAccess audit report
- Annual facade inspectionsFacade condition report
- Bank branch auditsBranch standards report
Other disciplines
Rebuild your fire door 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.