Skip to content
Illustration for the Fire Regs Pro guide: The Weekly Fire Alarm Test: A Detailed Guide

Fire Regs Pro guide

The Weekly Fire Alarm Test: A Step-by-Step Guide Under BS 5839-1

How to carry out the weekly fire alarm test under BS 5839-1: call point rotation, ARC procedures, panel operation, verification and log book records.

·Fire Regs Pro Team

The weekly fire alarm test is the most routine task in the life of a fire detection and alarm system. It’s also one of the easiest to get wrong. It takes a few minutes, but done properly it shows that the whole chain is working: a manual call point initiates, the control and indicating equipment (CIE) recognises the fire condition, the alarm devices sound, and the signal reaches whoever is monitoring the system.

For engineers studying for FIA units or maintenance qualifications, this topic comes up often. You need to know what BS 5839-1 expects of the user, how that differs from the periodic servicing a competent engineer carries out, and the practical steps that stop a simple test turning into a false alarm or a damaged device.

What BS 5839-1 Expects From the Weekly Test

BS 5839-1 puts the weekly test with the user, meaning the premises’ responsible person or someone they nominate. It doesn’t require an engineer. The core recommendations are:

  • Operate a manual call point every week during normal working hours.
  • Confirm the system goes into fire, the sounders (or other alarm devices) operate, and, if the system is monitored, the alarm receiving centre (ARC) gets a fire signal.
  • Test at roughly the same day and time each week, so occupants learn that a short alarm at that time is a test and not a real evacuation.
  • Use a different call point each week, rotating through every call point on the system.

The weekly test checks more than one call point. It checks the whole system from input to output, plus the off-site signalling if there is any. Treat it as an end-to-end check.

Occupants have a part to play as well. Because the test happens at a predictable time, anyone who notices a quiet sounder, a beacon that doesn’t flash, or a sounder they didn’t hear at all should report it. Over months, those reports often find poor audibility that a formal survey would otherwise only pick up at the next service.

Many sites in the UK choose Tuesday, and the industry often calls it “Test it Tuesday”. The standard doesn’t specify a day. Pick one that suits how the building is occupied. The standard also has extra recommendations for shift workers who are never present at the normal test time, so check the current published edition for the exact wording.

Call Point Rotation on Larger Systems

The standard asks for only one call point per week. On a system with 150 call points, that means each device gets tested roughly once every three years. Many organisations test several call points each week to shorten the cycle, which is sensible because each extra call point only adds a minute or two.

Whatever rotation you use, you need a device list. You have to record exactly which call point you tested, and you can’t do that without knowing where they all are.

Know Your System Before You Start

The responsible person should have the as-fitted drawings, device lists and zone plans in the O&M documentation handed over at completion. That can be a hard copy or an electronic file. If it’s missing, ask the maintenance provider to produce it. They may charge for this, but a system without accurate records can’t be tested properly.

The user also needs a handover from the installer or maintainer that covers:

  • How to get access to the user level of the panel (access level 2). On many panels you must enter a code before any controls will work.
  • How to silence and reset the panel.
  • How to read the panel’s fire indication, whether it’s text on an addressable panel or a zonal LED on a conventional one.

The user doesn’t need the engineering manual. They need the user guide for their model of panel, which manufacturers usually publish. If the panel still has its factory default user code, change it with the maintainer.

Monitored Systems: Putting the ARC on Test

If the system sends signals to an ARC, always put it on test before operating a call point. Each ARC has its own procedure. Some use an automated phone line where you enter a site code, and others need you to speak to an operator.

A common bad habit is putting the system on test for the longest period the ARC allows. Avoid it.

A fire can start at any time, including during a test window. If the test will take 20 minutes, set the test period to about that. Take the system off test as soon as you finish, and confirm the ARC received the test signal.

Some sites also have supplementary remote monitoring or management devices fitted to the panel. These may have their own test or “weekly test” mode, set with a key switch or a remote command, so that test signals aren’t sent on as real events. If your site has one, the maintainer should include it in the handover. If not, skip this step.

Use the Correct Test Key

Call points are tested in different ways depending on the manufacturer and model. Some test keys go into the bottom of the unit, some into the front or side, and a single manufacturer may use several key types across its product range. The wrong key, or too much force, can break the mechanism. The call point then has to be replaced, and until it is, that location has no manual call point.

If you aren’t sure which key you need, ask the maintainer. Don’t break the frangible element or use improvised tools.

