Overview
Emergency lighting is one of those systems that can look “fine” until a real event exposes gaps:
- failed batteries
- dead fittings
- missing test records
- bulkhead lights that no longer provide meaningful coverage
For property teams, the goal is simple: regular checks, clear evidence, and defects closed out.
The simple purpose of testing
Emergency lighting is there to support safe evacuation if normal lighting fails.
Testing is basically asking two questions:
- Do fittings operate when needed? (functional checks)
- Do they stay on for the required duration? (duration testing)
If you can answer those two questions with evidence, you’re most of the way there.
What “monthly” and “annual” tend to mean
Different sites use different terms, but a common structure is:
- regular functional checks (often monthly): confirm fittings operate as expected when tested
- full duration test (often annual): confirm the system supports its rated duration
The exact regime depends on the system and the building profile. If you’re unsure, defer to competent guidance.
Functional vs duration testing
| Test type | What it proves | Typical disruption | What to record |
|---|---|---|---|
| Regular functional checks (often monthly) | Fittings illuminate when tested | Low | Date, areas checked, failures, actions |
| Full duration test (often annual) | System sustains the rated duration | Higher | Start/end time, duration achieved, failures, remedials |
Common system types (why it affects testing)
- Maintained: fittings are on during normal operation and stay on during a power failure.
- Non-maintained: fittings are off normally and come on only in an emergency.
- Self-test: some systems run automated tests and report results.
- Central battery: a central source powers multiple fittings.
The testing approach and what “evidence” looks like can differ depending on which of these you have.
Common failure points to watch
| Failure point | What it looks like | Why it matters |
|---|---|---|
| Fitting failure | No illumination or intermittent light | Loss of coverage on escape routes |
| Battery degradation | Lights come on but fade quickly | System may not last the rated duration |
| Exit signage issues | Missing/unlit signs | Confusing wayfinding in an evacuation |
| Coverage drift | New partitions/layout changes | “Looks compliant” but no longer matches the building |
A practical routine that works in real buildings
1) Keep a schedule
- define your check frequency per site
- set named owners (who tests, who reviews, who closes out)
2) Make defects easy to report
When a fitting fails a test, record it with:
- a unique ID (so it doesn’t get lost)
- exact location
- what failed (no illumination, dim, intermittent)
- priority
3) Close out with evidence
Defect close-out is where programmes fall down. Capture:
- date fixed
- what was done (battery / fitting / control issue)
- retest outcome
What a “monthly” functional check can look like
Your exact method depends on the system, but a practical approach is:
- Trigger the test (using the system’s test facility or method).
- Confirm key fittings operate (especially along escape routes).
- Record any failures immediately with locations.
- Reset/return the system to normal operation.
The goal is not to create disruption; it’s to detect failures early and keep a clear log.
What an annual duration test is trying to prove
An annual test is typically about proving the system can support its rated duration.
Plan this carefully because it can create disruption:
- agree the test window
- coordinate with occupants (especially care settings)
- ensure responsible people know what is happening
If you have self-test systems, make sure the reporting is retained and reviewed — automated tests only help if someone reads the results.
Areas to prioritise during checks
If time is limited, prioritise escape routes and decision points first.
| Area | Why it matters |
|---|---|
| Stairs and protected routes | Primary evacuation paths |
| Corridors and changes of direction | Where wayfinding failures happen |
| Final exits and signage | Helps people get out quickly |
Common pitfalls we see
- tests done, but no record kept
- records kept, but defects never closed out
- a building changes (layouts/uses), but coverage isn’t revisited
- “pass” recorded with no detail of what areas were actually tested
What good records look like
For each test cycle, keep it simple:
- date and test type
- areas covered
- defects logged (with location and unique IDs)
- remedials completed and sign-off
Suggested logbook fields
| Field | Why it helps |
|---|---|
| Date + test type | Proves cadence and intent |
| Person carrying out test | Supports accountability |
| Areas covered | Stops vague “whole building tested” claims |
| Defects found (IDs) | Enables close-out tracking |
| Defects closed since last test | Shows governance over time |
| Notes/constraints | Explains access limits and assumptions |
Self-test and central battery systems (recording tip)
If your system produces automated reports (self-test or central battery monitoring), keep a simple routine: export/save reports, review failures, and log close-out against stable IDs. Automation only helps if the results are retained and acted on.
FAQs
Do we need to test every fitting every month?
It depends on the system and your maintenance approach. The important part is a consistent, defensible routine with evidence and defect close-out.
What if occupants complain about disruption during tests?
Plan tests for low-impact windows and communicate in advance. For sensitive settings (e.g., care homes), coordinate to minimise disruption while still meeting maintenance needs.
Related pages
Note
This article is general information and not legal advice. Align testing routines with competent guidance, system manufacturer requirements, and the building’s risk profile.