In operational terms, NFPA 25 — the standard governing inspection, testing, and maintenance of water-based fire protection systems — says something most building operators have never heard stated plainly: your sprinkler system is not one compliance obligation. It’s seven of them, running on seven different clocks, simultaneously, forever. Weekly. Monthly. Quarterly. Semiannually. Annually. Every five years. And event-driven obligations that have no calendar at all.

The penalty for getting this wrong isn’t only the citation. A sprinkler system with a documented ITM gap is an insurer’s first stop after a loss event and a plaintiff attorney’s first exhibit after an injury — and NFPA’s own research gives the gap a face: in sprinkler systems that failed to operate when needed, the leading cause, at 61% of failures, was a closed valve. Not exotic equipment failure. A valve someone closed and nobody’s inspection caught — which is precisely what the weekly and monthly frequencies exist to catch.

What most operations believe covers them

The common model, described to us repeatedly in interviews: “Our fire vendor comes once a year, does the inspection, tags the system, leaves the report.” Sometimes there’s a quarterly contract. The belief is that the vendor’s visit is the compliance — and the belief has an understandable origin, because the annual inspection is the most visible, most formalized, and most invoiced event in the cycle.

But map that model against the standard and the gap is structural, not marginal. The annual visit covers the annual obligations. The weekly and monthly valve inspections — gauges on certain system types, control valve positions, the items that catch the 61% problem — belong to the owner, not the vendor, unless explicitly contracted otherwise. NFPA 25 is unambiguous about where responsibility sits: the property owner or designated representative holds the ITM obligation. The vendor performs tasks; the owner owns the program. Most operations have a vendor. Far fewer have a program.

NFPA 25 is unambiguous about where responsibility sits: the property owner or designated representative holds the ITM obligation. The vendor performs tasks; the owner owns the program.

What the standard actually requires

Walk the seven clocks. Each clock generates documentation requirements: what was inspected, by whom, when, with what findings, and what was corrected. An inspector reviewing your program isn’t asking whether the system works today. They’re asking whether seven parallel documentation streams exist and are current — and a missing weekly log is a finding even if every valve is open.

Frequency NFPA 25 ITM Requirements
Weekly Control valve inspections on systems without electronic supervision — verifying valves are open, accessible, sealed, or locked.
Monthly Gauge inspections on wet systems, valve checks where supervision allows the longer interval.
Quarterly Alarm device tests, water flow alarm tests, pressure gauge inspections on dry systems.
Semiannually Vane and pressure-switch type waterflow device tests, valve supervisory signal testing.
Annually The main event — full system inspection, main drain test, antifreeze solution testing, fire pump flow test where applicable.
Five-Year Internal pipe inspections, gauge replacement or recalibration, obstruction investigations where conditions indicate.
Event-Driven After any system activation, repair, or modification — obligations with no date until the day they suddenly exist.

The three things an inspector checks first

The pattern reported by people who’ve sat through fire inspections is consistent.

CHECK 1 The Valves Themselves

Position, accessibility, and supervision are verified immediately because the 61% failure statistic is as familiar to inspectors as to owners.

CHECK 2 Documentation Trail

High-frequency items are scrutinized. Annual vendor reports are usually present; weekly valve logs usually aren’t, representing instant findings.

CHECK 3 Prior Corrections

Inspectors check if prior deficiencies were resolved. Unaddressed findings convert this year’s conversation into something much harsher.

The gap technology closes

Seven concurrent frequencies across one system — multiplied by every system across every site — is not a memory problem any human should be assigned. It’s a calendar-generation problem, and it’s mechanical: a compliance engine that knows the NFPA 25 frequency table creates each work order before its due date, routes owner-level items to staff and vendor-level items to qualified contractors, requires completion evidence at the point of work, and flags the misses as named exceptions instead of silent gaps.

The documentation streams assemble as a byproduct of execution — which is the entire difference between a schedule and a verified program, and the reason Sweven FM ships NFPA frequencies as templates rather than asking operators to rebuild the standard from scratch. A serious facility management compliance program doesn’t track sprinklers as one line item, because the standard never did.

The Readiness Audit

So return to the question in the title, now with the full table in view: of the seven clocks NFPA 25 runs on your system, how many is your operation tracking with documentation an inspector would accept — and who, by name, owns the weekly one?

Sources: