Emergency Lighting Testing PPM Services for RTM Boards – BS 5266 Monthly & Annual Tests

Your RTM board should check scope, testing cadence, reporting, remedial follow-up, and who owns the evidence trail.

A contract for communal emergency lighting should do more than promise a visit. It should show exactly what will be tested, how often it will be tested, how failures will be reported, and how your board will track repairs to closure. If those points are vague, the board often ends up doing the missing admin itself.

That matters because emergency lighting in common parts is part of the wider fire safety picture. Under the Fire Safety Order, the focus is not simply whether a contractor attended. The focus is whether the system that supports escape routes is being maintained and recorded properly. BS 5266 points in the same direction. It supports routine inspection, testing, and record keeping, not just a once-a-year certificate.

The cheapest quote often leaves the board paying in time, uncertainty, and repeated follow-up.

Which parts of the contract should be defined before your board signs?

Your board should insist on clear wording about assets, visits, records, and defect handling before approving the service.

The contract should state which communal areas are included, how fittings are identified, and whether the provider is working from a live asset list or correcting an inherited one. That sounds basic, but many blocks carry old labels, moved fittings, and mixed records from previous contractors. If the starting point is unclear, the reports that follow are usually unclear too.

Your board should also be able to see whether the contract includes:

• monthly function testing
• annual full-duration testing
• logbook updates
• defect reporting against clear locations
• remedial quotations
• retest evidence after repair
• confirmation of the next due date

That level of detail helps directors make service-charge decisions that are easier to explain later. The RICS Residential Management Code supports a documented, reasoned approach to management, and this is one place where that principle matters in everyday practice.

Which warning signs usually show the contract is too soft?

A contract is too soft when it describes attendance clearly but leaves responsibility unclear after a failure is found.

That usually shows up in phrases like “testing carried out as required” or “report provided after visit” without any detail on what happens next. If a fitting fails, your board should not have to guess whether a quote will follow, whether the defect will be tracked, or whether the contractor will retest the item once repaired.

Ask one direct question during review: If a fitting fails next month, who records it, who proposes the fix, and how does the board see when it is closed? If the answer is vague, the service model is vague.

A simple contract comparison helps:

Why does this contract affect more than the lights themselves?

It affects how confidently your board can answer later questions about safety, spend, and oversight.

If the contract creates weak reporting, every later decision gets harder. Directors spend more time decoding old reports. Managing agents inherit unclear files. Residents ask whether faults were fixed, and the board cannot answer quickly. That is when a routine maintenance contract turns into a recurring management burden.

NFCC guidance and board-level good practice both favour a simple principle: if something safety-related is tested, the record should help the responsible people understand what happened and what still needs action. A contract that supports that is worth more than one that only looks competitive on day one.

If your board wants to compare providers on control as well as cost, a contract review with All Services 4U can help you test whether the service on offer will genuinely reduce board workload rather than quietly shifting it back onto volunteers.

Communal emergency lighting usually needs monthly function tests and annual full-duration tests.

Those two tests are not interchangeable. A monthly test checks whether fittings respond when the normal supply is interrupted. An annual test checks whether they can stay on for the required emergency duration. For an RTM board, that difference affects planning, budget timing, reporting, and how seriously to treat a failure.

BS 5266 is the main reference point here. It supports a short routine test during the year and a longer endurance test annually. In practice, one tells you whether the fitting changes over. The other tells you whether it can keep an escape route lit for long enough if the building loses power.

A fitting that flicks on for a moment has not yet proved it can protect the route out.

What does the monthly test actually tell your board?

The monthly test shows whether each recorded fitting responded properly on the day of inspection.

That is more useful than it first sounds. Many faults stay hidden under normal power. Residents see the fitting every day and assume it works. A monthly routine reduces the gap between a fault appearing and the board finding out about it.

A good monthly visit can help your board spot:

• fittings that do not illuminate
• obvious battery or charger faults
• damaged or missing exit signs
• mismatched asset labels
• defects that keep appearing without proper closure

That gives your board earlier visibility and a cleaner trail into the annual test.

Why does the annual test create more pressure?

The annual test shows endurance, and endurance failures usually lead to more decisions.

A full-duration test will often expose weak batteries, failed fittings, and gaps in the asset list that monthly checks do not fully reveal. It can also create resident questions if recharge periods or repeat visits are not explained well. In blocks with mixed records, the annual test often reveals two problems at once: the technical issue and the poor quality of past reporting.

That is why annual reports tend to carry more weight with directors. They do not just show whether the lights responded. They show whether the system can perform for the full emergency period that the building depends on.

What is the practical difference between the two tests for your board?

The practical difference is that one supports early fault spotting, while the other drives heavier remedial planning.

A simple comparison makes the distinction easier to follow:

The annual test also has a recharge consequence. After a full discharge, fittings may need time to recover. That affects timing, resident communication, and any follow-up visits.

When does this stop being routine and start becoming strategic?

It becomes strategic when regular testing reduces surprise, repeat faults, and rushed approvals.

