Fire door inspection is one of the more commonly overlooked recurring compliance requirements in commercial buildings, partly because it doesn’t look urgent day to day — a fire door usually still closes and looks fine right up until the moment it’s actually needed and doesn’t perform correctly. How often the code actually requires it, though, depends on which code applies, and getting that number wrong in either direction is a real issue: less often than required is a genuine compliance gap that can go unnoticed for years, and promising a frequency that doesn’t match the applicable code sets an expectation nobody’s actually bound to hit — which is its own problem when an authority having jurisdiction asks for records.
In the US, NFPA 80 sets the standard for fire door assemblies and requires a documented inspection at least annually, along with an ongoing active-maintenance obligation between inspections — a door that’s been quietly propped open or modified doesn’t get to wait for the next annual check to become a problem. The active-maintenance piece is easy to overlook next to the annual inspection requirement, but it’s arguably the more important half of the obligation in practice: it means a facilities team is expected to notice and correct issues as they arise — a closer that’s stopped working, a wedge left under a door — rather than treating the annual inspection as the only checkpoint that matters.
In Ontario, the equivalent obligation is codified under O. Reg. 213/07, and set at a materially higher frequency: Article 2.2.3.4(4) requires monthly fire door inspection, with Article 2.2.3.2 covering the broader active maintenance requirement the inspection sits inside. A building operating under Ontario Fire Code and only inspecting annually — even diligently, even with a genuinely thorough annual check — is not meeting the actual requirement, and “we do it once a year like NFPA 80” is not a defense if the applicable jurisdiction is Ontario. This is a case where a US-style compliance instinct, applied without checking the local code, actively creates a gap rather than closing one.
Why the two jurisdictions land in such different places is worth understanding rather than just memorizing. Ontario’s higher frequency requirement reflects a regulatory approach that treats fire door integrity as something that degrades faster than an annual cycle can catch — door hardware in active commercial use, especially in high-traffic buildings, can develop an issue well within twelve months, and a monthly check catches that drift long before it becomes a full failure. NFPA 80’s annual baseline, paired with its active-maintenance obligation, is built on the assumption that ongoing observation between inspections handles the drift a monthly formal check would otherwise catch — two different structures aiming at a similar outcome by different mechanisms.
What a real inspection actually checks, in either jurisdiction, is more specific than a glance at the door: that the door closes and latches fully without manual assistance, that hardware — closers, hinges, latching mechanisms — is functioning and undamaged, that there’s no unauthorized hardware installed that would compromise the door’s rating (a common and easy-to-miss issue — a coat hook, a kick-down doorstop, a lock that wasn’t part of the original rated assembly), and that gaps and clearances around the door remain within tolerance. A door that’s been quietly propped open with a wedge for months, or has had a coat hook screwed into it by someone who had no idea it was a rated assembly, has been non-compliant that entire time even though nothing looked obviously wrong to anyone walking past it.
The gap this closes is documentation, not just the physical check. A photo-verified inspection record for every door, on the schedule the applicable code actually requires, is what turns “we check our doors” into something that holds up if it’s ever asked for — by an authority having jurisdiction, an insurer following a claim, or a tenant improvement inspection triggered by a lease change. Without that record, even a building that’s fully compliant in practice has no way to demonstrate it, which functionally puts it in the same position as a building that isn’t compliant at all. Fire door inspection and compliance covers what that documented process looks like in practice, including how the inspection frequency is matched to whichever code actually applies to a given building.
For buildings addressing fire doors alongside other small facility items, a fire door check can also be scheduled as part of a bundled site visit rather than as a standalone call — a practical fit for facilities managing this recurring requirement alongside routine punch-list items, since it’s often the same buyer coordinating both.
A question that comes up often for facility teams managing buildings in more than one jurisdiction: which schedule applies if a portfolio spans both the US and Ontario? The answer is straightforward but easy to get wrong by defaulting to whichever code a facility team is more familiar with — the applicable code is determined by the building’s actual jurisdiction, not by a company-wide policy chosen for convenience. A facility manager overseeing buildings in both Charlotte and the Greater Toronto Area, for instance, is genuinely managing two different inspection frequencies for functionally similar equipment, and treating them as interchangeable is exactly how a building ends up out of compliance with its own applicable code.
That’s also a reason a single point of accountability across a multi-jurisdiction portfolio is worth more than it might initially seem. Rather than each building’s facility team independently tracking which code applies and when the next inspection is due, a centralized inspection schedule that’s already mapped to the correct code per building removes the risk of a jurisdiction mix-up entirely — the monthly Ontario doors get inspected monthly, the annual US doors get inspected annually, and nobody has to remember which rule applies to which building on top of everything else they’re managing.