EICR Example and Template

A complete EICR must contain: client details, the extent of inspection, any agreed limitations, the Condition Report Schedule of Inspections, the Schedule(s) of Circuit Details, the Schedule(s) of Test Results, Section K observations each coded with a single C1, C2, C3 or (exceptionally) FI code, and the overall outcome — satisfactory, unsatisfactory, or limited in scope. Issuing the report without all three schedule types means the documentation is incomplete (GN3 Reg 3.11). The overall outcome must be recorded as unsatisfactory wherever any observation carries a C1 or C2 code (GN3 Reg 3.11).

A useful EICR example is not just a blank form with headings. It shows the shape of a report that someone can actually complete on site without losing the thread. The client, installation, extent of inspection, and any agreed limitations should be obvious before the inspection findings start.

If you want a cleaner checklist for the report sections themselves, what to include on an EICR is the best companion page to read alongside this one.

If the values and the wording do not agree, the report starts to look rushed. That is why the schedule of test results matters so much when you are building the final document.

The best templates do not just save typing. They help you finish the job with less friction, fewer missed fields, and a cleaner handover. That matters whether the report comes back satisfactory, unsatisfactory, or limited in scope.

If you are trying to keep the whole workflow together, digital EICR certificates make it easier to complete the report, keep the observations aligned, and move on to the next job without rebuilding the paperwork.

A4:2026 note: BS 7671:2018+A4:2026 introduced Reg 421.1.7, which recommends the installation of arc fault detection devices (AFDDs) on AC final circuits of a fixed installation to mitigate the risk of fire from arc fault currents. The regulation is recommendatory rather than mandatory. On post-October 2026 EICRs, absence of AFDDs where the recommendation applies may warrant a C3 observation — record it consistently if you note it on one circuit.

An EICR template is only as good as the data going into it. The boxes on the form are not the work — they are the record of the work. If you fill in the template before you finish testing, or copy values forward from a previous report, the document weakens immediately. Treat each section as a checkpoint: complete the testing, record the result, move on.

The most common mistake with templates is using them as a script for the inspection itself. The template should follow the testing sequence, not lead it. Open the supply, prove dead, complete continuity and insulation resistance, take the loop impedance readings, then sit down with the template and translate the results into the right boxes. That order keeps the inspection honest.