That is usually the moment boards stop seeing monthly testing as a chore and start seeing it as a control tool. A reliable monthly rhythm means fewer unexplained failures at the annual stage, cleaner records, and less time spent asking what happened last quarter.

If your board wants to check whether your current monthly and annual testing rhythm is helping or simply generating paperwork, All Services 4U can review the cycle with you and show where the pattern is breaking before the next annual window creates more pressure.

Planned maintenance usually costs less because it reduces repeat visits, unclear defects, and reactive approvals.

Ad hoc testing can look cheaper when your board first compares quotes. The annual figure is low, the contractor promises support when needed, and the service appears flexible. The cost problem usually shows up later, when defects are rediscovered, reports are vague, and directors spend time approving small pieces of reactive work that should have been grouped and managed as part of a routine programme.

SFG20 is useful here because it supports structured planned maintenance rather than improvised response. In a residential block, that matters because the visible invoice is only part of the true cost. The other part is the time spent chasing, clarifying, re-attending, and explaining repeated failures to leaseholders.

Where does ad hoc testing become false economy?

It becomes false economy when the board pays more than once to identify or explain the same defect.

A common pattern is easy to recognise. The annual test finds several failures. The report is unclear. A quotation follows, but one location needs clarification. One item gets repaired, another is deferred, and another returns in the next report because the reference was too vague to track properly. Your board has now paid for attendance, clarification, and rediscovery.

That is not just a contractor cost. It is also director time, managing-agent follow-up, and a weaker explanation if leaseholders question repeated spend.

How does planned maintenance make service-charge decisions easier to defend?

It creates a visible chain from inspection to defect to approval to confirmed closure.

Leaseholders and advisers tend to challenge costs when the file looks disjointed. They are less likely to challenge where the sequence is clear. Planned maintenance helps because it shows that the block was tested regularly, a defect was identified, approval was given, and closure was evidenced afterwards.

That is much easier to explain than a bundle of separate call-outs and partial notes. It also fits the broader discipline expected by the RICS Residential Management Code, where the reasoning behind procurement and oversight should be visible rather than guessed.

What does the cost difference look like in practice?

In a planned model, your board pays for rhythm. In an ad hoc model, it often pays for interruption.

A small or medium block may not notice the difference immediately. But over time, repeated small inefficiencies add up: extra visits, unclear reports, delayed approvals, and defects that drift from one cycle into the next. Those costs are often spread across different invoices and different months, which makes them less visible but no less real.

A simple comparison helps:

When should your board move from reactive to planned?

Your board should switch when the annual test keeps producing surprises or the same defects keep coming back.

That is usually the point where the issue is no longer the fitting alone. The issue is the management model around it. If your directors are spending more time interpreting reports than approving sensible next steps, the block has probably outgrown the ad hoc route.

If you want to compare the true cost of the two approaches using your own reports rather than generic promises, All Services 4U can review your current pattern and show which route gives your board cleaner control and lower admin over time.

Your RTM board should keep records that show what was tested, what failed, what was fixed, and when closure was confirmed.

A certificate on its own rarely gives enough continuity. It proves something happened on a date, but not always what the live status of the system is now. Good records should help a new director, managing agent, insurer, valuer, or adviser understand the present position without rebuilding the history from old emails.

BS EN 50172 supports ongoing inspection and record keeping. That matters for RTM RMC boards because directors change, contractors change, and inherited files are often mixed. The aim is not to build a perfect archive. It is to keep a working record set that is clear enough for the next decision and the next handover.

Which records should be easy to retrieve quickly?

Your board should be able to retrieve the current asset list, test history, defect status, and close-out evidence within minutes.

A practical emergency lighting file should include:

• the current fitting or luminaire schedule
• monthly function test records
• annual full-duration test reports
• current logbook entries
• an open and closed defect tracker
• remedial quotations or approvals
• completion evidence and retest confirmation

If those items sit in separate places with different naming styles, the board still has a records problem, even if the testing itself has happened.

Consistent fitting references stop the same defect from being described three different ways.

That is one of the most common points of failure in inherited records. One report says “upper stair light.” Another says “exit fitting on landing.” A third says “stairwell emergency unit.” Directors cannot tell whether the same asset failed three times or whether three different assets failed once each.

A stable naming model fixes that. Once each fitting or location is consistently referenced, defect history becomes easier to trust, approvals become easier to defend, and retests become easier to match back to the original fault.

What should a future reviewer be able to understand at a glance?

A future reviewer should be able to see scope, test history, open defects, actions taken, and proof of closure.

A compact file structure should answer five basic questions:

That kind of continuity is useful not only for board handover. It also helps in insurer reviews, refinancing questions, and routine management changes.

How should your board improve inherited records without turning it into a major project?

Start with naming, chronology, status, and closure proof before trying to tidy everything else.

Boards often delay record improvement because they imagine a full archive rebuild. Usually the first gains come from simpler steps: one current asset list, one clear defect tracker, one filing order, and one naming convention. Once those are in place, older reports become easier to interpret.

