Emergency Lighting Monthly Test Log
Monthly log for testing emergency lighting units after a simulated power loss, so you can verify illumination, battery readiness, and track corrective actions in one place.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Commercial Real Estate · Warehousing And Distribution · Manufacturing · Healthcare Facilities · Education
Overview
This Emergency Lighting Monthly Test Log is a field-ready inspection template for documenting the monthly functional check of emergency lighting units after a simulated loss of normal power. It captures the basics that matter for egress safety: where the unit is located, what type it is, whether it activates on demand, how long it runs during the test, whether the light output is adequate for the exit path, and whether the battery or charger shows signs of trouble.
Use it when you need a repeatable record for stairwells, corridors, exit routes, warehouses, tenant spaces, or any area where emergency illumination supports safe evacuation. The template also gives you a place to record deficiencies and corrective actions, which helps prevent a failed unit from being forgotten after the inspection.
Do not use this log as a substitute for annual duration testing, electrical troubleshooting, or a full life-safety audit. It is a monthly operational check, so it is best suited to confirming readiness and catching obvious failures early. If a unit flickers, dims, fails to activate, or has a damaged battery pack or loose wiring, document it here and route it for repair and retest. The template works best when paired with a clear SOP, a defined inspection route, and a maintenance process that closes the loop on every deficiency.
Standards & compliance context
- This log supports emergency egress readiness expectations under OSHA general industry safety requirements and common workplace life-safety programs.
- It aligns with NFPA-based emergency lighting inspection and maintenance practices that expect routine functional testing and documented corrective action.
- For buildings subject to local fire code enforcement, the template helps satisfy AHJ expectations for traceable inspection records and repair follow-up.
- If your site operates under a formal safety management system, the log also fits ISO 9001-style record control and non-conformance tracking.
- Use your adopted code, manufacturer instructions, and site SOP to define the exact activation and duration criteria for each unit.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Inspection Details
This section establishes who inspected what, when, and under which standard or SOP so the record is traceable.
- Inspection date and time
- Inspector name and title
- Building, area, or floor inspected
- Inspection type
-
Reference standard or SOP
Record the applicable site procedure or standard used for the inspection, such as OSHA 29 CFR 1910.37 and NFPA 101 emergency lighting requirements.
Emergency Lighting Inventory
This section identifies each unit and its location so the same fixture can be found, repaired, and retested later.
-
Unit identifier or location
Record the specific emergency light, exit sign/light combo, or zone being tested.
- Unit type
-
Normal power source identified
Confirm the unit is connected to the intended branch circuit or normal power source.
-
Physical condition of unit
Assess housing, lens, signage, mounting, and visible damage.
-
Photo of unit identification plate or location
Capture evidence of the unit or its location if required by site procedure.
Monthly Functional Test
This section captures the core pass-fail evidence for emergency activation, illumination, and runtime behavior after power loss.
-
Simulated loss of normal power performed
Verify the unit was tested by interrupting normal power or using the approved test method.
-
Emergency illumination activated within required time
Confirm the unit illuminated when normal power was removed.
-
Test duration
Monthly functional tests should be documented for at least 30 seconds.
-
Light output adequate for egress path
Verify the emergency light provided visible illumination for the intended egress route or area.
-
Any flicker, dimming, or intermittent operation observed
Record any unstable operation during the test.
Battery and Power Readiness
This section checks the support systems that determine whether the unit will actually work when normal power is lost.
-
Battery indicator or charger status normal
Confirm the unit indicates normal charging or ready status before and after the test.
-
Battery pack condition
Document visible battery condition or any signs of failure.
-
Wiring, connectors, and plug-in power supply secure
Check for loose connections, damaged cords, or exposed conductors.
Deficiencies and Corrective Actions
This section turns inspection findings into follow-up work so failures are assigned, repaired, and closed out.
- Deficiencies identified
-
Corrective action required
Document whether repair, replacement, or escalation is required for any deficiency.
-
Corrective action details
Describe the repair, replacement, retest, or work order reference.
How to use this template
- 1. Enter the inspection date, inspector name and title, area covered, inspection type, and the reference standard or site SOP before starting the walk-through.
- 2. Record each emergency lighting unit by identifier or exact location, and note the unit type, normal power source, physical condition, and a photo of the identification plate or location.
- 3. Simulate loss of normal power for each unit, confirm that emergency illumination activates within the required time, and observe the test duration and light output along the egress path.
- 4. Note any flicker, dimming, intermittent operation, weak battery indication, damaged battery pack, or loose wiring and power connections as individual deficiencies.
- 5. Assign corrective actions for every failed or marginal unit, then retest and close out the log only after repairs are completed and the unit passes.
Best practices
- Test units in the same order every month so missed fixtures are easier to spot.
- Use exact locations such as stairwell north landing or aisle 4 exit door instead of vague room names.
- Photograph the unit identification plate or location at the time of inspection so technicians can find the same fixture later.
- Treat flicker, dimming, or intermittent operation as a deficiency even if the unit briefly turns on.
- Verify that the light actually covers the egress path, not just the wall or ceiling near the fixture.
- Record battery or charger status before leaving the area so weak units are not mistaken for passing units.
- Separate cosmetic damage from safety-related defects, and flag any condition that could affect activation or illumination.
- Close the loop on every deficiency with a repair date and retest, not just a note that work was requested.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this Emergency Lighting Monthly Test Log cover?
It covers the monthly functional check of emergency lighting units after a simulated loss of normal power, plus the basic condition and battery-readiness checks that support the test. The log is built to document whether each unit activates, how long it stays on, and whether the light output is adequate for the egress path. It also captures deficiencies and corrective actions so failures do not get lost after the walk-through.
How often should this log be used?
Use it monthly for the emergency lighting units in the area you are inspecting, unless your site procedure or local code requires a different cadence. Many facilities pair the monthly log with a separate annual or extended-duration test record. If your building has mixed occupancy or critical egress areas, keep the monthly cadence consistent by floor, zone, or asset group.
Who should complete the inspection?
A trained facilities, safety, or maintenance employee should complete it, and the person should be familiar with the building's emergency power arrangement and egress routes. The inspector does not need to be a licensed electrician for a visual monthly log, but they should know how to safely simulate a loss of normal power without creating a hazard. If your SOP requires it, have a competent person review the findings and close out corrective actions.
Does this template align with OSHA or fire code requirements?
Yes, it is designed to support documentation expected under OSHA general industry safety practices and fire-life-safety expectations for emergency egress lighting. It also fits well with NFPA-based inspection programs and local AHJ requirements that expect emergency lighting to be tested, maintained, and kept operational. Always confirm the exact frequency and acceptance criteria against your adopted code, SOP, and local authority requirements.
What are the most common mistakes when using this log?
A common mistake is recording only that the unit 'passed' without noting whether the light actually illuminated the egress path or how quickly it activated. Another is skipping the battery or charger status check, which can hide a unit that works during the test but will not hold charge when needed. Teams also miss location-specific identification, making it hard to find the same fixture later for repairs or retesting.
Can I customize this for different building types or zones?
Yes, you can tailor the inventory section by floor, tenant space, warehouse aisle, stairwell, or exit corridor, depending on how your site is organized. You can also add fields for unit manufacturer, model, battery type, or last annual duration test if those details help your maintenance workflow. Keep the core test items intact so the log still proves activation, illumination, and corrective action follow-up.
How does this compare with an ad-hoc checklist or spreadsheet?
An ad-hoc checklist often misses repeatable details like activation time, light output, and battery readiness, which makes trend review and repair follow-up harder. This template gives you a consistent record for each unit, so deficiencies can be assigned, tracked, and retested in the same format every month. It is also easier to audit because the same fields appear every time.
Can this log connect to maintenance or CMMS workflows?
Yes, the corrective action fields can be used to create work orders in a CMMS or maintenance ticketing system. Many teams also attach the photo of the unit identification plate or location to help technicians find the fixture quickly. If you use digital workflows, map the unit identifier and deficiency fields to your work-order system so follow-up stays traceable.
Related templates
Go deeper on the topic
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
-
A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
Discover 5 practical ways screenshot and screencast tools improve workplace communication—from SOP documentation to issue reporting—with guidance on...
-
See how MangoApps Forms helps teams collect, track, and analyze employee data in real time — with mobile access, file uploads, and enterprise-grade security.
Ready to use this template?
Get started with MangoApps and use Emergency Lighting Monthly Test Log with your team — pricing built for small business.