Emergency Lighting Test: How to Complete This Monthly Health and Safety Check

Why emergency lighting testing matters

Emergency lighting exists for one purpose: to help people escape when normal lighting fails. During a fire, power cut, or other emergency, these battery-powered lights illuminate escape routes, emergency exits, and high-risk areas so people can find their way out safely.

But emergency lighting is only useful if it works. Batteries lose capacity over time. Bulbs burn out. Charging circuits fail. And because emergency lights only activate during power failures, you might not discover a fault until the worst possible moment — when you actually need them.

Monthly testing verifies that your emergency lighting system is ready. By simulating a power failure and checking every unit, you catch faults while there's still time to fix them.

Legal requirements

Most fire safety regulations require emergency lighting in commercial and public buildings, along with regular testing to ensure the system works. Monthly functional tests are standard practice internationally.

In the UK, the Regulatory Reform (Fire Safety) Order 2005 requires the responsible person to ensure fire safety measures, including emergency lighting, are maintained in working order. British Standard BS 5266-1 specifies monthly functional tests plus annual full-duration tests. Similar standards exist in the US (NFPA 101, NFPA 110), EU member states (EN 50172), Australia (AS 2293), and most other jurisdictions.

The monthly test is a brief functional check — you're verifying that units illuminate, not running down the batteries. The annual test by a professional contractor involves a full three-hour discharge to confirm battery duration under load.

The consequences of not testing

Battery failure goes unnoticed. Emergency light batteries typically last 3-4 years, but they can fail earlier. Without testing, you won't know until the power fails.

Bulb failures accumulate. A single dead bulb might not seem critical, but if multiple units have failed, your escape routes may be dangerously dark.

False confidence. Staff assume the emergency lighting will work because it's "always been there." That assumption could prove fatal.

Enforcement action. Fire safety inspectors check emergency lighting test records. Missing or incomplete records can result in enforcement notices, fines, or closure.

Insurance implications. If a fire causes injury and you can't demonstrate proper maintenance, your liability exposure increases significantly.

Frequency and timing

Monthly functional tests

Emergency lighting must be tested once per month, every month. This is a brief test — you simulate power failure, walk the building to verify all units illuminate, then restore power. The whole process typically takes 10-15 minutes depending on building size.

The monthly test should NOT fully discharge the batteries. You're checking that units work, not testing battery duration. Keep the test brief — typically a few minutes at most. Running down batteries monthly degrades them faster and could leave you with inadequate backup capacity.

When to test

Choose a quiet time when a few minutes of reduced lighting won't cause problems. Early morning before opening or late afternoon during a quiet period works well. Avoid testing during:

• Peak service when reduced lighting could cause accidents
• Times when vulnerable people are present
• Periods when escape routes are congested

Warn building occupants before testing. Sudden darkness can cause alarm, especially in areas without natural light.

Annual professional tests

Monthly staff testing doesn't replace annual professional inspections. Once a year, a qualified contractor should:

• Conduct a full three-hour duration test
• Inspect all units for physical damage and deterioration
• Test battery capacity under full load
• Check charging circuits and connections
• Verify illumination levels meet standards
• Provide a detailed report and certificate

Schedule this alongside your annual fire alarm maintenance if possible — many contractors service both systems.

How to complete the check

1. Emergency lighting test procedure

This checklist guides you through the complete testing process from start to finish. Each step must be completed and verified, not just assumed.

Why it matters:

Emergency lighting systems have multiple components that must all work correctly. The charging circuit keeps batteries topped up. The battery stores energy. The changeover circuit detects power failure and switches to battery. The lamp or LED provides light. A failure anywhere in this chain means no light when you need it.

The monthly test verifies the entire system functions as intended — from detection of power loss through to light output.

Detailed guidance for each check:

Notified all occupants before testing

Before cutting power, warn everyone in the building. Even a brief period of reduced lighting can cause alarm, particularly in windowless areas like toilets, cellars, or internal corridors.

Use whatever method reaches everyone — verbal announcement, tannoy, team messaging, or signs. Make sure back-of-house staff and anyone in storage or prep areas knows what's happening.

Isolated mains power to emergency lighting circuit

Locate the test switch or circuit breaker that controls your emergency lighting. This is usually in the main electrical panel, sometimes with a dedicated "Emergency Lighting Test" label.

Different systems work differently:

