Copyable Fire Alarm Test Log Template for UK Responsible Persons

Published 01 October 2026 · gribit

Responsible person recording fire alarm test

A fire alarm test log is the written or digital record that proves you have tested, inspected and maintained your fire detection system. Keep every entry legible, dated and complete, and use a structured template or an electronic logbook so the record stands up to scrutiny. Under Article 17 of the Regulatory Reform (Fire Safety) Order 2005, these records are your evidence of due diligence, referenced throughout guidance built around BS 5839-1.

TL;DR:

Weekly tests should rotate through different call points and be conducted at the same time each week to prevent masking faults and ensure full area coverage.

Records must detail the test date, location, fault descriptions, remedial actions, and responsible personnel, ideally using a structured digital logbook for backups and reminders.

Full system servicing by a competent engineer is required at least every six months unless a documented risk assessment extends this interval, and automatic door release checks must happen weekly anyway.

In case of faults or false alarms, log every incident with clear cause, actions taken, and follow-up to identify recurring patterns that might require system adjustments or repairs.

Always notify the Alarm Receiving Centre before weekly tests to avoid unnecessary fire service dispatches and keep both the log and fire risk assessment updated and cross-referenced for compliance.

Gribit

Keep Fire Alarm Records Organised

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

Visit Gribit

Template fields to include in your fire alarm test log

A usable log needs enough detail that anyone, not just the person who wrote it, can understand what happened and what came next. Fire and rescue service templates, such as the one published by Avon Fire & Rescue Service, structure this into clear columns rather than free text, which makes gaps obvious at a glance.

Copy these fields into a spreadsheet, a printed book or a digital logbook:

Date and time the test was carried out.
Tester name and role, so accountability is clear.
Device or call point ID and zone or location, matching the building’s fire alarm zone plan.
Test type, whether a visual check, an operational weekly test or a full periodic inspection.
Result, pass or fail, with enough detail to be meaningful.
Fault description, where applicable, written in plain terms an engineer can act on.
Remedial action, the person responsible for it, and the completion date.
Signature or initials, plus a reference to any engineer’s certificate issued for that visit.

A log built this way does double duty: it satisfies an inspector and it gives your own staff a quick way to see whether a recurring fault is being ignored or actually fixed.

How often to test the alarm and what each frequency checks

Different checks catch different problems, and mixing them up is the most common log-keeping mistake. Fire service guidance sets out a consistent pattern across daily, weekly, monthly and periodic checks.

Daily: a visual check of the control panel for faults or warning indicators, recorded only when something needs attention.
Weekly: operate one manual call point, rotating which one you use, and confirm the alarm sounds and the panel registers it correctly.
Monthly: supplementary checks on linked equipment such as standby generators or batteries, where your system includes them.
Six-monthly and periodic: servicing and certification carried out by a competent person, covering the full system rather than a single point.

The periodic interval should not exceed six months unless a documented risk assessment justifies a different schedule. Some modern systems make weekly testing impractical, and a risk assessment can justify monthly user testing instead, provided the six-monthly competent-person service still happens on schedule. Automatic door releases linked to the fire alarm usually still need checking weekly regardless of any change to the main test frequency.

Running the weekly test safely and logging it properly

A weekly test done badly can trigger an unwanted call-out or mask a fault instead of finding one. The fix is a short, repeatable routine rather than anything elaborate.

Choose a different call point each week and record its ID in the log, working through the building systematically.
Test at the same time each week so staff expect it and can confirm the sound reaches every area it should.
If the system is monitored, notify the Alarm Receiving Centre before you start and again once you finish, so the test does not trigger an automatic fire service attendance.
Reinstate full operation immediately afterwards and note any linked systems, such as door releases, that you checked at the same time.

Pro Tip: Keep the Alarm Receiving Centre’s phone number taped inside the log book itself, so nobody has to go searching for it on the morning of the test.

Recording faults, false alarms and remedial action correctly

Every actuation belongs in the log, not just the ones you intended. South Wales Fire & Rescue Service’s template treats false alarms the same way as genuine tests: they need a time, a location, a cause where known, who investigated and what was done about it.

Record the time, zone and suspected cause of every false alarm, not just confirmed faults.
Note the remedial action taken, who is responsible for it and the date it was cleared.
Review the log periodically for repeat false alarms from the same zone or device, since a pattern usually points to a fault that a one-off test will not reveal.

Treating false alarms as data rather than noise is what turns a log from a compliance chore into a tool that actually reduces unwanted activations.

Who is responsible: the responsible person and the competent person

The responsible person, usually the employer, building owner or occupier, carries legal accountability for fire safety under the Fire Safety Order even when day-to-day testing is delegated to staff. That accountability does not transfer with the task.

Record every competent person visit: the company name, the engineer’s name, the scope of work carried out and the certificate reference number.
Keep the logbook alongside the fire risk assessment, since inspectors expect to see both together rather than one without the other.
Check that servicing certificates are filed, not just mentioned in a log entry, so the paper trail is complete if challenged.

Electronic versus paper logbooks: what actually helps at inspection time

Paper logbooks work, but they are easy to lose, damage or leave unfilled for weeks. A digital logbook timestamps entries automatically, keeps an off-site backup, sends reminders before a test is due and exports a clean report for an inspector on request.

Timestamping removes any doubt about when a test actually happened.
Off-site backup means a fire, flood or simple misplacement cannot destroy years of records.
Automated reminders catch the test nobody remembered to schedule.
Exportable reports turn an inspection request into a few clicks rather than a search through a filing cabinet.

Gribit’s digital logbook is one example built specifically for small sites that want this without a large system to manage.

