What happens after an issue is identified on an HV network?
A maintenance visit finishes and a report arrives. Somewhere in it is a finding: a reading outside the expected range, a component showing wear, moisture where there shouldn’t be any, a discrepancy between the drawings and what is actually installed.
The question that follows is rarely “is this a problem?” It is “how much of a problem, compared with everything else I am responsible for this month?”
That is a harder question, and a report that simply lists observations does not answer it.
Four possible responses, not one
Most HV findings resolve into one of four routes.
Continue to monitor. The finding is real but stable, and the sensible response is to track it at the next scheduled visit and see whether it moves. This is a legitimate outcome, not an avoidance of one. A provider who never recommends monitoring is not exercising judgement.
Investigate further. The finding indicates something, but not clearly enough to act on. Additional testing, a thermal survey, oil sampling or an intrusive inspection during a planned outage will establish whether there is an underlying fault. Worth being clear about what the additional work will and will not tell you before committing to it.
Carry out remedial work. The cause is understood and correctable. Gaskets, bushings, cable terminations, protection settings, earthing, labelling, access and security all sit here. The asset stays; the defect goes.
Treat it as an asset decision. The finding is a symptom of something that repair will not resolve, or repair is possible but no longer the better use of money. This is the point where a maintenance conversation becomes a capital one, and where other people in the organisation need to be involved.
What you need in order to choose
Three things make the choice straightforward, and their absence makes it guesswork.
The first is a stated priority. Not everything is urgent. A finding that makes continued operation unacceptable is different from one that should be planned into the next twelve months, and the report should say which it is in plain terms.
The second is the distinction between what is required and what is recommended. A report should separate actions required for safety or compliance, where they apply, from recommendations based on condition, reliability or good engineering practice. These are not the same category and should not be presented as though they were. Where a report does not make the distinction, it is a reasonable thing to ask for.
The third is ownership of the next step. Whether the action sits with ESE, with the site, with a network operator or with another contractor determines what actually happens next. Findings can go quiet simply because nobody was named.
When the decision leaves your desk
Many of these routes need a budget that sits with someone else, often someone without an electrical background. What travels well into that conversation is short: what was found, what it means for the site if nothing changes, what the realistic options are, and what each costs. What travels badly is a copy of the technical report.
If you are regularly having to translate findings into an internal case on your own, that is worth raising with whoever carries out your maintenance. Producing the case is part of the job.
Where the finding concerns an ageing asset rather than a correctable defect, the next question is a different one. We have covered that separately in when does an ageing transformer become an asset decision?
The wider point
A maintenance visit that only confirms an inspection has taken place has done the minimum. The value is in what it tells you about the next decision: what to watch, what to fix, what to plan for, and roughly when.
If your current reports leave you unclear on priorities or next steps, we can talk through what is in them and what further information or testing would make the next decision clearer. Our HV maintenance service is built around producing findings you can act on.