Weekly Fire Alarm Test: Procedure, Rotation and What to Record (UK)

Quick answer: Test the fire alarm once a week, during normal working hours, at roughly the same time each week, by operating a manual call point. Use a different call point every week so that every call point in the building is tested in rotation. Confirm the panel shows the correct zone and the sounders operate, put any monitoring centre on test first, and record the date, time, call point used, result and your name in the fire safety logbook. That is what BS 5839-1 recommends and what a fire officer will ask to see.

The weekly test is the single most frequently inspected fire safety record in UK premises, and the one most often done badly: the same call point pressed every Monday for three years, no entry when the manager was on holiday, faults on the panel never written down. This guide sets out the procedure that satisfies the standard, the rotation logic behind it, and the exact fields your record needs.

Where the duty comes from

The Regulatory Reform (Fire Safety) Order 2005 (the Fire Safety Order) does not use the words "weekly test". What it does is place a duty on the responsible person, under article 17, to ensure that fire safety equipment is maintained in an efficient state, in efficient working order and in good repair. Article 9 then requires the significant findings of the fire risk assessment, including the arrangements for maintaining that equipment, to be recorded where the premises has five or more employees, is licensed, or is subject to an alterations notice. Scotland (Fire (Scotland) Act 2005) and Northern Ireland (Fire and Rescue Services (NI) Order 2006) impose equivalent duties.

BS 5839-1, the British Standard for fire detection and fire alarm systems in non-domestic premises, is the recognised benchmark for how that maintenance duty is discharged. Section 6 of the standard sets out the routine attention the user should give the system, and the weekly test is at the top of the list. It is a recommendation rather than a statute, but a fire and rescue authority inspecting officer will treat the absence of weekly test records as evidence that the system is not being maintained, and enforcement notices routinely cite it.

The weekly test procedure

1. Pick the call point for this week from your rotation schedule (see below). Note its identifier and zone before you start.
2. Tell the alarm receiving centre. If the system is monitored, phone the ARC and put the system on test for the duration. Otherwise the weekly test becomes a false alarm attendance, and repeated ones can attract charges from the fire and rescue service.
3. Check the panel first. Before operating anything, look at the control panel. Note any fault, disablement or pre-alarm indications. A fault that has been showing for six weeks and never recorded is exactly what an inspecting officer looks for.
4. Operate the call point using the test key. Confirm the panel indicates the correct zone or device address and that the alarm sounders (and any voice alarm messages or visual alarm devices) operate throughout the building. In larger premises, have a second person confirm audibility in the areas furthest from the panel.
5. Keep it short. The alarm should sound long enough to confirm the sounders operate everywhere, and no longer. Prolonged weekly tests train occupants to ignore the alarm.
6. Reset the call point and the panel. Confirm the panel returns to normal with no outstanding fault. If interfaces are connected (door holders, lift grounding, plant shutdown), confirm they re-set too.
7. Take the ARC off test and confirm they received the signal during the test. This proves the transmission path, not just the sounders.
8. Record it. Make the logbook entry immediately, while the details are in front of you.

Why a different call point every week

Each manual call point is a separate device with its own contacts, wiring and, on addressable systems, its own address. Pressing the one nearest reception every week proves that one call point works and tells you nothing about the other forty. BS 5839-1 therefore recommends that a different call point is used for each weekly test, so that all call points are tested in rotation over a period.

The practical way to manage this is a numbered call point schedule: a list of every call point (the commissioning certificate or zone chart gives you this), each with a number, its location and its zone. Test them in sequence and tick them off. With 30 call points, every one is tested at least once every 30 weeks. Keep the schedule in the front of the logbook so anyone covering the test can see which one is next.

Two refinements are worth adopting. First, if the building has more than one entrance used at different times, vary which door the tester starts from so audibility is checked from different positions. Second, if any zone has not produced an alarm at the panel for a long time because its call points are few, make sure the rotation reaches it rather than clustering on the busy floors.

When to test, and telling people

Test during normal working hours, at approximately the same time each week. Consistency is the point: occupants learn that the alarm at 10am on a Tuesday is the test, and that an alarm at any other time means evacuate. Publish the test time on the fire action notices or staff noticeboard, brief new starters at induction, and if the time has to move, tell people beforehand. If the premises runs shifts, choose a time when the largest number of people are present, and consider a periodic test during other shifts so everyone hears the alarm at least occasionally.

Do not test at a time when the building is empty. The weekly test is partly a check that the sounders can be heard by the people who need to hear them, and that only works if they are there.

