Practical guide
NFPA 72: preparing inspection and testing
Inventory, criticality, work windows and evidence for planning fire detection and alarm maintenance.
A fire detection and alarm maintenance programme starts with understanding what each device protects and how the system is expected to respond. BBS recommends connecting every activity to the inventory, approved sequence and closing evidence. This helps distinguish assessed equipment from points that still require evaluation.
Inspection, testing and maintenance serve different purposes
Inspection observes equipment and installation conditions; testing verifies a function through an authorised procedure; maintenance preserves or restores operation. Cleaning equipment or seeing a fault-free screen alone does not demonstrate the performance of notification, event transmission or building interfaces.
NFPA 72 is a reference for alarm and signalling systems. Activities, methods and frequencies depend on the applicable edition, device type, manufacturer instructions and approved scope. A single maintenance frequency cannot be assigned to every item in an installation.
Information to gather before requesting a quotation
- Control panels, annunciators, power supplies, batteries and devices, with the location and identifier of each point.
- Models, software releases, firmware, licences, manuals and configuration backups, including their date and validation status.
- Alarm history, recurring trouble conditions, previous work and changes to room layouts.
- As-built drawings, the cause-and-effect matrix and interfaces with access control, ventilation, lifts and water-based systems.
Turn the inventory into a useful record
| Record | Document | Closure |
|---|---|---|
| Point or circuit | Identifier, location, method and applicable reference. | Result, date and traceable evidence. |
| Interface | Source event, destination and authorised response. | Validation by both system owners. |
| Finding | Impact, priority and outstanding condition. | Agreed owner and deadline; verify before closing. |
Plan the work window
The technical lead must agree notifications, permissions, contingencies and return-to-service criteria before intervention. Tests affecting life safety or building services require coordination with operations and field validation. Inaccessible devices, excluded interfaces and untested functions must be identified in the report.
For acceptance, request records by device and function, prioritised findings, completed changes, available backups and outstanding actions. An overall progress percentage does not replace the list of items actually assessed.
How BBS organises the work
- Initial assessmentInventory, fault history and criticality.
- Intervention planScope, permissions, owners, contingency and acceptance.
- Execution and testingChange control and verification of authorised interfaces.
- Handover and follow-upEvidence, validated results and outstanding actions.
Sources and scope
Public reference sources checked on 5 October 2026. This BBS guide provides planning recommendations; applicable editions and requirements must be validated for each project.
LET’S TALK