Fire Alarm Weekly Test Guide: How to Test & Record It

Basic checks do not replace competent maintenance, design or fault diagnosis

Follow the premises fire procedure, preserve the first-event information and use formal impairment controls whenever testing, isolation or faults reduce protection.

KEY POINTS

Start with these checks

Rotating call point test A different manual call point should be used each week where practicable.

Alarm output confirmation Occupants or nominated staff should confirm audible and visual warning.

Monitoring notification Alarm receiving centres and other connected parties may need advance notice.

Log-book record The test point, result and any defects should be recorded.

◫ Typical situations Where this guidance is commonly used. ⌄

No alarm after operating call point
Some sounders silent
Panel does not show correct zone
Remote signalling not received
System will not reset after test

✓ Safe first checks Checks before reset, testing or engineering work. ⌄

Confirm there is no genuine fire condition.
Record the exact panel, device or alarm information.
Check the zone plan, log book and recent work.
Notify monitoring services and occupants before planned testing.
Do not leave any part of the system isolated without formal controls.

Important: Silencing, resetting or testing should never be used to hide an unresolved fault or unwanted-alarm cause.

1 Step 1 — Prepare the site Use authorised procedures and preserve the event information before reset, isolation or testing. ⌄

Notify occupants, monitoring services and any affected parties before the test.

2 Step 2 — Operate one manual call point Use authorised procedures and preserve the event information before reset, isolation or testing. ⌄

Use the correct test key and confirm the panel shows the expected zone or address.

3 Step 3 — Confirm outputs, reset and record Use authorised procedures and preserve the event information before reset, isolation or testing. ⌄

Check alarm operation, restore the call point, reset the system and enter the result in the log book.

⌁ What this check proves The purpose and limitation of this procedure. ⌄

A weekly test confirms that the system can receive a fire signal, operate the expected alarm outputs and be reset. It is not a substitute for periodic maintenance.

⌘ Further technical checks Competent-person or reference-level guidance. ⌄

Rotate test points over time.
Check any agreed remote signalling confirmation.
Record sounder, VAD or interface defects immediately.
Do not test by removing detector heads.
Escalate any failure to the maintaining organisation.

◇ Information and equipment needed Useful records and tools. ⌄

Panel make and model
Zone plan and as-fitted drawings
Cause-and-effect information
System log book and previous service reports
Manufacturer-approved test tools and instructions

▣ Parts, records or tools involved Common items linked to this guidance. ⌄

Manual call-point test key
Fire alarm log book
Zone plan
Monitoring contact details
Site test procedure

! When to stop and escalate Conditions requiring competent specialist attendance. ⌄

The system will not reset or return to normal.
Detection, alarm outputs or signalling are unavailable.
A power, battery, loop or network fault persists.
Repeated false alarms have no confirmed cause.
Programming, wiring or system design changes are required.
The site cannot maintain its intended fire strategy.

? Frequently asked questions Common testing and reference questions. ⌄

Does a weekly test replace servicing?

No. The weekly test is a user check and does not replace periodic inspection and maintenance by a competent person.

Should faults be reset to see if they return?

Only after recording the condition and checking the likely cause. Repeated resets can remove useful diagnostic information.

Can any multimeter be used on a fire alarm system?

The instrument and test method must be suitable for the circuit, voltage and connected electronics.