Never assume a repeated activation is false until the first event and area have been checked
Follow the premises fire procedure, capture the panel information before reset and use formal impairment controls where detectors or zones need to be isolated for investigation or building work.
MOST LIKELY CAUSES
Start with the first event and environment
Symptom variations Match the exact timing, location and environmental pattern. ⌄
- Alarm repeats with no obvious fire
- Same zone appears frequently
- Events occur at similar times
- Alarm follows cleaning, cooking or weather
- System resets but activates again
Safe first checks Checks for authorised site staff before engineering work. ⌄
- Treat the activation as genuine until the area is checked.
- Record the first zone, address, device and time before reset.
- Check for steam, dust, aerosols, insects, water or nearby work.
- Review whether the same device or time pattern repeats.
- Do not leave detectors covered, removed or disabled without formal controls.
Step 1 — Treat each activation as genuine first Treat every activation as genuine until the first event and cause are confirmed. ⌄
Follow the premises fire procedure until the cause is confirmed.
Step 2 — Capture the first event Treat every activation as genuine until the first event and cause are confirmed. ⌄
Record the exact zone, address, device text, time and event sequence before reset.
Step 3 — Look for a repeatable pattern Treat every activation as genuine until the first event and cause are confirmed. ⌄
Compare weather, occupancy, cooking, cleaning, maintenance and building-work activity.
What the activation usually means How this unwanted-alarm pattern develops. ⌄
Repeated fire alarm activations should be investigated from the first event recorded at the panel. Common causes include contamination, steam, dust, insects, water ingress, unsuitable detector type, poor siting or a failing device.
Engineer diagnostic sequence Competent-person checks after the site information has been captured. ⌄
- Review chronological event logs and analogue values.
- Identify whether the same device or environmental condition recurs.
- Check detector type and siting against the actual risk.
- Inspect for contamination, insects, moisture and cable damage.
- Confirm any replacement or design change through controlled testing.
Information and equipment needed Useful items for accurate investigation. ⌄
- Panel event log and first-event record
- Detector type, address and location
- Recent work, cleaning and weather history
- Manufacturer diagnostics and analogue values
- Approved cleaning and functional test equipment
Parts that may be involved Components commonly associated with this problem. ⌄
- Replacement detector
- Detector base
- Protective dust cover for temporary works
- Insect-resistant measures
- Updated cause-and-effect or device schedule
When immediate action is required Conditions that should trigger escalation or an impairment plan. ⌄
- The activation source cannot be confirmed.
- The same detector or area repeatedly causes evacuation.
- Building work is contaminating multiple devices.
- Water ingress, cable damage or external equipment is involved.
- Detectors are being covered or removed without control.
- The system cannot be returned to normal reliable operation.
Frequently asked questions Common unwanted-alarm questions. ⌄
Can a detector simply be moved away from steam or cooking?
Not without reviewing the design, coverage and fire strategy. Any relocation or detector-type change should be controlled and documented.
Should a detector that keeps triggering always be replaced?
No. The environment, base, wiring, type and siting should be checked as well as the detector head.
Can detectors be covered during building work?
Only under a managed impairment procedure with suitable temporary measures and prompt removal of covers when work stops.