fire alarm test logbook business

Direct answer. A fire alarm logbook should show when the system was tested, which call point or method was used, whether the alarm operated as expected, who performed the test, any fault or false alarm, and how the problem was resolved. Keep competent maintenance reports with the routine entries and link unresolved defects to an owner and interim safety decision. Government guidance for offices and shops describes weekly routine tests using successive manual call points, with periodic maintenance by a competent person. Those tests are part of the Responsible Person's arrangements under the Fire Safety Order; a signed entry cannot substitute for a working warning system. Government offices-and-shops fire-safety guide.

This guide applies to business premises in England and Wales under the Regulatory Reform (Fire Safety) Order 2005. It concerns the test and fault evidence trail, not alarm design or the selection of a system category. Existing Complys fire safety and FRA software pages own their commercial topics. Scotland, Northern Ireland and specialist premises need the applicable local regime and installation guidance.

Identify the installed system and its test method

Before copying a generic weekly checklist, obtain the current fire risk assessment, alarm specification, zone or device list, panel instructions, service contract and any monitoring or evacuation interface details. A conventional system with manual call points is different from a networked, addressable or partly automatic system. Where a fire alarm is linked to a monitoring centre, smoke control, door releases or other systems, agree the test procedure so the right people know it is a test and the connected functions are understood. A competent maintainer should advise if the method is unclear.

Give each manual call point a stable location or ID. The government guide says a different call point should be used for each successive weekly test for electrical systems, commonly with a test key. That rotation helps test the path from the call point through the control equipment to the warning devices. A log with “alarm sounded” but no device ID makes it hard to see whether only one point has ever been exercised. Government guide, testing and maintenance.

Do not let a routine test become a dangerous surprise. Tell relevant staff and any monitoring centre according to the premises' procedure, consider vulnerable occupants or activities that may be disrupted, and restore the system to normal afterward. A test which leaves the panel in fault or disablement is not complete.

The legal frame and the limits of a weekly tick

Article 17 of the Fire Safety Order requires suitable maintenance of fire-safety equipment where necessary to safeguard relevant persons. The Responsible Person's assessment and arrangements under articles 9 and 11 determine what system and management are appropriate. Government small non-domestic premises guidance asks for weekly alarm testing, periodic servicing and a suitable record of testing and maintenance. The offices-and-shops guide describes a weekly routine test and competent periodic maintenance.

The weekly test is a limited functional sample. It does not replace competent inspection and servicing of detectors, sounders, batteries, interfaces, wiring and other system elements, nor does it prove the whole fire strategy is adequate. The precise service interval and task should reflect the installation, current standard, manufacturer instructions and competent advice. Do not turn a generic web list into a claim that every site has an identical statutory service table.

Government guidance also advises checking panel status regularly and recording false alarms and maintenance. A system can pass a call-point test one week and develop a fault the next day; the business needs a route to recognise and act on panel indications between scheduled tests. Government guide, fire-safety records.

The minimum useful entry

Record the premises, system or panel ID, date and time, tester, call point or test method, whether the panel received the signal, whether audible or visual warning operated where expected, whether any monitored or linked function behaved as intended where part of the agreed test, and whether the system was reset to normal. Add the next planned call point, a fault number or contractor job reference if needed.

If any part cannot be tested, record not tested, why, and who will complete it. Avoid a “pass” on a partial test. Where the test produced an unexpected result, describe it in ordinary language, not only an unexplained fault code. The code and panel display can be attached for a maintainer, but the manager needs to know whether warning coverage is impaired.

The log should also hold or link to:

• periodic inspection and service reports by a competent person;
• detector or device changes and software/configuration changes where relevant;
• faults, disablements and their start/end times;
• false alarms and the cause or investigation outcome;
• repairs, tests after repair and return-to-service decisions;
• changes to building layout or use that may require reassessment.

