NFPA 10 (2026) Lets You Argue for Fewer Extinguisher Inspections

The 2026 edition of NFPA 10 adds a way to stop inspecting fire extinguishers every 30 days. It's in new Section 7.2.5, and most of the coverage has walked straight past it.

Here's the provision. A performance-based inspection program is permitted as an alternate means of compliance with 7.2.1 through 7.2.4, subject to the approval of the authority having jurisdiction (7.2.5.1) (NFPA 10 Second Draft Report).

And there's a ceiling. Section 7.2.5.5: "An inspection shall be performed in accordance with 7.2.1 at intervals not to exceed 90 days."

Read that carefully, because it points two directions at once. It sets a 90-day outer limit, but the inspection it requires is one performed "in accordance with 7.2.1" — and 7.2.1 in the same draft calls for inspection at intervals not exceeding 31 days, at least once per calendar month. Anyone planning around a quarterly cycle needs to resolve that cross-reference against the published standard and with their AHJ before committing. What is clear is that 7.2.5 is the mechanism by which inspection frequency becomes something you argue for rather than something fixed.

What you have to give up to get it

The frequency reduction isn't free, and the conditions are where this gets interesting.

AHJ approval (7.2.5.1). Same gatekeeper as every other alternative method in Chapter 7. Nothing here happens without a fire marshal saying yes.

Independent third-party evaluation of your data (7.2.5.3). Inspection program data has to be evaluated by an independent third party acceptable to the AHJ. Not your team, not your vendor — a third party the AHJ will accept.

A written technical justification, per site (7.2.5.4, 7.2.5.4.1). The standard is explicit that this isn't a portfolio-wide argument: "A technical justification shall be provided for each site." And under 7.2.5.4.1.1, a site with multiple buildings has to address the individual buildings and their environments — so a campus is not one argument either.

Review at least every three years (7.2.5.6). Inspection program data must be reviewed at intervals acceptable to the AHJ, "not to exceed three years," to verify the program still meets the goal established under 7.2.5.2. This is not a one-time approval you file and forget.

Re-review when things change (7.2.5.7). A change of hazard, occupancy or ownership triggers another review. In a portfolio with normal tenant turnover, that clock resets more often than the three-year one.

Read those together and the shape becomes clear. This isn't a relaxation. It's a trade: you may inspect less often if you can prove, per site, with data an independent party will vouch for, that less often is safe.

The requirement hiding inside that trade

Every one of those conditions is a documentation requirement.

You cannot build a technical justification for extending inspection intervals without inspection history. Not "we did the monthly walk-around" — actual data. How many extinguishers were found discharged, obstructed, missing, or depressurized, at which sites, over what period, and at what rate. A third-party evaluator assessing whether 90-day intervals are defensible at a specific building is going to ask what the failure rate at that building has been.

Most extinguisher inspection records cannot answer that question. A tag with a date and initials proves an inspection happened. It says nothing about what was found. Twelve years of tags and paper checklists filed by building is a compliance archive, not a dataset — and it will not survive contact with a third-party evaluator.

That is the real barrier to 7.2.5, and it's a higher one than the AHJ conversation. The contractors and owners who can act on this provision in 2026 will be the ones whose inspection records already capture outcomes per unit per site in a form somebody else can analyze. Everyone else needs to start recording that way now and come back in a couple of years with a history worth submitting.

What the coverage got wrong

Much of the reporting on the 2026 edition has framed it as the moment electronic monitoring became permissible. That is about twenty years off.

An amendment to NFPA 10 and NFPA 72 covering electronic monitoring "in lieu of mandatory physical 30-day inspections" took effect at the beginning of September 2006 (Electrical Contractor Magazine, September 15, 2006). The 2010 edition carried it — Minnesota's Department of Health, summarizing NFPA 10-2010 for licensed facilities, wrote that "as an alternate to the monthly visual inspection, electronic monitoring is allowed" (Minnesota Department of Health). By the 2018 edition it was framed as an explicit choice of inspection method for the owner or owner's agent (Koorsen), and the draft text carries that structure at 7.2.2.1, conditioned by 7.2.2.2: any method of inspection other than manual inspection requires the approval of the authority having jurisdiction.

So the notable thing about 7.2.5 isn't that technology is newly allowed. It's that the standard now describes a documented, reviewable procedure for changing how often you inspect — with the evidentiary burden spelled out.

Where to start

Confirm which edition of NFPA 10 your jurisdiction has actually adopted, because none of 7.2.5 is available to you until your jurisdiction adopts the 2026 edition into law.

Then look honestly at your inspection records and ask whether an independent evaluator could compute a per-site failure rate from them. If the answer is no, that's the project — and it's worth starting well before the code reaches you, because the justification 7.2.5 demands is built out of history you have to have already collected.

On sourcing. The section text quoted here comes from the NFPA 10 Second Draft Report rather than the published 2026 standard. Chapter 7 inspection frequency was actively contested during this cycle — a certified amending motion seeking quarterly inspections for hospitals was put to a floor vote at the June 2025 Technical Meeting and failed. Confirm the final language against the printed edition, and confirm what your jurisdiction has adopted, before building a program on it.

If your extinguisher records are tags and scanned checklists, they can prove an inspection happened but not what it found. Joyfill lets you build inspection forms that capture outcomes per unit per site, complete them in the field, and keep the data in one place you control.