Why an incomplete statutory report is worse than a late one
A late examination is a visible gap that can be closed. An incomplete report is a document that looks like compliance and is not, sitting in the file until someone reads it properly. Why validation belongs at the point of issue, and what a system can honestly promise about it.
By Hovermarks team
Quick answer. A late examination is a known gap: visible, dated, and closable. An incomplete report is a document that reads as compliance and is not one, because LOLER, PUWER and PSSR each require a record of a particular shape, and a document short of it does not satisfy the regulation even where the examination behind it was carried out properly. The duty holder believes they are covered the entire time, which is exactly why it is the worse failure.
Every duty holder can tell you when an examination is overdue. Nobody can tell you, by looking at a folder, which of the reports inside it are missing a required particular. That asymmetry is the whole argument.
The two failures are not the same shape
A late examination announces itself. The due date passes, a schedule flags it, and the position is unambiguous: this equipment is out of examination and must not be used until it is examined. Unpleasant, expensive, survivable. Everyone involved knows where they stand.
An incomplete report announces nothing. It has a date, a signature, a company letterhead, and a defect section. It passes a filing check, a spot check, and usually an insurance renewal. It fails at exactly one moment: when somebody reads it against the regulation, which in practice means after an incident, during an enforcement visit, or when a claim is being resisted.
The difference in consequence follows from the difference in visibility. With the late examination the duty holder knew and could act. With the incomplete report they believed they held a valid record, made decisions on that basis, and discover otherwise at the worst available moment.
Why the regulations work this way
Each regime asks for the record, not merely the activity:
- LOLER requires a report of thorough examination containing the information in Schedule 1. A document missing a particular is not that report, however good the examination was.
- PUWER Regulation 6 requires the result of the inspection to be recorded and kept until the next is recorded. An unrecorded inspection satisfies nothing, and a maintenance log that mentions a check is not a record of an inspection.
- PSSR Regulation 9(5) requires the report to state four specific things. A report silent on one of them is short of what the regulation asked for.
None of these are technicalities invented by auditors. They exist because the record is what the next person relies on: the operator deciding the equipment is safe to use, the insurer pricing risk, the investigator reconstructing what was known and when.
Where incomplete reports actually come from
Rarely from carelessness. Usually from these:
- Templates that predate a change. A form built years ago quietly omits a particular the regulation asks for, and every report from it inherits the gap.
- Fields left for later. The examiner intends to add the remedy-by date once the customer confirms a slot; the report issues; later never comes.
- A defect recorded in one place and a conclusion in another. The examination noted a defect; the summary says safe to operate; nothing in the system compares them.
- Missing history. The date of the last thorough examination is unknown because the equipment changed hands, so the field is skipped rather than addressed.
- Retyping. A record moves from a phone to a spreadsheet to a document, and the field that was captured is not the field that was printed.
Each is a process failure, not a competence failure, which is precisely why a system can help with them.
Validate at issue, not at audit
If a particular is missing, there is one moment when saying so is cheap: while the examiner is still in front of the equipment, with the record open. Every later moment is more expensive, and the audit is the most expensive of all.
That is the argument for refusing to issue an incomplete report rather than issuing it with a warning. A warning shifts the decision to someone under time pressure who wants to get to the next site. A refusal, with a list naming each missing particular and where to set it, turns a compliance failure into a two-minute task.
It also removes an uncomfortable ambiguity. A system that will produce an incomplete statutory report on request is, at the moment it does so, manufacturing a document that looks like assurance and is not. Declining is the more useful behaviour even though it is the less convenient one.
What this does not fix
Validation makes a report complete. It cannot make an examination competent.
No check on a document can tell whether the right components were examined, whether wear was correctly judged, whether a defect classified as acceptable should have been classified as dangerous, or whether the person carrying out the examination had the knowledge and independence the role requires. Those judgements sit with the competent person, and the legal duty sits with the duty holder. That division is in the regulations, and no tool moves it.
Anyone selling software that implies otherwise is selling reassurance rather than a capability, and reassurance is the one thing a compliance system should never be in the business of manufacturing.
Where Hovermarks fits
Hovermarks refuses to issue a statutory report that is missing a required particular, and names each gap with the regulation it comes from and where in the record to set it. It also refuses to issue a report that contradicts its own findings, such as a safe-to-operate declaration standing alongside a defect recorded as a danger to persons. Statutory reporting is on every paid plan. The statutory reporting page covers the validator, and the statutory reporting guide sets out what each regime requires.