• Self-contained units — Each light has its own battery. You may need to test using a fish-tail key in each unit, or there may be a central test switch.
• Central battery systems — A single battery powers multiple lights. There's usually a main test switch that simulates power failure.

If you're not sure how to safely initiate the test, ask your maintenance contractor to show you during their next visit. Never test by switching off the main building supply — this affects other systems and is potentially dangerous.

Walked through all areas to check lights illuminated

This is the critical step. You must physically walk the entire building and visually confirm that every emergency light unit is illuminated.

Check:

• Escape route lights — The lights along corridors and in stairways
• Exit signs — Both internally illuminated signs and externally lit exit signs
• High-risk areas — Plant rooms, kitchens, anywhere with particular hazards
• Open areas — Large rooms where escape routes cross

As you walk, note whether each light is:

• Illuminated at normal brightness
• Illuminated but dim (suggesting battery weakness)
• Not illuminated (failed)
• Showing any fault indicators

Checked exit signs are illuminated

Exit signs deserve special attention. These are often the most critical emergency lights — they show people where to go. Check every exit sign, both:

• Internal signs — Pointing towards exits along corridors
• Final exit signs — Above the actual doors to outside

Verify the signs are clearly readable, not just glowing. If the text or symbol is dim or uneven, the unit may be failing.

Brightness sufficient to illuminate escape routes

Emergency lighting doesn't need to be as bright as normal lighting, but it must be bright enough for people to see where they're going and identify obstacles. As you walk, ask yourself:

• Could I safely walk this route in only emergency lighting?
• Are there any dark spots where someone could trip?
• Can I see door handles and exit hardware?

If any area seems inadequately lit, note its location for follow-up.

Restored mains power supply

After completing your walk-through, return power to the emergency lighting circuit. This is important — if you forget, the batteries will drain completely, potentially damaging them and leaving you unprotected.

Watch the units as power returns. They should switch back to charging mode smoothly. Any units that flicker, buzz, or show fault lights need investigation.

Confirmed all units returned to charging mode

Walk past a few units after restoring power to verify they've returned to normal standby mode. Most units have a small indicator light (often green) showing they're charging and ready.

If any unit doesn't return to charging mode, or shows a fault indicator, note its location. This unit may work briefly on battery but won't recharge for the next power failure.

Common mistakes (and how to avoid them):

Testing from one location — Standing at the switch and glancing down the corridor doesn't count. You must walk the entire building and check every unit.

Running the test too long — This isn't a battery duration test. A few minutes is sufficient to verify units illuminate. Longer tests unnecessarily drain batteries.

Forgetting to restore power — If you leave the emergency lighting on battery, you'll drain the batteries and leave the building unprotected. Make restoring power the final checklist item.

Testing only visible areas — Emergency lights in rarely-visited areas (storage rooms, plant rooms, roof access) still need checking. People may need to escape through these areas.

Best practices to follow:

• Create a floor plan showing all emergency light locations
• Follow a consistent route so you don't miss any units
• Carry a torch in case you need extra light while checking
• Test during similar conditions to normal operation (some natural light, typical activity)
• If unsure how to safely initiate the test, get contractor guidance

2. Number of units checked

Record the total number of emergency lighting units you inspected during this test.

Why it matters:

Counting units serves two purposes. First, it ensures you're checking the whole system — if you usually count 25 units but today only found 23, you may have missed some. Second, it provides evidence of thoroughness for inspectors and audits.

Your building should have a fixed number of emergency lighting units. If that number changes (units added, removed, or replaced), update your records.

What good answers look like:

Simply record the number: "24", "18", "32"

If your building is large or has distinct zones, you might record by area: "12 ground floor, 8 first floor, 4 cellar = 24 total"

How to answer this for yourself:

As you walk the building, count each unit you check. Keep a tally on paper or in your head. Cross-reference with your floor plan or previous test records to make sure you haven't missed any.

If you're not sure how many units you should have, ask your maintenance contractor for an inventory, or count carefully during this test and use that as your baseline.

Common mistakes (and how to avoid them):

Guessing the number — "About 20" isn't good enough. Count accurately each time.

Counting different numbers each month — This suggests you're missing units or counting inconsistently. Investigate the discrepancy.

Not knowing how many you should have — Create an inventory list. If you don't know your baseline, you can't tell if you've missed units.

Best practices to follow:

