Fire Alarm Weekly Testing and Log Keeping: Rotation of Call Points, Test Log Format and Building Owner Duties

Summary

Weekly fire alarm testing is one of the most commonly neglected maintenance duties in UK commercial buildings. Building owners and responsible persons often test the same call point every week out of habit or convenience, defeating the purpose entirely. BS 5839-1:2017 is explicit: the entire purpose of rotating call points is to verify that the full detection circuit, wiring, and panel response are functioning throughout the year — not just confirming one zone works.

The duty falls squarely on the building owner or their appointed responsible person, not the fire alarm contractor. Contractors carry out quarterly inspections and annual full inspections, but weekly testing is an in-house duty. Many employers delegate this to a facilities manager, site manager, or nominated member of staff. Where no one is nominated, the building owner remains liable.

Insurance implications are significant. Following a fire, insurers routinely request the fire alarm log book. Gaps in weekly testing records, a log that shows the same call point tested every week for three years, or no log at all are grounds for disputed claims. The fire authority can also request the log during a fire safety inspection under the Regulatory Reform (Fire Safety) Order 2005 and may issue enforcement notices or improvement notices where records are inadequate.

Key Facts

• Testing frequency — minimum once per week on a working day, at the same time each week where possible
• Method — use the test key to operate the call point without breaking the glass. Breaking glass is never required for weekly tests
• Rotation requirement — each call point must be operated at least once per 12-month period; systematically rotate through all call points to achieve this
• Panel response — the panel must activate the alarm, and the tester must verify sounders operate audibly throughout the affected zone
• Log retention — the log book must be kept for a minimum of three years; BS 5839-1 recommends keeping logs indefinitely
• Log format — must record: date, time, call point location and zone, result (satisfactory/unsatisfactory), any fault observed, and name/signature of tester
• Fault response — any fault found during a weekly test must be reported to the responsible person immediately and a qualified engineer called; the system must not be left unmonitored
• Audibility check — the tester should walk the building to confirm sounders can be heard in all occupied areas, particularly at the furthest points from the sounders
• Keyholders — the name of the keyholder and their out-of-hours contact details must be noted in the log
• Contractor inspections — weekly tests do not replace the quarterly service inspection required under BS 5839-1 Clause 34
• Evacuation drill — weekly tests are not a substitute for fire drills; BS 5839-1 recommends drills at least annually (twice annually for multi-shift premises)
• False alarm management — if the weekly test activates monitoring centre, the alarm receiving centre (ARC) must be notified in advance to suppress a false dispatch
• Remote monitoring — where an ARC is connected, the tester must call the ARC before and after testing each week
• Legal framework — Article 17 of the Regulatory Reform (Fire Safety) Order 2005 requires maintenance of fire-fighting equipment and fire detection systems

Quick Reference Table

Detailed Guidance

Setting Up a Call Point Rotation Schedule

The most reliable method is to list every manual call point in the building on a single sheet pinned inside the log book. Number them sequentially and rotate through the list week by week. For a building with 26 call points, you complete one full rotation in exactly 26 weeks — each call point is tested twice in 12 months, comfortably exceeding the annual minimum.

For larger buildings with 52 or more call points, one full rotation per year may mean some call points are tested no more than once. This is the minimum; nothing prevents more frequent testing. In high-risk premises or where detectors have had previous faults, increase the rotation frequency.

A simple rotation tracking sheet looks like this:

Call Point Rotation Tracker — Building Name
-------------------------------------------
Week 01 (w/c 05 Jan)  → MCP-01 (Main entrance)
Week 02 (w/c 12 Jan)  → MCP-02 (Stairwell A, Ground)
Week 03 (w/c 19 Jan)  → MCP-03 (Stairwell A, First)
...and so on

Stick to the schedule. If a call point is out of service (being repaired, zone isolated for building works), skip it, note this in the log, and return to it once reinstated. Do not substitute another call point from the same zone.

The Weekly Test Procedure Step by Step

Before testing:

1. Notify the building occupants that a fire alarm test will take place at a specific time
2. If the system is monitored by an ARC, call them and give your name, site name, account number, and the time you expect to test
3. Ensure at least one other person is present to confirm sounder coverage in remote parts of the building

During testing:

1. Go to the call point scheduled for this week's test
2. Insert the test key and operate the device per the manufacturer's instructions — do not break the glass element
3. Walk to the fire alarm panel (or have a colleague stationed there) to confirm the panel illuminates the correct zone and goes into alarm condition
4. Walk the building to confirm all sounders are audible. Pay particular attention to plant rooms, toilets, and storerooms where sounder coverage is weakest
5. Reset the panel using the reset key
6. Confirm the panel returns to normal condition (no residual faults)

After testing:

1. Call the ARC to confirm the test is complete and they should resume monitoring
2. Notify building occupants the test is finished
3. Complete the log book entry immediately

What to Do When a Fault Is Found

If a fault is discovered during the weekly test — for example, a sounder fails to activate, the panel shows a fault condition, or the call point does not trigger the alarm — the procedure is:

FAULT FOUND DURING WEEKLY TEST
        |
        v
Is the fault a total system failure?
        |
   YES  |  NO
        |
        v        v
Evacuate     Assess zone affected
building     Is this zone critical?
             (sole means of detection
              in high-risk area?)
                  |
             YES  |  NO
                  |
                  v         v
            Consider      Log fault,
            evacuation    notify responsible
            precautions   person, arrange
                          engineer within
                          next working day

Regardless of fault severity, the following must happen:

• Record the fault in the log book immediately with the exact nature of the fault and time discovered
• Notify the responsible person in writing (email is acceptable)
• Contact the fire alarm maintenance contractor
• If the system is monitored, notify the ARC

