Alarm Permits, False Alarm Fines and the Dealer's Part
Why this matters
The first time many customers hear that their city requires an alarm permit is when a letter arrives after their third false alarm, carrying a fine and a warning that police response may be suspended. They call the dealer, and the call goes badly, because from the customer's side nobody told them. Most of that is avoidable at the sale. The dealer cannot write the ordinance, but it controls what the customer is told, whether the permit number is on the account, and whether the false alarm record exists before the city's letter does.
What alarm ordinances usually contain
There is no national alarm ordinance. Cities, counties and sometimes states write their own, and they differ in almost every detail. The pieces below appear often enough that a dealer should expect them and check for each one locally.
- A user permit or registration. The alarm user (usually the homeowner or tenant, sometimes the property owner) registers the system with the city or the police department, gets a permit number, and in many places renews it each year. Some localities charge for it; some do not.
- No permit, no dispatch, in some places. A few ordinances direct the agency not to respond, or to respond at lower priority, to an alarm at an unpermitted address, and require the monitoring company to give the permit number on every dispatch request.
- Counting false dispatches. The agency tracks dispatches that turn out to be false, usually per permit year. A false alarm is generally defined as a dispatch with no evidence of a crime or emergency; weather and power events are treated differently from one ordinance to the next.
- An escalating fine schedule. A set number of free false dispatches in the permit year, then fines that step up with each further one.
- Suspension. After a set count, the permit is suspended and the agency stops responding until the user does something: fixes the system, takes a class, pays outstanding fines, or shows the system was serviced.
- Obligations on the alarm company. Some ordinances license or register alarm businesses, require two-call verification before dispatch on burglary signals, require CP-01 compliant panels on new installs, or fine the alarm company directly for false alarms caused by its installation or its operator skipping verification.
- An appeal process. Usually a written appeal within a short window after the notice. The dealer's records are often the evidence.
The numbers that matter (how many free dispatches, the step size of the fines, the suspension count, the appeal window) are set locally and change when the ordinance is amended. Read the current ordinance for each city and county you work in and keep a one-page summary per jurisdiction where the office can find it.
Who owns what
| Task | Owner | Why |
|---|---|---|
| Applying for and renewing the user permit | Customer, in most ordinances | The permit is in the user's name |
| Telling the customer the permit exists | Dealer, at sale | Nobody else is in a position to |
| Putting the permit number on the account | Dealer and central station | Some agencies will not take a dispatch request without it |
| Verification before dispatch | Central station, under the dealer's instructions | Often required by ordinance |
| Keeping the false alarm record | Dealer | It is the evidence for a fix, a follow-up and an appeal |
| Fixing the cause of a false alarm | Dealer, if it is equipment or programming | The customer cannot |
| Paying fines | Usually the customer; sometimes the dealer, where the ordinance charges the company | Depends on the ordinance |
The line that trips dealers up is the last one. Where an ordinance can fine the alarm company, a false alarm caused by an installation fault or a skipped verification call is the dealer's cost, and the record has to show which kind it was.
What the dealer does, in order
At sale. Tell the customer, in plain words, that the city or county requires a permit if it does, what it costs to get (in hours of their time, if not money), how many false alarms are allowed before fines start, and that the fines are theirs. Give them the form or the link to the jurisdiction's registration page. Put it in the contract paperwork as well as saying it.
At activation. Do not activate dispatch on an account in a no-permit, no-dispatch jurisdiction until the permit number is in hand, or until the station's procedure for a pending permit is set. Enter the permit number and its expiry date on the account in your system and confirm the station has it. See related: The Monitoring Activation and Account Onboarding SOP.
At renewal. If the jurisdiction renews annually, set a reminder ahead of the expiry date. An expired permit can turn the next alarm into a no-response or a fine for the customer and a support call for you.
After every false dispatch. Log it: date, time, zone, cause (user error, equipment, environment, unknown), what was done, and whether the operator followed verification. Call the customer within a business day, find the cause, fix it or schedule the fix, and record what you did. See related: The False Alarm Follow-Up SOP.
At the threshold. Know where each account sits against its jurisdiction's free count. An account one dispatch away from fines or suspension gets a service visit and a training session, not another reminder.
Worked example: one account through a permit year
A residential account sits in a city whose ordinance, as summarized in the dealer's jurisdiction file, allows two false dispatches free in the permit year, fines each further false dispatch on a rising schedule, and suspends response after the fifth false dispatch in the year until the user shows the system has been serviced. The permit year runs from the permit's issue date. These are this city's terms; the next town over differs.
Month 1. Installed and activated. The dealer gave the customer the permit form at sale, and the permit number was entered on the account before activation. Expiry date entered, renewal reminder set eleven months out.
Month 3. False dispatch 1. A new house cleaner tripped the back-door entry delay without a code. The operator's two calls rang out and the station dispatched. Cause: user error, no user code. The dealer adds a code for the cleaner and walks them through the keypad. Logged.
Month 5. False dispatch 2. Front-door alarm at 15:00, nobody home. The dealer pulls the signal history: an alarm and restore on the front door with no opening before it. The tech finds the door contact's magnet loose on a door that had been planed after it started sticking, so the gap had grown past the contact's rating (see related: Door and Window Contact Types and Gap Ratings). Cause: equipment, dealer-repairable. Fixed and logged. That is the last free dispatch for the year.
Month 8. False dispatch 3. Hall motion alarm at 02:00 while the family is away. The history shows a single zone, no second zone, and the operator's calls unanswered. The tech finds a new portable heater blowing across the detector's view. Cause: environment. The customer moves the heater, the dealer adds a note on detector placement to the training record. This one is fined, the first under the schedule.
At this point the dealer's record shows three dispatches with three different causes, each found and fixed within days. Two more and response is suspended.
The dealer's next moves:
- Review the account's programming against CP-01 defaults (see related: False Alarm Reduction Features in the SIA CP-01 Standard). The exit delay is found at 30 seconds, set short at the customer's request at install. It is reset to the panel's compliant default.
- Offer video verification on the back door and hall, where two of the three alarms happened (months 3 and 8), so the operator can see what tripped them before calling the agency.
- Retrain every household member and the cleaner on arming stay and on cancelling with the passcode.
Month 12. No further false dispatches. The permit renewal reminder fires a month before expiry; the customer renews; the dealer updates the expiry on the account. Three false dispatches in the year: two free, one fined, none suspended.
What the record bought. When the city's fine letter for month 8 arrived, the customer called upset. The dealer could say exactly what happened on each date, what was fixed, and what was changed to stop a fourth. Had the month 5 alarm instead been caused by an installation fault the dealer should have caught, and had this ordinance charged the alarm company for that kind of false alarm, the record would also have shown who owed it.
Where the dealer gets this wrong
- Treating the permit as the customer's problem only. Legally it may be; operationally, a suspended account is a monitoring contract that delivers nothing and a customer who will not renew.
- Activating without the number in a jurisdiction that requires it on dispatch requests. The first real alarm reaches an agency that will not roll.
- Logging false alarms in the station's records only. The station logs the event. It does not record cause, fix and customer conversation, and those are what an appeal and a follow-up need.
- Using one ordinance summary for the whole service area. City and unincorporated county rules often differ for addresses a mile apart.
References
- The current alarm ordinance for each city and county in the service area
- The responding agency's alarm response and permit procedures
- See related: The False Alarm Follow-Up SOP
- See related: The Monitoring Activation and Account Onboarding SOP
- See related: Alarm Verification Methods: Calls, Video and Audio