Why evidence quality matters
PUWER is not a paperwork hobby. It is how you demonstrate that work equipment is suitable, maintained, inspected where needed, and used by people who know what they are doing. The HSE and clients do not only ask whether you “did a PUWER” — they ask whether the record proves it.
Weak evidence shows up as: vague findings, photos with no asset link, actions with no owner, and reports that read differently depending on who wrote them up on Sunday night.
What a defensible report usually needs
Exact formats vary by organisation, but strong assessments tend to make these things obvious without a detective story:
- Clear asset identity — what was assessed, where it sits, and enough context that another competent person could find it again.
- Scope of the review — what was covered (and what was not), so the report cannot be stretched beyond the visit.
- Findings tied to duty — not just “guard issue,” but which requirement or risk the finding relates to.
- Evidence of observation — photos, notes, and measurements captured while still with the machine.
- Risk / priority language — enough to decide what must be fixed first.
- Actions with ownership — who does what, by when, and how close-out will be shown.
- Who did the work — competent person, date, and a trail of review or sign-off where your process requires it.
Where traditional methods lose the thread
Most failures are process failures, not competence failures. Engineers know the plant. The process fails because capture and reporting are disconnected.
- Dropdown tax on every hazard
Slow digital forms still burn minutes per item. People skip fields or write free-text that never maps cleanly later.
- Inconsistent regulation mapping
Two surveyors, same defect, different wording and different “home” in the report. QA and clients notice.
- Report rewrite after the visit
Memory fills gaps. Photos live in a camera roll. Action lists are rebuilt in Word. The trail from observation to output snaps.
On-site habits that strengthen the record
Before you leave the asset:
- Confirm identity and location while you can still point at it.
- Capture the finding and the photo in the same breath.
- Name the duty or requirement while the context is fresh.
- Draft the action as if someone else must execute it next week.
- Note uncertainty honestly — “not verified / not accessible” beats fiction.
What “good” looks like when challenged
A strong report lets a reviewer answer, quickly: What was assessed? What was wrong? Why does it matter under PUWER? What happens next? Who owns it? When was it done?
If those answers require three folders, two inboxes, and a phone call to the engineer who has already moved to another site, the evidence is fragile — even if the underlying assessment was sound.
How Ardie approaches this
Ardie is built so capture, regulation mapping, and outputs stay in one flow: less dropdown tax entering hazards, findings mapped consistently, and high-quality reports and action lists produced from the review — as turnkey SaaS or integrated into systems you already run. The point is not a prettier PDF. It is recoverable engineer time and a record that still makes sense under scrutiny.
This article is practical guidance, not legal advice. Always confirm duties against current HSE guidance and your organisation’s competent-person arrangements.