Fixed Wire Testing PPM Services UK – Periodic Inspection & Testing

Fixed wire testing (EICR) deals with your building’s wiring; PAT deals with the plug‑in kit your people actually touch.

An Electrical Installation Condition Report is your IET Wiring Regulations (BS 7671) check on the fixed electrical installation: incoming supply, distribution boards, final circuits, earthing and bonding, and fixed accessories like sockets, isolators and lighting points. Portable appliance testing sits under the Electricity at Work Regulations and focuses on anything that can be unplugged – laptops, kettles, vacuums, extension leads, small tools. An EICR will never see the cracked kettle flex in a staff kitchen; PAT will never pick up a loose termination in a distribution board that can overheat and lead to a fire. If you want to sleep at night on both fire and electric shock risk, you stop treating them as either/or and see them as complementary parts of one electrical safety regime.

How do EICR and PAT split responsibilities in day‑to‑day risk control?

A simple way to think about it:

• EICR: = “Is the fixed installation sound and correctly protected if something goes wrong?”
• PAT: = “Are the appliances people plug in today safe to use in the way they actually use them?”

Health and Safety Executive guidance leans on this split: your duty is to prevent danger “so far as is reasonably practicable”, which means looking at both the infrastructure and the items connected to it. In real buildings, most electrical incidents come from a mix of both – tired sockets, overloaded extension leads, older boards with limited protection, and portable heaters dragged into corners year after year. When you line EICR and PAT up under one plan, you can see patterns: boards that constantly feed high‑risk circuits, areas where appliances regularly fail, times of year when certain problems spike.

All Services 4U typically bundles EICR and PAT into one combined electrical services safety programme: one calendar, one set of naming conventions, one defects log and one evidence trail. That lets you show a regulator, insurer, lender or board that you have joined-up control of the whole system instead of two disconnected spreadsheets that only tell half the story each.

Where does a combined EICR and PAT approach really prove its value?

You feel the benefit most in buildings with complexity and churn:

• Multi‑occupancy residential blocks and high‑rise residential buildings (HRBs).
• Blocks with mixed tenure where multiple parties own appliances.
• Purpose‑built student accommodation (PBSA) and build‑to‑rent schemes.
• Multi‑let offices and flexible workspace with frequent tenant changes.
• Any portfolio where units change hands regularly.

These settings constantly introduce new plug‑in equipment and new usage patterns into an installation that may already be under pressure. Running EICR and PAT with different suppliers, processes and formats almost guarantees gaps and blame‑shifting when a serious defect appears. A combined All Services 4U package gives you aligned test dates, shared access notes, a single observation register and common coding for follow‑up work. It positions you as the person who has thought about both the building fabric and the everyday behaviours that stress it, rather than someone hoping a single test label will keep scrutiny away.

If you want your electrical safety storey to stand up to questions from an HSE inspector, building safety regulator or insurer, this is exactly the point where bringing EICR and PAT under one programme starts to pay for itself.

You start from IET Wiring Regulations and official guidance, then apply risk and build a forward‑looking calendar your team can actually run.

For rented homes, many landlords work with a maximum five‑year EICR interval because it matches private rented sector regulations and common lender expectations. BS 7671 and the accompanying IET Wiring Regulations, however, push you back to inspection frequency “as determined by the person responsible”, taking into account use, environment, loading and history. A relatively modern office with stable occupancy may justify longer recommended intervals than a damp plant room, a workshop with frequent reconfiguration, or supported housing where portable heaters, oxygen concentrators and mobility equipment are common.

In commercial or mixed‑use buildings, you follow the same logic: you take the last EICR’s recommendation as a starting point, then tighten intervals where you see harsh environments, frequent modifications or a run of significant C1 and C2 observations. Health and Safety Executive advice consistently stresses that you should consider patterns of damage and previous findings when you set inspection frequency, not just default to a single headline number.

The real shift happens when you stop tracking all of this in one over‑worked spreadsheet and move to a structured calendar: each property and each distribution board with a last‑tested date, next‑due date, notes on limitations and who is responsible. That’s the point where answering “what’s overdue, and why?” becomes a quick conversation, not a week‑long hunt through email chains.

How can you rebuild an EICR calendar that has already drifted out of control?

You deal with it as triage rather than trying to fix the entire country in one go. A practical method:

