How to Write a Defensible FI Code Under BS 7671 Amendment 4

Last reviewed: 21 October 2026

An FI no longer automatically fails an EICR. That gives inspectors more room for judgement, and it means every FI now has to explain itself. Here is how to write one that stands up.

Since Amendment 4 took over from the previous edition of BS 7671 on 15 October 2026, the redrafted notes in Appendix 6 have changed how a Further Investigation observation affects the overall outcome of an EICR. For a decade, any FI meant an Unsatisfactory report. Now an FI does not need to be treated that way, and the inspector decides. (We explain the change itself in Does an FI Code Still Fail an EICR?)

Most of the discussion so far has been about whether that’s a good idea. The more useful question for anyone signing reports is practical: when an FI and a Satisfactory outcome appear on the same report, what does the report need to say for that decision to hold up? Sooner or later someone will read it and ask, whether that’s a scheme assessor, a dutyholder’s insurer, another inspector or a solicitor.

Under the old convention, an FI carried its own consequence, so the wording barely mattered. Under Amendment 4, the wording is the evidence for your judgement. A vague FI next to a Satisfactory outcome now looks less like caution and more like a gap.

Is FI the right code at all?

The purpose of FI hasn’t changed. It’s for an apparent deficiency that can’t be fully assessed within the agreed extent of the inspection. Before reaching for it, three questions sort most cases:

  1. Have I seen an actual indication of a problem? FI needs something observed: discolouration, an unexpected reading, a circuit that doesn’t match its label. A part of the installation you simply didn’t get to is a limitation and belongs in the limitations section, not an FI.
  2. Could I have assessed it within the agreed scope? If the answer is yes and it wasn’t done, the fix is to do the test, not code an FI. Isolation being inconvenient on the day is not the same as being outside the agreed extent.
  3. If I can already say what it is, have I coded it? Missing RCD protection you can see is a C2 or C3, not an FI. FI is for genuine uncertainty about the classification, not uncertainty about how the client will react.

If the observation passes all three, it’s a legitimate FI. The next job is to write it so the next reader understands exactly what was seen, what couldn’t be checked and why.

Three FIs, written two ways

A defensible FI answers four things: where it is, what was actually observed, why it couldn’t be assessed further, and what needs to happen next. The examples below are illustrative, but they’re typical of what turns up in occupied commercial buildings.

1. The energised “spare”

  • Weak: FI – DB2 circuit 7 unknown.
  • Defensible: FI – DB2 (first-floor riser), way 7: 20 A Type B MCB labelled “spare” but energised. Load not traced as the first-floor offices were not accessible on the day, as recorded in the agreed limitations. Insulation resistance and Zs within limits; no signs of thermal damage at the board. Trace the circuit, update the chart and reclassify once identified.

Nothing observed points to danger, the test results are sound and the limitation is recorded. This FI can sit beside a Satisfactory outcome with a clear conscience.

2. The warm termination

  • Weak: FI – overheating DB-12.
  • Defensible: FI – DB-12 (ground-floor plant room): discolouration at neutral bar terminal 4. Thermal image attached shows the termination noticeably warmer than adjacent terminals under normal load. Not dismantled because the board supplies the server room and no shutdown was within the agreed scope. Arrange a planned shutdown and inspect and remake the termination without delay.

Here the uncertainty could easily hide a C2. That reasoning, written down, is what justifies an Unsatisfactory outcome, and the photograph means anyone can see why.

3. The cable you can’t follow

  • Weak: FI – external lighting circuit.
  • Defensible: FI – DB1 way 11, external lighting: cable enters the wall void at high level and could not be followed to its termination without removing finishes, which was outside the agreed scope. Insulation resistance and RCD operation satisfactory. Inspect the route and the external enclosures at the next opportunity.

Again the evidence points one way, and the report says so.

The difference in every case is the same. The weak version tells the reader that something is unknown. The defensible version tells them what the inspector knew, what they didn’t, and why that gap does or doesn’t change the overall picture.

When only FIs remain: making the call

With no C1 or C2 on the report, the overall outcome rests on the FIs. A simple rule of thumb: ask what each one is most likely to turn out to be. If the honest answer for every FI is “probably fine, needs confirming”, Satisfactory is defensible. If any one could reasonably be hiding a C1 or C2, Unsatisfactory remains the right call.

Whichever way it goes, put the reasoning in the report. A sentence in the general condition section, explaining that the FIs relate to circuits that could not be traced, that test results on them were within limits and that nothing observed indicated danger, turns a judgement into a record. Amendment 4’s explicit recognition of photographic and thermographic evidence makes that record far stronger, and Regulation 653.2’s requirement for recipient guidance is the place to tell the dutyholder what the FIs mean for them and how soon to act.

Three habits worth building into every firm’s coding policy now:

  • No FI without an observation. If nothing was seen, it’s a limitation.
  • No Satisfactory-with-FI without written reasoning. One or two sentences is enough.
  • Photograph anything that drove a judgement call. If it influenced the outcome, the next reader should be able to see it.

The point of the change

The industry worry is that FI becomes an easy exit: a short visit, a handful of FIs, a Satisfactory outcome. That risk is real, but the protection against it is the same thing that makes good reports useful to clients: clear, specific wording backed by evidence. Amendment 4 trusts inspectors to judge. Writing FIs that show the judgement is how we keep that trust.

Need a report you can rely on?

Inspect Electrical Ltd is an NICEIC Approved Contractor based in Chislehurst. We carry out commercial EICRs and fixed-wire testing with clearly reasoned, evidence-backed findings, and independent electrical inspections where a report or installation is in dispute.

Request an EICR quotation

This article provides general technical guidance for inspection and testing practitioners. The current edition of BS 7671, IET Guidance Note 3 and your scheme provider’s requirements take precedence.

Need an electrician in Bromley, Chislehurst or SE London?

NICEIC Approved · 30+ years’ experience · Free written quotes

Scroll to Top