Fire Alarm False Alarm Management: Confirmed Alarm Systems, Investigation Zones and CFOA Guidance

Summary

False alarms from fire detection and alarm systems are a major operational issue for the UK fire and rescue service. The NFCC reports that in a typical year, over 95% of fire brigade responses to automatic fire alarm signals are false alarms — either from equipment faults, unwanted alarm signals (cooking fumes, steam, dust), or malicious activations of manual call points. This wastes fire brigade resources, disrupts building occupants, and erodes confidence in fire alarm systems.

For the fire alarm installer and designer, false alarm management is a BS 5839-1 obligation, not an optional service upgrade. Annex C of BS 5839-1:2017 provides a decision framework for selecting appropriate false alarm countermeasures based on the likely sources of false alarms. The choice of detector technology, zone design, alarm confirmation strategy, and operational procedures all contribute to false alarm reduction.

Understanding the available tools — confirmed alarm systems, investigation alarms, coincidence detection, and detector technology — allows the designer to specify the right countermeasures for the specific risk profile of the building.

Key Facts

• Unwanted alarm signal (UAS) — the BS 5839-1 / NFCC preferred term for what was previously called a false alarm; includes equipment false alarms (device malfunction), unwanted alarms (cooking, steam, dust), and malicious activations
• NFCC (formerly CFOA) — National Fire Chiefs Council; issues guidance on responding to repeated false alarms; has power to suspend automatic fire brigade response
• AFBR (Automatic Fire Brigade Response) — the arrangement where an ARC automatically requests fire brigade attendance when an alarm is received; repeated UAS can lead to AFBR suspension
• BS 5839-1:2017 Annex C — the false alarm management annex; decision flowchart and countermeasure descriptions
• Alarm confirmation system — panel configured so that a general alarm is not generated until a second device activates, or a responsible person confirms the alarm is genuine
• Investigation alarm — a limited audible signal (buzzer or panel sounder only) that alerts a responsible person to investigate before triggering full evacuation
• Coincidence detection — requires two devices in the same or adjacent zone to activate before alarm; reduces single-device false alarms
• Class A detector — BS EN 54 performance classification; enhanced false alarm rejection built into detector algorithm; reduces UAS from dust, steam, aerosols
• Time-based alarm routing — during working hours, investigation alarm → staff investigate; outside hours, direct full alarm; reduces daytime UAS disruption
• Pre-alarm stage — first detector activation triggers pre-alarm (staff alert only); second activation triggers full alarm; 3–5 minute investigation window typical
• BS 5839-1 Clause 23 — coincidence detection requirements; conditions for safe use
• Detector contamination — dirty detectors are a leading cause of UAS from equipment; annual cleaning is mandatory; contaminated detectors must be replaced
• Manual call point malicious activation — dual-action call points (lift cover then break) reduce malicious UAS; resettable call points allow test without glass replacement

Quick Reference Table

Detailed Guidance

BS 5839-1 Annex C: The Decision Framework

Annex C provides a structured approach to reducing unwanted alarms. The key recommendation is to address false alarm causes in priority order — the correct order is:

1. Investigate the cause of existing false alarms before applying countermeasures
2. Correct the root cause where possible (replace contaminated detectors, relocate detectors away from steam)
3. Apply the minimum countermeasure that addresses the cause without compromising detection
4. Review the outcome and apply additional countermeasures if the first step is insufficient

This hierarchy prevents over-engineering the solution. Applying coincidence detection as the first response to a kitchen false alarm is disproportionate — relocating the detector or changing it to a heat detector may be sufficient.

Annex C flowchart summary:

UNWANTED ALARM SIGNAL RECEIVED
├── Single occurrence? → Investigate cause; no countermeasure change yet
├── Repeated from same device?
│   ├── Contamination? → Clean or replace detector
│   ├── Wrong detector type for location? → Change to appropriate type
│   └── Genuine environmental issue? → Change detector type or relocate
└── Pattern from multiple devices / general alarm for same cause?
    ├── Apply alarm confirmation (investigation alarm or coincidence detection)
    ├── Review automatic fire brigade response arrangements
    └── Consider time-based alarm routing

Alarm Confirmation Systems

An alarm confirmation system introduces a delay or additional trigger requirement between the first alarm signal and the full evacuation alarm. The design intent is to give a responsible person time to investigate and confirm or cancel the alarm.

Types of alarm confirmation:

