Weekly Tests and Six Monthly Servicing: UK Rules and Logbook Entries

Published 05 October 2026 · gribit

Manager carrying out weekly fire alarm test

Most non-domestic premises in the UK need regular visual checks of the fire alarm panel, weekly user tests that rotate manual call points, and periodic inspections and service by a competent person, with additional checks as identified by the system or premises risk assessment. As the responsible person under the Fire Safety Order, you must also keep a logbook recording every test, fault and service visit. This schedule follows BS 5839 practical guidance and GOV.UK guidance.

TL;DR:

Weekly user tests should rotate manual call points and be notified to the alarm receiving center if monitored, with logs recording test details and follow-up actions.

Six-monthly inspections by a qualified fire alarm engineer are needed to verify detectors, batteries, and control panels, with certificates recorded in the logbook.

Maintaining detailed, searchable digital records of all tests, faults, and service visits helps ensure compliance and simplifies inspections or incident investigations.

Higher-risk premises or those with false alarms require more frequent checks or additional testing, as determined by the fire risk assessment rather than a fixed schedule.

Accurate logbook entries, including dates, personnel, device identifiers, results, faults, remedial actions, and service details, are essential for legal protection and insurance coverage.

Gribit

gribit.co.uk

Keep Every Safety Check In Order

Gribit helps you record tests, manage follow-ups, and store certificates and documents securely in one digital logbook.

Visit Gribit

Routine test frequencies: daily, weekly, six-monthly and annual

Each check in the fire alarm routine has a distinct purpose, and missing one weakens the whole sequence.

A daily visual check of the control panel confirms the system shows normal operation with no fault lights, usually carried out by whoever opens the premises. The weekly user test is more involved: someone activates a manual call point, confirms the panel registers it and the sounders operate, then resets the system. Guidance from Manchester Fire & Rescue Service recommends using a different call point each week so that every device gets tested across a rotation, and notifying the alarm receiving centre beforehand if the system is monitored, to avoid an unnecessary emergency response.

Some sites with linked systems, such as emergency lighting on the same test cycle, add monthly checks into the mix, though this depends on what the risk assessment calls for rather than a blanket rule.

The bigger distinction is between the user test and the competent-person inspection:

Weekly: user test, rotating call points, carried out by trained staff
Six-monthly: full inspection and service by a competent person, covering detectors, batteries and panel function
Annual: additional checks some systems or premises need, set out in the risk assessment

A rise in false alarms or a change of use on site is a signal to review whether the current frequency still fits, rather than waiting for the next scheduled visit.

Who is legally responsible and what the law requires

The responsible person, typically an employer, owner, landlord, occupier or manager, carries the legal duty to keep the premises safe from fire. That duty comes from the Regulatory Reform (Fire Safety) Order 2005 and, for residential blocks in England, the Fire Safety (England) Regulations 2022.

Under this framework, you must carry out a fire risk assessment, review it regularly and put in place the testing and maintenance routines the assessment depends on. GOV.UK guidance is explicit that the responsible person must keep records of these routines, not just perform them.

The fire risk assessment drives which checks apply and how often
Records are the evidence that the assessment’s assumptions are actually being met
Enforcement officers expect to see logs, not verbal assurance, during an inspection

How to run the weekly user test: a practical checklist

A weekly test only takes a few minutes, but skipping the preparation and recording steps is where most sites fall down.

Prepare and warn: pick the next call point in your rotation, notify the alarm receiving centre if the system is monitored, and let staff or occupants know a test is about to happen.
Execute: activate the call point, confirm the panel registers the signal and the sounders operate, then reset within a minute or two rather than letting it run.
Restore: return the system to full operation and confirm with the monitoring centre that it’s back online.
Record: log the date, time, call point used, result and anyone affected, then note any follow-up action needed.

Pro Tip: Keep a simple numbered list of call points pinned near the panel so whoever runs the test always knows which one is next in the rotation.

Testing at the same time each week, ideally outside busy trading hours, keeps disruption predictable for staff and customers.

Competent-person servicing: scope, qualifications and intervals

A competent person is someone with the training and experience to inspect and service a fire alarm system properly, usually a qualified fire alarm engineer rather than general maintenance staff. Delegating this work to someone without that background risks the service counting for nothing during an inspection.

The periodic service, typically every six months under BS 5839 guidance, covers:

A full inspection of detectors, call points and sounders
Battery and panel checks to confirm backup power works
Verification of cause and effect, meaning the system triggers the right linked responses

The exact interval depends on the system category, how high-risk the premises are and the site’s false alarm history. Each visit should produce a certificate naming the engineer and the work carried out, which then goes straight into the logbook.

Record-keeping: what belongs in a logbook entry

A defensible logbook entry needs enough detail that an inspector, insurer or fire investigator can reconstruct exactly what happened without asking follow-up questions.

Date and time of the check or test
Name of the person carrying it out
Device or call point identifier
Result, including any fault found
Remedial action taken and by whom
Service visit details, including the engineer’s name and certificate reference

A good fire alarm log records the date and time of weekly tests, any faults or false alarms, and full details of service visits and who carried them out, which is the baseline most fire and rescue services expect to see on inspection.

Keeping these entries searchable and time-stamped, rather than scattered across paper sheets, makes it far quicker to answer an inspector’s questions or support an insurance claim after an incident. For sites running several locations, consistent record formats across every logbook make it straightforward to spot which site is falling behind.

Managing and recording false alarms

Frequent false alarms breed complacency among staff and occupants, which is exactly the opposite of what the system is there to prevent. Every activation, true or false, should be investigated and logged.

