If you inspect fire alarm systems in Ontario, the standard you're graded against changed in 2026. Effective January 1, 2026, the Ontario Fire Code (O. Reg. 213/07), as amended by O. Reg. 87/25 requires annual inspections to follow CAN/ULC-S536-19, and verifications on new or altered systems to follow CAN/ULC-S537-19. That replaces the previous editions most buildings had been inspected under for two decades. AHJs are already asking for reports that prove you used the current standard.
Here's what actually changed, and where crews are getting tripped up.
Three standards, rewritten together
Installation (S524), inspection and testing (S536), and verification (S537) used to drift out of sync. The 2019 editions were developed concurrently and harmonized, so the requirements line up across the whole life of a system. In practice, the way a panel gets verified at commissioning now maps onto how it's inspected every year after, with fewer seams for an AHJ to pick at.
Standardized forms aren't “suggested” anymore
This is the change that catches the most crews off guard. In the 2004 edition, the report forms lived in the appendix as a suggested format, so you could use your own layout. Under CAN/ULC-S536-19, the standardized documentation is required. Inspections now expect device-level reporting, technician attendance logs, full deficiency tracking, and owner sign-off, all captured on the standardized report. If your form doesn't carry the fields the standard calls for, in the structure it calls for, you have a compliance gap no matter how clean the field work was.
For a shop still running a homegrown Excel sheet or a PDF it built in 2015, that is a real problem.
The battery test grew teeth
The old check-the-voltage-and-move-on approach is done. S536-19 calls for a battery load test with the measured values written on the report. “Battery: OK” doesn't satisfy it. You record the actual numbers, every time. Small change on paper. It quietly rewrites what a defensible report looks like.
Monthly logs count too
It's easy to read this as an annual-inspection problem. It isn't only that. The standard also expects monthly inspection records on the current forms, so the documentation trail has to stay consistent all year, not just at the annual.
The cost of getting it wrong isn't abstract. A report an AHJ won't accept means a re-inspection, a second truck roll, and an owner asking why the building's fire alarm paperwork is out of compliance. Across a portfolio of buildings, a handful of bounced reports a month adds up fast, in labour hours and in the trust that keeps a service contract renewing.
Insurers and property managers increasingly ask to see that documentation trail as a condition of coverage or renewal, so a gap in the paperwork can surface months later as a failed audit rather than a same-day fix. On a fifty-building book, that is not a rounding error.
S537-19: verification isn't the same as inspection
Worth being precise here, because these terms get used loosely on the truck. Verification (S537) is the one-time confirmation that a new or altered system was installed and works as designed. Inspection and testing (S536) is the recurring annual and monthly work that follows. The same O. Reg. 87/25 moved both standards to their 2019 editions at once, so if you commission or modify a system in Ontario now, the verification has to meet S537-19 before the system goes into service, and every inspection after that follows S536-19. Mixing up which standard governs which task is an easy way to hand an AHJ a reason to reject the paperwork.
Seeing S536:2024 mentioned? Ontario still grades on the 2019 edition
ULC published CAN/ULC-S536:2024, a revision of the 2019 sixth edition, in August 2024, while S537 remains at its 2019 edition (CAN/ULC-S537-19). Its headline addition is data communication link testing. The edition an AHJ grades against is the one the Fire Code references, and O. Reg. 87/25 references the 2019 editions, so S536-19 and S537-19 are the baseline requirement in Ontario. Can you inspect to the 2024 edition instead? Often, yes: it covers everything the 2019 edition requires and adds to it, so many AHJs will take a 2024-edition report as meeting or exceeding the requirement. But that's the AHJ's discretion, not a right; the regulation names the 2019 editions. Confirm before you standardize your templates on 2024.
The pattern behind this is worth thirty seconds. ULC writes the standards. The National Fire Code of Canada references them as a model code. Each province then decides what to adopt and when, which is why British Columbia has required S536-19 since March 2024 while Ontario's date is January 1, 2026. Same standard, different provincial clocks.
Newer equipment, explicit requirements
The 2019 edition also caught up to what's actually on the wall now. Carbon monoxide detection tied to the fire alarm has its own requirements. Wireless devices are addressed directly, rather than being wedged into conventional-device language. Air-sampling detectors get provisions that reflect how those systems really get tested. If you service newer buildings, you're already touching this equipment, and the paperwork now has to account for it. Confirm the specific device clauses in your own copy of the standard before you rebuild a report template around them, because the device sections are where legacy templates most often fall short.
A real example: the Friday-afternoon annual
Picture a two-tech annual on a mid-rise at 3:30 on a Friday. Under the old process, the crew tests devices, jots the batteries down as “good,” notes a couple of deficiencies on a legacy form, and heads out. Under S536-19, that same job needs each device logged individually, the battery load values recorded, attendance logged, deficiencies tracked to closure, and all of it on the standardized report with owner sign-off. Done on paper or a legacy template, that's an extra hour of reconciliation back at the office, plus a real chance a required field gets missed and the report bounces back from the AHJ.
Where this actually bites: the paperwork, not the field work
Most fire alarm techs already know how to test a system correctly. The gap is documentation, and S536-19 widened it. Device-level records, recorded battery values, deficiency tracking, monthly logs, owner sign-off. That's administrative surface area, and it's exactly where a rushed report goes sideways.
Which is the part worth automating. Essential builds the S536-19 report into the technician's mobile inspection app, so the required fields get captured on site, in the right structure. No rebuilding forms in the truck, no discovering a missing field when the AHJ calls.
Before your next inspection
Getting the field work right was never the hard part. Proving it, on the current standard, every time, is where shops quietly lose hours. If that's where your team is stuck, book a 15-minute walkthrough and watch Essential generate a complete S536-19 report from a live inspection.
