Fire alarm test log template

A fire alarm log should show that the planned test was performed, which point or system was checked, what happened and what was done about any fault. Use the tables below for routine test and maintenance records. Adapt them to the building's alarm design, fire risk assessment, manufacturer instructions and competent service schedule. A signed row is evidence of a check, not proof that the entire system is compliant or will operate perfectly in a fire.

For non-domestic premises in England and Wales, Article 17 of the Fire Safety Order requires suitable maintenance of fire-safety facilities and equipment where necessary. GOV.UK's small non-domestic premises guide describes a suitable test and maintenance record as a logbook or electronic record. It describes weekly alarm tests using a different manual call point each time where applicable. Scotland and Northern Ireland have different fire-safety legislation; apply their requirements and local fire strategy separately.

Copyable premises and system details

Keep an up-to-date list of manual call points and zones. A rotating test is only meaningful if the person conducting it knows which point was used last and which is due next. Where a building has a different fire-warning arrangement, such as a small premises with a manually operated warning device, record the appropriate test method instead of pretending it has an electrical call-point system.

Copyable weekly test record

The GOV.UK offices-and-shops guide describes weekly testing following the manufacturer's or installer's instructions, with a different manual call point on successive tests for an electrical system. It says the test checks that the control equipment receives a signal and activates the warning alarms. Do not infer from one weekly call-point test that every detector, sounder, cause-and-effect sequence or backup power source has been individually tested. Those require the maintenance regime appropriate to the installed system.

Warn occupants according to the building procedure so a planned test is not mistaken for an emergency, while ensuring people still respond to alarms outside the agreed test period. If the system is monitored, follow the alarm receiving centre's procedure before and after testing to avoid an unwanted emergency call. Record any bypass or isolation and verify it is restored. Do not leave an alarm zone disabled after a routine check.

If the panel shows a fault before testing, record it. A successful call-point activation does not clear a pre-existing fault. Mark a test incomplete if the intended area was not checked or a connected control could not be observed. Never enter “pass” solely because the test key was turned.

Copyable competent maintenance and service record

Routine user tests and competent-person servicing are different tasks. The GOV.UK fire-safety guidance says testing and maintenance should be carried out by a competent person, with a named person supervising routine arrangements. The exact service frequency and technical checks should follow the current applicable standard, system design, manufacturer and fire risk assessment. This template does not prescribe a universal six-month visit or certify conformity with BS 5839.

Attach or reference the service report. If the engineer recommends replacement, record a separate action and owner. “Engineer attended” is not a closure outcome when a fault remains. A defect should have a repair reference, interim arrangement, retest and sign-off.

Copyable fault, false-alarm and repair tracker

Record false alarms separately from planned tests. Note the cause if known, affected zone, response and investigation. Repeated false alarms can lead occupants to disregard warnings; the GOV.UK places-of-assembly guidance advises investigating and remedying excessive false alarms. A false-alarm record should not be used to delete evidence of an actual activation or hide an unresolved defect.

If part of the system fails, the responsible person should assess what fire-safety function has been lost and what can safely continue. Depending on the building and fault, this could require a competent engineer, temporary procedure, changed occupancy or other control. The log records the decision; it cannot determine the building remains safe. Make sure fire wardens, facilities teams and relevant occupiers know about any temporary arrangement.

How to use the log each week

1. Check the panel and prior open items. Review existing faults, isolates and last call point before initiating a test. Stop and escalate a significant unexpected condition.
2. Follow the site's test procedure. Tell the alarm receiving centre and occupants where required. Use the intended call point or device and record its exact ID. Follow the manufacturer's instructions for safe operation and reset.
3. Observe the outcome. Confirm that the panel receives the signal and the alarm is heard in the area the procedure requires. Note linked releases or controls only if the agreed test includes them. Do not claim a test of something not observed.
4. Restore normal operation. Reset the call point and panel, clear any permitted temporary isolate and check that the panel returns to its expected state. Record any remaining fault and the person responsible for it.
5. File evidence and raise action. Enter the result promptly, attach the system printout or service report where useful, and assign any defect. An overdue repair stays visible until verified.

Keep the test time reasonably consistent where that suits occupancy, but account for night and weekend users. The GOV.UK offices-and-shops guidance notes additional tests may be needed so people present outside normal hours can hear the alarm. That decision belongs in the fire strategy, not a one-size-fits-all schedule copied from this template.

Worked example

On Tuesday morning, the caretaker tests call point MCP-07 in the east corridor, the next point in rotation. The panel receives the signal but one occupied rear office does not hear the alarm. The log records a fail for audibility rather than a pass because the panel activated. The fire safety manager arranges an immediate assessment, tells affected staff about the interim arrangement and asks the service company to investigate. The engineer finds a sounder fault, repairs it and records a retest. Only after the responsible person reviews that evidence is the defect closed. The next week's routine test continues the call-point rotation; it does not erase the fault history.

Frequent questions

Does the alarm have to be tested every week? The GOV.UK guidance for common non-domestic premises describes weekly testing and call-point rotation. Confirm the applicable fire law, building's system, current technical standard and competent advice. This is not a universal statement for every domestic smoke alarm or unusual fire-warning design.

Can the digital log replace a paper book? GOV.UK recognises an electronic record. It should remain available to the responsible person and inspectors, preserve history and attachments, and make open faults visible. A digital tick without device or result detail is weaker than a complete paper record.

Is a weekly test the same as maintenance? No. Routine activation checks one part of the warning chain. Competent maintenance examines the system according to its design and applicable standards. Keep both records and link them.

Complys and internal links

The intended money-page relationship is the verified Complys fire risk assessment software page, subject to exact host, live route and product verification. Ask Complys to demonstrate how current functionality stores test logs, asset IDs, attachments and open defects. Do not claim that it tests alarms, monitors panels, certifies BS 5839 compliance or calls the fire service automatically without technical proof. Link to the fire risk assessment owner for the whole-building strategy and the emergency-lighting log for that distinct system, rather than combining two test types into one ambiguous form.

Source and writer-side QA record

Intent/cannibalisation: A copyable alarm-specific test log, distinct from fire risk assessment, installation design and emergency lighting. Public search on 6 October 2026 found no exact Complys owner at proposed path; repository check pending. Product truth: no automatic testing, panel integration or certification claim. Internal links: proposed routes need canonical-host verification. Writer-side disposition: READY.