• Maintain an inventory of all emergency lighting units with locations
• Count as you walk, don't estimate afterwards
• Investigate if your count differs from previous months
• Update the inventory when units are added, moved, or removed

3. Number of faulty units

Record how many units showed faults during the test. Enter 0 if all units worked correctly.

Why it matters:

This field captures the outcome of your test in quantifiable terms. A single faulty unit needs attention. Multiple faulty units suggest a systemic problem — ageing equipment, environmental issues, or poor maintenance.

Tracking faulty units over time reveals patterns. If the same units keep failing, they may need replacement. If different units fail each month, there may be a broader system issue.

What good answers look like:

Be precise:

• "0" — All units working correctly
• "1" — One unit failed
• "3" — Three units showed faults

If you found faults, you'll provide details in the notes section.

How to answer this for yourself:

Count units that showed any problem during testing:

• Units that didn't illuminate at all
• Units that were noticeably dim
• Units showing fault indicators
• Units that flickered or buzzed
• Units that didn't return to charging mode

Be conservative — if a unit looked questionable, count it as faulty and investigate.

Common mistakes (and how to avoid them):

Only counting complete failures — A dim light is still a faulty unit. It's showing battery weakness and will likely fail completely soon.

Ignoring fault indicators — If a unit has a red warning light but still illuminated, it's still faulty. Something is wrong and needs investigation.

Not recording faults to avoid paperwork — This defeats the entire purpose of testing. Record faults honestly so they get fixed.

Best practices to follow:

• Count any unit that wasn't working perfectly
• Include units showing warning indicators, not just dead units
• Record the fault count before leaving the building while it's fresh
• Use the notes to explain what each fault looked like

4. Test result

Record whether the overall test passed or failed.

Why it matters:

The pass/fail result provides a clear summary of system status. This is what inspectors look for, what managers review, and what trends reveal over time.

A system can pass with minor observations (notes for follow-up) or fail with faults requiring repair. The distinction drives different actions.

What good answers look like:

Pass — all units working: Every unit illuminated correctly, no fault indicators, adequate brightness throughout, system restored to charging mode without problems.

Fail — faulty units identified: One or more units didn't work correctly. This requires repair and follow-up.

How to answer this for yourself:

Ask: "Would this emergency lighting system effectively guide people to safety during a power failure right now?"

If any unit failed, if any escape route was inadequately lit, or if any exit sign didn't work, that's a fail. One dead unit in a critical location can make the difference between safe evacuation and someone being trapped in the dark.

Common mistakes (and how to avoid them):

Passing when there were faults — If you found faulty units, record it as a fail. You can note that faults were minor or that adequate coverage remained, but the formal result should reflect that something wasn't right.

Being overly harsh — A single non-critical fault in a well-lit area with redundant coverage might warrant a pass with notes. Use judgement, but err on the side of recording issues.

Best practices to follow:

• Record the result immediately after completing the test
• Be honest — a documented fail that gets fixed is better than an undocumented problem
• Use notes to provide context for the pass/fail decision
• Track pass/fail trends over time

5. Notes

Record details of any faulty units, their locations, and actions taken. Note any observations about the system even if it passed.

Why it matters:

The notes field turns a simple pass/fail into useful information. When a unit fails, someone needs to know where it is and what's wrong. When a contractor visits, they need specifics. When an inspector reviews records, they want to see that you investigated and acted on problems.

Good notes also track the system's condition over time. Patterns become visible — certain units failing repeatedly, certain areas always problematic, gradual decline in overall brightness.

What good answers look like:

For a clean pass:

• "All 24 units working correctly. Good brightness throughout. No concerns."
• "Test completed successfully. All escape routes and exit signs adequately illuminated."

For a pass with observations:

• "All units working. Noted unit in gents toilets seems dimmer than others — monitor next month."
• "Pass. Unit above cellar stairs showing amber indicator but still illuminated. May need battery replacement soon."

For a fail:

• "Unit in main corridor (between bar and kitchen entrance) not illuminated. Appears completely dead. Reported to [contractor], visit booked for Thursday."
• "2 faulty units: (1) First floor landing — very dim, probably battery failure. (2) Kitchen fire exit sign — flickering. Both reported to maintenance."
• "Exit sign above front door not working. Adequate light from adjacent units but sign itself is critical for direction. Emergency repair requested."

How to answer this for yourself:

For each fault, record:

