Premises and responsible persons
Address, contacts, areas controlled, competent persons and shared-building interfaces.
Free premises record
Keep testing, maintenance, training, drill, defect and remedial evidence in one controlled record that supports day-to-day fire-safety management.
Download the free resourceResource structure
The document uses clear prompts and practical writing space to make the record useful. It does not present completion of a form as proof of compliance.
Address, contacts, areas controlled, competent persons and shared-building interfaces.
Weekly tests, different call points where appropriate, defects, resets and competent service visits.
Routine function checks, duration testing, failures, repairs and service evidence.
Routine condition checks, obstructions, final-exit operation, defects and escalation.
Visual checks, servicing, suppression, smoke control and other premises-specific systems.
Who participated, scenario, observations, learning, actions and follow-up.
Date, circumstances, immediate response, investigation and resulting changes.
Reference, risk, interim control, owner, target, status and verified closure evidence.
Purpose
A logbook should demonstrate that planned checks happen, defects are escalated and corrective work is verified. It should help the responsible person see patterns rather than create an archive of signatures with no follow-up.
The record should match the actual premises and systems. Manufacturer instructions, standards, the FRA and competent service advice may require additional records.
Every entry has a date, activity, result and identifiable person.
Failures create tracked defects rather than disappearing into comments.
Contacts, systems and schedules are updated after change.
Relevant people can find records during management, service or inspection.
Testing and maintenance
A signature proves only that somebody made an entry. It does not establish that a test was correctly performed, that coverage is suitable or that a defect was repaired.
Use competent contractors where required, retain their certificates and make sure internal checks connect to the same defect and action process.
Shared premises
A tenant may test local arrangements while a landlord manages common alarms, stairs or smoke control. Each responsible person should know who holds which records and how faults affecting others are communicated.
The logbook should identify shared systems, contacts and escalation routes. Relevant findings and impairments should not remain inside one organisation’s file.
Free editable resource
Choose the printable PDF or editable Word version. Both are available immediately without providing an email address.
Professional support
If the records reveal uncertainty, overdue actions or a building that is beyond an in-house review, request an assessment quote from a provider serving London or Surrey.
Resource FAQs
The law does not prescribe one universal logbook format, but responsible persons must manage, maintain and record relevant arrangements. A logbook is a practical way to retain evidence and control defects.
Yes, provided records remain reliable, accessible, backed up and capable of showing dates, responsibility, changes, defects and closure evidence.
There is no single retention period for every record. Consider legal duties, system standards, contracts, insurance, enforcement and the value of showing maintenance history. Avoid deleting records simply because a calendar year has ended.
Named staff can record routine checks, while competent contractors provide service and inspection records. The responsible person should ensure roles, escalation and review are effective.
Sources and limitations
This page provides general information for England. The resource is not legal advice, certification or a substitute for competent building-specific assessment and action.