Project Management, Documentation, and Records
Documentation is a deliverable
NFPA 72 Chapter 7 treats documentation as part of the system. Before installation, submit shop drawings, a sequence of operations matrix, battery and voltage-drop calculations, device and appliance layouts, and manufacturer's data for approval; work installed before approval risks removal. At closeout, deliver as-built drawings, the Record of Completion, site-specific software and backup, operating instructions, and training for the owner's personnel. The owner keeps a copy on the premises, and the AHJ keeps or reviews a copy as required.
Running the job
A fire alarm project is a coordination exercise. Early scope review identifies the code basis, the adopted edition, and any local amendments. Submittals, requests for information, and change orders must be tracked in writing because the sequence of operations and device counts drive both cost and the acceptance test. Coordinate ceiling and wall conditions with electrical, mechanical (duct detectors, smoke dampers), and architectural trades before rough-in; retrofits after ceilings close are the classic schedule and margin killer.
Acceptance and closeout
Plan the acceptance test from the sequence of operations, walk the system first as a pretest, correct deficiencies, then run the witnessed test with the AHJ and owner's representative. Publish a punch list, close items, and document them. Training and O&M turnover are contractual and code items, not favors.
Traps
Treating the Record of Completion as a contractor's internal form rather than a required deliverable; confusing as-builts with design drawings; failing to obtain AHJ approval before installation; and omitting the sequence of operations, which makes both testing and future service ambiguous.
Rule of thumb
If the panel cannot be tested from a written sequence of operations, the documentation is incomplete, no matter how good the drawings look.