4 ways to automate emergency lighting testing

#1 - Simple checklist

Who it's for: Single-site venues where the manager runs the test themselves and wants the paper log on a phone.

What it is: Emergency lighting testing confirms the lights work when the power fails. This version is the tick-list of 7 checks, a pass/fail result, and a notes field. It covers triggering the test (the key switch or test facility), confirming each fitting comes on, checking none are damaged or out, and confirming they reset when the mains returns.

Available on: Basic.

In practice: A single-site venue runs the monthly function test. The manager operates the test switch, walks the building confirming each fitting is lit, marks pass or fail, notes one fitting over the back stairs not coming on, and the test is logged with the fault to fix.

Why it works: The list lives on the canvas, so the test covers every fitting the same way. The notes field captures the failed fitting, the one thing that matters, so it gets fixed rather than forgotten.

Steps included:

• 1 checklist (7 test steps)
• 1 pass/fail result
• 1 notes field

When to upgrade:

1. Rota staff run the test and don't all know the monthly vs duration test
2. You want photo proof the test was done
3. You run more than one site and want a named sign-off

#2 - With guidance

Who it's for: Venues where the test is delegated to whoever is on the rota.

What it is: The simple test with a guidance note: a short monthly function test confirms each fitting comes on when triggered, and a longer periodic duration test (often annual) confirms they stay lit long enough to evacuate. The note explains both and reminds staff to let batteries recharge after a duration test.

Available on: Standard.

What it adds to the previous template:

1. The difference between the monthly and the duration test is spelled out
2. Staff know to walk and confirm every fitting, not just trigger the switch
3. The test is consistent whoever runs it

Why it works: The guidance sits with the checklist, so a new starter knows which test they're running and what a pass looks like.

Steps included:

• 1 guidance note (monthly function test vs duration test)
• 1 checklist (7 test steps)
• 1 pass/fail result
• 1 notes field

When to upgrade: When a tick is no longer enough and you want photo proof (Emergency Lighting #3), or a named sign-off (Emergency Lighting #4).

#3 - With photo evidence

Who it's for: Venues that want proof the test was actually run and every fitting lit.

What it is: The guided test plus a photo of the fittings lit during the test. A photo of the lit emergency lights (or the test switch operated) is proof the test was done on the day.

Available on: Standard.

What it adds to the previous template:

1. A photo of the lit fittings, captured at the time
2. Proof the test was actually run, not just logged
3. A visual record tied to the day

Why it works: A monthly tick is easy to keep up without operating the switch. A photo of the lit fittings proves the test really happened.

Steps included:

• 1 guidance note (monthly function test vs duration test)
• 1 checklist (7 test steps)
• 1 pass/fail result
• 1 notes field
• 1 photo of the lit fittings

When to upgrade: When the test needs a named, dated sign-off so an audit can see who did it (Emergency Lighting #4).

#4 - With photo and signature

Who it's for: Multi-site groups where each site's lighting tests have to stand up to a fire-risk assessment or insurer review.

What it is: The photo test plus a signature. The person running the test signs to confirm every fitting was tested and works. For a group, that signature makes each site accountable for its emergency lighting.

Available on: Standard.

What it adds to the previous template:

1. A signature confirming the test was done and passed
2. Named accountability for each site's lighting test
3. A complete record (checklist, photo, signature) an auditor or insurer treats as best practice

Why it works: Emergency lighting records are part of the fire log a fire officer reviews. A signed, photo-backed record is the evidence that holds up.

Steps included:

• 1 guidance note (monthly function test vs duration test)
• 1 checklist (7 test steps)
• 1 pass/fail result
• 1 notes field
• 1 photo of the lit fittings
• 1 signature

When to upgrade: When you want Poppi to flag a failed fitting or a missed test to the manager, or pull every site's tests into one report. Those versions are coming in the next post update.

How to pick the right version

You don't need to know our product to choose. Just answer three questions.

Is it just you running the test, or do other people do it too?

If you do it yourself and know both tests, a plain list is enough. The moment rota staff do it, the guidance needs to be on the screen. If only you test, #1 is fine. If anyone else does, start at #2.

Do you need proof, or is a record enough?

A record tells you the test was logged. A monthly tick can be kept up without operating the switch. If you want proof, #3 adds a photo of the lit fittings.

Does someone need to sign off the tests?

In one venue, the record speaks for itself. Across sites, a fire officer or insurer wants to know who confirmed each. If no sign-off is needed, #3 is enough. If you run more than one site, #4 adds a signature.

Related workflows

• Fire exit check - the escape routes this lighting illuminates
• Fire alarm testing - the weekly alarm test
• Fire door check - keeping fire doors working

Conclusion

Emergency lighting only earns its keep in the seconds after the power fails, so an untested fault stays invisible until the worst moment. A recorded, photo-backed test turns it into something you can prove. The versions above move from a simple list to a signed photo record.

Five more versions are coming in the next refresh that bring AI into the test. Poppi can flag a failed fitting or a missed test to the manager, and pull every site's tests into one report. Those need more review time and will land separately.

→ Build your own emergency lighting test on Pilla. The Basic plan unlocks the simple checklist today.