Somewhere in a proposal you are reading, or in a sentence a salesperson said on a site walk, is the phrase "our monitoring is ULC."
It is meant to land as reassurance, and it usually does. The buyer hears a quality badge — this company is the serious kind, the monitoring is the good monitoring, somebody official has looked at it. Nobody is necessarily being dishonest. The phrase is simply doing a job it cannot do: it is not a claim you can check, and a claim you cannot check is not worth much on the day it matters.
This article is about what a listing actually is, why that sentence is the wrong shape, and the one thing to ask for instead. We are also going to be unusually explicit about the limits of what we will tell you — and that limit is the point rather than an apology.
A listing is a certification regime, not an adjective
Start with the category error. "ULC" here is not a product feature, the way waterproofing is a feature of a camera housing. It is a certification regime: a set of published requirements, maintained by a standards body, that a monitoring facility and an installation are measured against by a certificating organization, with a document issued at the end saying the measurement was made and what it found.
Regimes of this kind cover the same broad territory — the facility itself and how it is built and protected, the procedures its operators follow, the redundancy behind it so a single failure does not take the service away, and the record keeping that proves afterwards what happened and when. The specific requirements under each of those headings are set out in published standards.
Two consequences follow, and both are more useful than anything a brochure will tell you. A regime with requirements has an outcome — a pass, recorded on paper, so if the regime exists and nobody can produce the document it generates, that is information. And a regime measures something specific; it does not float free as a general property of a company.
The certificate belongs to an installation, not to a vendor
This is the sentence to carry away from the article: a certificate under this kind of regime is issued for a specific installation, at a specific level, valid to a specific date.
It is not a badge a company wears. It is a document that names a protected premises — your address, your building, your system — and records that that installation, connected to that facility, was certificated at a stated level for a stated period.
Once you see it that way, the marketing sentence falls apart. "Our monitoring is ULC" is a statement about a supplier in general; the certificate is a statement about your building in particular. The two can differ in every way that matters:
- The facility can hold everything it says it holds while your installation was never certificated — nobody ordered it, or the installation as built does not meet the level being claimed.
- A certificate can exist for your building at a lower level than your insurer or contract asked for. Levels are not decoration; they are how these regimes express different grades of protection, and one level does not satisfy a requirement for another.
- A certificate can have expired. Certification is a period, not an event. A document from several years ago tells you about several years ago.
- A certificate can be for a different site in your portfolio — one building done properly during a fit-out becomes the story the whole portfolio tells about itself.
None of these is a scandal; they are ordinary drift. But they all look identical from the outside, and they all sound like "our monitoring is ULC."
What we are deliberately not telling you here
Here is the part where we draw a line, on purpose and in public.
We are not going to tell you what any ULC standard requires. We will not name a standard number, state what any particular level demands, list the criteria a facility must meet, or walk you through the certification process step by step. Not vaguely, not approximately, not as a "generally speaking."
The reason is simple. Those requirements live in published standards sold by the standards body, and we have not read them for the purposes of this article. Anything we wrote about their specific contents would be recollection — the kind of half-remembered technical detail that circulates in the industry, gets repeated confidently, and is wrong in exactly the places where being wrong costs someone money.
We would rather be useful than impressive. An article telling you what document to demand and what it should name is worth more than one that half-remembers a clause, because the first you can act on this week and the second you would have to verify anyway.
If you need the requirements themselves, they are sold by the standards body, whose storefront is linked in the Sources below. We link it so you know where the real answer lives — not because we have read it and are summarizing it for you. Those are different things, and a great deal of confident security-industry writing quietly blurs them.
Why anyone cares: the requirement usually comes from a contract, not a code
The commercial reality is often misunderstood in a way that works against owners. Certificated monitoring shows up as a requirement in one of two places: an insurance policy — an underwriter wanting certificated protection on a risk, sometimes as a condition and sometimes attached to a rate — or a contract, where a landlord, tenant, franchisor, client organization or lender writes it into the agreement.
What it usually is not is a building requirement imposed on you by the province because of the kind of building you occupy. There are corners of regulation where certification is named — we will show you one below — but the everyday driver is commercial, not statutory.
That distinction changes what you do about it. A code requirement is discovered through permitting, and someone will eventually stop you. A contractual or insurance requirement is discovered by reading your own paperwork, and nobody will stop you, ever. The gap between "our monitoring is ULC" and a certificate naming your building at the level your policy asked for can sit there for years and surface exactly once — on a claim, at a renewal, during a lease audit — which is the worst possible time to learn that a word in a proposal was doing more work than it could carry.
So find out where your requirement comes from before shopping for a solution to it. Read the policy schedule. Read the lease clause. Ask the underwriter or broker what, precisely, they want to see — the answer is a document with specific contents, and once you know those you know what to buy.
The one place we can show you it named in BC
There is a live BC example, worth seeing because it shows the "type and level" structure in an instrument's own words rather than in ours.
Vancouver's Security Alarm System By-law No. 7111 — in the consolidation amended to include By-law No. 10642, effective January 29, 2013 — places a duty on alarm companies to attempt contact with the permit holder or a key holder before an alarm incident is passed on for attendance. Then section 30 carves out an exception:
Section 27 does not apply to an alarm system installed in a bank, trust company, or credit union, or any other alarm installation that requires Underwriter's Laboratories of Canada certification as Financial Type System, Level 1 to Level 4, or Commercial Type System, Level 1 to Level 4.
Notice what the by-law does not do: it never describes what any of those levels requires, and neither will we. What it confirms is the structure — certification is expressed as a type and a level, attached to an installation. "Any other alarm installation that requires," it says. Installation, singular, specific.
It also carries an operational consequence for commercial and strata sites. The Commercial Type limb is not an exotic carve-out for vaults; it is potentially you. If your installation falls inside it, the verification-call duty described in our article on false alarm costs in BC does not apply in the same way, which changes how your alarms flow. Good reason to know which type and level your certificate names — and a bad thing to assume in either direction.
What to ask for, and what it should name
Replace the unverifiable sentence with a verifiable one. Ask your provider, in writing:
"Please provide the certificate for this installation, showing the level and the expiry date."
If a certificate exists, it should tell you:
- The protected premises — the actual address and, on a multi-building or multi-suite site, which part of it. If it names a different site than the one you asked about, you have your answer.
- The type and level, which you then compare against what your insurer or contract asked for, in their words. Matching them is the whole exercise. A certificate at any level is not a certificate at the level.
- The monitoring facility it connects to, so the certificate and the service you actually receive describe the same arrangement.
- Dates — issue and expiry. Ask what triggers renewal, what it depends on, and who initiates it. The common failure here is not refusal; it is that nobody was assigned the calendar entry.
- Who issued it. A certificate comes from a certificating organization, not from the company selling you the service.
One more, about your own side: what would invalidate it? Certification describes an installation as it was assessed, and installations change — a device added, a panel swapped, a communication path reconfigured, a tenant renovation moving a wall. Ask which changes require notification, so a routine alteration next year does not quietly undo the thing your policy depends on.
An integrator who works in this space will answer all of it without difficulty. Vagueness on question 1 or 4 is itself a finding — not proof anything is wrong, but proof that nobody currently knows, which is operationally the same position as not having it.
A note on equipment, since it always comes up
Buyers expect a shopping list here, but the certificate is upstream of the shopping list, not downstream of it: the panel and devices are one element among the facility, the procedures, the redundancy and the records, and the best panel in the world installed against no certificate still produces no certificate.
Equipment choice is not neutral, though. For certificated-grade intrusion work our practice is to build on DSC, Bosch and Honeywell panels and devices — a standing position about product lines we stand behind, not an implication that buying a particular box makes an installation certificated. Nothing off a shelf does that. A document issued after an assessment does.
For the layer underneath — how a signal leaves your building and reaches a monitoring facility, and why the path matters as much as the panel — see how your alarm talks to monitoring. For what "ULC listed" means across Canadian security equipment generally, see what ULC listed means in Canada.
The short version
"ULC monitored" is a vendor attribute, and vendor attributes cannot be checked. A listing is a certification regime — covering the facility, its procedures, its redundancy and its record keeping — whose requirements sit in published standards we have deliberately not paraphrased here, and whose output is a certificate for a specific installation at a specific level valid to a specific date. Your requirement, if you have one, almost certainly comes from an insurer or a contract rather than a building code, which means nobody is going to catch the gap for you.
So do not argue about the adjective. Ask for the document, check it names your address, check its level matches what your paperwork demands, check the expiry, and find out who owns the renewal. Five minutes of asking replaces an unverifiable sentence with a verifiable one. That is the entire upgrade.
