False alarms and what they actually cost you in BC

Either an invoice landed on your desk with a number on it you weren't expecting, or you've realized you're on your third alarm this year and someone should probably look into what that means. Both are the same question underneath: what does a false alarm actually cost, and who decides?

The answer people want is a table — seven Lower Mainland cities, a dollar figure beside each. We're not going to give you that, and the reason is the most useful thing in this article: that table would be wrong within a year, and it is probably already wrong on whichever municipal web page you found it on.

Here is what to understand instead.

There is no BC false alarm rule. There are dozens.

False alarm charging is municipal. Each city or district writes its own bylaw, sets its own model, and revises the numbers on its own schedule. There is no provincial standard sitting behind them, and — this is the part that catches multi-site owners — the models are not variations on a theme. They are structurally different from one another.

Three municipalities, verified against the actual bylaws, make the point.

Burnaby: escalating by count, with a grace allowance

Burnaby's false alarm fees are set out in the Consolidated Fees and Charges Bylaw No. 14485C, Schedule A5. As printed in that consolidation (retrieved 10 August 2026), the police false alarm fees, per calendar year, are:

• First false alarm: free
• Second false alarm: free
• Third false alarm: $225.00
• Fourth false alarm: $300.00
• Fifth and each subsequent false alarm: $400.00

Two things matter here more than the amounts. First, the counter resets each calendar year — two in November and two in February costs nothing, while four inside one calendar year costs $525. (The schedule says only "in a calendar year"; it does not say whether the count follows the premises or the permit holder, so confirm that with the City if you run several sites.) Second, the escalation is steep and open-ended at the top. A chronically faulty rear door contact isn't a $225 problem; by the sixth alarm it's a $400-per-event problem with no ceiling in sight.

Surrey: charged from the first one, escalating on late payment

Surrey works on a completely different axis. Fees are charged under the Surrey Security and Fire Alarm By-law, 1997, No. 13168, and set in the Surrey Fee-Setting By-law, 2001, No. 14577. As printed in that fee-setting bylaw (retrieved 10 August 2026):

• False Alarm Fee, paid within 14 days of the invoice: $133.00
• False Alarm Fee, paid after 14 days of the invoice: $165.00
• Fire False Alarm Fee: $286.00

All fees are subject to applicable taxes. Surrey's alarm by-law itself — By-law No. 13168, read on 10 August 2026 — also sets a minimum penalty for a violation of that by-law at a fine of $75.00, separate from the false alarm fee.

Read those two lists side by side and the trap is obvious. There is no free allowance in Surrey; you're billed on the first one. And the escalation isn't driven by how many alarms you had — it's driven by whether accounts payable processed the invoice inside fourteen days. If your invoices route through a property manager, a strata treasurer, or a head office in another city, that fourteen-day window is a real operational risk and it has nothing to do with your alarm system at all.

A Burnaby site owner reasoning from experience would assume the first two are free and would not treat the invoice as urgent. Both assumptions are wrong in Surrey.

Vancouver: a duty on the alarm company, before anyone is dispatched

Vancouver's route is different again, and it's the one most often described inaccurately. Security Alarm System By-law No. 7111 (consolidated for convenience, amended to include By-law No. 10642, effective 29 January 2013) puts an obligation on the alarm company, not on you.

Section 27: before notifying the Police Department of an alarm incident originating from a monitored alarm system, an alarm company must contact — by telephone or other electronic means, to establish whether the incident is a false alarm — the permit holder at the alarmed premises, or, if the permit holder is not available, one of the three key holder references.

Section 29 is the enforcement edge: if the Police Department receives notice of an alarm incident and the alarm company has not complied with section 27, the Police Department may refuse to provide attendance to the premises where the security alarm system is located.

Be precise about what that does and does not say. It is a condition on the alarm company's conduct on a specific incident. It is not a condition attached to your permit, and it is not a general power to decline attendance. And it is emphatically not "verified response" — none of the municipalities surveyed here operates a verified-response model where attendance requires independent confirmation that a break-in is occurring. Vancouver's is a call-verification duty, which is a different mechanism with a different failure point.

