Emergency Light Checklist Template in Excel: What to Include

How-to basics · Updated November 22, 2026

Yes. An emergency light checklist template in Excel can track each fixture’s location, inspection dates, test results, defects, corrective actions, and next due date. Set the inspection intervals from the rules that apply to your building and the equipment manufacturer’s instructions; a spreadsheet organizes records but does not replace a required test or a competent inspection.

What an emergency light checklist covers

Emergency lighting is intended to provide illumination when normal lighting fails, helping people find escape routes or reach areas where work can be made safe. The exact equipment and inspection duties vary by building, system, jurisdiction, and adopted code. A useful checklist covers both the asset being checked and what happened during the test, rather than recording only a tick or a date.

Depending on the site, the log may include self-contained battery luminaires, exit signs, central-battery circuits, and other designated emergency fixtures. Keep the scope clear: an emergency light record is not automatically a complete fire-safety, electrical-maintenance, or exit-route inspection. Coordinate related checks where appropriate, but record distinct duties separately.

For each check, make it possible to answer four practical questions: Which unit was inspected? What test was performed? Did it meet the expected outcome? If it did not, who is addressing the problem and when will it be checked again?

Choose inspection intervals from applicable requirements

There is no single interval that can safely be assumed for every building. Requirements may come from local regulations, the edition of a standard adopted by the authority having jurisdiction, a fire-risk or safety plan, and the manufacturer’s instructions. The responsible building manager should confirm which requirements apply, including any rules for the type of system installed.

In the United States, NFPA 101 is one standard that may be adopted and used for life-safety requirements. Provisions in commonly referenced editions include periodic functional testing and a longer-duration test, but the applicable edition, local adoption, equipment provisions, and permitted test arrangements matter. Do not treat a generic spreadsheet interval as proof of compliance. In other countries, standards and required test durations can differ.

Separate short functional checks from duration tests in the workbook. A short check may establish that the unit operates when normal power is interrupted; a duration test assesses whether it continues operating for the required period. A visual inspection is different again: it can identify a damaged fitting, blocked light, or indicator warning, but it does not demonstrate battery endurance.

  • Enter the required interval and test type for each asset or asset group.
  • Record the source of the interval, such as the applicable site procedure or confirmed regulatory requirement.
  • Use the manufacturer’s instructions for test switches, indicators, and system-specific procedures.
  • Have the responsible person confirm whether a test needs advance coordination or temporary precautions.

Recommended columns for the Excel template

A practical workbook can use one row per fixture for asset details and one row per inspection in a separate history sheet. This avoids overwriting the previous result every time someone tests a unit. For a small site, a single sheet may be adequate if it includes a new dated row for each inspection rather than reusing the same row.

  • Asset ID: a unique label that matches the physical unit or site asset register.
  • Building, floor, and location: for example, Building A, level 2, east stair landing.
  • Equipment details: fitting type, manufacturer or model if known, and system type, such as self-contained or central supply.
  • Test details: test date, test type, test duration where relevant, and the person completing or recording the check.
  • Outcome: Pass, Fail, or Not tested, with a notes field for the observed condition.
  • Fault and action tracking: fault description, priority or risk category used by the organization, action owner, target date, and repair status.
  • Follow-up: retest date and outcome, plus the date a defect was closed.
  • Next due date: calculated from the recorded test date and the interval set for that test.

Use a consistent ID, such as EL-001, rather than relying on a description like “light by the stairs.” Locations can change or be interpreted differently; a fixed ID makes the log easier to compare with labels, drawings, and maintenance records. Do not include sensitive access codes or unnecessary personal information in a broadly shared workbook.

Build the workbook so records stay usable

In Excel for Microsoft 365 on Windows, put the column headings in row 1, select the range, and choose Home > Format as Table. You can also use Ctrl+T on Windows and confirm that the table has headers. In Excel for Microsoft 365 on Mac, use Command+T to create a table; the ribbon wording and layout can vary slightly by update. Tables make it easier to filter inspections, extend formulas to new rows, and keep headings visible when working with a long list.

Consider using two sheets: Asset Register for stable details such as ID and location, and Inspection Log for dated test events and faults. A third sheet can hold the site’s confirmed test intervals, result choices, and procedure references. If the workbook is kept on a shared drive, agree who can edit it, how changes are reviewed, and where the authoritative copy lives. A spreadsheet is only useful as a record if people can find the current version.

Use Data Validation to reduce inconsistent entries. Select the result cells and choose Data > Data Validation; set Allow to List and enter choices such as Pass, Fail, and Not tested. Create a separate list for fault status, such as Open, In progress, and Closed. Keep free-text notes available because a short fixed choice cannot describe every defect.

Add due-date formulas carefully

For a simple schedule, keep the last test date and the interval in separate columns. Suppose the inspection log has the last test date in C2 and the interval in days in D2. With C2 entered as 1 April 2026 and D2 set to 30, enter =IF(OR(C2="",D2=""),"",C2+D2) in E2 for the next due date. The result is 1 May 2026. This is calendar-day arithmetic; if the applicable schedule uses another method or period, follow that method rather than assuming that a number of days is equivalent.

