CAN/ULC-S537: Verification of Fire Alarm Systems
What verification means, when it is required, who can perform it, and what the report should contain — explained for technicians, officials, and building owners.
What verification is
Verification, in the Canadian fire alarm world, has a precise meaning. It is the formal acceptance testing performed on a fire alarm system after it has been installed or modified, carried out in accordance with CAN/ULC-S537, the Standard for Verification of Fire Alarm Systems. Its purpose is to confirm two things: that the system was installed in accordance with CAN/ULC-S524 and the approved design, and that it actually works — every device, every function, every interconnection.
Verification is not a spot check. The standard requires testing of each individual initiating device, each notification appliance, and each control unit function. It is a one-time, milestone event tied to the installation work itself, which is what distinguishes it from the recurring inspection and testing that follows for the rest of the building's life.
The result is a verification report — a document that authorities having jurisdiction, owners, insurers, and future service providers all rely on as evidence that the system left the gate in compliant, working condition.
When verification is required
Verification is triggered by installation work, not by the calendar. The common triggers are:
- New installations. Every new fire alarm system must be verified before the building is occupied. Occupancy permits routinely hinge on the verification report.
- Modifications and additions. Adding devices during a tenant fit-out, extending circuits into a new wing, replacing a control panel, or changing system programming all require verification of the affected work. The extent of re-testing depends on what was touched — a panel replacement reaches much further into the system than adding a single detector.
- Repairs that alter the system. Like-for-like component swaps under maintenance are generally handled under the testing standard, but work that changes the system's configuration crosses into verification territory.
When in doubt about whether a piece of work triggers verification, the authority having jurisdiction makes the call — and most take a conservative view.
Who performs verification
Verification must be performed by someone independent enough and qualified enough that the report means something. In practice:
- The technician must be trained and experienced with the specific type of equipment installed, and able to demonstrate that competence. Industry certification — most commonly registration with the Canadian Fire Alarm Association (CFAA) — is the widely accepted benchmark, and some provinces and municipalities require it explicitly.
- Many jurisdictions and specifications expect the verifying organization to be acceptable to the authority having jurisdiction, and some require independence from the installing contractor so the installer is not grading their own work. Requirements vary by province, so confirm the local rules early in the project.
- Verification of a modern addressable system also requires access to the manufacturer's programming tools and documentation, which in practice often means a technician authorized on that product line.
What gets tested
A proper S537 verification is comprehensive. Expect the technician to work through:
- Every initiating device. Each smoke detector, heat detector, manual station, water flow switch, and supervisory device is individually activated and confirmed to report correctly — right device, right address or zone, right response at the panel.
- Control unit functions. Alarm, supervisory, and trouble operation; two-stage sequences where applicable; resets; signal silence behaviour; and correct response to circuit faults such as open and ground conditions.
- Annunciation. Confirmation that the annunciator displays match reality, so responding firefighters are sent to the right place.
- Audibility and visibility. Notification appliances are checked for operation, and sound levels are measured to confirm occupants can hear the alarm where they live, work, and sleep. Visual signals are confirmed in the areas that require them.
- Ancillary functions. Everything the fire alarm system is supposed to trigger or monitor: elevator recall, door hold-open release, fan and damper control, suppression system supervision, magnetic lock release, and transmission of signals to the monitoring station.
- Power supplies. Operation on emergency power, battery condition and capacity, and proper transfer when normal power is lost.
- Wiring and installation conformance. A check that the physical installation — device placement, mounting, wiring methods — conforms to S524 and the approved drawings.
The verification report
The deliverable is as important as the testing. The verification report documents the system description, the equipment installed, the test results for each device, sound level readings, deficiencies found, and the verifier's identification and qualifications. ULC publishes standard report forms for this purpose, and authorities generally expect them.
Deficiencies are listed, not hidden. A report with deficiencies is normal on a first pass; what matters is that they are corrected and the corrections are documented. The completed report should be kept with the building's fire safety records permanently — it is the baseline document every future inspection, renovation, and service call refers back to.
How S537 relates to S524 and S536
The three standards form a sequence. CAN/ULC-S524 governs how the system is installed. CAN/ULC-S537 is the one-time acceptance test that confirms the installation meets S524 and functions correctly. CAN/ULC-S536 then takes over for the life of the system, governing the recurring inspection and testing — including the annual test — required by the fire codes.
The confusion between S537 and S536 is the most common one in the field. The shorthand: verification (S537) happens once per installation or modification and proves the system was built right; inspection and testing (S536) happens on an ongoing schedule and proves the system still works. An annual S536 inspection does not substitute for a missing verification, and a verification does not replace the annual inspection due that year's cycle.
Frequently asked questions
Is verification the same as the annual fire alarm inspection?
No. Verification under S537 is a one-time acceptance test after installation or modification. The annual inspection falls under S536 and recurs every year. They use different procedures and different report forms, and one cannot stand in for the other.
Can the installing contractor verify their own work?
It depends on the jurisdiction and the project specifications. Some authorities and many consultants require an independent verifier; others accept verification by a qualified technician from the installing firm. Confirm the expectation with the authority having jurisdiction before pricing the job.
We only added three devices — do we really need a verification?
Yes, for the affected portions. Any modification to the system triggers verification of the work performed, including confirming the new devices report correctly and that the modification has not disturbed the rest of the system. The scope is smaller than a full-building verification, but it is still a documented S537 process.
How long does a verification take?
It scales with device count and system complexity. A small single-panel system might be done in a day; a high-rise with voice communication, hundreds of devices, and extensive ancillary functions can take a crew the better part of a week. Owners should budget time for deficiency corrections and re-testing as well.
What should I do with the verification report as a building owner?
Keep it for the life of the building, alongside the approved drawings. Your fire department, insurer, and every future service contractor will ask for it. If you own a building and cannot locate a verification report for the system, raise it with a qualified fire alarm contractor — reconstructing that baseline is far easier before a problem than after one.