Weekly fire alarm testing procedure
- Plan the test. Confirm the time, device or zone, and communication needed before the alarm sounds.
- Carry out the test. Activate the selected call point or device and confirm the alarm operates as expected.
- Record the result. Log the date, time, device or zone, user, outcome, notes, and any follow-up action.
Repeating the same process each week makes the logbook easier to audit and reduces the risk of vague entries such as "tested ok" without context.
What should be recorded after a weekly test?
Record enough information for someone else to understand the test later. Include the premises, date, time, person completing the test, call point or zone, result, faults found, action taken, and any attachment or photo if needed.
A digital fire logbook helps by keeping the entry tied to the site and user, rather than depending on handwritten notes or spreadsheets.
How should missed fire alarm tests be handled?
Missed tests should not disappear. They should be visible, explained, and followed up. If a test was not completed, record the reason and assign the next action so the compliance gap is clear.
Fire Logbook Pro includes reminders and escalation emails so missed checks are easier to spot before an audit. See our fire safety compliance software page for the broader workflow.
Using QR codes for weekly test records
QR codes are useful when the test is carried out at a fixed location, such as near a fire alarm panel. Scanning the code opens the correct site record and reduces the chance of logging activity against the wrong premises.
Learn more about QR code fire logbook access.
Make weekly fire alarm tests easier to evidence
Create a cloud logbook with reminders, QR access, attachments, and exportable evidence packs.
Create account