5.5 Documentation, Records, and Service History

The Required NFPA 72 Records

NFPA 72 Chapter 7 (documentation) and Chapter 14 make several records mandatory, and NICET expects you to know what each proves:

• Record of Completion — completed before the AHJ approves a new or modified system, it documents the as-installed system (devices, circuits, software/zoning, sequence of operations). A copy is stored at the fire alarm control unit (FACU), and it must be revised and kept current whenever the system is modified.
• Inspection and Testing Form — an NFPA 72 report (commonly Form 72A or an AHJ-approved equivalent) completed for each periodic ITM event, listing what was inspected/tested, the method, the result, deficiencies/impairments, corrections, retest results, and final status.
• Record retention — documentation must be available for examination and maintained for the life of the system, not discarded after a year.

Strong vs Weak Records

NICET maintenance questions reward candidates who think like the person responsible for evidence. A system can be tested, repaired, and restored in the field, but the work is incomplete if the record cannot show what was done. A good service record is not a vague story; it separates what was observed from what was corrected and states the actual result, not just the attempted action.

If a duct smoke detector failed to report to the FACU, a record that simply says "detector serviced" is weak. A strong record identifies the detector and its location, states the failed response (no alarm annunciated at the panel), names the corrective action, gives the retest result, and confirms the final normal condition.

Evaluate report choices with this list:

1. Does the record name the exact item or function?
2. Does it state the actual result, not just the action attempted?
3. Does it preserve deficiencies and impairments instead of hiding them?
4. Does it show who was notified when protection was reduced?
5. Does it state whether the system/affected portion was restored?
6. Does it separate resolved items from unresolved follow-up?

Documentation Traps and Role Scaling

The most common trap is choosing the shortest record because it sounds efficient — fire alarm records must be useful to the owner, AHJ, and next technician for the life of the system. A second trap is writing "corrected" with no documented retest: a future reviewer cannot tell whether the fix actually restored the required function. A third is forgetting that the Record of Completion at the FACU must be updated when the system is modified — leaving stale as-builts is itself a deficiency.

NICET scales documentation by role. Level I records the work performed; Level II and III outlines explicitly include maintaining and preparing records for owners, AHJs, and project files. The unsuccessful-candidate score report breaks results out by domain, so if documentation is weak after practice, drill it by rewriting bad records into good records — force device identity, condition, correction, retest, status, and follow-up into every entry.

Because NICET items use exhibits, a recordkeeping question may show a device map and ask what information is missing; match the record to the point, room, circuit, status, and action shown, not just the device type.

What the Record of Completion Captures

The Record of Completion is the system's birth certificate and running history. Beyond device counts, it documents the system description and type, the service organization and responsible parties, the circuit/pathway designations and class, the device inventory by zone/address, the secondary power (battery) calculation, the sequence of operations / input-output matrix, and the interfaces (elevator, HVAC, suppression, off-premises monitoring).

When the system is modified — devices added, software changed, monitoring re-pointed — the Record of Completion must be revised and kept current, with the updated copy at the FACU. An out-of-date as-built record is a deficiency in its own right, because the next technician and the AHJ rely on it to know what should be there.

The Inspection and Testing Form

Each periodic ITM event produces an Inspection and Testing report. NFPA 72 provides a model form (often referenced as Form 72A), and AHJ-approved equivalents are acceptable. The form ties together the date and site, the personnel and their qualification, the devices/functions inspected and tested, the method and expected vs actual result per item, deficiencies and impairments found, corrective actions and retest results, and the final system status. A best practice is to attach the device-by-device test log so a reviewer can confirm coverage — not just a blanket "system tested, passed."

Records as the Owner's Compliance Evidence

Because NFPA 72 places the maintenance duty on the owner, these records are the owner's proof of compliance to insurers, the AHJ, and during incident investigations. That is why they must be retained for the life of the system and be available for examination. For NICET candidates, the durable lesson is that the field work and the record are a single deliverable: a perfectly executed test with a vague record is incomplete, and a thorough record of a test that skipped the retest is dishonest.

Practice writing the record as you perform each step, capturing identity, method, result, correction, retest, and restoration in real time rather than reconstructing it later.