Study guide

9.2 Inspection & Test Reports

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

9.2 Inspection & Test Reports

Key Takeaways Explain This Topic AI

A proper ITM report identifies the facility/system, date, tech identity, devices/functions tested, pass/fail results, measured values where applicable (such as sensitivity), deficiencies, and corrective status

Device-level detail beats vague summaries—address/ID, location, and result allow retest, trending, and AHJ review

AHJs commonly expect complete, legible reports that match Chapter 14 methods and frequencies, with open deficiencies clearly called out—not buried

The false “all devices OK” report without device lists or measured data is a documentation and ethics trap, not a time-saving best practice

Last updated: August 2026

9.2 Inspection & Test Reports

Quick Answer: A valid inspection/test report is a device- and function-level record : who tested, when, what was tested (IDs), how it performed (pass/fail and measured values where required), what failed, and what remains open. “All devices OK” with no list is not a report—it is a claim without evidence. Level II technicians write reports the next tech and the AHJ can use without a phone call.

Blueprint item 2.2.3 and Chapter 14 ITM only work if results are captured. This section is the practical anatomy of that capture for NICET Fire Alarm Systems Level II.

Purpose of the Report

An inspection and testing report serves four audiences:

  • Owner — Proof of due diligence and a punch list of deficiencies affecting life safety and liability
  • AHJ — Evidence that required frequencies and methods were applied
  • Next technician — Baseline for trending (sensitivity, trouble history) and retest after repairs
  • Your company — Quality control and professional record of work performed

If any audience cannot answer “what failed on which device on which date,” the report is incomplete.

Required Content Concepts

NFPA 72 forms and annex examples evolve by edition; contracts and AHJs may mandate specific templates. Regardless of template branding, Level II reports should include the following content types :

  • Content element Why it matters Weak substitute to avoid
  • Facility / system ID Ties report to the correct building and FACU First name of the property manager only
  • Date (and time window) Proves schedule against frequency tables “Spring 2026” with no day

Service organization & technician identity Accountability; some AHJs want cert/license numbers Illegible initials only

Inspection vs test vs maintenance scope Shows which Chapter 14 activities were performed Mixing “looked at” with “functionally tested” without distinction

  • Device / circuit / function identification Enables retest and mapping to as-builts “Smokes upstairs OK”
  • Result (pass/fail or status) Core evidence Blank cells

Measured values Required for sensitivity and useful for voltages, currents, intelligibility checks where taken “Sensitivity fine” with no number

  • Deficiencies Separates working system from paper claim Omitting fails to avoid owner conflict
  • Corrective action / open-item status Tracks impairment-to-repair closure “Will fix later” with no item ID

Comments / impairments / AHJ notifications Context for partial tests and life-safety controls Silent partial testing

Device identification standards

Use identifiers that match the panel and drawings when possible:

  • Addressable point number / loop-device address
  • Circuit and device number for conventional systems
  • Clear location (floor, room, landmark)—especially when addresses were never labeled in the field
  • Appliance circuit and candela/setting notes when notification is in scope

Scenario: Report says “SD-12 failed.” As-builts show two different SD-12 labels on two floors after a renovation. Without room location and panel address, the repair tech replaces the wrong detector.

Pass/fail and “not tested”

Every in-scope device/function should end in one of:

  • Pass (met criteria)
  • Fail (did not meet criteria)
  • Not tested (out of scope today, inaccessible, impaired, or scheduled later)—with a reason

Never convert “not tested” into “pass.” Inaccessible locked electrical rooms, occupied ORs, or elevators awaiting the elevator contractor are not tested , not automatic passes.

Sensitivity and other measured values

Where Chapter 14 or manufacturer instructions require sensitivity testing (or other quantitative checks), record the value and units (and the tool/method if the form provides for it), not only pass/fail. Sensitivity history detects drift before nuisance alarms or missed detection. If a detector is replaced, note old/new model and that sensitivity baseline restarts for the new device.

Other quantitative notes often worth capturing when performed:

  • Battery float/charger observations and load-test notes per procedure
  • NAC voltage under alarm at end-of-line (when measured)
  • Ground-fault or impedance troubleshooting readings when used to justify repairs
  • Intelligibility or ambient sound notes for EVACS troubleshooting (when in scope)
  • Deficiencies vs notes

Classification Example Report handling

Deficiency / fail Pull station did not initiate alarm; speaker dead Fail result + deficiency item + recommended corrective action

Impairment System (or zone) out of service for repair with fire watch Cross-reference impairment record; do not hide as “N/A”

Observation / recommendation Dusty detector still within sensitivity but dirty environment Note for cleaning schedule; not a silent ignore

