Study guide

7.6 As-Builts, Closeout Packets, and Record Discipline

NICET Fire Alarm Systems Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: NICET FAS Levels, Exams, and Application Path

1.1 Program Purpose and Technician Role 1.2 Levels I Through IV and Role Expectations 1.3 Exam Counts, Times, Fees, and Format 1.4 Application, Work History, and Verification 1.5 Scheduling, Security, Scoring, and Retakes 1.6 Certification Maintenance and Study Planning

2 Code Navigation, References, and Exam Strategy

2.1 Reference Stack by Level 2.2 Physical and On-Screen Reference Rules 2.3 NFPA 72 Navigation Strategy 2.4 NFPA 70, Ugly's, and Electrical Reasoning 2.5 Building, Life Safety, and Management References 2.6 Timing, Exhibits, and Multi-Answer Strategy

3 Fire Alarm System Fundamentals and Components

3.1 System Architecture and Signal Flow 3.2 Control Units, Annunciators, and Interfaces 3.3 Initiating Devices and Detection Concepts 3.4 Notification Appliances and Occupant Signaling 3.5 Power Supplies, Circuits, and Supervision Basics 3.6 Basic Electricity, Electronics, and Field Vocabulary

4 Installation, Pathways, Devices, and Job-Site Safety

4.1 Work Plans, Drawings, and Field Conditions 4.2 Pathways, Raceways, and Cable Routing 4.3 Mounting Boxes and Peripheral Devices 4.4 Terminating Conductors and Labeling Circuits 4.5 Job-Site Safety for Fire Alarm Technicians 4.6 Commissioning Prep, Punch Lists, and Turnover Readiness

5 Inspection, Testing, Maintenance, and Impairments

5.1 Maintenance Domain Map for NICET FAS 5.2 Inspection, Testing, and Maintenance Distinctions 5.3 Periodic Testing Workflow 5.4 Deficiencies, Impairments, and Corrective Action 5.5 Documentation, Records, and Service History 5.6 Restoration, Troubleshooting, and Closeout

6 Power Supplies, Circuits, Loading, and Calculations

6.1 Power and Loading Domain Map for NICET FAS 6.2 Standby and Alarm Load Logic 6.3 Battery Sizing and Secondary Power 6.4 Notification Appliance Circuit Loading 6.5 Initiating and Signaling Circuit Supervision 6.6 Voltage Drop and Wire Resistance

7 Submittals, Technical Drawings, and System Layout

7.1 Drawing Package Purpose and Blueprint Fit 7.2 Site-Condition Surveys and Field Verification 7.3 Shop Drawing Content and Coordination 7.4 Layout Decisions for Devices, Pathways, and Interfaces 7.5 Drawing Review, Approval, and Level Responsibility 7.6 As-Builts, Closeout Packets, and Record Discipline

8 Commissioning, Acceptance, Troubleshooting, and Closeout

8.1 Commissioning Readiness and Systematic Startup 8.2 Acceptance Testing and Witness Coordination 8.3 Troubleshooting Faults and Deficiencies 8.4 Exam Exhibits, Scenario Logic, and Multi-Answer Items 8.5 Coordination with AHJ, Owner, Contractor, and Trades 8.6 Turnover, Closeout, and Post-Acceptance Support

9 Supervision, Project Coordination, and Work History

9.1 Level III and IV Supervision Boundaries 9.2 Coordinating Work Activities and Site Constraints 9.3 Leading Installation and Commissioning Teams 9.4 Managing Testing, Deficiencies, and Impairments 9.5 Documentation, As-Builts, Closeout, and Records 9.6 Work History, Verification, Recommendations, and Major Project Evidence

10 Complex Systems, Interfaces, and Specialty Operations

10.1 Level IV Complex Operations Frame 10.2 Suppression System Interfaces and Release Coordination 10.3 Networked Control Units and Distributed Systems 10.4 Smoke Control and High-Rise Interface Coordination 10.5 Air Sampling and Specialty Detection Strategy 10.6 Voice Evacuation, Emergency Radio, and Industry Coordination

11 Level-by-Level Review and Domain Remediation

11.1 Blueprint-First Review Method 11.2 Level I Remediation: Installation and Maintenance 11.3 Level II Remediation: Layout, Commissioning, and Coordination 11.4 Level III Remediation: Supervision, Records, and Approval 11.5 Level IV Remediation: Complex Operations and Leadership 11.6 Score Report Remediation and Practice Routing

12 Integrated NICET FAS Scenarios and Final Readiness

12.1 Integrated Scenario Reading Method 12.2 Final Seven-Day Study Plan 12.3 Exam-Day Reference and Logistics Checklist 12.4 Testing Interface, Timing, and NDA Readiness 12.5 Retake Decision Tree and Rescheduling 12.6 After Passing: Certification and Recertification

7.6 As-Builts, Closeout Packets, and Record Discipline

Key Takeaways Explain This Topic AI

