Keep the record practical, traceable, and within scope
Fire-alarm documentation should identify what is installed, where devices and circuits are located, how the system was configured, what was tested, what deficiencies were found, and how corrections were verified. The record must be clear enough for authorized service personnel and the customer to follow later.
This guide is an organizational aid only. It does not replace NFPA standards, adopted codes, the authority having jurisdiction, approved drawings, manufacturer instructions, licensing requirements, or the project’s required test and inspection forms.
Project, site, and fire-alarm scope
A clear project summary helps later readers distinguish installation, renovation, service, inspection, and deficiency-correction work. Record the approved scope and the parties responsible for design, programming, monitoring, interfaces, and acceptance.
- Customer, site, address, building, floor, project number, permit, and work phase
- Owner, facility, fire-alarm contractor, monitoring provider, electrician, designer, and AHJ contacts
- New, modified, replaced, relocated, removed, existing, and out-of-scope equipment
- Approved drawings, sequence, calculations, submittals, change orders, and revision references
- Interfaces with suppression, elevator, smoke control, access control, HVAC, and other systems
- Inspection, testing, impairment, monitoring, acceptance, training, and closeout milestones
Control panel, annunciator, and system information
Panel records identify the system’s central equipment, installed software, power, batteries, network relationships, and the locations from which the system is operated or displayed.
- Panel ID, manufacturer, model, serial number, firmware, software, and physical location
- Annunciator, remote display, network node, transponder, and graphic interface information
- Cabinet, circuit, disconnect, grounding, surge protection, tamper, and environmental notes
- Power-supply and booster-panel IDs, models, ratings, addresses, loads, and locations
- Battery quantity, type, rating, manufacture date, calculation reference, and test result
- Configuration backup, programming file, password-custody process, and responsible service organization
Initiating devices, notification appliances, modules, and interfaces
The device inventory should connect a field label and physical location to the panel address, circuit, programmed description, device type, and test record.
- Device ID, address, type, manufacturer, model, serial number where applicable, and location
- Smoke, heat, duct, beam, manual station, sprinkler, flow, tamper, pressure, and supervisory devices
- Horn, strobe, speaker, chime, bell, textual appliance, and visible or audible circuit information
- Monitor, control, relay, isolator, interface, releasing, and specialty module details
- Elevator, suppression, HVAC, smoke-control, access-control, and monitoring interface purpose
- Programmed label, input type, output function, sequence reference, and approved exception
Use a panel description such as “B2-L3-EAST MECH RM DUCT SD-3” rather than “DUCT 3” so the event can be located quickly during service.
SLC, NAC, circuits, addressing, and power
Circuit documentation should show how devices are grouped, routed, powered, and supervised. Keep circuit IDs consistent across panel schedules, labels, drawings, test records, and as-builts.
- SLC, NAC, IDC, speaker, network, data, auxiliary-power, and interface circuit identifiers
- Origin panel or booster, terminal, circuit class or style where documented by the project, and destination
- Device address, module point, circuit sequence, isolator boundaries, and branch information
- Cable type, conductor count, gauge, rating, shield, pathway, junction, and end-of-line location
- Power-supply loading, synchronized appliance details, voltage measurements, and battery support records
- Open, ground, short, supervision, spare, abandoned, rerouted, and corrected circuit status
Communicator and central-station information
Where monitoring is part of the project, document the communicator, transmission method, account references, event routing, and test confirmation without placing passwords or sensitive account secrets in an unrestricted closeout package.
- Communicator manufacturer, model, serial number, firmware, location, and panel connection
- IP, cellular, radio, telephone, or dual-path method and responsible service provider
- Central-station name, public contact information, account reference, and protected-premises identification
- Alarm, supervisory, trouble, test, restore, and communication-failure event routing
- Primary and backup path status, signal or connectivity notes, and transmission test date
- Responsible party for account changes, call lists, permits, and secure credential custody
Programming and change records
A programming history explains what changed and why. Preserve the pre-change backup when appropriate, identify the approved request, and connect the revised database to the testing performed after the change.
- Change date, technician, service request, approved drawing, change order, or deficiency reference
- Added, removed, relocated, relabeled, readdressed, disabled, or re-enabled points
- Changed input types, output functions, groups, zones, logic, delays, and message text
- Sequence or interface changes and the affected systems or responsible trades
- Database or configuration filename, version, storage location, and backup confirmation
- Post-change test scope, witness, result, exception, and final accepted revision
Record “Relabeled module 071 and revised AHU-3 shutdown mapping per approved RFI-18; function tested with mechanical contractor” rather than “program updated.”
Testing, inspection, and functional records
Testing records should identify the procedure or required form used, the device or function tested, the expected result, the actual result, the witness, and any retest. Use the forms and methods required for the specific project.
- Control unit, annunciator, power supply, battery, communicator, and system trouble functions
- Initiating-device activation, address, programmed description, annunciation, and restore
- Notification-appliance operation, synchronization, audibility or visibility records where required
- Alarm, supervisory, trouble, ground, open, short, loss-of-power, and communication conditions
- Elevator, HVAC, access, suppression, smoke-control, and other interfaced-system sequences
- Date, technician, witness, instrument, expected result, actual result, deficiency, and retest
The checklist can confirm that a required test record is present and traceable. It does not determine the test method, frequency, acceptance limit, or authority approval.
Deficiencies, corrective actions, and service records
A deficiency record should preserve the original condition, operational impact, interim action, responsible party, correction, and verification. Do not erase the history when an item is repaired.
- Unique deficiency ID, discovery date, device or circuit, exact location, and observed condition
- Operational impact, impairment status, notification record, and temporary measure where applicable
- Responsible party, required correction, priority, target date, and material or access dependency
- Service action, parts used, programming change, completion date, and technician
- Retest procedure reference, result, witness, restored status, and supporting photo
- Open, deferred, customer-responsibility, third-party, corrected, and verified status
Photos, as-builts, sign-off, and final closeout
Final records should match the installed device locations, addresses, circuit routes, panel schedules, sequence, programming revision, and accepted test documentation. Keep protected or sensitive information separate where appropriate.
- Panel, annunciator, communicator, booster, battery, circuit-label, device, interface, and completion photos
- Final floor plans, riser, device schedule, address list, circuit schedule, sequence, and interface diagrams
- Approved field changes, programming backup, test and inspection forms, and deficiency-resolution evidence
- Manuals, warranty information, spare devices, keys, training, and monitoring information delivered
- Technician, project-manager, customer, monitoring, interfaced-trade, and AHJ sign-off as required
- Open exceptions, final revision date, delivery method, customer receipt, and retained service copy
A consistent field record
Standardize documentation without slowing the work.
Standardized fire-alarm documentation helps keep device, circuit, programming, test, deficiency, and as-built records connected. It can improve handoff and future service while remaining subordinate to the project’s required procedures and authorities.
View the Fire Alarm Documentation Pack