8.1 NFPA 25 Inspection, Testing, and Maintenance Reporting Forms & Records
Key Takeaways
Use the report matched to the assigned activity and system; distinguish an inspection observation from a test measurement or maintenance action.
A defensible record identifies the property, system, component, location, date, activity, observed result, measurements, deficiencies, notifications, and restoration.
NFPA 25 establishes record and responsibility principles, while the exact form fields and portal can be set by the owner, employer, insurer, or AHJ.
Write observations rather than unsupported causes, legal conclusions, or copied boilerplate.
Correct errors transparently under the employer’s record-control process and preserve the original evidence.
8.1 Inspection, Testing, and Maintenance Reports
The Level I outline asks the technician to identify the correct reports for inspection, testing, and maintenance activities. A report is useful when another qualified person can determine what system was examined, what was done, what was observed, and whether normal protection was restored. A form filled with check marks but no traceable component information does not meet that purpose.
Match the record to the activity
Inspection is generally a visual examination of a system or portion of a system to verify apparent operating condition and freedom from physical damage. Testing uses an operation or measurement to determine status or performance. Maintenance is work that keeps equipment operable or makes a repair. One visit can include all three, but the record should not blur them.
Select the form or report section that matches the system and task: sprinkler inspection, valve inspection, main-drain test, waterflow alarm test, supervisory-device test, hydrant work, hose-system activity, or impairment. The exact form name and electronic portal are not universal NFPA requirements. Employers, owners, insurers, and authorities having jurisdiction may specify additional fields or submission methods.
Core information
A strong record ordinarily identifies:
- property and protected building or area;
- system, riser, valve, device, or component identifier;
- exact location;
- date and, when material, time;
- activity performed and applicable procedure;
- observed condition or measured result with units;
- comparison or acceptance criterion used by the supervisor;
- deficiency or impairment facts;
- people or organizations notified;
- corrective or temporary action taken; and
- final restoration and signal status.
The form may also request owner representative, technician, weather, water-supply condition, monitoring account, or other administrative information. Complete required fields, but do not teach every possible field as a universal NFPA mandate. The governing form and procedure define the local administrative requirements.
Objective language
Record what you saw, measured, heard, or verified. “North riser supply gauge read 42 psi static” is an observation. “City main is failing” is a diagnosis that the reading alone does not prove. “PIV target indicated SHUT; supervisor notified at 09:18” is more useful than “bad valve.”
Use consistent identifiers. If the system calls a valve CV-3, use CV-3 in the report, photograph label, and impairment record. Include units for pressure, time, distance, and temperature. State whether a pressure was static or flowing. If an alarm signal was verified, identify the signal type and receiving location rather than writing only “alarm passed.”
Do not copy a prior reading into a current result. Prior records are a comparison source, not a substitute for the present observation. If a component is inaccessible or a task cannot be completed, mark it accordingly and explain why. Never mark a task satisfactory when it was not performed.
Deficiencies, impairments, and notifications
Describe the component, exact condition, location, and effect known at the time. The supervising technician can then classify it using NFPA 25 definitions and system context. A condition may be noncritical, critical, or an impairment depending on actual consequence; the Level I technician should not force every example into a predetermined label.
When prompt notification is required, record whom you contacted, when, and what information was provided. If temporary safeguards or impairment tags were applied under direction, identify them. Do not state that a fire department or insurer was notified unless confirmation exists.
Corrections and integrity
Follow the employer's controlled process for correcting paper or electronic records. Preserve the original entry, identify the correction, and provide date or attribution as required. Do not erase a failed result, delete a photograph, or rewrite history after a repair. The repair and successful retest belong in subsequent traceable entries.
Protect sensitive building and alarm information according to policy. Upload records only through approved systems. Photographs should avoid unrelated personal information and should be tied to the component and location.
Final quality check
Before submission, reconcile the component inventory with the work completed. Check that every measurement has units, every failed or incomplete item has an explanation, all required notifications are documented, and the final system and signal status is stated. Sign or attest only to work you actually performed or observed and only within your authorization. A precise preliminary record allows the Level II or III supervisor to review, classify, and issue the final report without guessing what happened in the field.
Which entry is the most objective?
“The city supply is definitely failing”
“Everything looked normal”
“North riser gauge G-1 indicated 42 psi static at 09:05; prior report listed 58 psi; supervisor notified”
“Probably a closed valve somewhere”
Who can define additional report fields or an electronic submission method?
Only a universal NFPA web portal
The owner, employer, insurer, or AHJ through the applicable process
No one; all reports must have identical fields
Only the gauge manufacturer
A test could not be completed because the component was inaccessible. What should the report show?
Mark it satisfactory to avoid delay
Copy the prior result
Leave the entire form blank
Mark it incomplete or inaccessible and explain the exact reason and notification
Sections you finish are checked off in the contents.