NFPA 72 7.6 requires record (as-built) drawings reflecting actual installation; 7.5 requires the completion documents and Record of Completion.

The owner package includes record drawings, the owner's manual, manufacturer instructions, the written sequence of operation, and for software-based systems a record copy of the site-specific software.

Records of testing and operation are retained per NFPA 72 (at least until the next test plus one year, generally a 2-year practical floor).

The exam trap is reconstructing as-builts from memory at the end instead of capturing approved changes and field markups in real time.

Last updated: June 2026

The Completion Package NFPA 72 Requires

At turnover, NFPA 72 Chapter 7 requires a defined completion package , not a loose pile of paper. NFPA 72 7.5 covers completion documents including the Record of Completion — the standardized form that documents the system description, devices, circuits, and the parties responsible. NFPA 72 7.6 requires record (as-built) drawings that reflect the system as actually installed , including any approved field changes. The owner's on-site documentation set, required by Chapter 7, typically includes:

Completion / closeout item NFPA 72 basis and value

Record of Completion 7.5 standardized form; certifies what was installed, by whom, and what tests passed.

Record (as-built) drawings 7.6; numbered drawings showing final device locations, circuits, and pathways.

Owner's manual Operating instructions and routine-test guidance for the owner.

Manufacturer's instructions Listed-product data for replacement and compatibility.

Written sequence of operation The narrative/matrix used to troubleshoot alarm, supervisory, trouble, and interface events.

Site-specific software record copy Required for software-based systems so the program can be restored.

Test/acceptance records What was verified at turnover (ties to Chapter 14).

NFPA 72 also sets records retention : testing and operating records are kept at least until the next required test and then one year thereafter — a two-year window is the common practical floor. Those records are not clerical leftovers; they are the technical map a future technician relies on.

Record Discipline Across the Project

An as-built must reflect actual device locations, control equipment, pathway changes, circuit assignments, interface points, power-supply locations, and final sequence information, and it must agree with the acceptance-test records and the approved revisions. If a field change is allowed during construction but never captured in the final documents, the next technician wastes time or makes an unsafe assumption — and the owner's NFPA 72 7.6 record set is non-compliant.

NICET ties this to levels: Level III installation tasks include compiling as-builts and close-out documents; Level IV includes as-builts and closeout at a department/management level.

Worked example (Level III). Notification-appliance circuit numbers are changed during installation to solve a routing conflict. The correct closeout action is to update the record drawings, the loading/voltage-drop documentation if affected, and the testing records — the field success is incomplete until the final record matches the installed system. Level IV version: multiple projects deliver late closeout packages with repeated owner complaints; the best answer is a closeout checklist, earlier assignment of responsibility, and a requirement to capture field markups before acceptance.

Exam trap: waiting until the project ends to reconstruct as-builts from memory. A reconstructed drawing rarely matches what the field actually installed, which is exactly the accuracy NFPA 72 7.6 demands of the record set. A practical study move is to think backward from a service call : if a technician arrives five years later with a ground-fault trouble, what final records help them find the module, read the sequence, and confirm circuit assignments? If the closeout package cannot answer that, it has failed its purpose.

The completion documents are the bridge between the install team's work and the system's entire service life under NFPA 72 Chapter 14 inspection, testing, and maintenance.

The Record of Completion and On-Site Documentation

The Record of Completion is the centerpiece completion document, and the exam expects familiarity with what it captures: the protected property and owner, the installing and servicing contractors, the type of system and the code edition used, the device and circuit inventory, the types of initiating devices and notification appliances, the secondary power supply and battery rating, the alarm-receiving (supervising) station and method of transmission, and a checklist of completed tests with the signatures of the parties who verified them.

It is not a marketing form; it is the legal and technical attestation that the system was installed and tested to NFPA 72. Under NFPA 72 7.5 , the Record of Completion must be completed and signed by the responsible parties at acceptance, with a copy provided to the owner and a copy retained on site; later modifications or additions to the system require the form to be updated or re-executed so the record always reflects the system as it currently stands.

NFPA 72 Chapter 7 also requires a defined on-site documentation set to be left at the FACU so the next technician and the owner are never stranded. That set normally includes the record drawings, the owner's manual, the manufacturer's published instructions, the written sequence of operation, a copy of the Record of Completion, and — for software-based panels — the site-specific software record copy and any program backup needed to restore the system.

Record of Completion (signed, with the device/circuit inventory and test checklist).

Numbered record (as-built) drawings reflecting the installed system.

Owner's manual and manufacturer's instructions for operation and routine testing.

Written sequence of operation / input-output matrix.

Site-specific software record copy for software-based systems.

Retention ties the package to the system's life: NFPA 72 requires testing and inspection records to be kept at least until the next required test and then for one year afterward, so the documentation cycle started at submittal never actually ends — each ITM event under Chapter 14 reads, relies on, and adds to the records the install team created. A candidate who treats closeout as the start of the maintenance record, not the end of the install, will answer these scenarios correctly.