Design/code concern beyond ITM scope Missing device in a renovated room vs original design Document and escalate; do not “pass” a non-existent device

Sample Table Structures

Use tables that force device-level honesty. Simplified models:

Initiating device functional test log

  • Device ID / address Type Location Method Result Measured (if any) Deficiency / notes
  • L1D042 Photo smoke 2nd fl corridor outside 214 Listed aerosol Pass 2.1 %/ft (example format) —
  • L1D057 Photo smoke Elec closet 2B Listed aerosol Fail Over range / no entry Replace & retest
  • P2-04 Manual pull Stair 2 discharge Operate station Pass — Cover broken—replace cover
  • Notification appliance sample
  • Circuit Appliance ID Location Candela/setting Result Notes
  • NAC-3 S-18 Waiting 110 75 cd Pass Temporal correct
  • NAC-3 S-19 Waiting 112 75 cd Fail No flash—repair
  • Interface / function matrix lines
  • Function Input used Expected output Result Notes
  • Elevator recall primary Lobby smoke L2D010 Cars to primary floor Pass Witnessed with elevator tech
  • AHU-3 shutdown Duct L3D004 Fan stop / damper per design Not tested AHU offline for mechanical work—scheduled
  • Waterflow Riser 1 flow switch Alarm + SS receipt Pass SS ticket #…
  • Report header block (every multi-page package)
  • Site name / address
  • FACU make/model / software revision if known
  • Contract type (annual ITM, reacceptance after remodel, service call)
  • Technician name, company, phone, date
  • Standards referenced (NFPA 72 edition as adopted) and whether AHJ was present

Attach photos of panel revision screens, deficiency conditions, and end-of-line voltage readings when they clarify the written row.

Common AHJ Expectations

AHJs differ, but patterns repeat:

Completeness — Frequencies claimed match devices present; interfaces not silently skipped.

Legibility and permanence — Readable ink/PDF; permanent site file.

Open deficiencies highlighted — Not buried in paragraph 14 of a narrative.

Consistency with as-builts — Device counts and labels roughly match drawings or differences are explained.

Timely submittal when local rules require forwarding annual reports to fire prevention.

Impairment documentation when systems were off-normal during testing.

Retest documentation after repairs before “closed” status.

Scenario: AHJ audits three years of reports. Year 1 lists 120 smokes with addresses. Year 2 says “all smoke detectors tested OK” with no list. Year 3 lists 95 smokes after a remodel with no note about removals. The AHJ questions both Year 2’s credibility and Year 3’s unexplained device-count change.

The “All Devices OK” Trap

Blanket statements fail for technical and ethical reasons:

  • Problem Consequence
  • No device inventory Cannot prove 100% of required devices were included
  • No fail detail Owner cannot prioritize repairs; liability ambiguity
  • No measured values Sensitivity drift invisible; manufacturer warranty disputes harder
  • Encourages pencil-whipping Technician under time pressure marks pass without testing
  • Breaks multi-year sampling records Heat-detector sampling and similar programs need identifiable history
  • NICET / professional ethics conflict Misrepresentation of work performed

Acceptable short summary language only after detailed attachments exist: “See device log: 118/120 initiating devices pass; 2 fails open—see deficiency list.” The summary points to evidence; it does not replace evidence.

Exam trap: Choosing the answer that says a one-line “system tested satisfactory” meets documentation requirements for full annual ITM of a large addressable system.

Writing Quality Habits for Level II

Pre-load device lists from the panel point report or last year’s log; reconcile missing/extra points before you start.

Record fails immediately; do not rely on memory after 200 devices.

Separate test results from sales recommendations so owners and AHJs see safety defects clearly.

If testing is partial (phased floors, occupied critical care), title the report honestly as partial and list untested scope.

After repairs, issue a retest report or update referencing the original deficiency IDs—do not only mark the work order “done.”

Align report language with the sequence of operation: wrong signal type (alarm vs supervisory) is a fail even if “something happened at the panel.”

Relationship to Impairments and Corrective Action

When a fail creates an impairment, the ITM report should point to the impairment procedure (notification, fire watch, tag) covered in the impairments chapter. When the repair is complete, documentation should show fail → repair → retest pass as a chain. Broken chains are a common AHJ finding: many open fails, no closure records.

Exam Focus

Select answers that demand device-level IDs, pass/fail, measured values when applicable, tech identity, date, and deficiency tracking . Reject blanket “all OK,” conversion of not-tested into pass, and reports that omit interfaces while claiming complete annual testing. Prefer forms/tables that a second technician can execute without guessing.