← All guides

CAN/ULC-S536: Inspection and Testing of Fire Alarm Systems

What the standard covers, how often systems get tested, who can do the work, and why the paperwork matters as much as the testing.

What S536 is for

CAN/ULC-S536 is the Canadian standard that defines how existing fire alarm systems are periodically inspected and tested to confirm they still work. A fire alarm system is only useful if it functions on the day of the fire, and components degrade: batteries lose capacity, smoke detectors drift out of sensitivity, wiring gets damaged during renovations, and devices get painted over or blocked. S536 exists to catch those problems on a schedule, before they matter.

The standard sets out which components must be checked, what each check involves, how often it happens, and how the results are recorded. It applies to systems that are already installed and in service — which is the key distinction from its sibling standard, S537.

S536 vs. S537: recurring testing vs. one-time verification

This is the most common point of confusion for people new to the ULC fire alarm standards, so it is worth being precise:

A simple way to remember it: S537 happens once (per installation or modification), S536 happens forever after. If a building owner asks "when was the system verified?" they mean S537; if they ask "when was the last annual?" they mean S536. The two reports look superficially similar but serve completely different legal and technical purposes, and one cannot substitute for the other.

Inspection frequencies: daily, monthly, annual

S536 structures its requirements around time intervals. The exact tasks at each interval are detailed in the standard itself, but the general framework works like this:

Daily checks

These are quick visual checks, typically done by building staff rather than a technician. The idea is to confirm the control unit shows normal status — no trouble signals, no alarm conditions, AC power present. It takes seconds, and it is the earliest possible warning that something has gone wrong with the system since yesterday.

Monthly checks

Monthly tasks go a step further. They typically involve operating selected components to confirm basic function — for example, initiating an alarm condition from a device and confirming the system responds, checking standby battery condition, and confirming annunciator and trouble indications behave correctly. Monthly testing is also commonly the interval at which voice communication features and connections to monitoring stations get a routine exercise.

Annual inspection and test

The annual is the big one, and it is what most people mean when they talk about "S536 testing." Over the course of the annual, essentially every component of the system gets individually inspected and functionally tested: every initiating device (smoke detectors, heat detectors, manual stations), every audible and visual signalling device, the control unit and its circuits, annunciators, batteries under load, and ancillary functions such as fan shutdown, door release, and elevator recall connections. Smoke detector sensitivity is confirmed to be within the acceptable range. The annual is a device-by-device exercise — not a sampling exercise — which is why it can take days in a large building.

What gets inspected and tested

Across the intervals, the scope of S536 covers the whole system, not just the panel:

Documentation and records

S536 is as much a documentation standard as a testing standard. Every inspection produces a report identifying the building, the system, the devices tested, the results, and any deficiencies found. The technician signs it; the building owner keeps it.

Record retention matters for two reasons. First, fire inspectors routinely ask to see the testing records — a missing annual report is treated much the same as a missed annual. Second, the records are the building owner's evidence of due diligence. After a fire, the question "was the alarm system maintained?" is answered with paper. Owners and property managers should keep current reports on site and retain historical reports; deficiencies noted in a report should have a documented trail showing they were corrected.

The Ontario Fire Code connection

An important structural point: S536 itself is not law. It is a standard that becomes mandatory when a regulation references it. In Ontario, the Ontario Fire Code is the regulation that requires fire alarm systems in existing buildings to be inspected and tested — and it points to CAN/ULC-S536 as the procedure for doing so. The same pattern holds in other provinces and territories through their fire codes, most of which adopt the National Fire Code model with local amendments.

So the division of labour is: the fire code says you must test and how often the obligation applies, and S536 says how the testing is performed. When a fire inspector writes up a building for fire alarm maintenance, the legal authority is the fire code; the technical content of compliance is S536. The obligation falls on the building owner, even though the work is done by a contractor.

Who can perform S536 inspections?

Qualification requirements vary by province, and this trips people up. In Ontario, fire alarm inspection and testing is generally performed by technicians registered under the CFAA (Canadian Fire Alarm Association) program or equivalently qualified persons, and many other jurisdictions and AHJs (authorities having jurisdiction) expect the same. Some provinces have their own licensing regimes. Daily checks can usually be done by trained building staff, but the monthly and especially the annual work is expected to be done by someone with demonstrated competence on fire alarm systems — and the AHJ ultimately decides what qualifications it will accept.

Building owners hiring a contractor should ask directly: who will perform the work, what are their qualifications, and will the report be in the format the local fire department expects?

Common questions

Is an S536 annual the same as a verification?

No. A verification (S537) is a one-time acceptance of a new or modified installation. The annual (S536) is recurring maintenance testing. If you modify the system — add devices, replace the panel, rezone — you need a verification of the affected work, and your annual cycle continues separately.

Does every single device really get tested every year?

For the annual, yes — the expectation is device-by-device functional testing, not a sample. This is why annual inspections in large buildings are scheduled over multiple days and coordinated floor by floor.

Who is legally responsible if testing is missed — the owner or the contractor?

The building owner. Fire codes place the maintenance obligation on the owner. Hiring a contractor delegates the work, not the responsibility, which is why owners should track due dates themselves rather than relying on the contractor's reminder.

What happens if the annual finds deficiencies?

They get documented on the report, and the owner is expected to have them corrected promptly. A report listing uncorrected deficiencies, repeated year after year, is a red flag to any fire inspector — and strong evidence of negligence if something goes wrong.

What are the consequences of skipping inspections?

Practically: undetected system failures. Legally: fire code violations, orders, and fines, and in serious cases prosecution of the owner or property manager. Financially: insurers can deny or reduce claims where required maintenance was not performed. The cost of an annual inspection is trivial against any one of those outcomes.

Have a specific question about this standard? Ask Codebook Carl — answers are sourced directly from the code books with exact clause citations.