The EICR that passed and failed at once.
In short
An EICR with C1 and C2 codes is a completed inspection and a failed installation. The next inspection is five years away; the remedial work is due now. Record both, give every finding a date, and never upload the same report twice.
What happened
An electrical installation condition report comes back unsatisfactory: a C1 (danger present) and several C2s. The property manager uploads it. The history line reads failed, which a colleague takes for a failed upload, so the report goes up again with the inspection date typed as the next due date, and the check reads overdue. Now the block carries two assessments from one document, a dozen duplicated findings, and a check that is at once overdue, in date to 2031 and unsatisfactory.
Meanwhile the thing that matters, the C1, has no due date and sits in a list of 616 open findings, none of which has one.
What to do
- Separate the inspection from the installationThe inspection was done; its next due date is the interval on the certificate, usually five years. The installation failed; that is a finding with a date of its own. One record for each, never one record trying to be both.
- Give every finding a date by its codeC1 is danger present: make safe now, repair within days. C2 is potentially dangerous: weeks, not months. C3 is improvement recommended. FI is further investigation. A finding with no date is a finding that will still be open next year.
- Read the outcome in words, not codesUnsatisfactory means remedial work needed, read from the certificate. A history line that prints the raw word failed will be misread as a failed upload by the next person.
- Never upload the same report twiceIf the record looks wrong, correct the record. A second upload makes two assessments and doubles every finding, and the duplicates are harder to clear than the original mistake.
How Servanda does it
A certificate dropped in is read by the software and shown to a person before anything is recorded: the type, the dates, the outcome and the findings, with the verdict in words (unsatisfactory: remedial work needed, read from the certificate) and what happens next. If the same report has been logged before, the form says so, names who logged it, and the button reads log it anyway.
The check row carries the next inspection date and, while the installation is unsatisfactory, a red line with the findings open and how many are urgent. Findings get a due date from their priority when the report gives none (urgent in seven days, high in thirty), and the urgent ones reach Today and the morning email until they are closed with a note and, if you have it, the certificate for the repair.
The check reads in date to 2031 and unsatisfactory today. The urgency lives in the findings, each with a date.
Questions
- Is an unsatisfactory EICR a failed inspection?
- No. The inspection was completed; the installation failed it. Record the inspection as done with its next date, and record each coded observation as a finding with its own due date.
- How soon must a C1 be fixed?
- A C1 means danger is present. Make the installation safe immediately and complete the repair within days. Treat it as the most urgent item on the block until it is closed.