5.2 Record of Completion & As-Builts

5.2 Record of Completion & As-Builts

Quick Answer: When commissioning finishes, NFPA 72 expects a usable documentation package for the owner and AHJ: Record of Completion (or equivalent completion documentation), record drawings that match the field, sequence of operation, supporting calculations, product data, manuals, and final software identification. Level II technicians gather accurate as-built markups and test data; they do not casually “sign for” design liability they do not hold.

A system that works on test day but leaves no trustworthy records is a future failure: wrong battery replacements, lost matrix logic, and ITM techs guessing at device locations. Domain 2.1.4 and later maintenance documentation topics all depend on what you capture at completion.

Why Documentation Is Part of Commissioning

Acceptance testing proves performance today. Documentation preserves:

• What was installed and where
• How the system is supposed to behave
• How it was tested and by whom
• What power and pathway design assumptions apply
• Which software revision is authoritative

NFPA 72 documentation requirements support inspection, testing, maintenance, modification, and AHJ review over the life of the system. Treat paperwork as a life-safety deliverable equal to a correctly wired NAC.

Core Package Contents

Exact forms vary by edition language, AHJ preference, and contract specifications, but Level II candidates should recognize this standard package:

Record of Completion

The Record of Completion is the flagship completion document referenced throughout fire alarm practice. Conceptually it captures:

• Premises and system identification
• System type/features (automatic detection, manual fire alarm, emergency voice, sprinkler monitoring, elevator recall, etc.) as applicable
• Organizations responsible for installation, and related roles as the form requires
• Confirmation that installation and testing were performed in accordance with the referenced standard and approved design
• Notes on deviations, incomplete items, or owner-accepted exceptions when the form provides for them

Do not treat the Record of Completion as a substitute for failing tests. If functions are incomplete, document the status honestly and complete retests—do not check boxes for interfaces that were never demonstrated.

Record drawings (as-builts)

Record drawings are the field-truth set. They start from approved shop drawings and incorporate:

• Relocated devices (with dimensions or clear room references)
• Added or deleted devices
• Actual conduit/cable routes when they differ materially from design (especially survivability-critical paths)
• Final circuit/address assignments
• Power supply and booster locations as installed
• Interface connection points (elevator controllers, AHU shutdowns, valve tamper switches)

Scenario: Lobby smoke detectors moved 8 feet to clear a decorative cloud ceiling. Shop drawings still show the old grid. Years later, an ITM tech cannot find devices and sensitivity testing is incomplete. That is an as-built failure born at commissioning.

Sequence of operation

Provide the final sequence of operation that matches programming:

• Alarm inputs → notification, off-premises signal, door release, HVAC, elevator, suppression logic as designed
• Supervisory inputs (tamper, duct supervisory if so designed, etc.) → supervisory signal paths without false “general alarm” if not required
• Trouble conditions → trouble annunciation and transmission rules

If programming changed during testing (common), update the matrix the same week—not six months later during a failed annual test.

Battery and voltage-drop calculations

Include calculations that support the accepted system:

• Standby load, alarm load, required times, and aging factor (commonly 20% additional)
• Battery type/quantity installed
• NAC/speaker circuit voltage drop with as-built lengths and currents

Store them with the owner package so future device adds trigger recalculation instead of tribal memory.

Cut sheets and manuals

Cut sheets should match installed models and listings. Owner manuals should cover:

• Normal operation indicators
• Alarm silence, reset, and drill procedures authorized for the owner
• Bypass/disable functions and their life-safety implications
• Battery replacement and basic ITM owner responsibilities vs contractor scope

Software and revision control

Addressable and networked systems need disciplined software control:

1. Identify final revision (name, date, version, checksum if used).
2. Archive a copy for the owner/responsible party per contract (panel upload capability alone is not a backup strategy if the panel fails).
3. Record who may modify programming after turnover.
4. After any post-acceptance change, update revision records and retest affected functions.

Exam trap: Believing “as-builts” means only architectural device dots. Circuit identity, software revision, and matrix logic are part of the living record.

Who Signs What at Level II Participation

NICET Level II describes technicians who work with limited supervision on installation and related tasks. Documentation roles break down roughly as follows (contracts and state law can add sealing requirements):

Level II boundaries:

• Do sign test records and installation statements that truthfully describe your testing and installation work.
• Do not sign as “designer of record” or stamp drawings unless you hold that legal role.
• Do not backdate or check acceptance boxes for untested elevators, HVAC shutdowns, or supervising-station receipt.
• Do escalate incomplete packages; refuse pressure to deliver a fraudulent Record of Completion.

Ethics and the NICET Code of Conduct align with this: inaccurate completion documents are not a paperwork shortcut—they are a professional integrity failure with life-safety consequences.

Practical Closeout Workflow

1. Freeze field changes; finish punch items that affect life safety.
2. Update redlines daily during final week; convert to record set.
3. Export final program; label revision; store offline copy with package.
4. Finalize battery/VD calcs from as-built loads.
5. Complete Record of Completion and attach test records.
6. Train owner operators; obtain acknowledgment if the project requires it.
7. Transmit package to owner and AHJ as required; keep contractor file copy.
8. Ensure supervising station account paperwork matches final zone/point descriptions.

Relationship to Later Maintenance Documentation

Chapter 9 of this study guide (maintenance documentation) builds on this package. Periodic ITM reports, impairment records, and record-drawing updates after renovations only work if the baseline at acceptance was accurate. Commissioning documentation is the zero point of the system’s life cycle.

Exam Focus

Prefer answers that include a complete package (ROC + as-builts + sequence + calcs + manuals + software ID), that update drawings after field moves, and that limit Level II signatures to truthful participation—not design seals or false “all interfaces tested” claims.