Why a living system matters
Every serious safety field learned the same thing. Where human behavior decides outcomes, static tools can’t keep people safe on their own. What works is a system that senses, learns, and adapts.
What safety science found
Every high-risk field has faced the same problem: people were hurt even when the rules were followed. The checklist was completed, the protocol was in place, the training was current, and the outcomes still weren’t good enough.
Safety science, the discipline built from decades of studying that problem in medicine, manufacturing, and other high-risk work, found that the answer was a specific kind of system rather than more rules. Risk lives in the moments where someone has to use judgment under uncertainty, and the system either supports them there or it doesn’t. No checklist can anticipate every situation.
Four principles came out of that work, and they apply to sexual abuse safety as they do everywhere else.
Support judgment where uncertainty is greatest. The moments that matter most are the ones no protocol fully covers.
Surface and track concerns. A concern nobody can see is a concern nobody can manage.
Measure the whole system. Whether training happened is a fact; whether the protection system is working is the question.
Sustain attention deliberately. Attention fades. Rhythm is what keeps a system alive between the moments or incidents that test it.
What "living" means
The system is called living because it learns and adapts. Every concern worked through, every control tested, and every review completed feeds back into it. A static tool looks the same on day one thousand as it did on day one. A living system on day one thousand reflects everything the organization has learned since it started, and the team that runs it has learned with it.
What the old tools can't do
The tools most organizations use were built to show that steps are in place. They do that well, and the commitment behind them is real. What they weren’t built to do is tell you whether the steps are working now, for the people in the room today, facing a situation the policy couldn’t foresee. As such, there’s nothing for them to sense, learn from, or adapt to. That isn’t a failure of effort. It’s just what the tools are.
What it looks like in Jigsaw
You build your own controls. You know your environment, where attention fades, and where gaps can form. A control you build is one you understand and keep.
Every control has a test written into it. Before a control goes live, it’s tested against three questions: does it serve our objectives, does it reduce uncertainty, and do people actually use it? A control that passes all three is one you can rely on, and the test stays with the control so it can be run again.
Monitoring and review ask two different questions. A monitoring check asks whether the control is running. A review asks whether it’s still the right control. Both happen on a schedule the team commits to when a control is promoted, and both produce learning.
The rhythm lives in meetings you already hold. The system prompts what needs checking and when, so nothing depends on someone remembering, and nothing stops quietly.
Defensibility is a byproduct
As a living system works, the record writes itself. Every check, review, and concern is dated as it happens. When a board, an insurer, or a court asks what you did, the evidence is ready, created when the system ran rather than assembled afterward. And anyone in the organization can explain why the controls are what they are, because they built them.
The other three foundations
A living system runs on ERM’s architecture, depends on facilitation to keep uncertainty discussable, and connects through the platform to what other organizations learn. Each changes what the others can do.