How CAN/ULC-S537 is organized

Before the north wing verification starts, Gerry hands Sasha and Nadia a copy of CAN/ULC-S537 and a blank verification report. 'Read the report forms first,' he says. 'The standard tells you what to check. The forms tell you how you'll prove you checked it. If you understand the forms, you understand the standard.' This lesson walks through how the verification standard is organized, how it connects to the building code and the installation standard, and what the finished report must contain.

Where the requirement comes from

The requirement to verify starts in the building code. In the National Building Code, the article on installation and verification of fire alarm systems (3.2.4.5 in recent editions) requires a fire alarm system to be installed in conformance with CAN/ULC-S524 and verified in conformance with CAN/ULC-S537. Saskatchewan adopts the National Building Code under its construction codes legislation, so the same requirement applies in Saskatoon, with the edition of each standard fixed by the edition of the code in force when the permit was issued. The building official won't issue an occupancy permit until the verification report has been received, and the fire department expects a copy for its records.

The verification standard sits beside two others you already know. CAN/ULC-S524 says how the system must be installed. CAN/ULC-S537 says how to check that a newly installed or modified system meets S524 and works. CAN/ULC-S536 says how to inspect and test it every year after that. The three were written to work together, so a device's installation rule, its verification test and its annual test all describe the same expected behaviour.

The parts of CAN/ULC-S537

CAN/ULC-S537 is a short standard compared with S524, but every part of it matters on the job. The 2019 edition, which replaced the 2013 edition, is organized in a sequence that follows the work itself:

• Scope and definitions: what the standard applies to (new installations and modifications) and the meaning of terms such as verification, verifier and field device.
• General requirements: who may verify, what must be in place before verification begins, and what documents the verifier needs.
• Verification procedures: how each type of field device, each circuit, the control unit and transponders, power supplies, annunciators, the voice and two-way communication equipment, ancillary outputs and the link to the signal receiving centre are inspected and tested.
• Measurements: how sound pressure levels and, for voice systems, speech intelligibility are measured and recorded.
• Report forms: the verification report, including a summary page, a documentation checklist, a record for every device, measurement records and lists of deficiencies and recommendations.

Sections of the report that don't apply to a system are kept in the report and marked not applicable. An authority reviewing a report with whole sections missing can't tell whether they didn't apply or were never done, and many authorities return such reports unaccepted.

Who may verify

CAN/ULC-S537 expects the verification to be carried out by qualified people who are independent of the installation. In practice, across most of Canada, verification of a new system is done by technicians working for the equipment manufacturer's authorized distributor or a fire alarm company acceptable to the authority, not by the electrical contractor who installed the wiring. The standard's annex describes the knowledge expected: the standards themselves, the equipment and suitable training or experience. Many authorities and owners also look for registration with a recognized technician program such as the Canadian Fire Alarm Association's.

On the north wing, Northline Electric installed the wiring and devices under Bramwell's supervision, and Bramwell, as the equipment supplier, provides the verification team. Gerry signs as the responsible verifier. Sasha and Nadia test, but their work is under his direction and his signature.

What must be in place before testing starts

Both countries expect certain conditions before the formal test begins. The installation must be complete, not nearly complete: every device mounted and connected, every cover on, ceilings closed where detectors are mounted on them, and the area clean enough that construction dust won't contaminate smoke detectors. The installer must have pre-tested and corrected the faults found. The panel must be programmed with the final sequence of operation. And the documents must be on site: the approved drawings, the sequence of operation, battery calculations, voltage drop calculations and data sheets for the equipment.

CAN/ULC-S537 lists the documents the verifier must have and records in the report which were received. A verifier who starts without approved drawings can only check that devices work, not that they are where the design and the authority approved.

The verification report

The finished report is the product of the verification. It includes a summary page stating the system, the building and whether the installation conforms; a list of the documents reviewed; an individual record for every field device showing its location, type, address or circuit and the test result; records of sound level and intelligibility measurements by zone; tests of the control unit, power supplies, annunciators and ancillary functions; and lists of deficiencies, recommendations and remarks. The verifier signs it, and a certificate or summary statement accompanies it for the owner and the authority.

