Fire Alarm Test: How to Complete This Weekly Health and Safety Check

Why fire alarm testing matters

Fire detection systems are your first line of defence in a fire. They detect smoke or heat, sound the alarm, and give people time to evacuate safely. But these systems are complex — they have sensors, wiring, control panels, sounders, and backup batteries. Any component can fail.

The purpose of weekly testing is simple: verify the system works before you need it. A fire alarm that fails during a real emergency could cost lives. Weekly testing catches problems while there's still time to fix them.

Legal requirements

Most fire safety regulations worldwide require regular testing of fire detection and alarm systems. The specific frequency varies by jurisdiction, but weekly testing of manual call points is standard practice.

In the UK, the Regulatory Reform (Fire Safety) Order 2005 requires the responsible person to ensure fire safety measures are maintained in working order. British Standard BS 5839-1 recommends weekly testing of the fire alarm system, including activation of at least one manual call point. Similar requirements exist in the US (NFPA 72), EU member states, Australia, and most other developed nations.

Beyond legal compliance, your insurance policy likely requires documented evidence of regular fire alarm testing. If a fire occurs and you can't prove your alarm system was being maintained, your claim could be rejected.

The consequences of not testing

Equipment failure goes unnoticed. Sounders can fail, call points can become stuck, wiring can degrade, and backup batteries can die. Without testing, you won't know until there's a real fire.

False confidence. Staff and customers assume the alarm will warn them. If it doesn't work, they may not react to other warning signs like smoke or shouting.

Legal liability. If someone is injured in a fire and you can't demonstrate proper maintenance, you face potential prosecution, civil claims, and insurance rejection.

Enforcement action. Fire safety inspectors check testing records. Missing or incomplete records can result in enforcement notices, fines, or even prohibition orders that close your business.

Frequency and timing

Weekly testing

Fire alarms should be tested once per week, every week, without exception. This applies whether your premises are busy or quiet, whether it's peak season or closed for refurbishment. The system needs testing regardless of how much the building is used.

Same time and day

Always test at the same time on the same day each week. This serves two important purposes:

Building occupants expect it. If everyone knows the alarm test happens at 9am on Tuesdays, they won't panic when it sounds. They also won't ignore a real alarm because they assume it's a test — if the alarm sounds at any other time, they know to evacuate.

Staff remember to do it. A fixed schedule is easier to follow than "sometime this week." Build it into your routine so it becomes automatic.

Choose a time that minimises disruption — typically a quiet period like early morning before opening, or mid-afternoon during a lull. Avoid testing during peak service, deliveries, or when vulnerable people might be present.

Rotating call points

Each week, test a different manual call point (the red boxes on the wall). Over time, you should test every call point in your building. This ensures all points are working, not just the one nearest the control panel.

Keep a record of which call point was tested each week. Some businesses number their call points and work through them in sequence. Others use a floor-by-floor rotation. Whatever system you use, make sure every call point gets tested regularly.

How to complete the check

1. Call point tested

Before you activate the alarm, record which manual call point you're testing this week. This creates a log showing that all call points are being covered over time.

Why it matters:

Manual call points can fail individually. A call point might become stuck, disconnected, or damaged without any visible sign of a problem. If you only ever test the same call point, you'll never discover faults with the others.

Rotating through all call points ensures comprehensive coverage. Over a few months, every call point in your building should be tested at least once. This catches location-specific problems like water damage, physical impact, or wiring faults.

What good answers look like:

Be specific about location. Anyone reading the record should be able to identify exactly which call point was tested.

• "Main entrance, right side of front door"
• "Kitchen corridor, by fire exit"
• "First floor landing, top of stairs"
• "Call point #7 (bar area, near cellar door)"

If your call points are numbered, use the numbers consistently. If they're not numbered, consider adding labels to make record-keeping easier.

How to answer this for yourself:

Before testing, identify the call point you'll use this week. Check your previous records to see which ones have been tested recently. Choose one that hasn't been tested for a while, or follow your rotation schedule.

Walk to the call point and note its location in clear terms. Think about how you'd direct someone to that exact spot if they needed to find it.

Common mistakes (and how to avoid them):

"Fire alarm call point" — This is too vague. You might have a dozen call points. Which one?

"The usual one" — Testing the same call point every week defeats the purpose of rotation. Force yourself to move around the building.

Forgetting to rotate — Create a simple schedule or checklist showing all call points and when each was last tested. Follow it systematically.

Not recording the location — If you don't write it down immediately, you'll forget which one you tested. Record it before you activate the alarm.

Best practices to follow:

• Number or label all manual call points in your building
• Create a rotation schedule showing which call point to test each week
• Record the location before activating the alarm
• Ensure every call point is tested at least once per quarter
• Check the call point visually before testing — is it damaged, obstructed, or clearly marked?

2. Fire alarm test checks

This is the main testing procedure. Work through each item systematically to verify the system functions correctly from activation to reset.

Why it matters:

A fire alarm system has multiple components that must all work together. The call point must trigger the panel, the panel must activate all sounders and beacons, and the system must reset cleanly afterwards. Testing each step confirms the whole chain is working.

