In brief: Build an emergency lighting test log that links every asset, function or duration test, fault, corrective action and verified closure.
An emergency lighting test logbook should connect each test to an identifiable asset, the observed result, any defect and verified corrective action. Buyers should define that record structure before approving luminaires, test controls or monitoring software. A date and a tick are not enough when the maintenance team cannot tell which fitting was tested or whether a fault was closed.
UK government fire-safety guidance for offices and shops recommends keeping maintenance and testing records and gives monthly function testing and annual full-discharge testing as UK examples. The applicable schedule must still come from the destination rules, risk assessment, manufacturer instructions and responsible project team; it is not a worldwide default.
What belongs in an emergency lighting test logbook?
| Record field | What to capture | Why it matters | |
|---|---|---|---|
| --- | --- | --- | |
| Asset identity | Unique ID, exact location, model and system or circuit | Prevents one test result being attributed to the wrong fitting | |
| Test event | Date, time, test type, initiation method and responsible person or system | Distinguishes a brief function check from a duration test | |
| Expected result | Required emergency operation, indication and test period | Makes pass or fail traceable to an agreed criterion | |
| Observed result | Light operation, indicator state, elapsed time and relevant notes | Preserves the evidence behind the decision | |
| Fault record | Fault class, affected asset, discovery time and immediate control | Separates a defect from a completed test | |
| Corrective action | Owner, action, replacement part or service reference and target date | Gives the fault a controlled route to closure | |
| Closure evidence | Retest result, closure date and approver | Shows that the defect was resolved rather than merely acknowledged | |
| Document link | Manual revision, report, photograph or work-order reference | Keeps supporting evidence connected without overloading the log |
The table is a procurement starting point. Retention periods, signatures, competent-person requirements and prescribed forms depend on the jurisdiction and organization.
Build the asset register before the first test
Every emergency luminaire, exit sign, conversion kit or monitored device needs a stable identity that matches the installed location. A practical register includes the floor, room or route reference, mounting position, exact model and revision, operating mode, rated duration, battery or replacement reference where applicable, test architecture, indicator legend and current instruction manual.
Use a floor plan or asset schedule to prevent ambiguous descriptions such as “corridor light 3.” If a device is replaced, preserve the location history while recording the new model, serial or batch identifier, commissioning date and reset or remapping work. Do not silently overwrite the old record.
The emergency light specification-sheet guide explains which product fields should stay tied to an exact model. For system selection, the self-test vs manual testing guide separates manual, stand-alone self-test and centrally monitored architectures.
Record the test, not just a pass mark
A useful test entry states what was commanded, what should have happened and what was observed. A short function test and a rated-duration test have different purposes, so the log should not collapse both into “emergency light checked.”
For a manual test, record the approved test control or circuit arrangement, the fittings or group covered, emergency changeover, light-source operation, visible indications and restoration to the normal condition. For a duration test, also record the ordered duration, start and finish times, acceptance criterion, result and post-test recharge arrangements.
The UK guide notes that full-discharge testing should occur at an appropriate low-risk time because batteries need to recharge afterward; alternative arrangements may be needed before the system is fully functional again. Treat that as a UK operational example and follow the exact product instructions and local project decision.
Keep faults separate from test history
A failed test creates work; it does not complete the maintenance process. Create a fault record that identifies the affected asset, observed condition, immediate risk control, responsible owner and target action. Close it only after repair or replacement and an appropriate retest.
Useful fault categories can include failure to enter emergency mode, inadequate duration against the specified criterion, abnormal indication, damaged enclosure, obscured exit legend, inaccessible test control, communication loss or asset-map mismatch. The categories should reflect the actual system and manual; do not invent diagnostic precision that the product does not provide.
The product inspection-plan guide covers sampling and acceptance before shipment. An installed-site logbook has a different job: maintaining traceability through commissioning, routine tests, faults, repairs and replacements.
Manual, self-test and central records need different controls
| Test architecture | Record source | Control buyers should specify | |
|---|---|---|---|
| --- | --- | --- | |
| Manual test | Human observation and manual entry | Asset list, approved procedure, complete route coverage, signer and review | |
| Stand-alone self-test | Local device schedule and indicator, often transcribed manually | Indicator legend, test timing, last-result behavior, inspection route and fault handoff | |
| Centrally monitored test | Controller or software linked to addressed devices | Device mapping, clock, event history, export format, retention, access, backup and remapping |
Automatic testing does not automatically create a usable maintenance record. Stand-alone self-test may show only a local code. Central monitoring can collect events, but the record still fails if device addresses do not match the floor plan, timestamps are unreliable, exports are unavailable or nobody owns the fault queue.
IEC 62034:2012 covers automatic test systems for battery-powered emergency escape lighting, while IEC 60598-2-22:2021 covers emergency luminaires. Naming either standard does not prove that a particular product exports records, retains a complete audit trail or meets a project-specific logbook requirement.
Emergency lighting logbook fields for an RFQ
Add these fields to the project specification:
1. Asset-ID convention and floor-plan reference. 2. Exact products, groups and test controls covered by each record. 3. Required function, duration and other project-approved test types. 4. Acceptance criteria and permitted result values. 5. Indicator codes and the manual revision that defines them. 6. Person, role or system permitted to create and approve entries. 7. Timestamp source, time zone and clock-synchronization rule for connected systems. 8. Fault priority, escalation owner, target action and closure approval. 9. Record retention, backup, access rights and export format. 10. Commissioning import, asset mapping, training and handover demonstration. 11. Device-replacement, address-change and history-preservation procedure. 12. Destination rules, project schedule and competent-person requirements.
Place the schedule inside the broader emergency lighting RFQ template. Keep record requirements separate from photometric performance, battery duration, IP rating and destination approval.
Commissioning handover should prove the record workflow
Before handover, select representative assets and demonstrate the complete path: identify the fitting on the plan, initiate an approved test, observe or retrieve the result, create a fault where a safe manufacturer-approved simulation exists, assign the action, restore the product and verify closure through retest. Do not create faults through unsafe wiring, battery abuse or unauthorized work.
For a connected system, also demonstrate address mapping, user roles, clock settings, report export, backup, communication-loss behavior and device replacement. Store the configuration backup, software version, licenses where applicable, manuals and training record with the handover package.
Product and OEM boundary
Hangzhou Dreamy Technology manufactures emergency wall lights, twin-head lights, downlights, exit signs and conversion kits. Category names and catalog photographs do not establish a test-record function. Buyers should request exact confirmation of test controls, indicator meanings, self-test behavior, communication interfaces and replaceable parts for the offered model.
Zhuiming can evaluate agreed OEM and ODM requirements for labels, manuals, batteries, drivers, indicators, test functions and packaging, subject to exact-model review and approved samples. Submit the destination, quantity, test architecture and record requirements through the OEM and ODM page or request a quotation. The project authority and responsible organization remain responsible for the installed maintenance regime and local compliance.
Sources
- UK government — Fire safety risk assessment: offices and shops
- UK government — A guide to making small non-domestic premises safe from fire
- IEC 62034:2012 — Automatic test systems for battery powered emergency escape lighting
- IEC 60598-2-22:2021 — Luminaires for emergency lighting
Sources reviewed 21 August 2026. This article provides procurement and record-design guidance. It does not replace the adopted rules, fire-risk assessment, manufacturer instructions, competent-person duties or approval for a specific installation.
Frequently asked questions
What should be recorded in an emergency lighting test logbook?
Record the asset or group ID, location, date and time, test type, method, expected and observed result, pass or fail, responsible person or system, faults, corrective action and verified closure. Link supporting reports or work orders where needed.
Is a monthly emergency lighting test required everywhere?
No universal schedule applies to every country and project. UK government guidance uses monthly function and annual full-discharge testing as regional examples. Confirm the destination rules, risk assessment, manufacturer instructions and responsible project decision.
Does self-test remove the need for a logbook?
No. Self-test can automate defined tests, but the organization still needs asset identity, result review, fault ownership, corrective action and retention. Stand-alone products may require manual transcription of local indicators.
Can emergency lighting test records be electronic?
They can be electronic when the applicable rules and organization permit it and the system preserves identity, timestamps, access, retention, backup, export and corrective-action history. A software dashboard alone does not prove those controls.
What happens when an emergency luminaire is replaced?
Keep the location and historical record, then add the replacement model or identifier, commissioning result, date and any new address or indicator information. Verify the new device is correctly mapped before closing the replacement action.
Final record rule
An emergency lighting logbook is complete only when a reviewer can trace one installed asset from test instruction to observed result, defect, corrective action and verified closure. Specify that chain before procurement; do not try to reconstruct it after a fault.
Frequently asked questions
What should be recorded in an emergency lighting test logbook?
Record the asset or group ID, location, date and time, test type, method, expected and observed result, pass or fail, responsible person or system, faults, corrective action and verified closure. Link supporting reports or work orders where needed.
Is a monthly emergency lighting test required everywhere?
No universal schedule applies to every country and project. UK government guidance uses monthly function and annual full-discharge testing as regional examples. Confirm the destination rules, risk assessment, manufacturer instructions and responsible project decision.
Does self-test remove the need for a logbook?
No. Self-test can automate defined tests, but the organization still needs asset identity, result review, fault ownership, corrective action and retention. Stand-alone products may require manual transcription of local indicators.
Can emergency lighting test records be electronic?
They can be electronic when the applicable rules and organization permit it and the system preserves identity, timestamps, access, retention, backup, export and corrective-action history. A software dashboard alone does not prove those controls.
What happens when an emergency luminaire is replaced?
Keep the location and historical record, then add the replacement model or identifier, commissioning result, date and any new address or indicator information. Verify the new device is correctly mapped before closing the replacement action.