Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Public Safety Fire Alarms topic
No spam. Unsubscribe anytime.
Council reviews ordinance changes to address nuisance fire alarms after rise in activations
Summary
Council members reviewed proposed changes to city code sections 280-3 and 280-4 to reduce repeated false and nuisance fire-alarm activations, discussed grouping by 911 address, staggered fees (example baseline $3.50 discussed), inspection requirements, and appeal processes; staff will refine language and return to council.
Council members and staff reviewed proposed amendments to local code (discussed as sections 280-3 and 280-4) intended to reduce unnecessary and nuisance fire alarms. Fire and code-enforcement staff reported that a small set of properties account for a large share of activations and that total activations increased from 334 in 2023 to 405 in 2024.
Staff said about 60 properties have alarm panels that connect to 911 and produce frequent activations; specific large parcels and campus-like properties were cited as driving most of the increase. Discussion focused on several potential changes: grouping counts by 911 address (so multiple buildings on one parcel count toward the same threshold), clarifying definitions for “unintentional activation” versus “nuisance alarm,” using a staggered fee schedule for repeat activations, and defining inspection and compliance expectations for third-party inspectors and licensed alarm contractors.
Participants discussed threshold examples used by staff: an alarm becomes a nuisance when there are two or more activations in a 48-hour period, three or more in a seven-day period, or four or more in a calendar year (language used by staff during the meeting). Staff discussed a staged fee structure as a compliance tool; one example mentioned in the meeting described a base administrative fee of $3.50 as a minimum and noted that the true operational cost per call — including overtime — could be “over $400” when fully accounted for. Council discussed the need to allow administrative review and an appeal to the Board of Public Service and to provide reasonable timeframes for property owners to correct problems when replacement parts are not immediately available.
Staff emphasized that the ordinance’s aim is compliance rather than punishment: if a property owner communicates promptly and is taking steps to repair an alarm, captains have discretion in counting events as a single incident. The meeting also noted enforcement challenges where large institutional property owners self-permit or operate under different inspection regimes, limiting the city’s leverage.
No vote was recorded. Council and staff agreed to refine the proposed language (including whether to index counts to 911 address) and to return for further consideration at a subsequent meeting; staff indicated a follow-up conversation would occur in two weeks.
Why this matters: Repeated unnecessary alarms consume emergency resources, create public-safety risk by diverting responders, and impose costs on the city. Defining nuisance thresholds, appealing processes, and reasonable compliance windows are central to both public-safety and fairness concerns.
Next steps: Staff to refine definitions, draft staggered fee language and appeal procedures, and return to council for further action; no ordinance number or final fees were adopted during the meeting.