If you only check that the alarm sounds, you might miss a sounder that's failed in a distant part of the building, a beacon that doesn't flash, or a panel that doesn't communicate with your monitoring company. Systematic checking catches these problems.

What good answers look like:

Each checklist item should be physically verified, not assumed. Don't tick "alarm sounded correctly throughout building" while standing next to the panel — walk the building and listen.

Detailed guidance for each check:

Notified all occupants before testing

Before activating the alarm, warn everyone in the building. This prevents panic, allows people to prepare (hearing protection, pausing phone calls), and ensures no one calls emergency services for a test.

Use whatever method works for your premises — verbal announcement, tannoy system, email, or text message. Make sure the notification reaches everyone, including those in back-of-house areas, offices, or outdoor spaces.

Activated call point

Break the glass or lift the cover on the manual call point to trigger the alarm. Use the test key if available — this allows you to activate without breaking the glass element. If you must break the glass, have replacement glasses ready.

Note the time you activated the alarm. This helps verify prompt response from monitoring companies and confirms the system triggers immediately.

Alarm sounded correctly throughout building

Walk through the building while the alarm is sounding. Listen in every room, corridor, and outdoor area where people might be. The alarm should be clearly audible everywhere — not just loud, but unmistakably a fire alarm.

Pay attention to:

• Areas with high ambient noise (kitchens, plant rooms, entertainment areas)
• Enclosed spaces (toilets, storage rooms, offices)
• Areas where people use hearing protection or headphones
• Outdoor spaces like beer gardens or smoking areas

If you can't hear the alarm clearly in any area, that's a fault that needs addressing.

All sounders and beacons activated

As you walk the building, check that every sounder is making noise and every visual beacon is flashing. Sounders can fail individually — a building might have ten sounders with one silently failed.

Visual beacons are essential for people with hearing impairments. They must flash brightly and be visible from all areas they're meant to cover.

System reset successfully

After testing, reset the system using the control panel. The alarm should stop, the panel should return to normal status, and there should be no fault indicators. A system that won't reset cleanly may have an underlying problem.

Check the panel display carefully. Are there any fault codes, warning lights, or error messages? These indicate problems that need investigation even if the test otherwise passed.

Notified monitoring company (if applicable)

If your fire alarm is monitored by a third-party company (who alert the fire brigade when the alarm activates), you must tell them before and after testing. Otherwise, they might dispatch emergency services to a test, wasting resources and potentially incurring charges.

Follow your monitoring company's procedures. Usually this means calling before you test to put the system "on test" and calling afterwards to confirm testing is complete.

Common mistakes (and how to avoid them):

Standing at the panel for the whole test — You can't verify the alarm sounds throughout the building without walking the building. Delegate panel duties to someone else while you walk around.

Rushing through the checklist — Each item requires actual verification, not a quick glance. The test takes a few minutes, not a few seconds.

Forgetting the monitoring company — This can result in fire brigade call-outs, charges from your monitoring company, and embarrassment. Put "notify monitoring company" at the top and bottom of your procedure.

Ignoring minor issues — A sounder that seems "a bit quiet" or a beacon that flickers might be about to fail completely. Report and investigate anything unusual.

Best practices to follow:

• Use two people — one at the panel, one walking the building
• Have a floor plan marked with sounder and beacon locations
• Record the time taken for the alarm to activate after triggering the call point
• Check all areas, including those not normally occupied during tests
• Test during conditions similar to normal operation (music playing, kitchen equipment running)

3. Test result

After completing all checks, record whether the system passed or failed the test overall.

Why it matters:

The pass/fail result creates a clear record of system status. Over time, this shows whether your fire alarm is reliably working or developing problems. A pattern of failures indicates systemic issues that need addressing.

This field also triggers different follow-up actions. A pass means normal operation continues. A fail means immediate investigation and repair.

What good answers look like:

Pass — system working correctly: All components functioned as expected. The alarm activated promptly, sounded throughout the building, all sounders and beacons worked, and the system reset cleanly.

Fail — issue identified: Something didn't work correctly. This could be a call point that wouldn't activate, a sounder that didn't sound, a beacon that didn't flash, a panel error, or any other malfunction.

Be honest. If anything was wrong, even something minor, record it as a fail and document the issue in the notes. You can still operate while arranging repairs, but you need the failure on record.

How to answer this for yourself:

Ask yourself: "If there was a real fire right now, would this system reliably alert everyone in the building?"

If the answer is anything other than a confident "yes," that's a fail. Don't let small issues slide — they become big issues.

Common mistakes (and how to avoid them):

Recording "Pass" when there were minor issues — Minor issues are still failures. A sounder that's "a bit quiet" in one room is still a sounder that might not wake someone in that room during a night-time fire.

Forgetting what happened during the test — Fill in the result immediately after completing the test. Don't wait until the end of the day when details have faded.

Pressure to always pass — No one wants to report failures, but unreported failures become real emergencies. A documented fail that gets fixed is far better than an undocumented problem that persists.

Best practices to follow:

• Record the result immediately after testing
• Be conservative — when in doubt, record it as a fail and investigate
• Use the notes field to explain any concerns, even for tests that pass
• Track pass/fail rates over time to identify deteriorating equipment