1. Pick a coherent slice – for example: all HRBs, all care settings, or all older stock built before a certain date.
2. List what you know – last EICR date, whether the report was satisfactory or not, and any specific recommendation on the next inspection interval.
3. Flag the obvious risks – unsatisfactory reports, long gaps between past inspections, buildings with known issues (e.g. recurring overloading, historic incidents).
4. Phase the work – spread EICRs month‑by‑month across the next cycle to avoid a “five‑year cliff” where everything lands at once.
5. Lock in the naming and filing – so each new report drops straight into the structure you are going to scale.

All Services 4U often starts with that kind of limited pilot. We take one region or asset class, map every board and area into a five‑year view aligned with BS 7671, show you the work volume by month and the likely remedial hotspots, then agree what is realistic for your budgets and operational constraints. Once you see that on one slice, you can roll the pattern across the wider estate without guessing.

Would a simple interval table help give you a steering wheel?

Used carefully, yes. You are not replacing engineering judgement, but you can give yourself a starting map:

*Always follow the actual EICR recommendation and relevant legislation.

When you can put a table like that in front of finance or a board and then show, building by building, where you sit against it, conversations about spend stop being vague and start becoming about risk choices. That’s the level where you no longer look like you are “broadly in date”; you look like you are deliberately managing your electrical safety cycle.

A credible visit follows a controlled method on site and leaves you with a BS 7671‑aligned report you can turn into actions, not just a PDF to file.

On site, you want to see a disciplined process rather than ad‑hoc testing. That starts with safe access and safe isolation under the Electricity at Work Regulations, agreed shutdown windows for sensitive circuits, and a clear scope for which boards and areas are in or out. An engineer should carry out visual inspection on accessible equipment, dead tests such as continuity and insulation resistance where conditions allow, and live tests such as earth fault loop impedance and residual current device checks in a structured way.

You should see limitations recorded specifically – “no access to flat 3A, consumer unit in locked cupboard” – instead of vague phrases like “limited due to occupancy”. In operational buildings, there should be a plan for night or weekend work where power loss during the day would disrupt critical services or resident safety. You are not paying for guesswork; you are paying for a documented check of the installation you can defend.

All Services 4U engineers work to agreed method statements and risk assessments before they touch a board. That protects your residents, your staff and your reputation when someone later asks how seriously you take electrical safety.

What should a modern EICR pack give you beyond the standard report?

A basic Electrical Installation Condition Report that simply ticks “satisfactory” or “unsatisfactory” and lists codes is not enough for portfolio control. You should expect:

• A clear overall assessment against BS 7671.
• A schedule of inspection items, marking what was actually inspected or tested.
• Test result schedules for the circuits where testing was possible.
• A list of observations coded C1, C2, C3 and FI with locations you can understand.

On top of that, a provider that understands how you work will give you:

• A defects register you can sort by code, site, board and asset.
• Photographs for significant items (e.g. overheated terminations, damaged enclosures).
• A simple indication of which findings are linked to life safety and which are more about resilience or compliance tidiness.
• Clear cross‑referencing between remedial certificates and the original observations when work has been completed.

All Services 4U designs this from the ground up so your team can move the data into your CAFM or compliance system without copying and pasting. That lets you answer technical and governance questions quickly – from HSE, a building safety regulator, an insurer or your own audit committee – with evidence at your fingertips instead of vague assurances that “we had someone in last year”.

How can you quickly tell if a testing visit was worth what you paid?

A simple sense‑check after any programme:

• Did the engineer follow a method you could see and understand?:
• Do the reports and test sheets match the agreed scope and your site layouts?:
• Can you see, in one view, what needs fixing, by when, and where?:
• Would you be comfortable handing this pack to a regulator or lender?:

If the honest answer to any of those is “not really”, it is time to tighten the brief or to work with a contractor that builds those expectations into their process from day one.

You pre‑agree what each code means in timeframes, owners and proof, so every report drops straight into a simple, repeatable playbook.

Under BS 7671, a C1 indicates danger present. That should trigger an immediate make‑safe response: isolate the circuit or fix the defect before leaving site, document precisely what was done, and, if needed, escalate to your responsible person. A C2 means potentially dangerous: it does not need the same‑hour response of a C1, but it should never be left without a defined service level – many organisations choose something like seven days for higher‑risk buildings and 28 days for lower‑risk assets.

“Further investigation required” (FI) is where many programmes quietly fail. It is not a polite suggestion; it is a statement that the engineer cannot confirm safety until more testing or intrusive inspection takes place. In risk terms, most organisations treat FI like a C2 until the investigation is complete: it goes onto the same queue with the same urgency, so it does not vanish into a vague “to do later” folder. C3 observations (“improvement recommended”) sit legitimately in your planned works and capital programmes, but repeated C3 themes – for example, lack of RCD protection on socket circuits in certain blocks – are often a signal that you should move faster in those areas.

