9.2 Inspection & Test Reports

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:

1. Owner — Proof of due diligence and a punch list of deficiencies affecting life safety and liability
2. AHJ — Evidence that required frequencies and methods were applied
3. Next technician — Baseline for trending (sensitivity, trouble history) and retest after repairs
4. 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:

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

Sample Table Structures

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

Initiating device functional test log

Notification appliance sample

Interface / function matrix lines

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:

1. Completeness — Frequencies claimed match devices present; interfaces not silently skipped.
2. Legibility and permanence — Readable ink/PDF; permanent site file.
3. Open deficiencies highlighted — Not buried in paragraph 14 of a narrative.
4. Consistency with as-builts — Device counts and labels roughly match drawings or differences are explained.
5. Timely submittal when local rules require forwarding annual reports to fire prevention.
6. Impairment documentation when systems were off-normal during testing.
7. 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:

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

1. Pre-load device lists from the panel point report or last year’s log; reconcile missing/extra points before you start.
2. Record fails immediately; do not rely on memory after 200 devices.
3. Separate test results from sales recommendations so owners and AHJs see safety defects clearly.
4. If testing is partial (phased floors, occupied critical care), title the report honestly as partial and list untested scope.
5. After repairs, issue a retest report or update referencing the original deficiency IDs—do not only mark the work order “done.”
6. 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.