Home › The approach
Systems fail. People cope.
Health and safety became a documentation discipline. The programme got longer, the forms multiplied, the audit scores improved — and the work on site carried on much as it had.
The gap between the system on paper and the job as actually performed does not disappear. Somebody absorbs it quietly, and that somebody is almost always a supervisor or a crew. Human and Organizational Performance is the body of practice that takes that gap seriously instead of treating it as non-compliance.
Purlin sits downstream of it. That isn't a philosophy bolted on at the end of an engagement — it decides what we write, what we delete, and how we handle an incident when one happens.
The four principles
What this commits us to.
Not the problem. The people doing the job know where the system stops matching reality, because they are the ones absorbing the gap every day.
People will make mistakes on every project you ever run. A system that only works when nobody errs is not a system — it's a hope.
Change the conditions and the behaviour follows. Change the poster on the wall and nothing does.
Finding the person who broke the rule ends the investigation exactly one step before it becomes useful.
Why this gets hired out
HOP programmes assume an internal team and years of runway, which describes almost none of the companies actually running crews. A full-time practitioner doesn't pencil at your headcount — which is exactly why the approach has stayed theoretical for most of the industry. We do the translation work, then hand it over and leave.
How this reads in practice
The difference is visible in a single paragraph.
Two write-ups of the same event. Only one of them tells you what to change on Monday.
Writing up an incident
The investigation determined the incident was caused by employee failure to follow established procedure.
The procedure assumed conditions that weren't there that morning. We looked at why the shortcut made sense at the time, and fixed the conditions that made it the reasonable choice.
How an engagement runs
Four stages, and what you have at the end of each.
- 01
Go and look
On site, watching the work, talking to supervisors and crews rather than only the safety lead. The gap between the written procedure and the performed job is only visible in the field.
- 02
Take the system apart
Every document, form and procedure on the table. What's required, what's redundant, what contradicts something else, and what's missing. You get the findings straight, including the parts that are working.
- 03
Rewrite and rehouse
Plain language at the reading level of the person doing the task. Forms built for a gloved hand and a truck dash. One source of truth, a named owner for every part of it, and the whole thing living in Wombat rather than a shared drive.
- 04
Build the capability, then leave
We train supervision to run it, watch them run it, and fix what doesn't hold. Then we go. If you need us back it should be because you grew, not because the system fell over.
The part most firms don't mention
There's usually a stretch around month two where this annoys people. Supervisors are being asked to change how they document work while still delivering production, and the new system isn't paying them back for the effort yet. It passes — but you should hear it now rather than after signing.
Want to see what this looks like on your sites?
The first conversation costs nothing and you'll get a straight read on whether there's work worth doing here.