An HSE inspector doesn't want a thick binder of generic templates. They want evidence that your safety management system reflects what happens on your site — the actual equipment, real risks, controls that are genuinely in place. When they ask for maintenance records, inspection logs and defect close-outs, "I'll need a few days to pull that together" is itself a finding. Oxmaint builds inspection-ready records automatically from every work order — timestamps, engineer sign-offs, photos, corrective actions, all indexed against the asset. Book a compliance demo to see an HSE audit trail from live activity.
What HSE Section 20 powers actually mean
Under section 20 of the Health and Safety at Work etc. Act, an inspector can take samples, require testing, and collect evidence on the spot. Missing records don't buy you time — they narrow the inspector's assumptions about what your management system is doing.
What an HSE Inspector Actually Asks For
Inspection isn't a document sprint. It's a specific list of evidence categories the inspector expects to see immediately, in a form that ties back to your actual operation. The categories below appear on almost every HSE visit — the difference between sites that pass smoothly and sites that end up with improvement notices is whether these records are searchable in minutes or scattered across binders, inboxes and shared drives.
HSE Inspector — Document Request
Planned maintenance logs — dated, with engineer identity and asset reference. Not a schedule of intent — evidence the work happened.
Statutory inspection reports — PUWER Reg 6 records, LOLER Schedule 1 reports, LEV thorough examinations, PSSR schemes.
Defect reporting and close-out — what was found, who owned the fix, when it was verified. The close-out is the item most often missing.
Engineer competence and sign-off — training matrix showing who is authorised to inspect what, with dated evidence.
Corrective and preventive actions — evidence the site learns from findings, not just repeats them cycle after cycle.
Accident, near-miss and RIDDOR records — with the maintenance history of the equipment involved, cross-referenced.
The Six Elements of a Defensible Maintenance Record
A record that says "inspection complete — no issues" is an audit liability, not an audit asset. Regulators will reasonably conclude the inspection was superficial because the record provides no evidence otherwise. Any maintenance entry that has to stand up to HSE scrutiny needs six specific elements — miss one and the record loses its evidential weight.
01
Equipment identification
Asset number, type and location — so the record maps to a single physical machine, not "the mixer in bay 3".
02
Date and time stamp
Captured at the point of work, not typed up later. Backdated entries visibly weaken evidence.
03
Inspector identity & competence
Named engineer, signature, and the basis for their competence to inspect this specific equipment.
04
Findings — including "no defects"
What was actually checked, what was found, with severity classification. Photo evidence attached where relevant.
05
Corrective actions
What needs doing, owned by whom, due by when. Linked back to the parent inspection record.
06
Close-out confirmation
Dated record that the corrective action was completed and independently verified. This is where most systems fail.
Every one of those six is captured by default when a work order is completed in Oxmaint — the technician cannot mark a job done without the required evidence attached. Sign up free to enforce record completeness on every work order across your team.
Mapped to the Regulations You'll Be Asked About
An HSE visit rarely stops at one regulation. PUWER inspection records, HSG65 management-system evidence, and RIDDOR incident links tend to be requested together, and the inspector will cross-check what one set of records says against another. A well-structured CMMS makes that cross-check unremarkable rather than adversarial.
| Regime | What HSE expects to see | Where Oxmaint holds it |
|---|
PUWER 1998
Reg 6 inspection records |
Written inspection records for every piece of work equipment, kept at least until the next inspection, available on request. |
Per-asset inspection history with timestamps, engineer sign-off and severity-classified findings. |
HSG65
Managing for H&S |
Evidence of Plan-Do-Check-Act — that findings feed back into planning, not just get filed. |
Corrective actions link to preventive tasks; recurring findings surface as review flags on assets. |
RIDDOR
Reportable incidents |
Incident record cross-referenced with the maintenance history of the equipment involved. |
Incident entries link directly to the asset record — full work-order history one click away. |
LOLER Reg 11
Report retention |
Schedule 1 reports retained and produced on request, tied to specific lifting equipment. |
Digital reports stored against each asset, exportable as a single audit pack per site. |
Section 20 HSW Act
Inspector powers |
Documents produced on request at the point of visit — not "we'll send them over next week". |
Site-level audit pack export in one click, filtered by date range or regulation. |
Build the Audit Trail While You Do the Work
Every completed work order becomes evidence. Timestamps, sign-offs, photos and corrective actions — all indexed against the asset and ready for an HSE inspector on the day they arrive.
What a Work Order Captures — Automatically
The point of a CMMS built for HSE readiness isn't to add data-entry burden on your maintenance team. It's the opposite: the required evidence is captured as a byproduct of the technician doing the job on their mobile. The screenshot-style view below shows what a single completed work order carries by the time it hits the audit trail.
Timestamp
12 Nov 2026 · 09:42 GMT (captured on device)
Engineer
S. Ahmed · PUWER-competent (cert on file · exp. 04/2028)
Regulation reference
PUWER 1998 Reg 6 · site inspection schedule
Checks performed
14 of 14 items · 1 minor finding logged
Photo evidence
4 images attached against specific check points
Corrective action
CAR-1183 raised · owner J. Reid · due 19 Nov · closed 17 Nov
Sign-off
Engineer signature + supervisor countersignature captured
Expert Perspective — Quality of Evidence Over Quantity of Documents
The shift in HSE inspection practice is settled: inspectors want quality of evidence over quantity of documents. A binder of generic templates doesn't reassure them — a searchable record that ties each maintenance event to a specific asset, engineer and date does. The question isn't "do you have records?" It's "can you produce a specific record against a specific machine, right now?"
Templates ≠ evidence
Off-the-shelf checklists that don't reflect actual site risk are treated as paperwork compliance, not real compliance.
The close-out gap
Most inspection programmes capture findings but not the dated confirmation the fix was completed and verified.
Records must be current
A risk assessment written five years ago and never reviewed will not satisfy an HSE inspector on site.
Producible on the day
"We'll email them across next week" is functionally the same as not having them at the point of inspection.
Who This Is Built For
Oxmaint's HSE-readiness workflow is used by the specific roles that carry the evidence burden day-to-day: maintenance managers who need every technician's job to produce compliant records without extra admin, HSE managers responsible for producing audit packs on demand, facilities heads managing multi-site statutory schedules, and operations directors who want inspection readiness to be a byproduct of routine work rather than a quarterly panic. Each role sees the compliance calendar and evidence trail filtered to what they need to act on. Sign up free and configure your HSE workflow with your team's real assets in the first session.
What Happens in the First 30 Days
Moving from spreadsheet-and-inbox record-keeping to an HSE-ready audit trail doesn't require rebuilding your asset base or retraining every engineer. Existing asset lists and legacy CMMS exports import directly. PUWER and LOLER intervals load against equipment classes on day one. Within the first inspection cycle every work order carries its six required evidence fields as standard, and the site-level audit pack export runs against real data. Sign up free to import your current asset list, or book a walkthrough to see the audit pack export on live data.
Turn Every Work Order Into Inspection Evidence
Stop assembling records the week before an audit. Oxmaint captures HSE-ready evidence from every completed job — searchable, signed, timestamped, and exportable as an audit pack on demand.
Frequently Asked Questions
Are digital maintenance records accepted by the HSE?
Yes. HSE guidance is explicit that inspection and maintenance records may be held electronically, provided they are stored securely and can be produced on request. What matters is not the medium but the content — timestamps, engineer identity, findings, corrective actions and close-out. A digital record that captures those elements automatically is stronger evidence than a paper record filled in from memory at the end of a shift.
How long do we need to keep PUWER inspection records for?
PUWER Reg 6 requires records to be kept at least until the next inspection of that equipment and made available to HSE inspectors on request. Best practice — and what most insurers and audit regimes expect — is retention for the life of the equipment or a minimum of five years, whichever is longer. LOLER Schedule 1 reports have separate retention rules under Reg 11. Oxmaint retains all records indefinitely by default and never deletes without explicit sign-off.
Does this replace our need for external competent-person inspections?
No — and it isn't meant to. Statutory examinations under LOLER and thorough examinations of power presses under PUWER Reg 32 still require a suitably independent competent person, typically an external engineer surveyor. What Oxmaint replaces is the record-keeping and scheduling layer around those inspections — booking, capturing the report, logging defects, driving corrective actions, and holding the audit trail. The external competence stays; the compliance admin doesn't.
How does Oxmaint help with RIDDOR-reportable incidents?
Every incident logged in Oxmaint links directly to the affected asset and its full maintenance history — the last inspection, outstanding defects, corrective actions in flight, and engineer sign-offs for the previous 12 months. That linkage is what an HSE inspector wants to see after a reportable incident: not just the incident report, but the state of the equipment before it happened. Oxmaint produces that cross-reference automatically instead of requiring hours of manual retrieval.
Can we get an audit pack together for a site at short notice?
Yes — that's the specific use case. A site-level audit pack export bundles every inspection record, work order history, corrective action, sign-off and photo evidence for a chosen date range into a single PDF pack. It runs in one click, in minutes, and produces exactly the evidence set an HSE inspector under section 20 powers can request on the day of a visit.
.png)
