What Should an Emergency Lighting Logbook Record?
Quick Answer: An emergency lighting logbook should record asset IDs, locations, test dates, results, defects, corrective actions, and responsible persons. In Australia, facilities should maintain exit light test records that support AS/NZS 2293.2 compliance and provide a clear audit trail for inspections, maintenance, fire safety audits, and incident investigations.
For commercial buildings, retail sites, and industrial premises, an emergency lighting logbook is more than a compliance folder. It is the evidence base that shows which units were tested, what failed, who fixed it, and whether the system remained fit for purpose. A well built logbook should capture exit light test records alongside battery checks, visual inspections, and corrective work, giving facilities teams a single record that supports audits, contractor handovers, and incident investigations. For B2B fire protection purchasing, see FireFactory.
Why an Emergency Lighting Logbook Supports Compliance and Safety
Emergency lighting protects egress routes during power failure, and the logbook is the record that the system was maintained. For fire protection contractors, electrical companies, and facility managers, the logbook should reflect the applicable Australian testing and documentation expectations. AS/NZS 2293.2 should be used as the reference point for the required test intervals, record fields, and maintenance expectations. Before finalizing a template, confirm the applicable clauses and edition through the AS/NZS 2293.2:2019 standards catalogue entry.
A complete logbook helps the facility answer three questions quickly. First, was the unit tested on schedule? Second, if a fault was found, what action was taken? Third, can the facility show who was responsible for the result? These details are essential when a fire authority, insurer, auditor, or incident investigator reviews the system.
Emergency Lighting Logbook Record Checklist
The following checklist provides a practical minimum data set. It supports traceability from the physical unit to the maintenance action.
| Record field | What to record | Purpose |
|---|---|---|
| Asset ID | Unique tag, serial number, and model | Identifies the unit and supports replacement |
| Location | Building, floor, room, and egress route | Locates the unit for response and verification |
| Unit description | Exit light, emergency lamp, sign, or control unit | Clarifies the scope of the test |
| Test date and time | Calendar date, time, and shift where relevant | Proves the test was completed |
| Test type | Visual check, battery discharge, automatic test, or manual test | Shows the method used |
| Result | Pass, fail, not tested, or defect found | Records the system status |
| Defect | Failure mode and observed condition | Supports corrective work |
| Corrective action | Work order, parts replaced, and completion date | Tracks repair status |
| Responsible person | Name, company, role, and signature or approval | Establishes accountability |
| Notes | Obstructions, temporary measures, or follow up actions | Preserves context for future review |
Exit Light Test Records: What the Testing Section Should Show
Exit light test records need enough detail to distinguish a routine pass from a unit that requires follow up. The testing entry should identify the exact unit, the location, and the condition observed during the test.
- Test identification: asset ID, location, and the test cycle or maintenance plan.
- Test date and time: calendar date and, where relevant, the time of the test.
- Test method: visual check, battery discharge, automatic test, or manual switch test.
- Observed condition: illuminated, dim, flickering, failed, blocked, or not tested.
- Environmental factors: mains power status, visible obstructions, heat, dust, or recent construction work.
- Tester information: name, company, role, and approval method.
The record should also state whether the test was completed as planned or triggered by a fault, a fire alarm event, or an inspection finding. This detail helps the facility separate routine maintenance from urgent safety risks.
Defects, Corrective Work, and Maintenance Accountability
A complete emergency lighting logbook records the problem, the response, and the verification. If an exit light fails to illuminate, the entry should capture the observed defect, the immediate action, and the corrective work required to restore the unit.
- Defect description: dead battery, failed lamp, dim output, damaged lens, control fault, or blocked exit sign.
- Immediate action: unit isolated, temporary lighting arranged, or escalation recorded.
- Corrective work: parts replaced, repair performed, work order number, and completion date.
- Verification: retest result and the person who confirmed the unit returned to service.
- Out of service status: reason, start date, expected restoration date, and mitigation.
When replacing components, record the original and replacement model, serial number, and electrical rating where available. This helps prevent incorrect substitutions and gives the next maintenance team a clear history. FireFactory supports B2B fire protection purchases, and exact model confirmation remains essential before ordering replacement parts.
Practical Selection and Purchasing Considerations
Facilities can use paper logbooks, spreadsheets, or maintenance software. The format matters less than data quality. The system should be easy to update, searchable, durable, and available during inspections or incident reviews. A digital record can support photos, work orders, and asset maps, but it must still capture the same core fields.
For multiple site retail operations or commercial buildings with large emergency lighting systems, standardize asset IDs and locations. This allows exit light test records to be compared across sites and reviewed by auditors without ambiguity. When a maintenance report identifies a failed component, the purchasing team should confirm the exact model, battery specification, and lamp rating before placing an order. FireFactory supplies B2B fire protection products, and its range can be used to check current availability for confirmed emergency lighting components.
Frequently Asked Questions
What is an emergency lighting logbook?
It is a structured record for testing, inspection, defects, and maintenance of emergency lighting units. It should link asset IDs, locations, test results, corrective actions, and responsible persons.
How detailed should exit light test records be?
They should record the test date, method, result, tester, and any observed defects. If a unit fails, the record should also show the corrective action, completion date, and verification.
Who should maintain the emergency lighting logbook?
The facility responsible person should appoint a manager or contractor to keep the record current. Fire protection and electrical contractors can complete test entries, while the facility retains oversight.
Can a digital app replace a paper logbook?
Yes, if the digital system captures the required fields, is backed up, and remains accessible for audits. The data should be searchable by asset, location, date, and defect status.
What records support AS/NZS 2293.2 compliance?
Records that show periodic testing, maintenance, defects, corrective work, and asset identity support compliance review. Confirm the current edition and applicable clauses before relying on a template.
How long should emergency lighting records be retained?
Retention periods depend on site policy, local requirements, insurance conditions, and the applicable standard. The facility should set a clear retention schedule and review it periodically.
FireFactory supports fire protection and electrical maintenance teams with B2B emergency lighting components and related products. For logbook driven repairs, confirm the exact model, battery type, and replacement specification before ordering, and contact FireFactory for current availability and technical details.