9.5 Documentation, As-Builts, Closeout, and Records

NFPA 72 Chapter 7 Is the Documentation Backbone

Documentation is a major supervision skill because it proves what was planned, installed, tested, corrected, and turned over. NFPA 72 Chapter 7, Documentation, is the controlling reference. Two parts dominate exam scenarios:

• 7.4 Shop Drawings (installation documentation): the working drawings prepared and approved before installation — floor plans showing device locations, the riser diagram, the sequence of operations (input/output matrix), battery and voltage-drop calculations, and equipment data. These are produced by personnel meeting NICET Level III standards and approved by the design professional in responsible charge.
• 7.5 Completion Documents: what is delivered on system acceptance — as-built (record) drawings, the owner's manual, the record of completion, and, for software-based systems, a record copy of the site-specific software. NFPA 72 requires a copy of the site-specific software so the system can be restored after a failure; the record of completion is signed at acceptance and carries a revision date whenever it is updated.

The records form a chain: approved submittals define intent, field-change notes explain deviations, test/commissioning records show verification, deficiency records show resolution, and the closeout package organizes everything for the owner and the next technician.

As-Builts vs Shop Drawings, and a Controlled Closeout

The most-tested distinction is shop drawings versus as-builts. Shop drawings are the intended, approved plan (7.4). As-builts (record drawings) must capture what is actually installed (7.5) after field routing changes, added or relocated devices, changed addresses, or revised interfaces. An answer that calls as-builts "another name for shop drawings" is wrong.

NICET FAS scenario guidance: a contractor asks for closeout even though device addresses changed during commissioning and the test record lists one area as inaccessible. The correct response is to update the as-built information, resolve or clearly document the inaccessible scope, and align the closeout package with verified installed conditions. Releasing a package that hides known gaps creates future service and acceptance problems and misrepresents unverified work as complete.

Closeout is a controlled transfer

Closeout is not merely an owner's manual. The completion package can include the record of completion, as-built drawings, test/acceptance records, equipment and product data, the site-specific software copy, warranty information, and deficiency-resolution evidence. The exam rewards the idea that closeout is a controlled transfer of technical information to the owner and future service provider.

Document-control habit for exam scenarios:

1. Start from the approved documents.
2. Record field changes as soon as they are known.
3. Link each deficiency to correction and retest evidence.
4. Update as-builts to match the installed condition.
5. Review closeout for gaps before turnover.
6. Keep records clear enough for a technician who never worked the original project.

This is also work-history material. Instead of "managed paperwork," a strong narrative says you compiled as-builts, reviewed test reports, maintained the record of completion, archived the site-specific software, resolved deficiency records, and coordinated closeout with the owner — the specific, verifiable responsibilities that NICET Level III and IV applications depend on rather than a job title alone.

What Goes Into a Defensible Record of Completion

The record of completion is the single most exam-relevant document because it is the signed statement, at acceptance, of what was installed and verified. NFPA 72 structures it so the responsible parties — installing contractor, owner's representative, and where applicable the AHJ — attest to the system.

A complete record of completion identifies the property and protected premises, the system type and the approving authority and adopted code edition, the system documentation on hand (drawings, sequence of operations, calculations, manuals), an itemized device and circuit count by type, the secondary-power (battery) data, the notification and pathway design basis, and the interfaces (HVAC, elevator, suppression, monitoring/supervising station).

Whenever the system is modified, the record is reissued with a revision date so the history stays traceable.

Records survive the project team

The deeper reason documentation is a supervision skill is continuity. The technician who services this system in five years was not on the install. If the as-builts show actual routing and addresses, the record of completion lists the real device counts and battery data, and the deficiency log shows what was found and closed, that future technician can troubleshoot, expand, and recertify the system efficiently. If the package restates the original shop drawings and hides the inaccessible area, every future service call rediscovers the same gaps.

NICET FAS scenario answers consistently reward the leader who keeps the record accurate, current, and usable by a stranger — because that is what protects the owner, the next technician, and the AHJ long after turnover. Releasing an inflated or incomplete closeout package to hit a turnover date is exactly the trap the exam sets, and the controlled-transfer answer is the right one.