Last updated: 17 October 2026
BS 5266 emergency lighting record keeping means logging every test, fault and repair for a building's emergency lighting so a "responsible person" can prove compliance with the Regulatory Reform (Fire Safety) Order 2005. BSI issued the current code of practice, BS 5266-1:2026, on 3 November 2026, widening its scope beyond escape lighting alone — per FSM Magazine (2026).
Key Takeaways
- BS 5266-1 is BSI's Code of Practice for the Emergency Lighting of Premises, reissued in full as BS 5266-1:2026 on 3 November 2026, replacing the 2016 edition — per FSM Magazine (2026).
- The 2026 revision expands scope to cover local area lighting and standby lighting alongside emergency escape lighting, the principal change from BS 5266-1:2016 — per BSI Knowledge (2026).
- Escape routes need a minimum of 1 lux across the full route width, open areas need at least 0.5 lux at floor level, and high-risk task areas need 15 lux or 10% of normal lighting, whichever is higher — per SparkyNinja's BS 5266-1:2026 guide (2026).
- Poor fire safety records carry real financial risk: Birmingham City Council secured a £50,000 fine against a freeholder in October 2026 over an unmet Improvement Notice covering emergency lighting, among other defects — per Blake Fire & Security (2026).
- The companion wiring standard, BS EN 50172, was updated in 2026 to add requirements for initial verification, handover documentation and the logbook itself — per BSI (2026).
Pulse Operations explains what BS 5266 is and what it requires for record keeping
BS 5266 is the British Standard series covering emergency lighting in non-domestic UK premises, with BS 5266-1 as its central code of practice setting out design, installation, testing and documentation. The current edition, BS 5266-1:2026, is a full revision of BS 5266-1:2016, and its principal change is an expansion of scope to cover local area lighting and standby lighting as well as emergency escape lighting, according to BSI Knowledge (2026).
BSI issued this revision on 3 November 2026, per Fire Safety Matters (2026). It sits alongside BS EN 50172, the harmonised European standard for emergency escape lighting systems, which governs installation, verification, operation, testing and the logbook itself.
Pulse Operations explains that, on record keeping specifically, BS 5266-1 requires a logbook that records the system design, commissioning details, every periodic test, every fault found, and every remedial action taken. It is not a tick-box exercise — fire risk assessors and enforcing authorities treat the logbook as the primary evidence that a system actually works, not just that it was installed.
For buildings being brought up to the current edition, Pulse Operations frames the practical question as less "do we need a logbook" and more "does our existing BS 5266-1:2016 logbook need updating for the wider 2026 scope" — a gap many duty holders haven't yet addressed.
Who is legally responsible for emergency lighting records in a commercial building?
The "responsible person" — defined under the Regulatory Reform (Fire Safety) Order 2005 (the RRFSO) as whoever has control of the premises, typically the employer, building owner or managing agent — holds the legal duty to maintain emergency lighting records. This is a statutory instrument, not a voluntary code, and it applies to virtually every non-domestic premises in England and Wales.
Under the RRFSO, the responsible person must ensure emergency lighting is provided, maintained in efficient working order, and that records of maintenance are kept. The Home Office guidance for persons with duties under the Fire Safety Order sets out these duties plainly, and BAFE's summary of fire safety law reinforces the same position.
In practice, responsibility often splits across a chain: a landlord may own the building fabric, a managing agent runs day-to-day compliance, and a facilities contractor physically tests the fittings. BS 5266 record keeping only works when one named person signs off that the whole chain is actually happening — which is precisely where paper logbooks and email trails fall apart in multi-tenanted blocks.
Pulse Operations's compliance runway exists for exactly this gap: it puts statutory building compliance, including emergency lighting obligations, on the same expiries runway as SIA licensing, BS 7858 screening and Martyn's Law readiness, so a managing agent or FM provider can see at a glance who owns what, and whether it's overdue. See /compliance for how that runway is structured.
What specific information must appear in an emergency lighting logbook?
A BS 5266-compliant logbook must record the system's design basis, every periodic inspection and test result, all faults identified, and the remedial work carried out to close each one. EN 50172:2026 added explicit requirements for initial verification, handover documentation and the logbook structure itself when it updated the 2004 edition, per BSI (2026).
At minimum, entries should capture:
- Date and time of the test or inspection
- Type of test (functional or full duration — see below)
- Who carried it out, including name and company/competency
- Results, including luminaire-by-luminaire status where faults exist
- Faults found and the corrective action taken
- Sign-off, with a named responsible person confirming closure
The East Sussex Fire & Rescue Service log book template is a useful illustration of what a fire and rescue authority actually expects to see on inspection — dated entries, named signatories and a clear fault-to-closure trail, not a single "all OK" tick at the bottom of the page.
A gap in any of these fields is what turns a routine inspection into an enforcement conversation. An inspector who sees "tested — OK" with no date, no name and no luminaire reference will treat the whole logbook as unreliable, even if every other entry is sound.
How often must emergency lighting be tested and the result logged?
Emergency lighting testing follows a fixed cadence under BS 5266-1 and BS EN 50172: a brief functional test monthly, and a full duration test annually, with both results logged every time, regardless of outcome. Missing a logged test is functionally the same as never having tested at all — there's no verbal exception.
| Test type | Frequency | What it checks | What must be logged |
|---|---|---|---|
| Functional/flick test | Monthly | Each luminaire illuminates on simulated mains failure | Date, pass/fail per fitting, faults, who tested |
| Full duration test | Annually | Full rated duration (commonly 3 hours) under battery power | Date, duration achieved, any early failures, remedial action, sign-off |
| Daily visual check | Daily (self-contained systems with indicator lamps) | Charging indicator lamp status | Simple logbook note or exception report only |
Between these, a daily visual check of indicator lamps on self-contained luminaires is good practice, though it's a quick glance rather than a formal entry unless something's wrong. The annual full duration test is the one that actually proves a building can be evacuated safely during a real power failure lasting the system's rated duration — commonly three hours in most commercial premises.
Functional test vs full duration test: how should each be recorded?
A functional test is a brief monthly check that each luminaire switches to emergency mode on simulated mains failure; a full duration test is an annual check that the system sustains that output for its full rated duration, commonly three hours. The two are recorded differently because they prove different things.
The functional test entry should log the date, confirm every luminaire illuminated (or list which didn't), and name the person who carried it out. It's quick, usually a walk-round with a test key or app, and any fault should trigger an immediate remedial note rather than waiting for the next cycle.
The full duration test entry needs more: the date, the duration actually achieved (not just "passed"), the state of charge indicators before and after, and — critically — confirmation that illumination levels met BS 5266-1's minimum standards during the test. Under BS 5266-1:2026, escape routes require a minimum of 1 lux across the full route width (excluding borders), open areas need at least 0.5 lux at floor level, and high-risk task areas need 15 lux or 10% of normal lighting, whichever is higher, with full illumination achieved within 0.5 seconds, according to SparkyNinja's guide to BS 5266-1:2026 (2026).
Because the full duration test takes the system offline for hours, it should be scheduled for low-occupancy periods and the logbook should note that arrangement explicitly — an inspector will ask how escape lighting was covered while the test batteries were discharged.
Paper logbook vs digital record: which format satisfies BS 5266?
BS 5266 does not mandate a specific format — a paper logbook and a digital/electronic system are both acceptable, provided the record is accurate, tamper-resistant and available on demand. The practical question for most businesses is which format actually survives contact with a real inspection, a staff change, or a multi-site portfolio.
| Factor | Paper logbook | Digital/electronic system |
|---|---|---|
| Tamper resistance | Low — pages can be lost, backfilled or altered | High, if the platform logs changes with a timestamp |
| Multi-site visibility | Poor — each site holds its own book | Strong — one dashboard across a portfolio |
| Survives staff turnover | Weak — knowledge often leaves with the person | Strong — history stays in the system |
| Audit speed | Slow — manual page-by-page review | Fast — exportable, searchable |
| Cost to start | Minimal | Varies by platform |
A logbook that an inspector can tell was filled in retrospectively — same pen, same ink, a suspiciously tidy run of identical entries — is worse than an honest gap with a corrective note. This is exactly the design problem Pulse Operations built its wider compliance record around: every checkpoint on a patrol is completed by a mandatory, watermarked photograph — officer, site, GPS, time — rather than a tag scan, and the underlying audit log is hash-chained (SHA-256) and tamper-evident, with a built-in integrity check that walks the whole chain. The same principle — a record that proves it wasn't altered after the fact — is what any emergency lighting logbook should aspire to, whether paper or digital.
How long must emergency lighting records be kept, and what happens if they're not?
Emergency lighting test records should be kept for the working life of the system, with most fire safety professionals treating a minimum of the previous five years as the practical floor for inspection purposes. Enforcement history shows what's at stake when records — or the underlying maintenance — fall short.
Birmingham City Council prosecuted Freehold Managers (Nominees) Limited, securing a £50,000 fine on 16 October 2026 after the company breached a Housing Act 2004 Improvement Notice requiring fire door repairs, emergency lighting improvements and adequate means of escape, per Blake Fire & Security (2026). Separately, enforcement action has previously seen one restaurant fined £13,000 and another small business fined £24,000 for fire safety regulation breaches that included inadequate logbook and maintenance records, according to the Fire Industry Association (2013).
These cases sit under the RRFSO's enforcement powers, which allow fire and rescue authorities to issue Enforcement Notices, Prohibition Notices, or prosecute in the magistrates' or Crown Court, with unlimited fines available on conviction. A missing logbook doesn't cause a fire — but it is frequently the evidence that turns an incident into a prosecution, because it proves (or disproves) that the responsible person knew about a fault and failed to act.
"Officers leave chaos, not work. Pay on time from clean records, don't ring them at 4am to fill a gap you could have seen on Monday, and let them see their own record standing up for them when a client complains. The basics done properly are the retention strategy." — Mo Hassan, Founder, Pulse
That principle — that clean, contemporaneous records protect everyone, not just the organisation — applies just as directly to a fire safety logbook as it does to a security rota.
Your BS 5266 emergency lighting record-keeping checklist
- Confirm which named person holds responsible-person duties under the Regulatory Reform (Fire Safety) Order 2005
- Check your current logbook against BS 5266-1:2026's expanded scope for local area and standby lighting
- Log every monthly functional test, even when the result is a clean pass
- Schedule and fully document the annual full duration test, including lux levels achieved
- Record faults with a clear closure date, not just an open action
- Decide between paper and digital records based on multi-site visibility and tamper resistance, not just upfront cost
- Retain records for at minimum the previous five years, and ideally the working life of the installation
- Cross-reference emergency lighting records against your wider fire safety and statutory compliance register
FAQ
What must be recorded in a BS 5266 emergency lighting logbook?
A BS 5266 logbook must record the system design, every periodic test (monthly functional and annual full duration), faults found, remedial action taken, dates, and the name of whoever carried out each check. Gaps in any of these fields undermine the whole record during an inspection.
Is an emergency lighting logbook a legal requirement in the UK?
Yes. The Regulatory Reform (Fire Safety) Order 2005 requires the responsible person to maintain emergency lighting and keep records of that maintenance, and enforcing authorities treat an absent or incomplete logbook as evidence of non-compliance.
How long should emergency lighting test records be kept?
Most fire safety guidance treats a minimum of the previous five years as the practical floor, though many professionals recommend retaining records for the full working life of the installation, particularly in multi-tenanted or leased buildings.
Who is responsible for keeping emergency lighting records under the Fire Safety Order?
The "responsible person" — the employer, building owner or whoever has control of the premises under the Regulatory Reform (Fire Safety) Order 2005 — holds this duty, though it's often delegated to a managing agent or facilities contractor in practice.
Can emergency lighting records be kept electronically instead of on paper?
Yes, BS 5266 does not mandate a specific format. A digital system is generally more defensible under inspection because it can timestamp changes and resist retrospective editing, whereas a paper logbook is easier to backfill or lose.
What changed in BS 5266-1:2026 regarding documentation?
BS 5266-1:2026, issued by BSI on 3 November 2026, is a full revision of the 2016 edition, with its principal change being an expanded scope covering local area lighting and standby lighting alongside emergency escape lighting — which affects what a compliant logbook now needs to cover.
What's the difference between BS 5266-1 and BS EN 50172 for record keeping?
BS 5266-1 is BSI's UK code of practice covering design, testing and documentation broadly; BS EN 50172 is the harmonised European standard specifically governing installation, verification, operation, testing and the logbook for emergency escape lighting systems, updated in 2026 with added requirements for initial verification and handover documentation.
Keeping emergency lighting records audit-ready with Pulse Operations
Emergency lighting logbooks fail inspection for the same reason security patrol records fail client audits: a paper trail that can't prove it wasn't filled in after the fact, or a responsibility chain where nobody can say who actually tested what and when. Pulse Operations's compliance runway puts statutory building compliance — including emergency lighting obligations — on the same expiries dashboard as SIA licensing, BS 7858 screening and Martyn's Law readiness, so a facilities manager or security operator can see what's overdue before an inspector does.
The same proof-of-service principle runs through Pulse Operations's patrol records: every checkpoint is completed by a mandatory, watermarked photograph rather than a tag scan, sitting in a hash-chained, tamper-evident audit log — the same standard any genuinely robust compliance record should meet, whether it covers a fire door, a plant room, or an emergency luminaire. If your estate needs one place to prove building compliance alongside security and FM delivery, get in touch with Pulse Operations for a walkthrough of the compliance runway at /compliance.
Related Reading
- Asbestos Management Record Keeping: 2026 UK Guide
- QR Code Guard Tour Disadvantages: UK Guide 2026
- Silvertrac Alternative 2026: Best UK Options Compared
Add pulse-operations.co.uk as a preferred source on Google
Back to all insights