Your Sprinkler System's Test Schedule Isn't Set by Your Company. It's Set by Whoever Has Jurisdiction Over That Building.

A corporate EHS lead building a fire protection compliance calendar for a twelve-site portfolio runs into a problem that doesn't show up in the regulation itself: 29 CFR 1910.160 requires that fixed extinguishing systems be inspected, maintained, and tested periodically to ensure they will operate as intended, but it does not say how often. The actual intervals — monthly, quarterly, annual, five-year internal inspections — come from the NFPA code that governs the specific system type, and which edition of that code applies, and how strictly it's enforced, depends on which local fire authority has adopted it for that building. Two sites running the same wet-pipe sprinkler system, in two different states, can legitimately be on two different testing calendars, and both can be correct.

This isn't a compliance gap so much as a structural feature of how fire protection is regulated in the United States. OSHA sets the baseline obligation that the system has to work and has to be verified to work. The specifics of how often and by whom largely come from NFPA 25 for water-based systems, NFPA 96 for commercial kitchen suppression, and NFPA 72 for the detection and alarm components tied to them — and all three are model codes that only bind a given site once the local authority having jurisdiction has adopted them, sometimes with amendments. A corporate calendar built around "test everything annually" will be right at some sites, in violation of a stricter local requirement at others, and paying for testing more often than required at a few more.

The System Inventory Problem Comes First

Before a portfolio can build a defensible testing schedule, it needs an accurate inventory of what fire suppression equipment actually exists at each site — and this is where a lot of multi-site programs are already behind before scheduling ever becomes the issue. A distribution center might have wet-pipe sprinklers throughout the warehouse floor, a dry-pipe system in an unheated dock area, and a clean-agent system protecting a server room, each governed by a different NFPA standard with a different testing cadence. A restaurant or food-service site adds a kitchen hood suppression system under NFPA 96, which has its own semiannual service requirement independent of the sprinkler schedule entirely. If the corporate asset list only captures "fire suppression: yes," it has captured the presence of a system without capturing the three or four different clocks running underneath that one line item.

Sites that have gone through renovations or tenant improvements are a particular risk here, because a system added mid-lease by a contractor doesn't always make its way back into a corporate asset register. A clean-agent system installed for a new server closet, or a pre-action system added for a sensitive storage area, can exist entirely on the local facilities team's radar and nowhere on the compliance calendar that corporate is tracking against.

Local Adoption Changes What "Compliant" Means

NFPA 25 itself has gone through multiple editions, and the interval it specifies for a five-year internal pipe inspection or a fire pump annual flow test has shifted somewhat between them. Which edition applies to a given site depends on what that jurisdiction adopted into its fire code and when — a site in a jurisdiction that adopted the 2020 edition is not necessarily on the same requirement as a site in a jurisdiction still running an earlier one, and a corporate standard that assumes a single national interval is not accounting for that variation. This is compounded by insurance carriers, who frequently impose their own testing frequency as a condition of coverage, sometimes stricter than what the locally adopted code requires. A site can be fully compliant with its fire code and still be out of compliance with its own insurance policy if the two intervals were never reconciled.

The practical consequence is that "our testing standard is NFPA 25" is not a complete answer to the question of what a given site owes. The complete answer requires knowing which edition that site's jurisdiction has adopted, what amendments (if any) that jurisdiction layered on top of the base code, and what the site's property insurer separately requires — three inputs that can each change independently, and none of which show up automatically in a document that just says "sprinklered."

Who Signs the Inspection Report Matters More at Scale

1910.160(b)(2) places the maintenance and testing obligation on the employer, but the actual inspections are typically performed by third-party fire protection contractors, and a multi-site portfolio can easily be running a dozen different local vendors with no shared reporting format. A single-site business can keep the inspection tags on the riser and call it documentation. A portfolio needs those inspection results rolled up somewhere corporate can see them, in a format consistent enough that a missed test at one site doesn't get lost in a stack of paper certificates that only the site manager ever looks at.

This is where the gap tends to open in practice: a contractor completes an inspection, tags the system, and leaves a paper report with the site. Unless there's a standing requirement for that report to be logged centrally — not just filed locally — corporate's visibility into "is every system currently within its testing window" depends entirely on each site remembering to report a negative as diligently as it would report a positive. A missed test is, by definition, something nobody generated paperwork for, which makes it the hardest gap for a rollup process to catch unless the rollup is checking for the absence of an expected report, not just reviewing the reports that arrive.

Impairments Need Their Own Tracking Layer

A system that's out of service — a sprinkler main shut down for a plumbing repair, a kitchen hood suppression system awaiting a replacement part — creates a fire watch obligation and a restoration deadline that operates on a completely different timeline than the routine testing schedule. NFPA 25 and most locally adopted fire codes require an impaired system to be either restored within a defined window or covered by a documented fire watch in the interim, and this is a category of risk that a testing calendar built around routine intervals won't surface on its own, because an impairment is by definition an unplanned event. A portfolio-level program needs a separate mechanism for a site to report "the system is down right now" and for that report to trigger a fire watch conversation immediately, not wait for the next scheduled compliance review to notice the gap.

What a Portfolio-Level Program Actually Tracks

The unit of compliance here isn't the company and it isn't even the site — it's the individual system, because a single building can host several systems on different NFPA standards, different locally adopted editions, and different insurer requirements, each with its own next-due date. A corporate fire protection program that can name, for every system at every site, which code and edition governs it, what interval that produces, who last tested it, and when the next test is due, has a genuinely defensible answer to an inspector or an insurer. A program that can only say "we require annual fire protection testing company-wide" is describing an intention, not tracking the actual obligation, and the two are not the same thing once a portfolio crosses a handful of jurisdictions.