"The fire department hasn't come by" is not the same thing as "the building is compliant," and it is the single most common misreading of Ontario's Fire Code. The plan and the testing log are the actual evidence — and a manager who can produce both on request is in a materially different position than one who is relying on the absence of a complaint.
Key takeaways
Two documents do most of the work in a fire-safety file: the fire safety plan itself, and the testing and maintenance log for the systems the plan describes. The first is a planning document approved once and updated as the building changes. The second is a living record that only has value if it is actually current — a plan on file from five years ago, describing a fire alarm panel the building no longer has, is close to useless in an actual inspection.
Ontario's Fire Code requires a fire safety plan for buildings that fall under specific occupancy classes, and for any building the Ontario Building Code requires to have a fire alarm system — which in practice covers most multi-unit residential buildings above a modest size. The Office of the Fire Marshal publishes technical guidelines that walk owners and managers through building one for their occupancy type — industrial, institutional, and others each have their own guideline — and where the Fire Code or the local fire department requires a plan, "a copy of the plan must be submitted to the Chief Fire Official for approval and be retained on site in an approved location." That last detail is easy to miss: an approved plan that only exists in a property manager's head office, and not physically on site where a responding crew or an inspector can find it, does not satisfy the requirement.
Ontario's own guidance page confirms directly that "municipal fire departments enforce the Fire Code," not a provincial inspector working independently of the local department. The statutory authority for that inspection comes from ss. 21(1) and 21(2) of the Fire Protection and Prevention Act, which give a fire department inspector the power to inspect land or premises to assess fire safety. Because enforcement is municipal, the practical cadence of inspections varies by jurisdiction — a building in a busy urban department may see more frequent proactive inspections than one in a smaller municipality that inspects mainly on complaint. Neither situation changes what the Fire Code itself requires; it changes only how likely a gap is to be caught before it matters.
Ontario's Fire Code incorporates testing and maintenance requirements by reference to standards that are not freely published, so a single universal number for "how often to test a fire alarm" is not something a manager can pull from a public government page. CCOHS's own fire protection guidance, a federal occupational-safety body, gives usable general guidance for building a testing cadence: "test periodically (monthly) or as required according to your jurisdiction," inspect portable fire extinguishers monthly, and conduct fire drills "at least twice a year (or as required by local jurisdiction)." The consistent qualifier — "as required by your jurisdiction" — is the honest answer: use CCOHS's cadence as a sound floor for a testing schedule, and confirm the specific interval that applies with the local fire department or a licensed fire protection contractor, since the Fire Code's incorporated standards can set a stricter number for a specific system.
A 1980s-built rental building has not had a proactive fire department inspection in the eleven years its current manager has worked there. The board treats that gap as evidence the building is fine. Treadstone Law's guidance on fire code compliance makes the actual risk explicit: municipalities "actively identify and pursue retrofit compliance in older multi-unit stock," and "the absence of a complaint or inspection to date doesn't mean the building meets current requirements." If that building is then sold, or an inspection is finally triggered by a resident complaint, a retrofit order for requirements that changed since the building was constructed — interconnected alarms, secondary egress, sprinkler coverage for certain configurations — can surface all at once, as a capital cost nobody budgeted for because nobody had confirmed compliance in eleven years.
A fire safety plan describes what the building's systems are supposed to do. A testing log is the separate proof that they were actually checked, and it is the document a fire inspector or an insurer's underwriter asks for first, because it answers a narrower and more immediate question than the plan does: is the equipment working right now. Ontario's Fire Code does not publish a free, specific record-content checklist the way some other regulators do, but a defensible log — consistent with the general safety-body practice CCOHS describes — records the date of each test, which system or device was tested, who performed it, the result, and what corrective action followed a failed test with the date it was closed out. A log with gaps, or one that only shows passes and never shows a failure being corrected, reads to an inspector as a log that was filled in after the fact rather than kept in real time.
A building's insurer typically wants confirmation that fire protection systems are maintained and tested on a defensible schedule before renewing coverage at a favourable rate, and a gap in the testing log is one of the more common reasons a renewal gets delayed while the insurer asks follow-up questions. Keeping the fire safety plan and the testing log current is therefore not purely a fire-department relationship — it is also evidence a manager can hand directly to a broker at renewal time, rather than reconstructing a year's worth of testing history under time pressure while a policy is about to lapse.
A current fire safety plan and testing log sit next to the same records a status certificate or an incident report pulls from during a claim, and the same emergency-management-plan discipline applies whether the emergency is a fire or something else entirely covered under elevator and lift device records. None of it replaces confirming the applicable standard with the local fire department directly.
Buildings that fall under specific Fire Code occupancy classes, and any building the Ontario Building Code requires to have a fire alarm system, need one. That covers most multi-unit residential buildings above a modest size.
The local Chief Fire Official, where the Fire Code or the fire department requires submission. The approved plan must then be retained on site in an approved location, not only at a head office.
Municipal fire departments, under ss. 21(1) and 21(2) of the Fire Protection and Prevention Act — not a separate provincial inspection body.
There is no single published number on a free government page. CCOHS's general guidance supports monthly testing or as required by the jurisdiction, but the Fire Code's own incorporated standards can require more; confirm with the local fire department or a licensed contractor.
Not necessarily. An uninspected building can still be behind current requirements, and municipalities are actively pursuing retrofit compliance in older multi-unit stock.
The order sets out what must be brought up to current requirements, on a compliance timeline set by the fire department. Costs can be significant if the building has gone years without confirming its own compliance status.
A 30-minute call is enough to tell you whether AI pays for itself here.
