Study guide
5.2 Record of Completion & As-Builts
NICET Fire Alarm Systems Level II Exam
Track your progress as you read
Finished sections get a check mark.
1 Exam Overview & Open-Book Strategy
1.1 Exam Facts, Eligibility & Logistics 1.2 Open-Book References & On-Screen Navigation 1.3 Certification Path & Performance Measures
2 Installation: Work Planning
2.1 Work Plans from Field Conditions 2.2 Drawings, Specs & Code Interpretation 2.3 Jobsite Safety & Trade Coordination
3 Installation: Circuits, Pathways & Survivability
3.1 Pathway Classes A, B, C, D, E, N & X 3.2 Survivability Pathway Levels 0–3 3.3 NEC Article 760, NPLFA/PLFA & Raceways 3.4 SLC Topology, T-Taps & Supervision
4 Installation: Equipment
4.1 Initiating Devices (Level II Applications) 4.2 Notification Appliances & NAC Design 4.3 Control/Monitor Modules & FACU Hardware 4.4 Voice EVACS Speakers & Intelligibility Basics
5 Installation: Commissioning
5.1 Acceptance Testing & Commissioning Sequence 5.2 Record of Completion & As-Builts 5.3 Functional Verification of Interfaces
6 Installation: System Interfaces
6.1 Elevator Recall Phase I & II 6.2 Shunt Trip & Heat Detector Placement 6.3 HVAC Shutdown & Duct Smoke Detectors 6.4 Suppression Interconnections (Waterflow, Tamper, Releasing, Clean Agent, Hood)
7 Maintenance: Periodic Testing
7.1 ITM Framework (NFPA 72 Chapter 14) 7.2 Device Test Methods & Frequencies 7.3 Interface, Waterflow & Tamper Tests 7.4 EVACS, Elevator & Special Function Tests
8 Maintenance: Impairments & Troubleshooting
8.1 Impairment Programs & AHJ Notification 8.2 Troubleshooting SLC, NAC & Power Faults 8.3 Corrective Actions & Retest Requirements
9 Maintenance: Documentation
9.1 Required Records & Retention 9.2 Inspection & Test Reports 9.3 Record Drawing Updates After Changes
10 Submittals: Shop Drawing Packages
10.1 Shop Drawing Package Contents 10.2 Cut Sheets, Calculations & Sequence of Operation 10.3 AHJ Submittal Expectations
11 Submittals: Site Survey
11.1 Occupancy, Construction & Fire Protection Features 11.2 Layout Constraints & Field Verification 11.3 Pathway Routing & Survivability Field Checks
12 Submittals: Basic Technical Drawings
12.1 Symbols, Risers & Floor Plans 12.2 Zone Schedules & Legends 12.3 Drawing Notes for Voltage Drop & Conduit Fill
13 Submittals: Power Supply & Loading
13.1 Standby & Alarm Load Basis (24 h + 5/15 min) 13.2 Battery Sizing with 20% Aging Derating 13.3 Voltage Drop Calculations 13.4 Conduit Fill & Wire Sizing (NEC Chapter 9)
14 Layout Knowledge: Supervising Station
14.1 Supervising Station Types (Chapter 26) 14.2 Transmission Paths & 90-Second Alarm Window 14.3 Protected Premises vs Supervising Station Roles
15 Management & Supervision
15.1 Coordinate Work Activities 15.2 Reporting Progress & Problems 15.3 Ethics & NICET Code of Conduct 15.4 Safety Leadership & Multi-Trade Coordination
5.2 Record of Completion & As-Builts
Key Takeaways Explain This Topic AI
NFPA 72 requires a documentation package at completion—commonly including the Record of Completion, record drawings, sequence of operation, calculations, cut sheets, and owner manuals
Record drawings (as-builts) must reflect actual device locations, circuiting, and field changes—not only the original approved shop set
Software revision control is part of life-safety documentation: the owner needs the final program identity that matches the accepted system
At Level II, technicians prepare and contribute accurate field data and test results; formal certifications and design responsibility remain with the roles defined by the contract, AHJ, and professional seals where required
Last updated: August 2026
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:
Document Purpose Common field failure
Record of Completion Formal statement that the system was installed and tested per applicable requirements; identifies system, parties, and test status Blank sections, missing signatures, unchecked interfaces that were never tested
Record drawings (as-builts) Show actual device locations, circuit numbers, panel locations, and pathway routes as built Shop drawings with no redlines after major field moves
Sequence of operation Cause-and-effect / matrix of inputs to outputs Outdated matrix that does not match final programming
Battery calculations Prove secondary capacity for required standby + alarm (with design factors) Calcs for original design counts after field adds
Voltage-drop calculations Prove end-of-line appliance voltage under alarm load Ignoring longer as-built cable runs
Cut sheets / product data Identify listed equipment actually installed Submittal cuts for Model A, field install of Model B
Owner manuals & O&M Operation, reset, silence, bypass, and maintenance guidance Manuals left on a truck; owner never trained
- Software / revision control Identify final program version and archive “Someone’s laptop” is the only copy
- Test records Device and function results from acceptance Pass/fail with no device IDs or dates
- 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)
- Drawing type At submittal At record/as-built
- Floor plans Proposed device layout Actual locations after field coordination
- Risers Design topology As-wired circuits and panel/booster nodes
- Schedules Design addresses/candela Final addresses, candela, module points
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:
Identify final revision (name, date, version, checksum if used).
Archive a copy for the owner/responsible party per contract (panel upload capability alone is not a backup strategy if the panel fails).
Record who may modify programming after turnover.
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):
Role Typical documentation actions
Level II technician Markup as-builts accurately; complete device test sheets; verify point lists; assemble package components; sign only for work and tests personally performed or verified within authority
Supervisor / engineer / qualifier of record Overall installation certification statements; design responsibility; professional seal on drawings where required by jurisdiction/contract
AHJ Approval/acceptance for occupancy or system use per local process—not a substitute for contractor completeness
Owner / owner’s rep Receipt of documentation, training acknowledgment, understanding of impairments and monitoring contracts
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
Freeze field changes; finish punch items that affect life safety.
Update redlines daily during final week; convert to record set.
Export final program; label revision; store offline copy with package.
Finalize battery/VD calcs from as-built loads.
Complete Record of Completion and attach test records.
Train owner operators; obtain acknowledgment if the project requires it.
Transmit package to owner and AHJ as required; keep contractor file copy.
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.