Fire alarm monitoring in Canada: what CAN/ULC-S561 requires and when you need it

Last updated: September 2026

Quick answer

• Monitoring means transmitting alarm, supervisory and trouble signals from the control unit to an off site receiving centre obliged to act on each one. A bell ringing in an empty building is not monitoring.
• In Ontario the Building Code decides whether you need it: Article 3.2.4.7, Signals to Fire Department, whose Sentence (4) says the notification has to conform to CAN/ULC-S561. The 2024 edition names S561 and nothing else, not the municipal fire alarm system older editions allowed.
• The Fire Code carries the duty afterwards. Article 6.3.1.2 makes the owner keep the monitoring running and hold written proof from the central station that the service complies.
• S561 covers the installation and the service, S559 the equipment. A vendor quoting one at you is not evidence of the other.
• Listed is a status, not a compliment: a listed centre has been investigated against the standard and published in a certification body's listings.
• The only proof monitoring works is a signal received and logged at the centre. The panel's own history proves it tried.

What monitoring actually means

Three classes of signal leave a Canadian fire alarm control unit, and a receiving centre exists to treat them differently. An alarm says there is a fire condition. A supervisory says something meant to keep a fire protection system ready has moved out of position, a closed sprinkler valve being the classic case. A trouble says the fire alarm system itself is hurt: open circuit, ground fault, lost battery, lost AC. What generates each is broken down in alarm, supervisory and trouble signals.

It is not only the panel. UL Solutions in Canada describes its Protective Signalling Systems programme as covering fire alarm and sprinkler monitoring, to CAN/ULC-S561:2020 with equipment meeting CAN/ULC-S559:2020, so the flow switches and valve supervisories land at the same centre as the pull stations.

When Ontario actually requires it

Size and storeys do not decide this. Occupancy, staging and sprinklers do. We read Article 3.2.4.7 in the free 2024 Building Code Compendium from the Ministry of Municipal Affairs and Housing, updated to 16 January 2025. The three triggering sentences, in plain terms:

Sentence (2) catches most buildings: once a building is sprinklered and the waterflow switches are on the fire alarm system, monitoring is required whatever the occupancy. Sentence (3) catches most residential high rises, because a two-stage system has to send the alert stage off site. If you are unsure which staging you have, see single-stage versus two-stage.

Two cautions. Sentence (1) as we read it lists only Group A over 300 and retirement homes, where earlier Ontario editions also named Group B, Group F Division 1, buildings within Subsection 3.2.6 and buildings with interconnected floor space. We could not see those clauses in the 2024 text and will not print them as though we had, so check Sentence (1) against your own copy. The article number also moves: 3.2.4.7 in 2006, 3.2.4.8 in 2012, 3.2.4.7 again in 2024. Standards editions drift the same way, hence our edition tracker.

The Fire Code obligation, which is the one that gets enforced

The Building Code speaks at construction. The Fire Code speaks every day afterwards, and it is the Fire Code the inspector arrives holding, a distinction we pulled apart in Building Code versus Fire Code.

Fire Code Article 6.3.1.2 is the monitoring article, and it does four things. Where either Code required monitoring, the owner must ensure it continues. Where a central station provides it, the owner must obtain written documentation that the service complies with the named standard. The operator must provide that attestation on request from the owner or the Chief Fire Official, and is responsible for maintaining the service and its equipment to that standard.

Article 6.3.1.2 was read on 5 September 2026 in the official e-Laws consolidation of O. Reg. 213/07, consolidation period beginning 1 January 2026, e-Laws currency date 2 September 2026, last amended by O. Reg. 303/25. The article number and the four duties are confirmed, not inferred from a reproduction. One detail is worth flagging, because it surprises people: Sentence (2) names two acceptable standards, CAN/ULC-S561 and the American NFPA 71, and the owner needs written documentation that the central station complies with one of them. Sentence (5) then requires a proprietary signalling system to be maintained in accordance with NFPA 72. That is the Ontario Code's own drafting, not ours, and NFPA 71 has long since been withdrawn by the NFPA while remaining a live option in Ontario regulation. S561 is the only standard the Building Code names.

