Fire Alarm Weekly Test: Procedure, Log, and Common Problems
The weekly fire alarm test is the most frequent interaction most people have with their fire alarm system. Done correctly, it takes about two minutes and provides an early warning of faults that could prevent the system from working in a real emergency. Done incorrectly — or skipped entirely — it's one of the most common findings during fire safety inspections.
This guide covers what the test should involve, who should do it, what to record, and what to do when something doesn't work as expected.
What BS 5839-1 Requires
BS 5839-1:2017 Clause 46.1 states that the fire detection and fire alarm system should be tested at intervals not exceeding seven days. The test should:
- Activate at least one manual call point (MCP) to confirm that the alarm sounders operate
- Rotate the MCP used each week, so that every MCP is tested regularly (the rotation ensures all MCPs are exercised over time, not just the one nearest the main entrance)
- Be carried out at a consistent time to minimise disruption and so building occupants learn to recognise it as a test
The standard does not require every detector to be tested weekly — that level of testing is part of the scheduled maintenance inspection (typically every 6 months under Clause 45 for systems in occupied buildings).
Who Is Responsible
The weekly test should be carried out by the "responsible person" or their nominated representative. Under the Regulatory Reform (Fire Safety) Order 2005, the responsible person is the employer (for workplaces) or the person in control of the premises.
In practice this is typically:
- A facilities manager or building manager
- A designated member of staff who has been trained in the procedure
- A security officer in buildings with 24/7 security presence
The test should not require a fire alarm engineer — it is a simple operational task, not a technical inspection. If building staff are unable to carry out the test without calling an engineer each week, that is itself a problem worth addressing.
Step-by-Step Procedure
Before the test
-
Notify the alarm receiving centre (ARC) — if your system is monitored, call the ARC to tell them you are about to carry out a test. Give them the site name, your name, and a password or PIN if required. This prevents a false alarm response from the fire brigade.
-
Notify staff — announce the test is about to begin, especially if the sounders are loud. In offices with open plans, this prevents unnecessary evacuation and distress.
-
Identify which MCP to test this week — check the test log to see which MCP was last tested, and move to the next one in the rotation.
The test
-
Operate the MCP — insert the test key (or use a ballpoint pen tip on key-operated MCPs) and rotate or press as appropriate. The MCP should activate.
-
Confirm the sounders operate — all sounders within the building (or relevant sounder zone) should activate audibly. For two-stage systems, the alert tone should sound first, escalating to full evacuation tone after the delay period.
-
Confirm the panel shows alarm condition — walk to the fire alarm panel and confirm it displays the alarm, showing the correct zone or device address.
-
Check for any other expected activations — if the system has outputs to door holders, dampers, or a BMS, check these are operating as expected (or confirm with staff in relevant areas).
After the test
-
Reset the panel — use the reset key or button on the panel. The sounders should silence, and the panel should return to normal.
-
Confirm the MCP has reset — visually inspect the MCP to confirm the element is back in its normal position. On some MCPs, the element (break glass or resettable element) must be manually reset after activation.
-
Notify the ARC — call back the ARC to confirm the test is complete and the system is back in normal operation.
-
Log the test — record the date, time, which MCP was tested, who carried out the test, and the result. Note any anomalies.
What to Log
The fire alarm log book (physical or digital) should record for each weekly test:
| Field | Example entry | |---|---| | Date | 05/07/2026 | | Time | 09:00 | | MCP tested | Zone 3, MCP 14 (1st floor south stairwell) | | Sounders operated | Yes — all zones | | Panel confirmed alarm | Yes | | Reset successful | Yes | | ARC notified before/after | Yes — reference 4821 | | Tested by | J. Smith (Facilities) | | Any faults noted | None |
If a fault is found during the test, note it in full — what was observed, what the panel displayed, what action was taken, and whether an engineer call-out is required.
Common Problems Found During Weekly Tests
Sounders not audible in part of the building
If you can hear sounders in some areas but not others, there may be a sounder fault on that circuit — the weekly test is your first indication. Note which areas couldn't hear the alarm and report to your fire alarm maintenance contractor.
Panel shows fault alongside alarm
If the panel shows a fault condition as well as the alarm when you activate the MCP, note the fault code or fault description. Some faults (like a mains fail fault from a power outage the night before) are incidental. Others (like a detector fault on the same zone you're testing) need investigation.
MCP didn't activate / no alarm
If operating the MCP produces no response:
- Check you're using the correct key and turning it the right way
- Check the panel is not already in engineer test mode (which suppresses sounders)
- Check the MCP is connected and the zone isn't isolated
- If the MCP is genuinely unresponsive, log it as a fault and contact your maintenance engineer
Do not consider a non-response as "the panel was fine last week so it must be fine." A non-functioning MCP is a fault that must be resolved.
Panel won't reset
If after operating the reset the panel doesn't return to normal — sounders continue, or the alarm indicator remains on — there may be a latched fault, or a second device has activated (cross-contamination in plant rooms with heavy dust, for example, can cause a nearby detector to activate shortly after the MCP reset).
Check the panel display for any remaining active zones or devices. If a device other than the MCP you tested is showing alarm, investigate before leaving.
Test was missed this week
If the weekly test is missed, record the reason in the log ("Building closed — public holiday") and carry out the test as soon as possible. The standard says intervals not exceeding seven days — a single missed test is not a major violation, but a pattern of missed tests is.
Maintaining the MCP Rotation
The purpose of rotating MCPs is to ensure that every MCP is physically exercised and confirmed functional, not just the most convenient one. For a building with 20 MCPs tested weekly, each MCP will be tested approximately once every five months.
Some organisations use a numbered sticker system — each MCP has a number, and the test log references the number. Others keep a simple diagram with MCPs marked and tick them off as they rotate.
For very large buildings with hundreds of MCPs, the weekly test may still use a single MCP, but the 6-monthly and annual engineer inspection provides the detailed device-by-device testing.
Digital Log Books
Many organisations are moving from paper log books to digital fire safety record systems. The weekly test record is one of the most frequently updated entries. A digital system should allow quick entry on a mobile device, automatic timestamp, and a clear audit trail showing when tests were carried out and by whom.
For regulatory inspections and insurance purposes, having a complete, unaltered digital log with timestamps is significantly easier to produce than a physical book.