The Avon Fire and Rescue Service logbook is a useful official example of a fire-safety record format. Use it as a template, not as proof that a particular system meets its design standard.

Rotate points and make the test audible to the right people

A planned sequence prevents the easiest call point from being used every Friday while others go untouched. The government guidance suggests testing at the same time each week as good practice, but notes that additional tests may be needed so staff or people present outside normal working hours can hear the warning. For a building with shifts, remote areas or noisy work, ask whether the routine arrangement actually gives assurance across the people and spaces at risk. Government offices-and-shops guide.

Do not assume a sounder heard in reception was heard in a plant room or by a person who relies on a visual alert. The test procedure should reflect the fire risk assessment and competent system design; a routine tester should raise an observed coverage problem rather than certify an inaccessible area by assumption.

If the system is linked to an automatic fire alarm transmission service, tell the monitoring party that a test is planned and follow the agreed procedure to avoid a false emergency response. Record any unexpected transmission or failure so the linkage can be investigated. Follow the site's actual contract and system instructions; this article does not prescribe a universal alarm-receiving-centre procedure.

Faults and false alarms need a decision trail

When a test fails, identify what warning function is affected and who is exposed. The Responsible Person, with competent help as needed, should decide an interim control: repair, increased supervision, temporary warning arrangement, restriction of use or another measure appropriate to the risk. Record the decision, owner and review point. A contractor booking is not a substitute for immediate protection if people remain in the building.

After a repair, retain the work report and verify the system returned to normal, including any disabled zone or monitoring link. A report that says “attended” is weaker than a report that identifies the fault, action and successful retest. Keep the original failed test entry; do not overwrite it with the later pass.

False alarms are also useful evidence. Record date, cause where known, affected zone, response and any corrective action. Repeated false alarms can affect how people respond to a genuine warning and may signal a device, environment or management issue. The government offices-and-shops guide specifically lists false alarms among fire-safety records. Do not label every unexplained activation a “false alarm” until it has been investigated.

Example: a weekly test exposes an isolated zone

A store supervisor operates the next call point in the rotation. The panel records the input but the warning does not sound in the rear stock area. The supervisor records the point ID, time, observed failure and panel indication, tells the Responsible Person, and follows the site's immediate safety and maintainer escalation procedure. A technician later finds a disabled circuit left after maintenance, restores it and performs a functional retest. The manager records the return-to-service decision and checks whether the maintenance handover process needs changing. The first entry remains a failure, with the later repair linked to it.

The example shows why a logbook must support exception management as well as proof that tests were scheduled.

Common mistakes

• “Tested weekly” with no call-point ID, result or reset confirmation.
• Using the same convenient call point repeatedly without a rotation plan.
• Treating a weekly user test as a replacement for competent periodic service.
• Failing to tell a monitoring centre or staff that the alarm will be tested.
• Leaving a zone disabled after a test or service visit.
• Recording a fault but not assessing its immediate effect on occupants.
• Deleting failed entries once a repair is made.
• Assuming a software tick or reminder demonstrates legal compliance.

Software and next step

A system can help organise schedules, log entries, service documents and open defects. Before describing a specific Complys alarm-testing feature, verify the deployed product; this draft does not assert that Complys fire safety runs the weekly test, receives panel telemetry, automatically contacts a monitoring centre or certifies the system. Ask any software provider to demonstrate a failed test, escalation, repair and retest using one identifiable device.

Next step: inspect last month's fire-alarm entries for one site. Check that call points rotated, the panel was restored, faults and false alarms have linked decisions, and competent service reports are available. Fix the real system issue first if any entry reveals one.

Primary sources

• Regulatory Reform (Fire Safety) Order 2005.
• Government fire-safety risk assessment guide for offices and shops and small non-domestic premises guide.
• Avon Fire and Rescue Service fire-safety logbook.

Reviewed 4 October 2026. England and Wales. Installation-specific instructions and current competent maintenance advice govern the actual test method and service schedule.