Fire alarm test log

The most-requested record on a fire inspection, and the easiest one to let lapse — it is weekly, so a gap is obvious.

No email address required. It is a file.

What it records

Testing a different call point each week is the usual practice, which is why the template has a column for it: a log showing the same point every week tells an inspector the rotation is not happening. The fault and action columns exist because a test that found something and was never followed up is worse evidence than a test that found nothing.

The columns

Column	What goes in it
Date	The date of the test.
Time	Useful where a site tests at a fixed time and staff need to expect it.
Call point	Which device was operated. Rotate through them.
Tested by	The person who did it, by name.
Sounders heard	Whether the alarm was audible everywhere it needs to be.
Result	Pass or fail.
Fault found	What was wrong, if anything.
Action taken	What was done, and by whom. Blank here with a fault recorded is the gap inspectors notice.

This is a starting point, not a compliance document. What your organisation actually needs to record follows from your own risk assessment and from the arrangements you have in place; a template cannot know either. Nothing here is legal advice.

Or stop keeping it in a spreadsheet

A spreadsheet records what you type into it. It does not chase you when a week is missed, turn a duty amber when a check falls due, or raise an action from a failed reading — and it is not much use as evidence, because it can be edited afterwards without trace.

How DutyHub handles fire safety Recurring checks See pricing