A short remedial policy that sets these rules out in plain language for your internal teams and contractors is one of the highest‑leverage governance documents you can introduce. It means that when a report lands with multiple codes, everyone already knows the rules of the game.

What does a clean, auditable EICR‑to‑remedials loop actually look like?

In a well‑run loop, each new EICR flows into a central log where every coded observation becomes a task with:

• The original code and description.
• A location you can recognise (site, board, circuit).
• A due date based on your agreed rules.
• A named owner (internal, contractor or both).
• A simple list of what will count as closure evidence.

That task list then drives work orders and purchase orders. When a job is closed, the engineer’s notes, photographs and updated certificates are attached to the same record. Once that is in place, you can answer questions like “What happened to that C2 on the riser board in Block B last summer?” by following the trail in seconds instead of trying to reconstruct events from memory.

All Services 4U can run this loop end‑to‑end: fixed wire testing, remedial work, re‑testing and documentation, aligned with your risk appetite and governance. For you, that turns unsatisfactory EICRs from a recurring drama into a routine process with clear start and finish lines.

How can you use code patterns to plan smarter, not just react faster?

Over time, a good observation log tells you more than just what needs fixing this month. You start to see:

• Buildings that consistently produce high numbers of C2 and FI items.
• Recurring C3 themes that justify a targeted upgrade project.
• Assets that rarely show anything more serious than low‑level housekeeping.

When you can show finance or your board that a relatively small investment in, say, RCD upgrades in a group of higher‑risk blocks will remove dozens of C2s and FIs from future reports, it becomes easier to win support. That’s the point where your electrical safety programme stops being a string of isolated test visits and becomes a tool for steering capital in the places it will reduce risk most.

You separate inspection from remedials, build three honest budget lines, and use real EICR data to stop pretending all buildings behave the same.

Inspection cost is essentially time on site: the number and complexity of distribution boards, how circuits are labelled, access constraints, whether night or weekend work is needed, and how much of the installation can safely be tested during a visit. Remedial work and follow‑up inspections then sit on top of that as separate, variable pieces.

A practical budgeting model has three lines:

• Inspection and testing: – cyclical EICR work based on your chosen intervals and the size/complexity of each building.
• High‑priority remedials and investigations: – making safe and resolving C1, C2 and FI findings within agreed timeframes.
• Planned improvements and upgrades: – recurring C3 themes (for example, limited RCD coverage) and known weak points.

You share with bidders the basics they genuinely need to price inspection work properly: approximate board counts per site, building types, typical access windows and any critical circuits that limit shutdown options, especially where wider electrical services may affect access or sequencing. You also set out how you want outputs delivered – structured EICR, observation log, photos and clear rates for remedials and re‑tests – so that you do not end up comparing one supplier’s fully resourced programme with another’s bare‑bones test‑only quote.

How do you avoid being trapped by attractive “from £X per circuit” offers that never reflect reality?

Those headline rates often assume ideal conditions: straightforward access, daylight working, well‑labelled boards, minimal reporting detail and no commitment on what happens when the report comes back unsatisfactory. They look tidy in a tender table and create a headache the first time you need to defend an incident or a claim.

A more grown‑up route is to run pilot buildings with a small number of serious bidders:

• Pick one or two sites that genuinely reflect your portfolio’s complexity.
• Agree a clear scope for each provider – what is in, what is out, what evidence you expect.
• Compare the actual hours on site, limitation rates, defect volumes and remedial pricing.

All Services 4U is comfortable starting with that level of transparency. You see how we handle awkward access windows, resident communication, out‑of‑hours work and untidy real‑world boards before you roll anything out wider. Once you have that data, you can set realistic per‑board or per‑circuit assumptions for different asset types – HRBs, general needs blocks, PBSA, single‑tenant offices, mixed‑use – and your finance conversations shift from debating guesswork to deciding which risks you will address first.

Can a simple budget table help you frame those conversations?

Yes, even a basic view keeps everyone honest:

When you walk into budget rounds with a structure like this and portfolio data from real EICRs, you sound like someone managing risk, not someone defending a single, mysterious line called “electrical”.

Audit‑ready means you can show, for any site, what was tested, what failed, what you did about it, and how you prove that today.

For multiple sites, you start with a basic electrical register that mirrors how auditors think:

• Portfolio → site → building → distribution boards → key circuits where you hold detail.
• Last EICR date and next‑due date for each board.
• Current EICR status (satisfactory/unsatisfactory) and counts of open C1/C2/FI items.
• Notes on limitations, special access rules and critical circuits.

That register then drives your workflow:

1. Scope and schedule testing based on risk and capacity.
2. Deliver site work under the Electricity at Work Regulations with agreed methods.
3. Capture EICR results into a central log.
4. Generate tasks from observations, with codes, due dates, owners and proof requirements.
5. Complete remedials, re‑tests and sign‑offs; attach evidence to the same record.
6. Refresh the register and your dashboards so you can see, at a glance, where you stand.

Over the top, you run simple views for different audiences: compliance dashboards, insurer and lender‑ready binders, and short narratives that explain how you set your inspection intervals and approach governance. For building safety regulators and other stakeholders, these short narratives often carry as much weight as the technical detail.

How do you keep that programme robust when people, platforms and suppliers change?

The only way to make the programme resilient is to standardise the way you name, record and check work so it does not depend on one hero engineer or one champion inside your team. That means:

• A clear naming convention for boards, risers and areas that every contractor uses.
• A defined “home” for documents – not shared drive chaos.
• A minimal but consistent structure in your CAFM or records system so you can philtre by BS 7671 tags, PRS obligations, HRB flags and critical circuits.
• Light‑touch quality reviews: for example, quarterly spot checks on a sample of EICRs from different sites and suppliers.

All Services 4U can either plug into your existing systems as a Tier‑2 delivery partner, following your standards, or run an end‑to‑end managed service for fixed wire testing with its own governance wrapper. In both cases, the goal is the same: if a regulator, HSE inspector, insurer, non‑executive director or lender asks a sharp question about a specific building, you can pull a complete, accurate storey in minutes – not spend days searching email and hoping the right files still exist.

How does this change how you are seen inside your organisation?

When you can consistently answer “Which sites are overdue?”, “How many open C2s do we have in HRBs?”, or “What happened after this unsatisfactory report last year?” with calm, evidence‑backed answers, you shift how colleagues see your role. You are no longer just “the person who books tests”; you become the person who manages a critical risk discipline that underpins safety, insurability and mortgageability across the portfolio. That is the reputation stakeholders remember when they decide who to trust with more responsibility.

You bring in structured help when you’re tired of guessing where you stand and want one priority building handled properly from first test to final sign‑off.

Clear trigger points tend to repeat across organisations:

• An upcoming audit, regulatory inspection or building safety review.
• An insurer renewal where the broker is already asking detailed questions about BS 7671 and your control of electrical risk.
• A run of unsatisfactory EICRs with no credible, time‑bound remedial plan behind them.
• A portfolio where no one can answer “which sites are overdue?” without opening three different spreadsheets and several email folders.

If any of that sounds familiar, your problem is usually not a lack of data; it is the absence of a coherent model. Reports exist, but they do not flow into a loop that everyone can see and trust. Bringing in a partner at that moment is not an admission of defeat; it is a choice to move faster and with less drama.

All Services 4U is built for exactly that junction: we sit where compliance obligations, property maintenance and day‑to‑day operations meet, and we are comfortable being judged on how one real building feels in your world, not on a slide deck.

What does a low‑risk pilot with All Services 4U actually involve?

A sensible starting point is a single, representative site:

• One high‑rise residential building that is already under scrutiny.
• One complicated mixed‑use block with shared services and awkward access.
• One flagship office where you know electrical resilience really matters.

From there, the pilot is straightforward:

1. You share whatever you already hold – past EICRs, access notes, any particular constraints.
2. We agree scope and risk rules with you – what must be tested, what can be phased, what cannot go off.
3. We carry out the EICR in line with IET Wiring Regulations and the Electricity at Work Regulations, with clear communication before, during and after visits.
4. We produce a structured defect register and evidence pack that your team can understand without translation.
5. Where you want us to, we deliver remedial work, re‑test affected circuits and update the records so the storey hangs together.
6. We hand back a completed pack designed to stand up in front of an insurer, lender, board committee or regulator.

You see the disruption level, the communication rhythm and the quality of the outputs in one live environment you care about. After that, you can either:

• Ask us to replicate the model across more sites, at a pace that fits your budgets and governance.
• Or keep the playbook and have your own teams or incumbent suppliers work to the same standards.

Either way, you come out of that first pilot as the person who took one important building from uncertainty to a clean electrical safety storey that would survive hard questions. If you want to be seen as the leader who fixed the picture rather than the one still hoping the next round of audits will somehow be kinder, that is a good moment to start.