Record the date, time, likely cause and corrective action taken
Attach any related service report to the entry
Watch for patterns: guidance from North Yorkshire Fire & Rescue Service sets out thresholds where repeated false alarms should trigger a service review or design change
Keep these records to hand when dealing with the Fire and Rescue Service or an insurer after an incident

Checking linked systems during alarm tests

A fire alarm test is only as useful as the systems it’s supposed to trigger. Emergency lighting, door releases and, where fitted, sprinkler interfaces should all be observed during the weekly test to confirm they respond correctly, with a more thorough check during the six-monthly service. Any change affecting a linked system should prompt an update to the fire risk assessment and a note in the logbook, since technical guidance on fire safety expects these interactions to be checked, not assumed.

Fire alarm connections to linked safety systems

What to record in a fire alarm logbook, with examples

Beyond the minimum fields already listed, a logbook earns its value from consistency. A typical weekly entry might read: “14 January, 09:05, call point 4, J. Smith, test successful, no faults, ARC notified before and after.” A six-monthly service entry would add the engineer’s name, company, certificate number and any parts replaced, such as a replaced smoke detector head or a battery swap.

A false alarm entry needs more detail again: the time of activation, the zone or device that triggered it, the suspected cause such as cooking fumes or a faulty detector, and what was done afterwards, whether that’s cleaning a sensor or calling the service provider early. Where a fault is found but not immediately fixed, the entry should note the interim arrangement, for example extra fire wardens on duty until an engineer attends.

What makes these examples useful isn’t the format, it’s that each one answers the same question an inspector or investigator will ask: what happened, who dealt with it and what changed as a result. A log that only says “tested, OK” week after week with no detail on rotation or faults gives an inspector little confidence that the routine is genuinely happening rather than being signed off from memory.

Consequences of non-compliance with fire alarm testing requirements

Failing to test and record checks properly exposes you on two fronts: safety and enforcement. If a fire occurs and the alarm didn’t work or wasn’t maintained, the consequences for occupants can be severe, and that failure will be scrutinised closely afterwards.

On the enforcement side, fire and rescue services can issue an enforcement notice requiring improvements, or in serious cases prosecute the responsible person under the Fire Safety Order. A missing or incomplete logbook is often the first thing an inspecting officer asks for, and its absence suggests the testing regime itself may not be happening as claimed, even if it is. Insurers can also decline a claim where maintenance records don’t support the cover they issued, leaving the business to absorb losses that would otherwise have been covered.

None of this requires a fire to actually happen. A routine inspection that finds gaps in testing or records can itself lead to formal action, and the cost of fixing those gaps after the fact, in time, documentation and sometimes retraining staff, is almost always higher than keeping the routine current from the start.

Consequences of non-compliance with fire alarm testing requirements — overview diagram

Adapting test frequency to building type and risk

The schedule above is a starting point, not a fixed rule for every building. A small shop with a simple detection system and low footfall carries different risk from a care home, a large office with vulnerable occupants, or a warehouse storing flammable stock, and the fire risk assessment should reflect that difference directly in the testing regime.

Higher-risk premises, those with sleeping occupants, complex escape routes or a history of false alarms, often justify more frequent competent-person checks than the standard six-monthly interval, or additional monthly checks on top of the weekly user test. Lower-risk, simple premises may find the standard schedule more than adequate, provided the risk assessment is reviewed whenever something changes: a refit, a change of use, new storage arrangements or a run of false alarms.

The key practical point is that the risk assessment, not a generic checklist, should set your actual frequency, with BS 5839 and GOV.UK guidance as the baseline to adjust from rather than a ceiling or floor that applies regardless of circumstances.

Why digitising fire alarm logs helps the responsible person

Paper logbooks go missing exactly when you need them most, during an inspection or after an incident. A digital log keeps every weekly test, service certificate and false alarm entry searchable in one place, and automated reminders mean a rota gap gets caught before it becomes a compliance problem.

A simple way to keep your fire alarm records in order

Running a weekly rotation, chasing six-monthly service bookings and keeping certificates somewhere findable takes real effort on top of everything else a small business has to manage. Our SITE LOGBOOK ANNUAL PLAN gives you a single place to schedule tests, timestamp every entry, assign follow-up actions to staff and store service certificates against the date they were issued.

Gribit

This is an administrative aid for keeping your records straight, not a substitute for a competent person’s inspection or service. It is designed for shops, pubs, offices and similar premises that need their fire safety paperwork in order without a spreadsheet falling apart. Current prices are available on the pricing page.

FAQ

How often should a fire alarm be tested in the UK?

Most premises need a weekly user test, rotating the manual call point each time, plus a daily visual check of the control panel. A competent person should then inspect and service the full system, typically every six months, following BS 5839 guidance.

What are the regulations for fire alarm testing in the UK?

Testing duties sit with the responsible person under the Regulatory Reform (Fire Safety) Order 2005, supported in England by the Fire Safety (England) Regulations 2022. GOV.UK guidance requires the responsible person to carry out a fire risk assessment and keep records of the routines it relies on.

How often must a fire alarm system be tested?

The practical split is weekly user tests by staff and six-monthly inspections by a competent person, though the exact interval depends on system category and premises risk as set out in the fire risk assessment.

How often do you need a fire risk assessment in the UK?

There’s no fixed calendar interval in law, but the responsible person must keep the assessment under regular review and update it whenever the premises, occupancy or systems change significantly.

What should go in a fire alarm logbook?

Each entry should record the date, time, person carrying out the check, call point or device tested, result, any fault found and the remedial action taken, alongside full details of any service visit.