Type A — Sequential confirmation: Two detectors in the same zone must activate (within a defined time window) before the general alarm. The first activation generates a pre-alarm (investigation signal). If no second device activates within the window, no general alarm is generated. Only applicable where at least two detectors are in the zone — cannot be applied to a single-detector zone.

Type B — Time-delay confirmation: The first device activation generates a pre-alarm. The responsible person has a defined investigation period (typically 2–3 minutes) to investigate and cancel. If not cancelled within the period, the full alarm activates automatically. Suitable for attended premises with a security desk or reception.

Type C — Alarm confirmation input: First activation generates a pre-alarm. An on-site responsible person must positively confirm the alarm (via keypad input, confirmation button, or communication to the ARC) before the general alarm activates. More controlled than Type B but relies on the responsible person being available.

When alarm confirmation is acceptable:

• Attended premises during working hours where investigation can be guaranteed within the time window
• Areas with known false alarm sources where the cause cannot be eliminated

When alarm confirmation is NOT acceptable:

• Sleeping risk buildings (hotels, care homes, HMOs) during sleeping hours — any delay to alarm risks lives
• Unattended premises where no one is available to investigate
• High fire-load areas where fire can spread rapidly during the investigation window
• Where the cause-and-effect requires immediate suppression system activation

NFCC guidance on alarm confirmation: The NFCC supports the use of alarm confirmation to reduce unnecessary fire brigade responses, but requires that the investigation procedure is formalised, that staff are trained, and that the investigation time is proportionate to the fire risk.

Automatic Fire Brigade Response (AFBR) and Its Suspension

When a fire alarm system is monitored by an ARC, the ARC can be configured to automatically request fire brigade attendance on receipt of an alarm signal. This is AFBR.

How AFBR suspension works: Fire and rescue services (FRSs) track AFBR calls and the resulting outcomes. When a premises generates a high number of false alarm responses within a defined period, the FRS contacts the responsible person with a formal warning. Continued false alarms lead to a review meeting, and persistent non-compliance leads to AFBR suspension — the ARC is notified not to request fire brigade response automatically.

Consequences of AFBR suspension:

• Fire brigade attendance becomes dependent on a human operator confirming the alarm (usually by calling the fire brigade directly)
• This introduces delay — during which fire can develop significantly
• Insurance implications: insurer may view AFBR suspension as a material change affecting cover

Avoiding AFBR suspension:

• Implement false alarm management proactively at commissioning stage
• Use confirmed alarm arrangement (investigation alarm + second activation) for problematic areas
• Ensure annual maintenance is thorough — dirty detectors are the leading cause of UAS
• Train staff on correct alarm response (do not automatically assume false alarm; investigate first)

Technology-Based False Alarm Reduction

Multi-sensor detectors: Combining optical smoke and thermistor measurements in one device. The onboard algorithm requires both sensors to agree before triggering an alarm. Steam triggers the optical chamber but not the thermistor — no alarm. Dust triggers the optical chamber but not the thermistor — no alarm. Both sensors activating together indicates a genuine fire signal. Significantly better false alarm rejection than standard optical detectors. Small cost premium over standard detectors; recommended for any area with moderate false alarm risk.

CO fire detectors (BS EN 54-26): Carbon monoxide is produced by smouldering fires before visible smoke develops. CO fire detectors are less susceptible to steam and dust false alarms than optical detectors. Recommended by BS 5839-1 Annex C specifically for sleeping risk areas where a UAS at night is particularly disruptive and costly.

Class A detector certification: BS EN 54-7 Class A classification means the detector has passed enhanced false alarm tests beyond the standard requirements. Class A detectors have internal algorithms that reject slow temperature rises, background smoke levels, and transient particles that would trigger standard detectors. Specify Class A where false alarm risk is high.

Beam detector technology: Beam detectors cover large open spaces. They are less susceptible to localised sources of false alarms (a single cooking event, a person vaping near a detector) because they integrate smoke density across the full beam path. They can false alarm from vibration-induced beam misalignment and from accumulated dirt on the lens — both preventable with correct installation and maintenance.

Manual Call Point False Alarm Reduction

Manual call point (MCP) activations can also be unwanted alarms — either from curiosity, malicious intent, or accidental activation.

Dual-action MCPs: Require the user to lift a cover or flip a guard before breaking the glass. Reduces casual activation significantly. BS EN 54-11 recognises dual-action as a valid MCP type. The additional action should not significantly delay genuine emergency activation — it is a brief second step, not a barrier.

Break glass guards / covers: A clear polycarbonate cover fitted over the MCP that requires deliberate action to remove before operation. Common in schools and public buildings where malicious activation risk is high.