4. Notes

Use this field to record any observations, issues, or actions taken during or after the test.

Why it matters:

The checklist and pass/fail result capture the basics, but the notes capture the detail. If something went wrong, this is where you explain what happened and what you did about it. If everything was fine, this confirms there were no concerns.

Notes are invaluable for:

• Explaining failures to maintenance contractors
• Demonstrating due diligence to inspectors
• Tracking recurring issues over time
• Reminding yourself what happened when reviewing old records

What good answers look like:

For a straightforward pass:

• "All working correctly. No issues observed."
• "Test completed successfully. Full building walk-through confirmed all sounders audible."

For a pass with minor observations:

• "Pass. Noted that call point cover was stiff to lift — may need lubrication. Sounder in ladies' toilets seemed quieter than usual but still clearly audible."
• "System working correctly. Panel showed low battery warning — scheduled battery replacement for next week."

For a fail:

• "Sounder in first floor office did not activate. Alarm audible from corridor but not inside office with door closed. Reported to [maintenance company], engineer visiting tomorrow."
• "Call point would not activate — button stuck. Used call point #4 instead for test (passed). Faulty call point reported and labelled out of order."
• "Test failed — panel showed zone 2 fault after reset. Full system inspection booked for [date]. Building still protected by remaining zones."

How to answer this for yourself:

Immediately after the test, ask yourself:

• Was there anything unusual or concerning?
• Did any component behave differently from normal?
• Are there any actions I need to take or arrange?
• Is there anything the next person doing this test should know?

Write notes as if you're leaving a message for a colleague who wasn't present. Give them enough detail to understand what happened.

Common mistakes (and how to avoid them):

Leaving notes blank — Even "No issues" is useful information. Blank notes suggest the test might not have been done properly.

Vague descriptions — "Sounder not working" doesn't help the engineer. "Sounder in first floor office (above bar, near window) did not activate. Other sounders working normally" gives them what they need.

Not recording actions taken — If you reported a fault, who did you report it to? When is it being fixed? This matters for demonstrating you acted on the problem.

Only noting failures — Positive observations are valuable too. "Particularly impressed by new sounder in beer garden — very audible" helps when planning future improvements.

Best practices to follow:

• Always write something, even if just "All working correctly"
• Be specific about locations and symptoms
• Record any actions taken and when repairs are scheduled
• Note anything you want to follow up on next week
• Include names of people you reported issues to

What to do when tests fail

Immediate actions

Don't panic, but don't ignore it. A failed test doesn't mean your building is unprotected — other parts of the system are probably still working. But it does mean you have a problem that needs fixing.

Assess the severity:

• Is the entire system down, or just one component?
• Is the affected area still covered by other sounders?
• Can people in that area hear the alarm or see beacons from adjacent zones?

Report the fault immediately. Contact your fire alarm maintenance company and explain what's wrong. Most contracts include emergency call-outs for system failures.

Implement interim measures. If an area isn't covered by the alarm, consider:

• Increased staffing in that area
• Temporary sounders or bells
• More frequent fire warden patrols
• Reducing occupancy until repairs are complete

Document everything. Record what failed, when you reported it, who you spoke to, and what interim measures you've put in place.

Getting repairs done

Fire alarm faults should be repaired as soon as reasonably practicable — not "when convenient" but with genuine urgency. A fault that persists for weeks without good reason is a compliance failure.

Your maintenance contract should specify response times for different fault types. A complete system failure might require same-day attendance; a single faulty sounder might allow a few days.

After repairs, retest the system to confirm the problem is fixed. Document the repair and the successful retest.

Recurring faults

If the same component keeps failing, there's an underlying problem. This might be:

• Equipment reaching end of life
• Environmental factors (moisture, dust, heat)
• Installation issues
• Interference from other systems

Discuss recurring faults with your maintenance provider. You may need component replacement, environmental protection, or system modifications rather than repeated repairs.

Common mistakes to avoid

Testing at random times. Inconsistent timing means occupants don't know when to expect tests, and staff forget to do them. Pick a time and stick to it.

Only testing one call point. If you always test the same call point, you'll never find faults with the others. Rotate systematically.

Not walking the building. The alarm might sound fine at the panel but be inaudible in distant rooms. Check everywhere.

Skipping tests when busy. A fire doesn't care how busy you are. Weekly testing is non-negotiable — reschedule if necessary but never skip.

Recording tests that weren't done. Falsifying records is fraud and puts lives at risk. If you missed a test, document that honestly and test as soon as possible.

Ignoring minor issues. Small problems become big failures. A sounder that's "slightly quiet" today might be silent tomorrow.

Not following up on failures. Recording a fault isn't enough — you need to fix it. Track repairs and confirm they're completed.

Summary

Weekly fire alarm testing is a legal requirement and a lifesaving habit. Test at the same time each week, rotate through different call points, walk the building to verify all sounders and beacons work, and document everything.

When tests pass, record that clearly. When tests fail, report the fault immediately, implement interim measures, and follow up until repairs are complete.

Your fire alarm is only useful if it works. Weekly testing proves that it does.