Emergency lighting is one of those systems most people don’t think about—until it fails. I’ve walked through plenty of buildings across Melbourne where everything looked fine on the surface, yet the logbook told a different story. Missed tests, unclear records, or faults that were never followed up. When the lights are needed most, that’s when gaps like these come back to bite.
If you manage a commercial facility, school, or healthcare site, your emergency lighting testing logs are more than just paperwork. They are your proof that the system will perform when it counts—and that you’ve met your obligations under Australian standards.
Why Emergency Lighting Logs Matter More Than Most Facilities Realise?
Emergency lighting testing logs form the backbone of compliance under AS 2293. They provide a clear, traceable record that your system has been inspected, tested, and maintained correctly over time.
From experience, this is where many sites either stay ahead of the curve or fall behind.
The Role Of Logs In Compliance And Liability
Emergency lighting maintenance logs serve a simple but critical purpose: they show that your building is safe to occupy.
Each entry in the log supports:
- Compliance with AS 2293 emergency lighting standards
- Workplace health and safety obligations
- Evidence during fire authority inspections
- Documentation for insurance claims
Without accurate logs, even a fully operational system can be treated as non-compliant.
I’ve seen this firsthand in a Footscray commercial office. The system passed every functional check during our visit, but the documentation had large gaps. No consistent monthly emergency light testing records. No clear annual inspection history. The site had to undergo a full compliance review before it could be signed off.
That situation could have been avoided with proper recordkeeping.
What Happens When Records Are Missing Or Incomplete?
If your emergency lighting audit requirements are not met, the consequences can escalate quickly.
Common outcomes include:
- Notices from regulators requiring urgent rectification
- Delays in occupancy approvals
- Insurance disputes after an incident
- Financial penalties for non-compliance
A missing or incomplete logbook sends a clear message to inspectors: the system cannot be verified.
To put it plainly, if it’s not recorded, it didn’t happen.
Why Consistency Matters More Than Perfection?
Many facility managers assume the logs need to be perfect. In reality, consistency is what matters most.
A clear, ongoing record that shows:
- Monthly emergency light testing records completed on time
- Annual emergency lighting inspection checklist followed
- Faults recorded and resolved
This builds a reliable history of the system.
Think of it like servicing a vehicle. You wouldn’t skip years of records and expect everything to check out. Emergency lighting is no different.
System Identification: The Foundation Of Every Emergency Lighting Log
Before you record a single test result, the log must clearly identify what is being tested. This is where many emergency lighting inspection records fall short. If the system is not mapped properly, testing becomes guesswork.
I’ve walked into sites where fittings had no labels, no consistent naming, and no updated layout. You end up chasing your tail trying to confirm which light was tested and which one was missed.
A solid system identification section fixes that from the start.
Building And Responsible Person Details
Every emergency lighting log should begin with clear building information. This is your reference point for all future records.
At a minimum, include:
- Building name and full address
- Type of facility (commercial, school, healthcare, industrial)
- Name of the responsible person
- Contact details for the site and service provider
Under Australian regulations, the “responsible person” carries accountability for ensuring compliance. That is usually the facility manager or building owner.
In larger sites across Melbourne’s western suburbs, we often see multiple stakeholders involved. Without clear documentation here, responsibility can fall through the cracks.
Fixture Inventory And Location Mapping
This is where the real groundwork happens. Every emergency light and exit sign must be accounted for.
Your log should include:
- Unique ID or tag number for each fitting
- Exact location (not just “Level 1”, but “Level 1 corridor outside meeting room 3”)
- Type of fitting (exit sign, emergency light, combo unit)
Here’s a simple example of how a fixture register might look:
| Fixture ID | Location | Type | Installation Date |
| EL-001 | Ground Floor Reception Exit | Exit Sign | 2019 |
| EL-014 | Level 2 Stairwell Landing | Emergency Light | 2021 |
| EL-027 | Warehouse Aisle 3 | Combo Unit | 2020 |
In one warehouse we serviced in Derrimut, half the fittings were labelled inconsistently. Some had handwritten tags, others had none. Once we standardised the inventory, testing time dropped significantly, and errors were reduced.
It’s a classic case of “measure twice, cut once.” Get the inventory right, and everything else becomes easier.
Technical Specifications And Battery Details
Accurate technical data helps you track performance over time and plan maintenance properly.
Each fixture record should include:
- Manufacturer and model
- Type of system (self-contained or central battery)
- Battery type and capacity
- Circuit or switchboard connection
This information becomes valuable during annual emergency lighting inspection checklists and battery discharge test records.
For example, if you notice multiple units with the same battery type failing early, that points to a broader issue. It could be environmental factors, load issues, or simply ageing components.
In Melbourne, temperature swings between seasons can impact battery performance more than many expect. Sites with poor ventilation or heat exposure often see reduced battery life. Without proper records, these patterns are easy to miss.
Keeping The Inventory Current As The Site Changes
Buildings are rarely static. Layouts change. New fittings are added. Old ones are removed.
Your emergency lighting maintenance logs must reflect these changes.
Key updates to record:
- New fittings installed (with full details)
- Removed or decommissioned units
- Relocated lights due to layout changes
- Switchboard or circuit modifications
I’ve seen sites fail audits simply because the logbook listed fittings that no longer existed. It creates confusion and raises questions about the accuracy of all records.
A simple checklist helps keep things on track:
- Review fixture inventory after any building works
- Update logs immediately after changes
- Cross-check during the next scheduled test
If the system changes, the documentation must change with it. That’s how you keep your records clean and audit-ready.
Monthly Emergency Light Testing Records: What Must Be Logged?
Monthly testing is where consistency shows. It is a simple check on paper, but in practice, it is often rushed or skipped. That is where gaps start to appear in emergency lighting maintenance logs.
Under AS 2293, a monthly test confirms that each light activates when mains power is interrupted. It is quick, but it must be recorded properly.
I’ve seen sites treat this as a tick-and-flick exercise. A quick walk-through, a few switches tested, and a box ticked. But when you dig into the records, there is no detail. That approach does not hold up during an audit.
What Does A Monthly Test Involve?
A proper monthly test follows a clear process:
- Simulate a power failure
- Confirm that each emergency light and exit sign activates
- Check indicator lights are functioning
- Observe any visible damage or irregular behaviour
The test usually runs for a short period, often around 30 seconds. The goal is not to test duration, but to confirm basic operation.
On a recent site in Sunshine, a routine monthly check picked up a unit that failed to activate near an emergency exit. No one had noticed it before. That small test prevented a bigger issue later.
What Must Be Recorded In Monthly Logs?
Each entry in your monthly emergency light testing records should include:
- Date of the test
- The time the test started and finished
- Name or initials of the tester
- Test type (monthly functional test)
- Result for each fitting (pass or fail)
- Notes on any issues observed
Here is a practical example:
| Fixture ID | Location | Result | Notes |
| EL-009 | Level 1 Corridor Near Lift | Pass | Operating normally |
| EL-015 | Exit Door Warehouse | Fail | Did not activate |
| EL-021 | Office Kitchen Exit | Pass | Minor dust on the lens |
This level of detail ensures clarity. Anyone reviewing the log can understand what happened without guessing.
Common Issues Found During Monthly Testing
Monthly checks often reveal early warning signs. These are easy to fix if caught early.
Typical issues include:
- Lights failing to switch on
- Flickering during activation
- Indicator lights not showing charge status
- Physical damage to fittings
In older buildings, wiring faults or ageing components are common. Catching these during monthly testing avoids larger failures during annual duration tests.
Simple Checklist For Monthly Emergency Lighting Logs
To keep your records consistent, follow this checklist:
- Confirm all fittings are tested, not just a sample
- Record results for each individual unit
- Note even minor issues, not just failures
- Ensure the tester signs or initials each entry
- Follow up on any failed units without delay
A well-kept monthly log tells a clear story over time. It shows that the system is being monitored, not ignored.
Why Small Details Make A Big Difference?
It is often the small details that separate compliant sites from non-compliant ones.
For example:
- Writing “checked” instead of recording actual results
- Skipping fixture IDs
- Leaving notes blank
These might seem minor, but during an inspection, they raise doubts.
One facility I worked with had logs that simply said “all OK” for months. When we tested the system properly, several units failed. The logs gave a false sense of security.
A good log does not just confirm things are working. It proves it.
Annual Emergency Lighting Inspection Checklist And Duration Tests
If monthly testing is a quick health check, the annual test is where the system is truly put through its paces. This is the test that shows whether your emergency lighting will last long enough during a real evacuation.
Under AS 2293, this is not optional. It is a required part of your emergency lighting audit requirements.
I’ve seen plenty of systems pass monthly checks without issue, then fall short during the annual duration test. That is where hidden problems come to light.
Duration Test Requirements Under AS 2293
The annual test checks whether each fitting can operate for its required duration after a full power loss.
In most commercial buildings, this means:
- 90 minutes minimum operation
- Some systems are designed for 2–3 hours, depending on the classification
During this test, the battery is fully discharged. The light must stay on for the full duration without dropping below acceptable brightness.
In one healthcare site in Melbourne’s inner west, several fittings ran out at around 60 minutes. On paper, everything looked fine throughout the year. The annual test told a different story.
What Must Be Recorded During A Duration Test
Your emergency light duration test records must be detailed and precise. This is not a simple pass or fail entry.
Each record should include:
- Date of the test
- Start and finish time
- Required duration for the system
- Actual duration achieved
- Light performance throughout the test
- Pass or fail result
Example entry:
| Fixture ID | Location | Required Duration | Actual Duration | Result | Notes |
| EL-012 | Level 3 Exit Corridor | 90 mins | 92 mins | Pass | Stable output |
| EL-018 | Basement Carpark Exit | 90 mins | 58 mins | Fail | The battery dropped early |
This level of detail supports compliance and helps identify weak points in the system.
Observations That Must Not Be Missed
Beyond timing, the condition of each fitting must be observed carefully.
Key points to record:
- Brightness level during operation
- Flickering or dimming
- Delayed activation
- Any unusual noise or overheating
A light that stays on but dims significantly may still fail compliance. That detail needs to be captured in your safety lighting maintenance documentation.
Common Failures During Annual Testing
From experience, the same issues tend to show up year after year:
- Batteries failing before the required duration
- Lights dimming well before the end of the test
- Units not activating after extended discharge
- Charging systems not restoring battery capacity properly
In older commercial buildings, battery wear is the main culprit. Once batteries start to decline, failures can happen quickly across multiple fittings.
Practical Timeline For Annual Testing
To keep things organised, it helps to follow a structured approach:
Week Before Testing:
- Review previous logs
- Identify fittings with past issues
- Notify building occupants if required
Day Of Testing:
- Conduct a full discharge test
- Monitor all fittings throughout the duration
- Record detailed results
After Testing:
- Log all failures immediately
- Schedule repairs or replacements
- Retest affected units
This approach keeps your emergency lighting performance tracking consistent and reliable.
Why Annual Records Carry More Weight During Audits?
During an audit, inspectors often focus heavily on annual emergency lighting inspection records.
They want to see:
- Proof that duration requirements are met
- Evidence of consistent yearly testing
- Clear records of failures and repairs
If these records are missing or unclear, the entire system can be questioned.
I’ve been on sites where everything hinged on those annual logs. When they were detailed and up to date, the audit moved smoothly. When they were not, the process slowed down fast.
It’s a case of doing the hard work once a year, so you don’t face bigger problems later.
Recording Faults And Corrective Actions Properly
A failed test is not the problem. Failing to record and fix it is.
Emergency lighting fault reporting logs must show the full story—from the issue through to the repair and retest. Anything less is incomplete.
What Must Be Recorded For Each Fault?
Every defect entry should be clear and specific:
- Fixture ID and location
- Description of the fault
- Date the issue was found
- Immediate action taken (if any)
Example:
- EL-018, Basement Exit
- The battery failed at 58 minutes
- Identified during the annual test
Vague notes like “not working” do not meet compliance expectations.
How To Record Repairs And Retesting?
Once a fault is identified, the log must show what was done to fix it.
Include:
- Repair details (e.g., battery replaced)
- Date of repair
- The person who completed the work
- Retest result and date
Simple checklist:
- Record the issue
- Fix the issue
- Retest the unit
- Update the log
I’ve seen sites log faults but never record the fix. During audits, that raises immediate concerns.
Why This Section Is Critical For Compliance?
Inspectors look closely at this part of your emergency lighting maintenance logs.
They want to see:
- No unresolved faults
- Clear timelines for failure to repair
- Evidence that the system was restored to full operation
If a light fails and there is no follow-up recorded, it suggests the system may still be compromised.
A clean fault log shows control. It proves the system is actively managed, not left to chance.
Emergency lighting testing logs are more than a formality—they are the proof that your system will perform when it matters most.
Across commercial sites, schools, and healthcare facilities, the difference always comes down to consistency.
Sites that maintain clear, accurate records tend to pass audits without issue, while those with gaps often face delays, extra costs, and compliance risks.
Keeping your logs up to date, recording every test properly, and documenting faults and repairs ensures your system remains reliable and compliant with AS 2293.
When everything is documented clearly, there is no guesswork—only a complete, traceable record that shows your building is safe and prepared.