Resettable MCPs: Some MCPs use a key-reset mechanism instead of a break glass — the glass element is not consumed on activation and no glass replacement is needed. Useful in high-activation environments where replacement cost accumulates.

CCTV monitoring of MCPs: Placing MCPs within the field of view of CCTV cameras deters malicious activation and provides evidence for prosecution. The deterrent effect is high if signage indicates CCTV is in use.

Frequently Asked Questions

What is the maximum number of false alarms before the fire brigade suspends AFBR?

There is no single national threshold — each fire and rescue service sets its own policy based on NFCC guidance. Typically, a first warning letter is issued after a defined number of unwanted alarm responses within a 12-month period (often 3–5 UAS). Continued false alarms lead to a formal review meeting, with AFBR suspension possible if the pattern continues without improvement. Contact the local FRS's fire safety team for the specific policy in your area.

Can I apply coincidence detection to the entire building to reduce false alarms?

Technically yes, but it should not be applied uniformly. Annex C identifies zones where coincidence detection is inappropriate — sleeping risk areas, high fire-load areas, and areas with limited escape time. Blanket coincidence detection applied without risk assessment analysis could delay alarm in genuinely high-risk areas. Always apply the Annex C decision framework zone by zone, not as a building-wide shortcut.

Does cleaning fire detectors reduce false alarms?

Yes, significantly. Dirty detectors — where dust accumulates on the optical chamber's lens or photoelectric surfaces — become progressively more sensitive over time. A detector at 25% compensation (drifting towards alarm threshold due to dirt) will alarm on a much smaller smoke signal than a clean detector. Annual cleaning, supplemented by mid-year checks in dusty environments, prevents drift-induced false alarms. Replace detectors that have drifted beyond the manufacturer's compensation limit.

If a premises has AFBR suspended, can it be reinstated?

Yes. The FRS typically requires evidence that the false alarm causes have been investigated and addressed before reinstating AFBR. This may involve: a formal false alarm audit, a maintenance inspection confirming all detectors are clean and calibrated, and an alarm management plan showing what operational and technical countermeasures have been implemented. Once the FRS is satisfied, AFBR is reinstated on a probationary basis, with the understanding that further false alarms will lead to immediate re-suspension.

Who is responsible for false alarm management — the installer or the responsible person?

Both. The installer is responsible for correct design (appropriate detector types for the environment), correct installation (no interference sources), and correct configuration (alarm confirmation where appropriate). The responsible person is responsible for ongoing maintenance (annual inspection, prompt repair of faults), staff training (correct alarm response, weekly call point tests), and operational procedures (not leaving toast under a detector). The BS 5839-1 Annex C framework is a joint responsibility — the installer implements technical measures, the responsible person implements operational measures.

Regulations & Standards

• BS 5839-1:2017 Annex C — false alarm management strategies; the UK code of practice reference for UAS reduction

• BS 5839-1:2017 Clause 23 — coincidence detection requirements and conditions for use

• BS EN 54-7:2000+A2:2006 — smoke detectors; Class A classification for enhanced false alarm rejection

• BS EN 54-26:2015 — CO fire detectors; relevant for sleeping area false alarm reduction

• BS EN 54-11:2001+A1:2005 — manual call points; dual-action types

• NFCC (CFOA) Guidance on Reducing False Alarms — national fire chiefs guidance on alarm signalling policy

• Regulatory Reform (Fire Safety) Order 2005 — responsible person's obligation to maintain a functioning fire alarm system

• NFCC False Alarm Guidance — National Fire Chiefs Council position on false alarm management and AFBR suspension

• BS 5839-1:2017 Annex C — BSI standard; Annex C false alarm management framework

• FIA False Alarm Reduction Guide — Fire Industry Association practical guidance on reducing UAS

• BAFE False Alarm Management — BAFE guidance within SP203-1 context

• CFOA Good Practice Guide on False Alarms — Archived CFOA (now NFCC) guidance; still widely referenced

• bs 5839 1 fire alarm standard — Annex C is part of this standard

• fire alarm detector types — Detector type selection as primary false alarm prevention

• fire alarm zoning design — Coincidence detection and zone design interaction

• fire alarm commissioning procedure — Commissioning tests that verify false alarm management configuration

• nsi bafe sp203 1 certification — SP203-1 certified companies obligated to address false alarm management

• alarm receiving centre arc — ARC's role in managing AFBR and false alarm notifications