To flag a result and due date, assume E2 contains the next due date and F2 contains the latest result. In G2, enter =IF(F2="Fail","Action required",IF(E2="","Enter due date",IF(E2<TODAY(),"Overdue",IF(E2<=TODAY()+7,"Due soon","Current")))). This checks for a failed result first, then a missing due date, then whether the test is overdue or within seven days. For example, if F2 is Pass and E2 is 1 May 2026, the formula returns Overdue on 3 November 2026. The seven-day warning window is only an example; adjust it to fit your process.

These formulas assume that dates are stored as Excel dates, not text. If a date appears unexpectedly, check the cell format and the value entered. For a more robust history, calculate the next due date from the relevant test record and interval, while retaining every dated inspection row. Avoid a formula that automatically treats a failed test as resolved just because a later due date exists.

Use filters and formatting to spot work

Filters help a coordinator focus on one floor, one test type, open defects, or overdue items. In an Excel table, use the drop-down arrows in the heading row. Keep the raw inspection history intact; filtering changes what is displayed, not the underlying records. Before distributing a report, state the date range and filters used so readers know what the view includes.

Conditional formatting can make urgent records easier to find. Select the due-date or status cells and use Home > Conditional Formatting to highlight values or text, such as overdue dates or the words Fail and Action required. Choose colors with enough contrast and do not rely on color alone: retain clear words such as Overdue and Open so the sheet remains understandable when printed or viewed by someone who cannot distinguish the selected colors.

Freeze the header row with View > Freeze Panes > Freeze Top Row when a long log would otherwise lose its headings while scrolling. For a printed checklist, use Print Titles or repeat the heading row on each page, check the print preview, and avoid shrinking the sheet so far that asset IDs and notes become unreadable.

Record a test and manage a failed unit

A checklist should describe what the tester actually did and observed, according to the approved procedure for that system. A recorded Pass should not be used merely because a fixture looks intact or because the test button was pressed. The required test method and expected duration should come from the applicable procedure, equipment instructions, and site requirements.

If a unit fails, record the symptom in plain language, such as “does not illuminate during test” or “indicator shows a fault,” rather than writing only “bad.” Add the asset ID, date, test type, and any relevant measured duration. Assign an action owner and target date under the organization’s process, and record repair and retest information separately. A closed work order does not by itself show that the emergency-lighting function was verified after repair.

Testing can affect occupants or normal lighting, particularly for longer tests or central systems. Follow the site’s authorized procedure, communicate planned interruptions where required, and arrange any necessary precautions before testing. Do not open equipment or attempt electrical repairs unless qualified and authorized to do so. Escalate a potentially unsafe condition through the building’s established maintenance and safety process.

Common spreadsheet mistakes and practical safeguards

  • One row per location rather than per asset: a single location may contain several units with different results. Give each unit an identifiable record.
  • Replacing old results: overwriting last month’s check removes evidence of history. Add a new inspection row or preserve an archived log.
  • Using a generic interval for every check: visual reviews, functional tests, and duration tests may have different requirements. Store test type and interval explicitly.
  • Leaving failed items without owners: a failure is not actionable if there is no responsible person, target date, and follow-up record.
  • Trusting a formula without checking inputs: blank dates, text-formatted dates, and an incorrect interval can produce misleading status labels. Review sample rows and formula results.
  • Treating the workbook as the compliance authority: the spreadsheet is a tracking aid. Confirm requirements against current local rules, the adopted standard, and site procedures.

Protecting formula cells can reduce accidental edits, but protection is not a substitute for access control or backups. Keep an approved copy, review changes to interval settings, and retain records according to the organization’s recordkeeping policy and applicable requirements.

When Excel is enough—and when it is not

Excel can be a practical choice for a small or moderately sized inventory when a named person maintains the file, records are reviewed, and the workbook is stored where authorized staff can access it. It is flexible for filtering, summaries, and printing, and users can tailor fields to a building’s equipment and procedure.

A shared spreadsheet can become difficult to govern when many sites or technicians enter data at once, when approvals and audit history are essential, or when reminders must be sent automatically and reliably. In those cases, a facilities-management or inspection system may offer controlled forms, user permissions, audit trails, and work-order links. A paper checklist may still be useful during a walk-through, but results should be transferred into the maintained record promptly and checked for completeness.

Frequently Asked Questions

What should an emergency light checklist include?
At minimum, include a unique asset ID, location, inspection date, test type, result, fault notes, action owner, follow-up status, and next due date. Add equipment details and test duration where relevant to the system and the applicable procedure.

How often should emergency lights be tested?
The interval depends on the applicable jurisdiction, adopted standard, building, system, and manufacturer instructions. Confirm the requirement with the responsible authority or qualified safety professional; do not copy an interval from a generic template without checking it.

Can Excel automatically show overdue emergency light tests?
Yes. Store the next due date as a real Excel date and use a status formula or conditional formatting to flag overdue records. Review the formula and date inputs, because an incorrect interval or a date stored as text can make the result misleading.

Should each emergency light have its own row?
Usually, yes. A unique row per fixture makes it easier to identify failures, assign repairs, and compare inspection history. If the log uses one row per test, retain the same asset ID on every inspection record.

Does a visual check count as a full emergency-light test?
Not necessarily. A visual check can reveal visible damage or warning indicators, but it does not establish that a unit operates or sustains illumination for a required duration. Record the actual type of check performed.

Can I use a template as proof that my building complies?
A completed log may support recordkeeping, but the template alone cannot establish compliance. The required test, procedure, equipment coverage, competent personnel, and record-retention rules depend on the requirements that apply to the site.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.