Never sign off a weekly test as satisfactory if any fault was found. If the fault is minor (e.g., a single peripheral device showing a supervisory fault unrelated to detection), it is acceptable to note this and confirm the detection function itself was verified — but be specific in the log.

Building Owner and Responsible Person Duties

Under Article 5(3) of the Regulatory Reform (Fire Safety) Order 2005, where there is more than one responsible person for a building, they must cooperate and coordinate on fire safety matters. In practice, this means:

• Multi-tenancy buildings: the landlord typically takes responsibility for common areas; each tenant is responsible for their own demise. The log book must cover all zones, and both parties should have access to it.
• Managing agents: where a managing agent acts on behalf of a building owner, the fire alarm log book is a document they must maintain or ensure is maintained. Absence of a log is treated as a failure of the building owner, not the agent.
• Change of occupancy: when a new tenant takes occupation or building use changes, the responsible person must review whether the current level of fire detection remains appropriate for the new use, and update the log book with the change.

The responsible person is also required under BS 5839-1 Clause 34.2 to ensure that the building's fire alarm system is maintained by a competent person. This means a qualified contractor carrying out quarterly inspections as a minimum, with a full annual inspection including testing of all devices. Weekly testing by in-house staff does not fulfil this requirement.

Documentation for Insurance and the Fire Authority

Insurance policies for commercial premises almost universally require that the fire alarm system is maintained in accordance with BS 5839-1 and that a log book is kept. Following a fire, the insurer's loss adjuster will typically request:

1. The fire alarm log book covering the past 12 months minimum
2. The most recent contractor service report
3. Evidence that weekly tests were carried out

Where the log book cannot be produced or shows irregular testing, the insurer may seek to reduce or void the claim on grounds of non-compliance with policy conditions. This is not hypothetical — it is a documented cause of disputed claims.

Fire safety inspectors from the local fire authority have powers under Article 27 of the RRO 2005 to inspect premises and request documentary evidence of fire safety measures. Improvement notices can be served for inadequate maintenance records. In serious cases, prohibition notices can close premises.

Frequently Asked Questions

Do I need to evacuate the building every time I do the weekly test?

No. The weekly test is a functional check of the detection and alarm system, not a full fire drill. You should notify occupants beforehand so they are not alarmed, but you are not required to evacuate. BS 5839-1 recommends that at least one person walks the building to confirm sounder coverage, but a full evacuation is not part of the weekly test procedure. Fire drills are a separate requirement under the RRO 2005.

Can I use the same call point every week for convenience?

No. BS 5839-1 requires that all call points are tested at least once in every 12-month period. Using only one call point means the rest of the detection circuit is never verified under a live alarm condition. Beyond the regulatory requirement, it defeats the purpose of the test: a wiring fault on zone 3 will never be discovered if you only ever test zone 1. Rotate systematically.

What if the building is unoccupied and no one can do the weekly test?

If a building is genuinely unoccupied for an extended period (e.g., a commercial property between tenants), the responsible person should arrange for a nominated person or the maintenance contractor to carry out the weekly test. The requirement does not pause during periods of non-occupation. Note in the log the circumstances if tests are missed due to building closure, and ensure the contractor is aware.

Does the weekly test count as part of the annual maintenance?

No. The quarterly and annual inspections carried out by a qualified fire alarm contractor under BS 5839-1 Clause 34 are separate from weekly testing. The annual inspection involves testing all devices, checking all wiring, inspecting battery condition, verifying panel operation, and issuing a formal inspection report. Weekly tests are a quick functional check, not a substitute.

My building has an addressable system — how does rotation work?

On an addressable system, each detector and call point has a unique address. The panel log will show which device triggered each alarm. For weekly testing purposes, rotate through the manual call points in the same way as with a conventional system. The addressable log on the panel is useful for confirming that the correct device triggered, but it does not replace the written log book — the log book is required for audit, insurance, and fire authority purposes.

Regulations & Standards

• BS 5839-1:2017 — Fire detection and fire alarm systems for buildings. Code of practice for design, installation, commissioning and maintenance of systems in non-domestic premises. Clause 34 covers maintenance; Annex L provides guidance on log books.

• Regulatory Reform (Fire Safety) Order 2005 (SI 2005/1541) — Article 17 requires responsible persons to maintain fire detection and alarm systems. Article 27 gives fire authorities inspection powers.

• PAS 79-1:2020 — Fire risk assessments for non-domestic premises. Requires current log book records to be reviewed as part of any fire risk assessment.

• BS 7671:2018+A2:2022 (IET Wiring Regulations) — Covers electrical supply and wiring requirements for fire alarm systems. Relevant to any faults discovered involving wiring during testing.

• Fire Safety Act 2021 — Amended the RRO 2005 to clarify responsible person duties in multi-occupied residential buildings, extending fire safety management requirements to those premises.

• BS 5839-1:2017 Fire detection and fire alarm systems — BSI, the primary standard governing maintenance and testing

• Fire safety in the workplace: your responsibilities — GOV.UK, overview of responsible person duties

• Regulatory Reform (Fire Safety) Order 2005 — legislation.gov.uk, full text of the statutory instrument

• Fire safety log book guidance — Fire Industry Association (FIA), practical guidance on log keeping

• HSE fire alarm maintenance guidance — HSE, supplementary guidance on alarm maintenance

• bs 5839 1 fire alarm standard — Full overview of BS 5839-1 design, installation, and commissioning requirements

• fire alarm commissioning procedure — Commissioning and handover documentation requirements

• fire alarm false alarm management — Managing false alarms and ARC notification procedures

• nsi bafe sp203 1 certification — Contractor certification requirements under NSI and BAFE SP203-1