Fault diagnosis and troubleshooting during a test

When a weekly test fails, work through the system logically rather than guessing. Start at the call point itself: check it is seated correctly and not physically damaged, then confirm the fault is not isolated to a single zone by testing a point elsewhere on the same circuit.

If the panel shows a zone fault rather than a device fault, the wiring or the zone card is the likelier cause, and that is a job for a competent engineer rather than a test sheet. A “general fault” indicator with no clear trigger often points to a battery nearing the end of its life, particularly on systems due their six-monthly service soon.

Record what you tried, not just the final result: which call point, what the panel showed and what you ruled out. That detail saves the engineer time on the next visit and stops the same diagnostic steps being repeated unnecessarily. Never silence a fault indicator without logging it first, and never leave a system in fault condition overnight without telling whoever is responsible for escalating it.

Fault diagnosis and troubleshooting during a test — overview diagram

Interpreting test results and deciding what happens next

A pass is straightforward: record it, note the call point used, move on. A fail needs a judgement call about urgency. A single call point failing to trigger the sounder is a defect to log and schedule for repair, but a sounder failing across an entire zone, or the panel failing to register any signal at all, means the system cannot be relied on and needs urgent attention, not a note for next week.

Treat the test log as a decision tool, not just a record. If the same fault reappears after supposedly being fixed, that is a sign the remedial action did not address the actual cause, and it is worth escalating to the servicing company rather than logging the same fix again. Where a fault leaves part of the building without adequate coverage, consider what interim measures, such as a fire watch, are needed until the repair is complete.

Common faults and the remedial action they need

Most recurring faults fall into a handful of categories, and recognising the pattern saves time.

A dead or dying battery usually shows as a general fault light with no obvious trigger: the fix is replacement, not a reset, and it is worth checking the last servicing date. A call point that fails to register is often a wiring or contact issue at that specific device: isolate it, log it clearly so it is not used again until fixed, and flag it for the next service visit. Smoke detectors triggering falsely, particularly in kitchens or bathrooms, point to the wrong detector type for that environment, which a competent engineer can usually resolve by swapping the detector head. Sounders that are inaudible in certain areas usually mean coverage was never adequate for that layout, which needs a proper assessment rather than a louder unit bolted on.

Common fire alarm faults and remedial actions

In every case, the log entry should separate the symptom from the fix, so a reviewer can see at a glance whether the same symptom has returned.

Auditing and reviewing your test logs for compliance

A log is only useful if someone actually checks it. Set a simple review routine: monthly, scan for missed weekly tests, unresolved faults and any false alarm pattern repeating from the same zone. Quarterly, check that every six-monthly service is booked or completed on schedule and that certificates are filed against the correct date.

Cross-reference the log against the fire risk assessment at least once a year, since a risk assessment that justified a change in test frequency needs to be revisited rather than left as a standing assumption. If you use a digital logbook, an export covering the last twelve months is the quickest way to spot gaps before an inspector does. A log with no faults ever recorded is itself worth questioning: it usually means tests are being signed off without being run properly, not that the system never fails.

Two mistakes I see repeatedly in fire alarm logs

The first is skipping the Alarm Receiving Centre call before a weekly test, which risks an unwanted fire service attendance over a two-minute phone call that should already be in the routine. The second is treating the logbook as the risk assessment itself: keep the two documents together and cross-reference them, because an inspector will ask for both.

— Jon

A simpler way to keep the log: Gribit’s site logbook

Running a fire alarm log by hand works until someone forgets a week, loses the book or cannot find last year’s engineer certificate when an inspector asks for it. Gribit’s digital site logbook handles the recurring admin: reminders before a test is due, central storage for every entry and certificate, and an export ready for an inspector without digging through a filing cabinet.

Gribit

Periodic servicing by a competent engineer is still necessary regardless of which system you use to record it. This changes how much time the recording itself takes.

Plan	Price	What it covers
Site Logbook Annual Plan	a yearly subscription fee per site	Digital logbook for recurring safety checks, reminders and document storage

Start a Site Logbook Annual Plan to keep your fire alarm records in one place.

Authoritative downloads and standards

The Regulatory Reform (Fire Safety) Order 2005 sets the legal duty to maintain fire safety equipment and keep evidence of due diligence.
Bedfordshire Fire & Rescue Service’s log book is a ready-made template covering daily, weekly and periodic checks.
BS 5839-1 is the technical code of practice behind most test frequency guidance.
Businesses storing records off-site should also understand their duty of care around confidential document handling.

Sources

FAQ

Is a fire logbook a legal requirement?

There is no specific legal requirement to keep a document called a “fire safety log book”, but Article 17 of the Regulatory Reform (Fire Safety) Order 2005 requires that fire detection and alarm systems are kept in efficient working order. Records of tests and maintenance are the practical way to demonstrate that duty has been met.

Where can I find a fire alarm test form?

Most fire and rescue services publish free logbook templates covering weekly tests, faults and servicing, such as the one from Avon Fire & Rescue Service. A digital logbook such as Gribit’s site logbook offers the same fields in a format that reminds you when entries are due.

What is the legal requirement for fire alarm testing?

The Regulatory Reform (Fire Safety) Order 2005 requires fire alarm systems to be maintained in efficient working order, with records kept as evidence. The technical detail on how often and how to test comes from BS 5839-1, which fire service guidance follows closely.

How often should I test my fire alarm?

A weekly test of one manual call point, rotated each week, is the standard recommendation alongside daily visual panel checks. A competent person should also carry out a full service at intervals not exceeding six months, unless a documented risk assessment justifies a different schedule.