The Weekly Test, Step by Step

  1. Check the panel is normal, showing no existing fire, fault or disablement that would affect the test.
  2. Put the ARC on test (if the system is monitored) and set any on-site monitoring device to test mode if your site has one.
  3. Warn occupants if needed. At a regular, well-known test time a brief announcement is often enough.
  4. Operate the call point with the correct test key. The element should move, the call point’s LED should light if it has one, and the panel should go into fire.
  5. Confirm the alarm devices are operating. Keep the alarm short, ideally under a minute, so occupants can still tell a test from a real alarm.
  6. Check the panel indication matches. The location text or zone LED should match the call point you operated. If you tested a call point in the plant room, the panel should say plant room, and that should agree with your device list.
  7. Enter the user code and silence the alarm.
  8. Reset the call point first, then reset the panel. If the call point is still activated, for example if the key mechanism hasn’t returned or the element hasn’t been refitted properly, the panel will go straight back into fire.
  9. Confirm the panel is back to normal, with no fire, fault or disablement showing.
  10. Take the ARC off test, confirm they received the signal, and return any monitoring device to normal mode.
  11. Record the test in the log book.

When Something Doesn’t Match

The text-matching step at point 6 is where weekly tests most often find real problems. If the panel shows a different location from the one you tested, there are a few possible causes:

  • The panel’s location text is wrong, which needs reprogramming by the maintainer.
  • On a conventional system, the zoning doesn’t match the zone plan.
  • The device list or drawings are out of date after alterations.

Each of these matters during a real fire, because it can send the fire service or the response team to the wrong place. Report any mismatch to the maintenance provider and record it in the log book. The same applies to a sounder that didn’t sound, an LED that didn’t light, or an ARC that didn’t receive the signal.

Recording the Test

The log book is the evidence that the responsible person is meeting their duties under the Regulatory Reform (Fire Safety) Order 2005, or the equivalent legislation in Scotland and Northern Ireland. For every weekly test, record:

  • Date and time
  • The call point or call points tested (by device or zone reference)
  • Who carried out the test
  • Any defects, unexpected results or occupant reports
  • What action was taken, including when the maintainer was told

Weekly testing doesn’t replace periodic inspection and servicing by a competent person, which BS 5839-1 recommends at intervals of no more than six months. The two go together. The weekly test finds problems quickly between visits, and the service checks the system in depth. Engineers who commission and maintain addressable panels should check during each service that the weekly test log is being kept up.

Exam and Practice Caveats

  • Clause numbers and some wording changed between editions of BS 5839-1. Check the current published edition before quoting a clause in an exam answer or a report.
  • Procedures vary by panel manufacturer, call point type and ARC. Always follow the manufacturer’s data and the site’s agreed procedures.
  • Project specifications or insurers can set stricter requirements than the standard, such as more call points per week or specific recording formats.
  • In exams, watch out for questions that mix up user responsibilities (weekly test, log book, reporting defects) with competent person responsibilities (periodic servicing, programming changes, certification).

How Fire Regs Pro Fits Into This

Weekly testing, user responsibilities and the line between user checks and competent-person servicing all come up regularly in FD&A maintenance exams. Fire Regs Pro has 1462 questions across 71 topics and 7 exam paths, so you can drill maintenance topics alongside design, installation and commissioning until the differences are second nature. Start with the free exam practice quiz or browse the exam paths to find the one that matches your qualification.

The app also has nine BS 5839 quick-reference areas for checking servicing intervals and user duties quickly, six calculators, and field records (certificates, service log and CPD), so you can record your own maintenance visits the same disciplined way you’d expect a site to keep its weekly test log.

Frequently asked questions

How often should a fire alarm system be tested under BS 5839-1?

BS 5839-1 recommends a weekly test, carried out by operating a manual call point during normal working hours. It should be done at roughly the same day and time each week, using a different call point each time so that every call point is tested in rotation.

Do I need to tell the alarm receiving centre before a weekly test?

Yes. If the system is monitored, put it on test with the alarm receiving centre (ARC) before you start. Choose a test period that matches how long you will actually be testing, take it off test as soon as you finish, and confirm the ARC received the fire signal.

Is testing one manual call point per week enough?

The standard only expects one call point per week. On large systems with many call points, testing more than one each week shortens the rotation, so each device gets tested more often.

What should be recorded after a weekly fire alarm test?

Record the date, time, which call point you tested, who tested it, and any defects or unexpected results in the system log book. Report any defect to the maintenance provider promptly.

Related articles