Each engagement is designed around the decision leaders need to make — assurance, due diligence, regulatory response, tender confidence, system uplift or critical-risk control.
Most safety work starts with the document and asks whether the work complies with it. This starts the other way around: with the work itself, and what it actually demands of the people doing it.
That matters because work is rarely as tidy as the procedure assumes. People adapt — they fill gaps, absorb pressure, and make the system function in conditions it was never quite written for. Those adaptations are usually why things go right. Occasionally they're why things go wrong. Either way, you can't see them from inside the folder.
So the goal isn't a thicker manual or a longer checklist. It's a system that builds capacity — one that helps people make good decisions when work becomes complex, pressured or unfamiliar, and that's honest about the difference between what's written and what's done.
Six moves — adapted to the engagement, never run on autopilot.
Clarify the leadership question first: what needs to be relied on, evidenced, improved or defended?
Identify the work, duty holders, critical risks, accountabilities and operational constraints that shape the engagement.
Examine documents, records and implementation — what the system claims and what it can demonstrate.
Pressure-test critical controls against operational reality, site practice and the decisions people actually make.
Rank findings by material exposure, consequence, effort and dependency — not by paperwork volume.
Convert findings into ownership, cadence and practical improvement so the work does not stop at the report.
It's the single idea underneath all of it. A system can be fully documented, fully audited and fully certified — and still leave the real risk untouched, because the risk lives in the work, not in the binder.
The job is to keep both honest: a system strong enough to rely on, and grounded enough to match what people actually do.
Not a fixed package, not a templated scope. A short call to understand what's prompting the question — and an honest view on whether this is the right way to answer it.