Article 6.3.2.2 we did read, in a government hosted copy of O. Reg. 213/07. It requires annual inspection and testing to CAN/ULC-S536, and requires the record for a monitored system to state whether the signals were received at the monitoring station. That is why a technician cannot close an annual without phoning the centre.

Existing buildings have their own hook: retrofit Section 9.7, covering care occupancies and retirement homes, requires provision for notifying the fire department and treats S561 compliant monitoring as satisfying it. Same consolidation, so verify it.

S561 and S559: which standard does what

These get quoted at owners interchangeably, usually by someone selling a service, and they do different jobs.

The automation software the operators actually watch has a third standard, CAN/ULC-S1981:2020. All are paywalled, so nothing here reproduces their text and the entries for CAN/ULC-S561 and CAN/ULC-S559 give designation and scope only. One gap we could not close: Sentence 3.2.4.7(4) names S561 without a year, and the binding edition sits in the Building Code's referenced documents table, which we did not read.

What "listed" means here, and how an owner checks

A listed receiving centre is one a certification body has investigated against the standard and then published. UL Solutions in Canada puts it this way: once an investigation is completed to assess compliance with the programme requirements and Canadian national standards, the company is ULC listed and authorised to issue ULC certificates in that category. The word to notice is category. A City of Vancouver bulletin names DAYIC for a listed monitoring company and DAYYC for a listed installation company: being listed to install is not being listed to monitor.

An owner can check this without any technical knowledge. Ask for the ULC certificate: only listed alarm companies may issue one, and it attests that the installation conforms, the equipment is properly listed and labelled, the workmanship is right and the maintenance obligations are being met. Ask which legal entity holds the listing, and in which category, because monitoring is often subcontracted and the name on the invoice is often not the name on the listing. Then look it up on the Product iQ site, where UL Solutions publishes its company listings, checking the term against our listed entry if it is new to you. Fire Code 6.3.1.2 gives you a further lever: the operator has to hand over a document attesting compliance when the owner or the Chief Fire Official asks.

Transmission paths, and what supervising them means

Historically this was two dedicated telephone lines, because a copper pair fails in a way that is easy to detect. Copper is being displaced: Canadian trade press was reporting ULC listed cellular fire alarm communicators sold explicitly to replace the landlines dedicated to the master control unit back in 2020. Today it is usually cellular, IP over the building network, or both as a dual path.

Supervising the path means the transmitter and the centre keep proving to each other that it is alive, so a cut line or a dead SIM shows up as a trouble rather than as silence. That is the whole reason a monitored system beats an autodialler: silence gets noticed.

We are not printing a number for how fast a failed path must be reported. S561 sets limits, but the standard is paywalled and we could not confirm the current figure from any Canadian source we would stand behind. Ask your provider for the contracted figure, and the edition it comes from, in writing. Two more questions worth asking on any job: is the second path genuinely independent, and what actually happens when one fails.

What the centre does with each signal

Its job is to keep the three classes distinct and act on each. An alarm has to arrive and be handled as an alarm, not flattened into a generic event: the operator dispatches the fire department, then works the contact list. On a supervisory the fire department is normally not dispatched, because a closed valve is a maintenance emergency rather than a fire, so the owner's designate and the service company are called. A trouble goes to the same people and is logged.

S561 sets time limits on all of this. An Ontario contractor presentation from 2016, summarising the 2003 edition, gives 60 seconds to receive an alarm from the premises, 30 seconds to contact the fire department, and 5 minutes to reach designated owner representatives on a trouble. Secondary, and describing an edition since replaced twice, but the right order of magnitude for what you are buying.

The operator is also only as good as the data in front of them. A stale contact list, a wrong civic address, or zone descriptions typed from a drawing that changed during construction will survive years of clean tests and then fail once.

Direct connection to the fire department

A municipal fire alarm system, meaning street boxes and dedicated circuits running back to the hall, used to be a legitimate alternative here: the 2006 and 2012 Building Codes offered it alongside a central station. In the 2024 sentence we read, it is gone. A few Canadian municipalities still run something like it, and if yours does the Chief Fire Official is your source. We found no Canadian government source explaining why most withdrew, so treat the usual reasons, circuit maintenance cost and nuisance call volume, as trade lore rather than documented fact.

What gets tested, and by whom

