Ontario Fire Alarm Inspection Requirements 2026: What Contractors Need to Know

On January 1, 2026, fire alarm inspections in Ontario changed in a big way.

Ontario Regulation 87/25 formally adopted CAN/ULC-S536:2019 (Inspection & Testing of Fire Alarm Systems) and CAN/ULC-S537:2019 (Verification of Fire Alarm Systems). The goal: more consistent, more detailed, and more defensible fire alarm inspections.

Fire and life safety contractors now face far more documentation requirements and much higher expectations for the quality of their inspection records.

This article breaks down what’s changing, why digital inspections are becoming the practical path forward, and how a platform like Inspect Point can help you get ready without turning your back office into a paper factory.

1. What’s actually changing in Ontario?

Regulation 87/25 – effective January 1, 2026

Ontario’s Regulation 87/25 amends the Ontario Fire Code and locks in:

• CAN/ULC-S536:2019 – Standard for Inspection and Testing of Fire Alarm Systems
• CAN/ULC-S537:2019 – Standard for Verification of Fire Alarm Systems

The intent behind these updates is to:

• Modernize how fire alarm systems are inspected and tested
• Align Ontario with the 2020 National Fire Code of Canada
• Tighten expectations around documentation and record-keeping for inspections and verifications

Along with these standards comes their documentation requirements. Once you look at what S536 and S537 actually require in terms of reporting, it becomes clear why “digital” is no longer a nice-to-have.

2. The documentation burden: why digital becomes the practical path

Standardized ULC inspection report formats

Under CAN/ULC-S536:2019 and S537:2019, every company performing fire alarm inspections in Ontario is expected to use the official ULC-prescribed report formats for:

• Annual inspections
• Monthly fire alarm checks/logs
• Verification inspections for new or modified systems

These aren’t simple one-page checklists.

They’re multi-page, structured reports that drive consistency and traceability across the province. That means:

• Device-by-device, step-by-step results
• Clear structure around what was tested, how, and by whom

Some of the typical required elements include:

• Technician attendance logs with names, dates, arrival and departure times
• Device-level results for detectors, pull stations, notification appliances, wireless devices, CO devices tied into the system, voice evac, air-sampling, RF links, and more
• Battery testing with measured values, not just “pass/fail”
• Clear separation of deficiencies vs. recommendations
• Monthly logs with defined fields and format
• A required on-site documentation bundle (as-builts, device lists, sequences of operation, etc.)

Contractor-focused guidance in the market is already warning building owners to expect 20–35% more labour/time for inspections under S536-2019 because of the added depth and documentation.

For contractors, the implications are obvious:

• More fields to capture
• More opportunities for errors on paper
• More time spent reconciling handwritten notes back in the office

If your inspection process is a fillable PDF, a generic form builder, or paper, you’re going to struggle to:

• Model devices and panels accurately
• Produce reports that actually mirror ULC formats
• Maintain a clean, traceable history over multiple years and system changes

You don’t have to go digital to comply, but at any meaningful scale, it becomes the only practical option.

2.2 “Written” vs. “digital”: what the law actually says

The Ontario Fire Code has historically required that inspection records be:

• In written form, and
• Retained at the building premises for at least two years after they’re made

That language predates most modern SaaS tools, but Ontario’s Electronic Commerce Act, 2000 (ECA) fills the gap.

Under the ECA, a requirement to provide a document “in writing” can generally be satisfied by an electronic record, unless another law explicitly says otherwise. Under the ECA (sections 5 and 6), digital records meet the “written” requirement when they:

1. Are accessible to the intended recipient (owner, AHJ, insurer, etc.)
2. Can be retained and referenced later
3. Are kept in a stable form (not easily altered without leaving a trace)

The Ontario Fire Code separately requires that records be retained at or accessible from the building premises. That can look like:

• Printed copies in an on-site binder, and/or
• A digital record accessible from a customer portal, on-site device, or secure link

There is some legal nuance around “cloud-only” storage vs. physically stored documents. Printing reports or keeping a local electronic copy (USB, on-site PC, etc.) is the safest approach. Consult your legal counsel for guidance specific to your operations.

The takeaway for contractors:

• You can confidently adopt digital workflows as long as your system supports retention, integrity, and reasonable on-site access.
• The real risk is not that your records are digital, but that they’re incomplete, inconsistent, or hard to produce when an AHJ or investigator asks for them.

3. What “digital fire alarm inspections” mean post-2026

When you translate all of this into day-to-day operations for an Ontario fire alarm contractor, “going digital” isn’t just scanning your old paper forms.

It means having a repeatable system that can deliver on four key outcomes:

1. Full CAN/ULC-S536/S537-style reports every time

• No more one-page, homegrown checklists for annual fire alarm inspections
• Reports that follow the prescribed structure and minimum data fields
• Clear, standardized outputs that AHJs immediately recognize and trust

2. High-fidelity inspection data, not just checkboxes

You need a record of:

• Who was on-site and when (tech attendance and time)
• Device-level results and measured values (e.g., battery readings)
• Photos, notes, and supporting details for complex systems
• Clearly separated lists of deficiencies vs. recommendations
• Evidence of proof of correction, tied back to the original inspection

All of this needs to live together, not scattered across clipboards, email threads, and spreadsheets.

3. Complete inspection histories at the building level

By 2026, a “compliant file” for fire alarms in Ontario will typically include:

• Annual CAN/ULC-S536:2019 inspection reports
• Monthly log forms for the same period
• CAN/ULC-S537:2019 verification certificates for new or altered systems
• As-built drawings, device lists, sequences of operation
• Tenant notification and suite-access records (where applicable)
• A deficiency log and associated proof of correction
• An up-to-date Fire Safety Plan that reflects the current system and procedures

