Walk into most commercial buildings and the fire alarm log book is a ring binder near the panel with the last four weekly tests filled in, a gap covering the summer, and someone's mobile number in the front. It is the single most useful document about the system and the one nobody owns.
Moving it to a digital record fixes some of that and none of the rest. Understanding which is which is the point of this page.
Who this is for
Responsible persons and facilities managers who have to keep the record, and engineers who have to read it, contribute to it and explain why the gaps matter.
Experience level
Competent engineer or an informed duty-holder. No specialist knowledge is assumed beyond familiarity with how a fire alarm system is used day to day.
Who the log book actually belongs to
This is worth being blunt about because it is the most common misunderstanding on site: the log book belongs to the responsible person for the premises, not to the maintenance contractor.
Under the Regulatory Reform (Fire Safety) Order 2005 the responsible person — the employer, owner, landlord, occupier or anyone else with control of the premises, as GOV.UK sets out — must put in place and maintain appropriate fire safety measures. The contractor contributes servicing entries. The weekly tests, the false alarm entries, the notes about building work and the record of who was told what are all site responsibilities. When a contract changes hands, the log book stays with the building.
What belongs in it
BS 5839-1 sets out what should be recorded. In practice the entries fall into six groups:
System particulars. What the system is: panel make and model, category, zones, date of installation, who designed and commissioned it, and who currently maintains it, with contact details that are actually current.
Routine testing. The weekly user test, with the detail set out below.
Periodic inspection and servicing. Each visit, what was covered, what was found, and reference to the service report.
Faults. When the fault appeared, what it was, who was told, when it was attended, and how it was resolved. Faults that were reported and not attended are as important as the ones that were.
False alarms. Every one, with enough detail to spot a pattern.
Alterations and events. Extensions, device changes, changes of building use or layout, building works affecting the system, disablements, evacuations and drills.
The weekly test entry
Small entry, disproportionate value. It should show the date, which call point or device was operated, its location or zone, confirmation that the alarm sounded as expected, and who did it.
The reason the device reference matters is rotation. Operating a different call point each week means all of them get exercised over the year, and the log is the only way to know which one is next and whether the rotation is real. A column of ticks with no device reference proves someone ticked a box.
False alarms are the entry that pays for itself
A false alarm entry with a date, time, zone, device address, weather, and what was happening in the building at the time is the raw material for solving the problem. Three entries reading "false alarm — reset" are worth nothing.
Patterns only emerge from detail: the same detector every time the kitchen extract is off, an address that goes at the same time each morning, a zone that activates whenever there is driving rain from one direction. That analysis is impossible without a record that captured the circumstances rather than just the event.
What changes when it goes digital
What genuinely improves. Entries get made at the time, on a phone, instead of being reconstructed later. Nothing gets lost when a folder disappears or a tenancy changes. Entries are attributable to a named person and time-stamped rather than initialled illegibly. Patterns across months become searchable instead of requiring someone to leaf through a binder. Multiple sites can be compared. And the record survives a change of contractor, which paper frequently does not.
What does not improve. A digital log book still only contains what someone enters. If the weekly test is not done, a digital system records the absence more clearly — which is an improvement in honesty but not in fire safety. It will not decide what should be recorded, and it will not make anyone act on a recurring false alarm.
What to check before adopting one. The record must be complete, attributable, time-stamped and tamper-evident. It must be available to whoever needs it, including a fire officer attending the premises — which means thinking about access when the network is down and about who holds credentials when the facilities manager is on leave. Exportable records matter: the responsible person should be able to take their data out. And the retention period should be agreed rather than assumed.
Common failings in real log books
- Weekly tests recorded as a tick with no device reference.
- Long unexplained gaps, most often over holiday periods.
- False alarms recorded as counts, with no circumstances.
- Contractor details years out of date.
- Disablements entered when applied but never closed out.
- Building works that changed the layout with no corresponding entry.
- Two parallel records — the site's and the contractor's — that disagree.
Relevant standards
BS 5839-1 is the code of practice for fire detection and fire alarm systems in non-domestic premises and is the reference for what should be recorded and how often testing should take place. The Regulatory Reform (Fire Safety) Order 2005 creates the legal duty on the responsible person, and GOV.UK guidance explains who that person is. The standard's recommendations are the recognised route to meeting the duty, not legislation themselves; always work from the current edition.
When not to rely on the log book alone
The log book records what happened. It does not certify that the system is correctly designed for the building it is in — that comes from the design documentation, the certificates and the fire risk assessment. A complete log book on a system that is the wrong category for the current use of the building is a well-documented problem, not a solved one.
Related documentation
Read this with the guidance on testing and maintenance requirements, on certification and handover documentation, and on managing false alarms. The log book is the thread that connects all three over the life of the system.
Professional disclaimer
This page is engineering support only and is not legal advice. It is not a substitute for the applicable standards, the manufacturer's instructions or the responsible person's own procedures. Record content and retention for a specific premises should follow the current edition of BS 5839-1 together with any insurer, contractual or enforcement requirements.