NFPA 25 records: proving fire protection inspection

Fire protection systems are the equipment nobody wants to use and everybody assumes works. NFPA 25 exists because that assumption fails quietly: a control valve left closed after maintenance, a fire pump that has not been run in months, a dry system with a frozen low point, a sprinkler head painted over during a refurbishment. The standard does not make the system reliable. The inspection, testing and maintenance it prescribes does, and the record is the only evidence that any of it happened. When the fire marshal, the insurer or the incident investigator asks, the question is never whether the system was fine. It is whether you can prove you checked. This paper describes what NFPA 25 and NFPA 72 require the record to show, and what that means for the software holding it.

What records does NFPA 25 require?

NFPA 25, Standard for the Inspection, Testing, and Maintenance of Water-Based Fire Protection Systems, places responsibility on the property owner or a designated representative. The general requirements chapter sets out the record-keeping duty in plain terms.

• Records shall be made for every inspection, test and maintenance activity the standard requires, and they shall indicate the procedure performed, the organization that performed it, the results and the date.
• Records shall be maintained by the owner and made available to the authority having jurisdiction (AHJ) on request.
• Original records of the system's acceptance testing are retained for the life of the system, as are as-built drawings, hydraulic calculations, original acceptance test records and manufacturer's data sheets.
• Records of subsequent inspection, testing and maintenance are retained for one year after the next activity of that type is due.
• Deficiencies and impairments found during ITM are classified and corrected, and the correction is recorded.

The standard also distinguishes three activities and expects the record to say which one occurred. An inspection is a visual examination to verify the system appears to be in operating condition and free of physical damage. A test is a procedure to determine the status of the system as intended by operating it or its components. Maintenance is work performed to keep equipment operable or to make repairs. A form that records "sprinkler system, quarterly, OK" does not meet the requirement, because it does not say which procedures were performed and what each found.

The owner remains responsible even when a contractor performs the work. The contractor's report is evidence the owner must keep, review, and act on.

What are the NFPA 25 inspection, testing and maintenance frequencies?

Frequencies are set per component and per system type across the standard's system chapters, and they are the backbone of any ITM schedule. The most common ones for a facility with sprinklers, standpipes, a fire pump and a water tank are these.

• Control valves. Inspected weekly if sealed, monthly if locked or electrically supervised. Operated through full range annually.
• Gauges. Wet pipe systems monthly; dry, preaction and deluge systems more frequently unless supervised. Gauges replaced or tested against a calibrated gauge every five years.
• Sprinklers, pipe, fittings, hangers and seismic bracing. Visual inspection annually from the floor level. Spare sprinklers and wrench in the cabinet checked annually.
• Sprinkler sample testing. Standard sprinklers at fifty years of service and every ten years thereafter; fast-response sprinklers at twenty years and every ten years thereafter; sprinklers in harsh environments every five years.
• Waterflow alarm devices. Mechanical water motor gongs tested quarterly; vane-type and pressure switch devices semiannually.
• Main drain test. Annually, and quarterly where the sole supply passes through a backflow preventer or pressure reducing valve.
• Dry pipe valves. Partial trip test annually; full flow trip test every three years. Low point drains on dry systems drained before freezing weather.
• Antifreeze systems. Solution tested annually.
• Backflow prevention assemblies. Forward flow test at system demand annually.
• Fire department connections. Visual inspection quarterly.
• Standpipe systems. Flow test every five years; hydrostatic test of manual and semiautomatic dry standpipes every five years.
• Fire pumps. No-flow (churn) test weekly for diesel drivers, monthly for electric drivers except where the standard requires weekly; annual flow test at rated capacity points.
• Water storage tanks. Water level and condition monitored monthly or weekly depending on supervision; tank interior inspected every three years without corrosion protection or every five years with it.
• Internal piping condition. An obstruction investigation every five years from a flushing connection at the end of a main and a branch line, and whenever obstruction indicators appear.

Each frequency is a scheduled record. A defensible program does not simply know the frequencies; it can show for each device that the activity occurred within the window, and where it did not, why and what was done.

How does NFPA 72 treat fire alarm records?

Water-based systems rarely stand alone. Waterflow switches, tamper switches and fire pump supervisory signals report to a fire alarm control unit governed by NFPA 72, the National Fire Alarm and Signaling Code, whose inspection, testing and maintenance chapter carries its own frequencies and record requirements.

• Visual inspection frequencies are tabulated by component: control equipment, batteries, initiating devices, notification appliances and supervising station connections, at intervals from weekly to annually depending on the component and whether it is monitored.
• Test methods are tabulated by component with their frequencies. Control unit functions, initiating devices and notification appliances are functionally tested annually. Smoke detector sensitivity is tested within the first year and on a fixed cycle thereafter, with extension permitted where results stay stable. Batteries carry load and voltage tests on their own schedule.
• Records must identify the property and its address, the date, the test frequency, the name and organization of the person performing the work, the results, and the AHJ where applicable, and the code provides an inspection and testing form for the purpose.
• ITM records are retained until the next test and for one year thereafter. The record of completion from the original installation and any subsequent modifications is retained for the life of the system.

The overlap with NFPA 25 is the waterflow and supervisory signals. Testing a waterflow alarm under NFPA 25 and verifying receipt of the signal at the control unit and the supervising station under NFPA 72 are two records of one event, and the program should be able to show both against the same device.