What the logbook entry must contain

An entry that just says "tested OK" with a tick is common and not good enough. Each weekly test entry should record:

• Date and time of the test.
• Call point tested: its number on the schedule, location and zone.
• Result: panel indicated correct zone or address; sounders operated throughout; interfaces operated and reset.
• ARC notified and confirmed receipt (where monitored).
• Any faults, disablements or pre-alarms showing on the panel, whether or not related to the test.
• Action taken on any fault, and who has been asked to attend.
• Name and signature or initials of the person who carried out the test.

Record faults even when they clear themselves. A recurring intermittent fault is a pattern, and the logbook is where patterns become visible. Record false alarms in the same book: BS 5839-1 expects every false alarm to be logged with its cause, and the false alarm rate is calculated from that record at each service visit.

Monthly and six-monthly attention

The weekly test is the user's job, but it is not the only routine. If the system has a standby generator, BS 5839-1 recommends it is started monthly and run under load for at least an hour, with the result recorded. Every six months the system should be inspected and serviced by a competent person, normally the maintenance contractor, who will test a proportion of devices, check batteries and standby supplies, review the false alarm record and issue a certificate. Both the monthly generator run and the six-monthly service belong in the same logbook, so the whole maintenance history sits in one place.

If the test fails

If the panel does not respond, the sounders do not operate in part of the building, or a fault cannot be cleared, the system is not in efficient working order and the responsible person has to act. Record the failure in full, notify the maintenance contractor the same day, and put interim measures in place proportionate to the risk: extra fire warden patrols, a temporary manual means of raising the alarm such as hand bells or air horns, and, in sleeping accommodation or high-risk premises, a waking watch. Note the interim measures and their start and end times in the logbook. When the fault is rectified, record the date, what was done and who did it.

Common failings inspecting officers find

• The same call point tested every week, sometimes for years.
• Gaps in the record during holidays or staff changes, with no one deputised.
• Fault and disablement indications on the panel that are never written down.
• Tests carried out at random times, so occupants can no longer tell a test from a real alarm.
• Monitored systems tested without the ARC being informed, generating recorded false alarms.
• No call point schedule, so nobody can say whether every call point has ever been tested.
• Logbook kept off site or in a locked office nobody present can open.

FAQs

Who can carry out the weekly fire alarm test?

Any member of staff who has been shown the procedure and understands what to record. It does not need an engineer. Nominate a named person and at least one deputy so the test still happens when the usual tester is away.

Is the weekly test a legal requirement?

Not in those words. The legal duty is to maintain the system in efficient working order (article 17 of the Fire Safety Order). BS 5839-1's weekly test is the accepted way to demonstrate that duty is being met, and fire officers expect to see the records.

How long should the alarm sound during the test?

Long enough to confirm the sounders operate throughout the building, and no longer. In most premises that is well under a minute.

Do I still test weekly if the system is monitored by an alarm receiving centre?

Yes. Put the system on test with the ARC first, then confirm afterwards that they received the signal. The test then proves both the local alarm and the transmission path.

What if the building has no manual call points, only detectors?

Systems without call points are unusual in non-domestic premises, but if that is your design, the weekly test is carried out by operating a detector with the appropriate test equipment, or via the panel's test facility, as advised by your maintenance contractor. Record it in exactly the same way.

Can the record be kept electronically?

Yes, provided it can be produced on request when a fire officer visits. Many sites keep a paper logbook at the panel and a digital copy; either is acceptable if it is complete and available.

Sources and further reading

• The Regulatory Reform (Fire Safety) Order 2005, articles 9 and 17
• GOV.UK: Fire safety in the workplace, your responsibilities
• GOV.UK: Fire safety risk assessment guides for business premises
• BS 5839-1: Fire detection and fire alarm systems for buildings, Code of practice for design, installation, commissioning and maintenance of systems in non-domestic premises (BSI)
• Fire Industry Association guidance on fire alarm maintenance and false alarm management

Reviewed by Jamie Dawson, Editor of Logbook.

⬇ Free download: our fire safety logbook template with weekly alarm test sheet (PDF & Excel) gives you the record sheets from this guide, ready to print or fill in.

Related guides

• Fire alarm logbooks: what must be recorded and how often
• Is a fire safety logbook a legal requirement in the UK?
• Emergency lighting logbook: monthly and annual test records
• Fire marshal training records: the employer's guide

Free download: our weekly fire alarm test log template holds a full year of tests on one sheet, with a column for the call point reference so the BS 5839-1 rotation is visible.