• Exact location (be specific enough that someone unfamiliar could find it)
• What the fault looked like (dead, dim, flickering, fault indicator)
• What action you've taken (reported to whom, when is repair expected)

For passing tests, record anything you want to monitor or follow up, even if not a current fault.

Common mistakes (and how to avoid them):

Blank notes — Even "All working correctly" is useful. Blank notes suggest a rushed or incomplete test.

Vague locations — "One light not working" doesn't help the electrician. "Unit above cellar stairs (third step from bottom)" does.

Not recording actions — If you reported a fault, note who you reported it to and when repair is expected. This demonstrates you acted on the problem.

Not following up — Notes from last month mentioned a dim unit. Did it get fixed? Did you check? Update the record.

Best practices to follow:

• Always write something, even for perfect results
• Be precise about locations — use landmarks, door names, or unit numbers
• Record who you reported faults to and expected repair dates
• Review previous month's notes and confirm issues were resolved
• Note anything you want to check or monitor next month

What to do when tests fail

Immediate actions

Don't panic, but do act. A failed unit doesn't necessarily mean your building is unsafe — there may be adequate coverage from other units. But it does mean your emergency lighting isn't at full capacity.

Assess the severity:

• Is the failed unit on a critical escape route?
• Are there other units providing coverage in the same area?
• Is this a single failure or multiple failures?

Report the fault promptly. Contact your emergency lighting maintenance contractor and explain what you found. Provide the location, symptoms, and any error indicators.

Consider interim measures. If a critical area has lost coverage:

• Could a portable emergency light provide temporary coverage?
• Should you restrict access to that area until repaired?
• Do fire wardens need briefing on the changed conditions?

Document everything. Record what failed, when you reported it, and what interim measures you've implemented.

Getting repairs done

Emergency lighting faults should be repaired promptly. A single failed unit in a non-critical location might wait a few days; a failed exit sign or lighting on a main escape route needs urgent attention.

Your maintenance contract should specify response times. Check what's covered and don't accept delays for critical failures.

After repairs, test the repaired unit to confirm it's working. Document the repair and successful retest.

Recurring faults

If the same unit keeps failing, there's an underlying problem:

• Battery end-of-life — Batteries typically last 3-4 years. Recurring failure often means replacement is needed.
• Environmental factors — Heat, moisture, or vibration can shorten component life.
• Electrical supply issues — Charging problems can cause repeated battery failure.

Discuss recurring faults with your contractor. Don't just keep replacing batteries — find and fix the root cause.

Monthly tests vs annual tests

Monthly functional test (this check)

Purpose: Verify that units illuminate when power fails.

Duration: Brief — a few minutes, not long enough to significantly discharge batteries.

Who does it: Trained staff member.

What's checked:

• All units illuminate
• Adequate brightness
• Exit signs visible
• System returns to charging mode

Annual full-duration test

Purpose: Verify that batteries can sustain illumination for the required duration (usually 3 hours).

Duration: Full rated duration — typically 3 hours.

Who does it: Qualified contractor.

What's checked:

• Battery capacity under sustained load
• Physical condition of units
• Illumination levels with photometer
• Charging circuit performance
• Full system report and certificate

Monthly testing keeps you aware of system status. Annual testing proves the system meets full specifications.

Common mistakes to avoid

Only checking visible units. Emergency lights in storage rooms, plant areas, and cellars still need checking. People may need to escape through these areas.

Running the test too long. Monthly tests should be brief — just long enough to verify units illuminate. Extended tests drain batteries unnecessarily.

Forgetting to restore power. Leaving emergency lighting on battery drains the batteries and leaves you unprotected. Make power restoration a checklist item.

Assuming the system is fine because it was fine last month. Faults can develop at any time. Test thoroughly every month.

Not knowing your unit count. If you don't know how many units you should have, you can't know if you've checked them all.

Ignoring dim units. A dim emergency light is a warning sign. The battery is failing and the unit may be completely dead next month.

Relying on monthly tests alone. Monthly staff tests don't replace annual professional inspections with full-duration discharge tests.

Summary

Monthly emergency lighting testing ensures your backup illumination system is ready for real emergencies. Simulate power failure, walk the entire building, check every unit, record what you find, and restore power promptly.

Count your units. Note the faulty ones. Be specific about locations and symptoms. Report faults immediately and follow up until they're fixed.

Your emergency lighting is the last line of defence when the power goes out. Monthly testing proves it's ready.