How should impairments be recorded?

An impairment is a condition in which a fire protection system, or part of it, is out of order. NFPA 25 devotes a chapter to it because an unrecorded impairment is the most common single cause of a system failing to perform. The procedure is specific.

• Impairment coordinator. The owner assigns a person responsible for the procedure.
• Preplanned versus emergency. Preplanned impairments are scheduled work and require prior authorization; emergency impairments are unplanned and must be handled as soon as discovered.
• Tag. A tag is attached to the affected system, typically at the control valve or the fire department connection, indicating the system, the date and the impairment.
• Notification. The fire department, the insurer, the alarm company, the property owner and the affected occupants are notified.
• Mitigation. Depending on the system and the duration: fire watch, temporary water supply, hot work restrictions, evacuation planning.
• Restoration. The system is returned to service, verified, the tag is removed, and the parties notified are informed of the restoration.

The record for an impairment therefore has a lifecycle: opened, mitigated, restored, with named people and times at each step. A checkbox on a monthly form cannot hold that. It needs a record with states, and a way to report on every impairment currently open, because an open impairment on a system that everyone believes is in service is exactly the failure the chapter is written to prevent.

What does an AHJ or insurer look for in ITM records?

The fire marshal, the insurer's loss control engineer and the internal auditor ask different questions with the same shape.

• Is every system and device in the program, and does each have a schedule consistent with the standard's frequencies?
• For each scheduled activity, is there a record within the window, and does it show the procedure, the person, the organization, the result and the date?
• Where deficiencies were found, were they classified, corrected, and is the correction recorded with a date?
• Were impairments handled through the procedure, and are there any open impairments now?
• Were the people doing the work qualified, where the jurisdiction requires a license or certification for fire sprinkler inspection?
• Can the record be reproduced as it was signed, or has it been edited since?
• Can you produce the last five years quickly, or does it require pulling binders from three contractors?

The last two questions expose paper and generic document systems. A scanned report proves the report existed; it does not prove what it said when it was signed, and it cannot be queried for every dry valve that missed its three-year full trip. A program whose evidence is a filing cabinet is a program that discovers its gaps during the inspection rather than before it.

How do you prove a fire protection inspection happened?

Proof is a matter of record design. An ITM record that will stand up has these properties.

• Identity of the device. Each valve, gauge, pump, tank, dry valve and hydrant is a durable record with a location and a stable identifier, ideally a tag that can be scanned in the field, so the inspection is bound to the device rather than to a floor plan sketch.
• The activity type. Inspection, test or maintenance, with the specific procedure from the standard.
• Structured results. Gauge readings, valve position, test pressures, pump flow and pressure points, trip times, alarm receipt times as fields, not prose.
• Evidence at capture. Photographs of the valve position, the gauge face, the tag, the pump test header, bound to the device and the activity at the moment they were taken.
• Identity of the person. An authenticated individual, with a signature that freezes the record, and their qualification on file. A shared login on a shared tablet defeats the purpose.
• Deficiency and impairment lifecycle. Findings that stay open until they are closed, with dates and names at each state.
• Field capability. Pump rooms, tank tops and valve pits have no signal, and a record that cannot be captured offline gets captured later from memory.
• Reporting. The AHJ wants the last year; the insurer wants trends; the coordinator wants open impairments today. All three should be queries of the same record.

None of this changes the standard. It makes the standard's record-keeping requirement something that can be produced on demand instead of assembled under pressure.

How intelliSPEC handles it

intelliSPEC's intelliFIRE is the module for fire protection condition, hazards and NFPA compliance, with fireproofing and passive fire protection appendices alongside active system inspection. Because the platform is metadata-driven, with forms and workflows configured through the form designer rather than code, the ITM procedures a site follows, the inspection, test and maintenance items for each system type at their frequencies, are configured forms whose fields are structured results rather than free text. Each device is a node in the asset graph with a location, identified in the field by QR or barcode scan, so the record binds to the valve or the pump rather than to a drawing.

Field capture is built for pump rooms and valve pits. The app works fully offline with no time limit on the local store, photos and video bind to the device at capture, GPS location can be recorded, and the signature widget captures per-signer identity on a shared device. Impairments and deficiencies run through workflow states; the platform's transitions include submit, approve, reject, hold, resume, reopen and owner sign-off, so an impairment is opened, held while mitigated, and signed off on restoration with names and times at each step. Scheduled reports with tenant branding produce the AHJ and insurer summaries on a cadence, and PDF generation and bulk export deliver the last year or the last five on request. Completed records pin the form configuration they were executed with, so a report renders as it was signed.

Technician qualifications, skills and training are held in intelliCREW and checked at assignment, which matters where the jurisdiction licenses sprinkler inspectors. Hot work permits, lockout and the safety records that accompany a preplanned impairment are held in intelliCOMPLY. Every create, update, approval and sign-off carries actor, tenant, request id, IP address and user agent and is linked into a SHA-256 hash chain per tenant that a verify routine can recompute for auditors, and audit events are never auto-deleted. Process facilities where fire protection sits beside process safety are described on the chemical page.

NFPA 25 asks a simple question of the owner: can you prove you checked. The record that answers it is the one that was built to be asked.