Which standards apply in Ontario?

Ontario enforces the Ontario Fire Code (OFC), O. Reg. 213/07, a regulation under the Fire Protection and Prevention Act, 1997 (FPPA). The OFC requires fire alarm systems to be maintained and tested in accordance with referenced CAN/ULC standards. Ontario AHJs currently accept modern editions of CAN/ULC‑S536 (inspection & testing) and CAN/ULC‑S537 (verification). Always confirm the edition adopted by your AHJ.

• Ontario Fire Code (O. Reg. 213/07) (e‑Laws): ontario.ca/laws/regulation/070213
• FPPA, 1997 (enforcement & penalties): ontario.ca/laws/statute/97f04
• CAN/ULC codes & standards overview (CFAA page): cfaa.ca/codes-and-standards/
• Verification primer – CAN/ULC‑S537 explainer (overview article): coggno.com/blog/can-ulc-s537/

Apply the edition your AHJ adopts. Municipal fire departments may issue bulletins clarifying accepted editions and report formats.

What version should be used on a Government of Canada building?

Federal facilities typically reference the National Model Codes and the editions of CAN/ULC‑S536 & S537 specified in contract documents. Many federal projects may also require a listed/qualified service provider for monitoring and related services. Confirm with the RFP/specs and contracting authority. (For Ontario‑based facilities, OFC maintenance/testing still applies.)

Do we need a Fire Watch during annual testing?

If detection or critical notification is impaired at any time, implement Alternate Measures/Fire Watch per the OFC and your FSP. If you temporarily inhibit outputs (e.g., NACs) to reduce noise but keep detection and monitoring active, you must provide an alternate notification method and station a trained person at the panel to restore outputs and initiate evacuation if an alarm occurs elsewhere.

• Post notices, place the system “on test” with your monitoring provider, and patrol affected areas when detection is offline.
• Follow your Fire Safety Plan and any AHJ directions.

Authority: Ontario Fire Code

What percentage of devices are tested annually?

100%. CAN/ULC‑S536 inspection is a full device test annually. That includes initiating devices, notification devices, supervisory devices, interfaces, and all end‑of‑line (EOL) devices. Keep individual device records in your report set.

Is a control panel inspection required?

Yes. S536 requires visual/physical inspection of control units & transponders (modules, terminations, labels, dead‑front, indications), plus battery condition/connection checks. Removing the dead‑front must be done by qualified personnel.

Can we bypass notification appliances (NACs) to keep down the noise?

Yes, with conditions. S536 permits inhibiting outputs during testing, but you must prove at least one device per zone/input circuit operates the required outputs, and maintain alternate notification while outputs are inhibited. Document which devices confirmed output operation (this corresponds to the “Output Circuit Operation Confirmed” checkbox in many Appendix C device forms).

How do we test key devices?

Smoke detector sensitivity checks

Use the device manufacturer’s accepted method (test instrument or method noted in the I&M manual). Many detectors allow verification via LED pattern or a built‑in feature.

Example manual (System Sensor i3 series – LED/sensitivity reference): Honeywell/System Sensor I56‑1800

End‑of‑line (EOL) resistor/device testing

S536 requires annual testing of each input and output circuit EOL device (open, short, ground), with results recorded on the individual device record. EOL testing was formalized in the 2004 edition and remains in current editions. If an EOL is hidden in the last field device, note location; recommend relocating to a labeled plate where practical.

How do we test for ground fault indication?

On conventional systems: momentarily short each side of each IDC and NAC to ground and confirm panel annunciation. On addressable systems: test the SLC loop(s) to ground (and any conventional NACs). Confirm indications at the panel/annunciator and in the report.

Supervisory vs. trouble—what’s the difference?

• Supervisory: off‑normal condition of a monitored protection feature (e.g., sprinkler valve moved, low air/water). Often latching until restored/reset.
• Trouble: a fault affecting system integrity (e.g., open circuit, ground fault, AC fail, battery fail). Requires service action.

Valve movement test: within ~two turns of the valve handle (or ~20% stem movement), a supervisory (or, on very old systems, a trouble) must annunciate. A flow alarm must override any valve indication if both share a zone.

Is an annual instrumented sound level test required?

Not by default in S536. You must confirm audibility/visibility is effective throughout the served area (judgment and functional checks). Run measured tests if required by design, the AHJ, or project specs (e.g., voice systems with intelligibility criteria). Keep notes in your report.

Who can perform the annual test in Ontario?

S536 expects a qualified person acceptable to the AHJ. In Ontario, many AHJs recognize CFAA‑certified technicians for annual fire alarm testing.

Resource (standards & references): CFAA — Codes & Standards

In‑suite access & notice (Ontario)

Annual S536 testing requires access to all connected devices, including in‑suite buzzers/sounders, smoke/heat detectors (if system devices), and speakers/strobes as applicable. For occupied residential suites, Ontario’s Residential Tenancies Act requires 24‑hour written notice for non‑emergency entry at a specified time window for a valid reason (e.g., mandated inspection/maintenance).

Sources: Residential Tenancies Act, 2006 · Ontario Fire Code

How often are bells/sounders tested in condos (Ontario)?

Building owners/managers conduct monthly checks (e.g., operate a pull on rotation so audibles sound) and keep logs per the FSP. The annual S536 test confirms operation of all notification appliances (with at least one device per zone proving output operation when NACs are otherwise inhibited).

How long will it take and what drives cost?

Time/cost scale with device counts, number of risers/transponders, isolation points, special functions (elevator recall, smoke control), documentation format (individual device records), and access logistics (multi‑tenant entry, after‑hours). Your AHJ’s expectations on documentation and scheduling will also affect scope.

What if the system is non‑compliant or was “passed” last year?

• Document all deficiencies (use individual device records and a clear summary).
• Tag appropriately (note “additional work required”), and notify the owner/manager and, when required, the AHJ.
• If incompatible (non‑ULC‑listed or non‑cross‑listed) devices are found on a Canadian system, fail/tag and recommend replacement with compatible ULC‑listed units.
• Do not operate unsafe equipment; reschedule verification/annuals when critical faults (e.g., active ground fault, inoperative panel) exist.

Enforcement authority: FPPA, 1997

Special notes for monitored systems

Before testing, place the system “on test” with your monitoring provider, coordinate signals, and confirm restoration after work. For background on Canadian monitoring/receiving centre requirements, see the (older) CAN/ULC‑S561‑03 copy below (confirm current edition with your AHJ/monitoring provider):

CAN/ULC‑S561‑03 (PDF)

More quick answers

Official references (client‑supplied URLs; verified)

• Ontario Fire Code (O. Reg. 213/07): ontario.ca/laws/regulation/070213
• FPPA, 1997 (enforcement): ontario.ca/laws/statute/97f04
• Residential Tenancies Act, 2006 (notice for entry): ontario.ca/laws/statute/06r17
• CFAA – Codes & Standards overview (CAN/ULC context): cfaa.ca/codes-and-standards/
• CAN/ULC‑S537 (verification) explainer: coggno.com/blog/can-ulc-s537/
• CAN/ULC‑S561‑03 (monitoring; older edition example): reedsecurity.com (PDF)
• System Sensor i3 – Installation & Maintenance Manual (LED/sensitivity): Honeywell I56‑1800 (PDF)

We intentionally removed all other external links and replaced them with the above client‑supplied working URLs.