NFCC guidance and practical fire safety management both favour records that help responsible people take action, not records that simply sit in a folder. If your current file set is usable but untidy, All Services 4U can help you standardise the core records first, so future directors inherit something workable rather than something mysterious.

Missed tests and open defects weaken both your safety position and your ability to show proper oversight.

The immediate issue is practical. If testing slips or faults stay open, your board knows less about whether the emergency lighting on escape routes will perform when needed. The slower issue is administrative. Once the record trail starts thinning out, later decisions become harder, reports feel less reliable, and resident or insurer questions take longer to answer.

This does not need dramatic language. It needs clear sequence. The board’s role is to show that known issues are identified, prioritised, and closed in a way that can be followed later. That is consistent with the Fire Safety Order, with NFCC guidance on maintaining precautions, and with broader good practice in block management.

Which delays usually create the most pressure later?

The most damaging delays are the ones where the technical problem and the record gap appear together.

That usually means:

• failed fittings with no retest evidence
• monthly checks missing for several periods
• annual failures with no approval trail
• defects that stay open across handovers
• reports that cannot be matched cleanly to locations

Those gaps tend to surface at awkward moments: a resident complaint, a fire risk assessment review, an insurer query after an incident, or a managing-agent handover.

Why does a small technical fault become a bigger management issue?

Because uncertainty around the history often grows faster than the defect itself.

A failed battery may be simple to replace. What becomes expensive is not knowing when it first failed, whether it was quoted, whether it was approved, or whether anyone confirmed the repair. That uncertainty creates extra visits, more emails, and slower board decisions.

It also makes recurring faults harder to spot. If your records are weak, the board may keep treating the same issue as if it were new.

How can your board explain the risk without sounding alarmist?

The clearest explanation is that delay makes future decisions slower, weaker, and harder to evidence.

That is usually enough. A director inheriting a patchy file is less confident approving new spend. A managing agent spends more time reconstructing history. Leaseholders are more likely to question repeat costs. A lender or insurer may ask for documents that should be easy to retrieve but now require detective work.

The Building Safety Act adds extra context where higher-risk buildings are involved, because record continuity and accountable oversight matter even more in that setting. But even outside HRBs, the basic management lesson stays the same: open issues should not be allowed to drift.

When should your board treat this as a reset point?

Treat it as a reset point when the same gaps are appearing across more than one testing cycle.

At that stage, the problem is no longer one missed test or one failed fitting. It is a broken management rhythm. The right response is to rebuild the sequence: live asset list, live defect tracker, current testing calendar, and clear close-out rules.

If your block has reached that point, a gap assessment with All Services 4U can help your board see what needs fixing first, what can be standardised quickly, and how to get back to a routine that is easier to defend and easier to manage.

Your RTM board should prepare enough information to show the current condition, likely gaps, and the right starting point.

You do not need a perfect file to have a useful contractor review. Most productive reviews begin with incomplete records. The real purpose is to avoid buying the wrong type of service. Some blocks need a clean move into routine PPM. Others need a baseline tidy-up first because the asset list is unreliable. Others need a remedial-first programme because known defects are already open and overdue.

A good review should leave your board with a clearer answer to one practical question: what should happen first in this block, based on the evidence already in hand?

The right programme starts with the real condition of the file, not the polish of the proposal.

Which information should the board gather before the review?

Your board should gather enough to reveal pattern and gaps, not every document ever created.

A useful starter pack usually includes:

• the latest annual test report
• recent monthly test records, if available
• current logbook pages
• any open defect list
• fire risk assessment actions that relate to lighting
• notes on access issues in communal areas
• recurring resident concerns, if relevant

If those records are scattered or inconsistent, that is useful in itself. It tells the reviewing contractor that the first job may be to stabilise the records before launching into routine cadence.

Which questions should the board ask during the review?

Ask questions that reveal workflow and judgement, not just price.

Useful questions include:

• how will fittings be referenced in future reports
• how will open and closed defects be tracked
• who updates the logbook
• what happens after a failed annual test
• how are monthly and annual outputs kept distinct
• how are inherited record gaps dealt with
• what does closure proof look like after remedials

These questions reveal whether the provider is thinking only about attendance or about helping a board run a reliable process.

Which outcomes should a good review produce?

A good review should point your board to one of three starting routes.

Those routes are usually:

That gives directors something practical to decide. It is far better than leaving the meeting with a generic quote that assumes every block needs the same thing.

Why does this preparation make the final decision safer?

It helps your board choose the right sequence rather than the most persuasive sales pitch.

That matters because emergency lighting management is not just about technical attendance. It is about buying the level of structure your building actually needs now. Some blocks need discipline. Some need reconstruction. Some need urgent clean-up before discipline has any value.

If your board wants a structured review that leads to a realistic next step rather than a generic proposal, All Services 4U can help you compare the options, match the programme to your actual records, and move forward in a way that gives directors more control from the first visit.