Ontario's fire alarm inspection requirements changed on 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 editions shops may have used for two decades. An AHJ may ask your report to show which edition you followed.
Confirm the adopted edition with the AHJ before the job.
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. The way a panel gets verified at commissioning now maps onto how it's inspected every year after.
S536-19 requires standardized forms
In the 2004 edition, report forms lived in the appendix as a suggested format, so you could use your own layout. Under CAN/ULC-S536-19, 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. A form missing required fields or using the wrong structure leaves the documentation incomplete even when the field work is correct.
If your crew keeps device readings in free-text notes on a homegrown Excel sheet or a PDF built in 2015, move those records into the standardized report.
Record the battery load-test values
S536-19 calls for a battery load test with measured values recorded on the report. A voltage check and “Battery: OK” don't supply that record. Write down the actual numbers every time, while you're at the equipment.
Monthly inspection records
S536-19 also expects monthly inspection records on the current forms, so the documentation needs to stay consistent throughout the year. Replace outdated monthly forms when you update the annual report template.
A rejected report can mean a re-inspection and a second truck roll. You'll also have an owner waiting for answers about the building's fire alarm paperwork. A handful of returned reports each month takes labor hours away from scheduled work and can put service renewals at risk.
An insurer or property manager may ask for those records when reviewing coverage or renewal. Missing paperwork could surface during an audit months after the inspection. On a fifty-building book, even a few requests for missing records can leave the office calling crews to reconstruct inspections they finished weeks ago.
S537-19: verification of new or altered systems
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. O. Reg. 87/25 moved both standards to their 2019 editions at once. For a system you commission or modify in Ontario, verification has to meet S537-19 before it goes into service; subsequent inspections follow S536-19. Submitting an inspection report for work that requires verification puts the paperwork in front of the AHJ under the wrong standard.
S536:2024 and Ontario's 2019 edition requirement
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). It adds data communication link testing. The Fire Code's referenced edition determines the requirement. O. Reg. 87/25 references the 2019 editions, making S536-19 and S537-19 Ontario's baseline. The 2024 edition 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. Acceptance is at the AHJ's discretion; the regulation names the 2019 editions.
ULC writes the standards; the National Fire Code of Canada references them as a model code. Each province decides what to adopt and when. British Columbia has required S536-19 since March 2024, while Ontario's date is January 1, 2026.
Newer equipment, explicit requirements
Under the 2019 edition, carbon monoxide detection tied to the fire alarm has its own requirements. Wireless devices are addressed directly, and air-sampling detectors have provisions that reflect how those systems are tested. A form designed around conventional devices may be missing fields for wireless equipment your crew already services.
A Friday-afternoon annual
Say your two-tech crew is finishing a mid-rise annual at 3:30 on a Friday. They've tested the devices. Their legacy form marks the batteries “good” and lists a couple of deficiencies. Under S536-19, the report needs individual device records, battery load values, attendance, deficiencies tracked to closure and owner sign-off on the standardized report. The office can transfer the notes into the current form, but “good” gives it no load-test values to enter. Someone has to call the crew for the readings. If no one recorded them, copying the notes onto a new form won't recover them. The office also has to pull both technicians' names from the job record and transfer the deficiency notes into the new report. Reconciliation could take an extra hour, and a missing required field could still send the report back from the AHJ.
S536-19 paperwork needs time on site
Allow time for documentation before the crew leaves, with one technician responsible for reviewing the report. A blank device entry gives the office no way to tell whether the test was missed or the result went unrecorded. Resolve it while the crew is still on site.
Essential builds the S536-19 report into the technician's mobile inspection app, so techs can capture the required fields on site in the report's structure. The crew can review missing entries while it's still at the building, reducing the office's work transferring field notes into a report.
Before your next inspection
Get AHJ acceptance before switching to a 2024-edition report. If your office keeps piecing together field notes, book a 30-minute demo to see Essential generate a complete S536-19 report from a live inspection. Bring the form your crew uses and compare its fields with the report generated during the demo.