And all of this must be:

• Consistent and standardized, not contractor-specific one-offs
• Accessible on-site, via binder plus digital access where possible
• Retained for at least two years (most larger owners will want longer)

4. Audit-ready, traceable documentation

Administrative monetary penalties under the Fire Protection and Prevention Act (enabled by Ontario Regulation 260/25, also effective January 1, 2026) make documentation quality a direct risk factor.

• Inspectors won’t just ask, “Did you do the inspection?”
• They’ll ask, “Can you prove it, and does your documentation stand up to scrutiny?”

If your reports are illegible, incomplete, or scattered, that puts both your customers and your business at risk.

4. How Inspect Point can help you get “Ontario 2026-ready”

If you’re thinking about this now, you’re ahead of most of the market.

A platform like Inspect Point is designed specifically for fire & life safety contractors and can help you close the gap between regulatory expectations and day-to-day reality without adding more admin burden to your team.

Standardized, repeatable inspection templates

Inspect Point provides structured inspection templates built for fire alarm systems, so your field teams aren’t forcing a ULC-level workflow into a generic form app.

You can:

• Configure inspection flows to align with CAN/ULC-S536/S537 reporting requirements
• Capture the right data in the right order, every time
• Produce clear, legible reports that AHJs and building owners can actually work with

Instead of re-creating ULC forms from scratch, you’re starting from a framework used by thousands of contractors daily, designed for fire alarm inspections, and refining it to match your market and services.

Device-level, asset-based inspection data

Because Inspect Point is built around systems and devices, not just checklists, your reports can show:

• Panel and device-level results
• History of inspection results for each device
• Detailed notes, photos, and readings tied directly to the asset

This is exactly the kind of high-fidelity data Ontario’s new standards push you toward, and it makes it much easier to demonstrate that every part of the system was inspected properly.

Technician accountability and time tracking

The new requirements emphasize who did what, when, and for how long.

Inspect Point supports:

• Technician check-in and check-out for jobs
• Capturing technician names, timestamps, and approvals
• Digital signatures and notes inside each inspection record

That helps you answer questions like:

• “Which tech inspected this device last year?”
• “How long were they on site?”
• “Who signed off on this panel test?”

All without digging through old timesheets and paper forms.

Deficiency lifecycle management

Finding a deficiency is just the start. Under the new regime, you also need to show:

• How that deficiency was communicated
• When and how it was corrected
• That the system now meets the required standard

Inspect Point helps you manage that full lifecycle:

1. Capture deficiencies during the inspection (with device, photos, and notes)
2. Generate quotes or proposals directly from those findings
3. Create work orders and track completion
4. Document proof of correction, linked back to the original inspection

By the time an AHJ or owner asks, you’re not scrambling. You can show the full story from inspection to resolution.

Customer-friendly reporting and access

For your customers, especially multi-site portfolios in Ontario, the real value is clarity and consistency.

With Inspect Point, you can:

• Deliver standardized digital reports after every inspection
• Print or export them for on-site binders
• Provide secure digital access so facilities teams and compliance managers can pull what they need, when they need it

That makes it far easier for owners to remain compliant and for you to be seen as a strategic partner rather than just another vendor.

5. What to do next

If you inspect fire alarm systems in Ontario and haven’t updated your inspection workflows yet, here’s a practical path forward:

• Audit your current alarm inspection reports. Do they resemble S536/S537 formats? Are all the required data points captured consistently?
• Quantify your documentation burden. How many annual and monthly inspections do you complete in Ontario? How many hours are spent on paperwork and report cleanup?
• Identify your biggest risks. Paper forms that get lost or misread. Inconsistent tech practices across branches. Gaps between inspection findings and proof of correction.
• Map those gaps to digital workflows. Where could standardized templates, asset-based data, and automated reporting remove friction and risk?
• Start with a pilot. Pick a subset of Ontario customers and run your next round of inspections through Inspect Point on a workflow that matches S536/S537 requirements. Standardize across branches from there, and build a documentation model you can scale to other jurisdictions as codes evolve.

Bottom line

Ontario’s 2026 changes raise the bar for fire alarm inspections, but they also create a real opportunity for contractors who move early.

Contractors who invest now in digital, standardized, and transparent inspection processes will be in the best position to:

• Win and retain the most demanding customers
• Pass AHJ scrutiny with confidence
• Grow efficiently as documentation requirements continue to increase

If you’d like help mapping your current inspection process to a compliant digital workflow, book a short working session with our team, and we’ll help you build a plan to move forward.

Frequently Asked Questions

Does Ontario Regulation 87/25 require digital inspection records?

No. The regulation requires written records, and Ontario’s Electronic Commerce Act allows electronic records to satisfy that requirement in most cases. Digital is not mandatory, but it’s the most practical way to meet the new documentation depth at scale.

When will these changes take effect?

January 1, 2026. CAN/ULC-S536:2019 and CAN/ULC-S537:2019 are now the referenced standards under the Ontario Fire Code.

What’s the biggest change for fire alarm contractors?

The level of detail required in inspection reports. S536:2019 expects device-level results, technician attendance logs, measured battery values, and clear separation of deficiencies from recommendations. That’s significantly more documentation than most contractors were producing under previous standards.

Can I keep paper records and still comply?

Yes. Paper records are still valid. But the volume and detail required under S536/S537 make paper-based workflows significantly harder to manage at scale, especially for multi-site portfolios.

How long do inspection records need to be retained?

The Ontario Fire Code requires records to be kept at the building premises for at least two years. Many building owners and insurers will expect longer retention.

This article is for informational purposes only and does not constitute legal advice. Consult your legal counsel and local AHJ for guidance specific to your operations and jurisdiction.