A deficiency found during verification of a new system must be corrected and retested before the verification report is issued as complete. The deficiency list in the report is mainly for modifications to existing systems, where parts outside the work may already have problems the verifier must record.

# Which edition applies? Look up the project's code edition and the referenced standard
adopted = [(2018, "NBC 2015 as adopted", "CAN/ULC-S537-13"), (2024, "NBC 2020 as adopted", "CAN/ULC-S537-19")]
permit_year = 2025
code = None
for start, ed, std in adopted:
    if permit_year >= start:
        code, standard = ed, std
print("permit issued:", permit_year)
print("code in force:", code)
print("test standard referenced:", standard)
print("use that edition, even if a newer one has been published")

permit issued: 2025
code in force: NBC 2020 as adopted
test standard referenced: CAN/ULC-S537-19
use that edition, even if a newer one has been published

The table in the code is illustrative; the real dates come from the province's adoption regulation. The point is that the permit date fixes the edition. The north wing's permit was issued under the 2020 National Building Code as adopted in Saskatchewan, so the verification follows the edition of S537 that code references, even though the inspection crews use the newer S536 edition for annual tests elsewhere.

Reading the standard alongside the code

CAN/ULC-S537 doesn't stand alone. Many of its tests point back to a requirement in CAN/ULC-S524 or in the building code: the audibility levels come from the building code, the mounting heights and spacings from S524, and the battery durations from the building code's emergency power requirements. A verifier who knows only S537 can follow its procedures but can't always tell whether a result is acceptable. That is why Bramwell's verification technicians carry three documents on every job: the verification standard, the installation standard of the same family, and the code's fire alarm requirements, together with the project's approved drawings.

The same applies to local rules. Many authorities publish their own requirements or guidelines for fire alarm testing: forms they want used, items they want witnessed, the notice they need before a test, and how reports must be submitted. These don't replace the standard, but an authority will reject a report or postpone a test that ignores them. Before the north wing verification, Sasha downloads the current guidance from the authority's website and adds its requirements to her plan.

Editions and transitions

New editions of the standards are published every few years, and the codes adopt them on their own timetable. During a transition a technician may verify one building to one edition in the morning and inspect another to a different edition in the afternoon. The differences are usually small but real: a new item in the report forms, a changed measurement method, a new requirement for a type of device. Gerry keeps a one-page summary of the differences between the editions in use and reviews it with the crew whenever a new edition comes into force.

When the edition that applies is unclear, for example where a permit was issued under one code and the work continued after a new one came into force, the answer comes from the authority, in writing, before testing starts. The report then states the edition used.

What the forms teach a new technician

Gerry's advice to read the forms first has a practical side. The forms are the standard's checklist in condensed form: every row on a device record is a question the standard expects the verifier to answer, and every blank on the summary page is a statement the signer must be able to make. A trainee who fills in a set of forms for a small building, even as an exercise, learns more about what the standard requires than one who reads it cover to cover. Nadia's first assignment on the north wing is to fill in the summary and documentation pages from the project files, before a single device is tested, and to list every document she couldn't find.

What the authority looks for first

Captain Strand reviews many verification reports every year, and she has a routine. She reads the summary page and the deficiency list first, then the documentation checklist, because a report built on superseded drawings can't be accepted however good the testing was. She looks at the sound level records for the rooms most likely to fail: rooms far from appliances, rooms with heavy doors, sleeping rooms. She checks that the number of device records matches the number of devices on the drawings. And she picks a few devices from the drawings and finds their rows, to see that they were really tested and described correctly. A verifier who knows this routine writes reports that pass it.

The lesson for a new technician is that the paperwork is read by someone who knows exactly where problems hide. Writing it carefully isn't a formality; it is the part of the job the authority actually sees.

Reading the standard as a working tool

Gerry keeps a tabbed copy of CAN/ULC-S537 in the truck, with the device test clauses and the report forms marked. When a question comes up on site, such as how a particular appliance is to be tested or what the report must say about a monitored interface, he opens the standard rather than relying on memory. He also keeps the referenced installation standard, CAN/ULC-S524, beside it, because many verification questions are really questions about whether the installation met S524 in the first place. A trainee who learns to find the answer in the clause, rather than asking someone who remembers it, becomes a verifier who can defend every line of a report.