The practical consequence for most sites is unglamorous but concrete: your monitoring provider is going to try to reach you or your keyholders first. Which means the quality of your contact list is, in Vancouver, upstream of whether anyone attends at all.

There is an exception, and it may be yours. The by-law carves out alarm systems installed in banks, trust companies and credit unions, and any installation requiring ULC certification as a Financial Type System or a Commercial Type System, Levels 1 to 4. For a site in that category no verification call is owed, so the keyholder list is not upstream of attendance in the same way. If you hold a ULC certificate for your installation, check which type and level it names before you assume this section applies to you.

The rule and the price usually live in different documents

Notice what happened above. Surrey's alarm bylaw — the instrument that creates the obligation — contains no fee amounts at all. It says the owner must pay the City a fee for each false alarm as specified in the Surrey Fee-Setting By-law, 2001, No. 14577, "as may be amended." The rule is in one bylaw; the price is in another, and that second one is revised on its own cycle.

Burnaby and Vancouver embed a schedule, so the rule and the number travel together. Elsewhere, the pattern varies again — some municipalities publish an information page that links out to a PDF held somewhere else entirely.

This is why municipal web pages so often show superseded figures: the page is almost never the instrument. A web page is a summary written by a communications team at some point in the past, describing a fee-setting bylaw that has since been amended by council. Nobody is doing anything wrong. The page is simply not the thing that has legal effect, and it doesn't get updated every time the thing that does gets amended.

Which is also why every figure in this article carries a date and a document name — including ours. We printed Burnaby's and Surrey's amounts because we read them out of the current fee bylaws on 10 August 2026. We deliberately did not print Vancouver's permit and reinstatement fees, because the consolidation we can verify is the 2013 one, and thirteen-year-old numbers presented without that caveat are exactly the failure this article is about.

What to actually do with this

Find your own municipality's fee-setting bylaw, not its web page. Search the city's bylaw library for the alarm bylaw, then follow it to whichever bylaw sets the fees. That second document is the one to bookmark and re-check annually.

Do not reason about one city from another. Richmond, Coquitlam, New Westminster, the North Shore municipalities, Langley, Delta, Abbotsford and everywhere else each have their own bylaws, and we have not verified any of them — so we're not going to tell you what they say. If you hold sites in more than one municipality, you need the actual bylaw for each one. There is no shortcut here, and anyone who hands you a tidy seven-city table is guessing on at least a few rows.

Date-stamp anything you circulate internally. If you're a property manager sending a memo to owners, put the retrieval date and the bylaw number in it. Otherwise your memo becomes next year's wrong web page.

The causes worth fixing before the next invoice

Most repeat false alarms at commercial and strata sites come from a short list of ordinary, fixable things:

• Doors that don't seal properly. A warped or dragging door lets a magnetic contact break in the wind. This shows up as alarms clustered on windy nights.
• Motion detectors aimed at moving air or moving objects. Heating vents, hanging signage, balloons, and seasonal decorations all trip passive infrared sensors. So do ceiling-mounted fans on a timer nobody remembers setting.
• Pets, pests and cleaning crews. Rodents inside a warehouse trip sensors reliably. So does a cleaning contractor whose schedule changed and whose code was never issued.
• Staff turnover with no code hygiene. Shared codes, codes taped inside a cupboard, and a departed employee's code that still works are all sources of alarms nobody can explain afterward.
• Dead or dying batteries and end-of-life sensors. Wireless devices degrade quietly and generate erratic signals well before they fail outright.
• A stale keyholder list. This one deserves its own line, because it's the one that converts a recoverable alarm into a billable one. The verification call gets made; the number rings a phone that belongs to a supervisor who left eighteen months ago; nobody confirms it's a false alarm; the event proceeds as real. The system worked exactly as designed and you still got billed.

The keyholder list is also the cheapest thing on this list to fix. Review it quarterly, keep three genuinely reachable contacts on it, and make sure at least one of them can attend the site rather than merely answer a phone. In Vancouver in particular — where, outside the ULC-certified and financial-institution exceptions above, the verification call is a bylaw duty rather than a courtesy — that list is doing more work than most owners realize.