At verification under CAN/ULC-S537 the monitoring connection is confirmed before handover. The Vancouver bulletin makes it concrete: where the installation is monitored, a ULC certificate completed by a listed monitoring or installation company forms part of the package submitted with the Appendix C verification report. More in what S537 verification involves.

At the annual inspection under CAN/ULC-S536 monitoring is checked again, and the Fire Code makes the record explicit: it has to say whether the signals were received. Not a box you tick from memory. The two exercises trip up a lot of people, so we separated them in verification versus annual inspection. Who may work on the transmitting end is a separate question again, answered through electrical licensing rather than the standards: see who can work on fire alarms in Ontario.

Contracts and cost, honestly

An owner is buying four things in one monthly line: a staffed and listed receiving centre, a communicator beside the panel, one or two transmission paths, and the labour to prove annually that it works. Providers price the bundle, which makes comparison hard on purpose. We are not publishing monthly prices, because every figure we found sat on a vendor's own sales page. Compare these instead.

• Which legal entity holds the ULC listing, in which category, and whether you can find it in the published listings.
• Whether a ULC certificate will be issued, by whom, and what happens to it if you change providers.
• Who owns the communicator. If the provider owns it, switching later means a truck roll and a new device.
• How many paths, whether they are independent, and the contracted response when one fails.
• Whether attendance for the annual S536 test is included or billed separately.
• Term, auto renewal clause and notice period.

The trap is a cheap monthly rate from a centre that is not listed: it fails the Fire Code documentation the owner has to hold, it fails at verification, and it surfaces at an inspection or after an incident.

The cost that actually hurts is not the monthly fee. It is dispatch for nuisance alarms. Toronto's Municipal Code fee schedule sets $1,711.50 for three crews and vehicles sent to a nuisance false fire alarm at an address other than a single family home, and $570.50 per vehicle for a malicious false alarm. A wet detector head in a parking garage can burn through more in fees over one winter than a decade of monitoring costs.

The technician's view: proving the signal arrived

"The panel says it sent it" is not proof. The event history records that the control unit told the communicator to transmit, not that a human being somewhere saw anything. What holds up on a report:

• Call the centre first and put the account on test for a defined window. Get the operator's name.
• Test each signal class separately. Trip an alarm, trip a valve tamper or low air switch, and create a real trouble by pulling the AC feed or opening a circuit, not by pressing a lamp test.
• Have the operator read back what they see before you tell them what you did. If the format carries point identification, confirm the point description, not just the account.
• Test each path separately. Disconnect the primary, confirm the secondary carries the signal, and confirm the loss of the primary itself reported as a trouble. A dual path running on one leg for months is a common find.
• Check the account data against the building as it stands today: civic address, entry instructions, keyholders, and the zone descriptions in the automation.
• Record it. Operator name, times and the centre's reference number, because the Fire Code record has to state whether signals were received.
• Take the account off test and confirm it is off. More systems have been left on test after a service call than have ever failed to transmit.

The owner facing version is in the guide for building owners.

What we could not confirm

• Article 3.2.4.7(1) as read lists only Group A over 300 and retirement homes. Earlier editions listed more. We did not print what we could not see.
• Fire Code 6.3.1.2 and retrofit Section 9.7 came from a secondary consolidation current to 1 January 2026, not the official Compendium.
• The NFPA 71 and NFPA 72 references in that consolidated 6.3.1.2 are the Ontario Code's wording, not ours, and nothing here rests on them.
• Path supervision timing in the 2020 edition of S561 is unverified, which is why no figure appears above.
• The edition of S561 the Building Code points at sits in the referenced documents table, which we did not read.

Each is worth a call to the authority having jurisdiction before it goes into a submission. Fire departments differ on what they accept as evidence that monitoring works, and the local Chief Fire Official decides.

---

Fire Alarm Academy provides educational content only. It does not confer any certification, licence or credential, and it is not affiliated with, endorsed by, or accredited by the Canadian Fire Alarm Association, the Electrical Contractors Association of Ontario, ULC Standards, UL Standards and Engagement, CSA Group, the Electrical Safety Authority, any authority having jurisdiction, or any manufacturer. Always work from the edition of any standard adopted by your authority having jurisdiction.