Control Readiness Explained: 4 Checks Before Critical Work

A control can exist in a procedure and still be unavailable when the job begins. Control readiness is the discipline of proving that the selected barrier is designed for the hazard, present at the point of work, understood by the people who rely on it, and able to respond when conditions change.

That distinction matters because ISO 45001, published in 2018, asks organizations to control risks through planned processes, while real work is exposed to changing equipment, weather, staffing, and production pressure. A signed document is evidence of intention. Readiness is evidence that the protection can perform.

Control readiness is the verified state in which a safety control is suitable for the identified hazard, physically available, understood by its users, and supported by an owner who can correct or stop the work when the control is missing or degraded.

Definition

Readiness sits between selecting a control and accepting residual risk. It asks whether the control is capable of doing its job today, under the conditions that actually surround the task. A guard that was specified but not installed is not ready. A permit that is complete but does not reflect the energy isolation is not ready. A rescue plan that names a phone number but has no trained response team is not ready.

James Reason's work on latent failures helps explain why this check is necessary. A visible operator action may be the last point in a chain whose earlier weaknesses include design, maintenance, supervision, and communication. A readiness review tests those earlier layers before they become an incident pathway, which is why it should be treated as a decision process rather than a paperwork inspection.

4 checks that show readiness

1. Confirm the control matches the hazard

Start with the credible exposure, not the control already listed in the form. If the task involves stored energy, the review must address isolation, dissipation, verification, and re-energization. If the task involves a temporary chemical-transfer connection, the team must examine compatibility, containment, pressure, routing, and emergency response. A control is not ready when it solves a different problem than the one the crew faces.

This check also clarifies the decision owner, whose role is to reject a weak control rather than approve it because the document is complete. The related distinction between hazard review, task observation, and control verification is covered in this evidence guide.

2. Verify presence at the point of work

Walk to the task and look for the control where it must operate. Confirm the barrier, device, isolation, boundary, or communication method, and test whether access, visibility, and condition support its use. A control that is locked in a cabinet, blocked by materials, or too difficult to reach is technically present but operationally weak.

Andreza Araujo's book Safety Culture: From Theory to Practice treats the gap between declared standards and everyday practice as a cultural signal. The same logic applies here. The field condition is the stronger evidence because it reveals what the organization is actually prepared to protect.

3. Test understanding and response

Ask the people doing the work to explain what the control prevents, what failure looks like, and what they will do if it is missing. The answers should be specific enough to guide the next decision, although they do not need to repeat the procedure word for word. If the supervisor, contractor, and operator describe different limits, the control is not ready.

For high-consequence work, include a short response test. Confirm who can stop the job, who owns escalation, and which condition requires a new review. Andreza's documented experience includes a 50% accident reduction at PepsiCo in six months, a result that reinforces why leadership behavior and field execution must be examined together rather than separated into training and compliance activities.

4. Define the recovery when the control degrades

Readiness includes failure. State what happens when a guard is damaged, a gas monitor alarms, a weather limit is exceeded, or the isolation cannot be verified. The team needs a clear temporary boundary, a named decision owner, and a restart condition, because an unplanned workaround can become the new normal when no recovery path exists.

Leaders who want to examine this issue further can compare readiness with the five proof levels in Control Acceptance Explained and with the warning signs described in Verification Debt.

How to differentiate readiness from related terms

The terms are connected, but they are not interchangeable. Readiness comes before acceptance, and verification supplies the evidence that makes acceptance defensible. When teams collapse all four questions into one signature, decision quality becomes difficult to trace, which is why a short field review can prevent a long investigation later.

When should a readiness review happen?

Use it before critical work starts, after a material change, when a control has failed or been bypassed, and whenever the team cannot explain the recovery path. The review is especially useful for non-routine maintenance, temporary arrangements, contractor interfaces, simultaneous operations, and tasks whose conditions can change during the shift.

In more than 250 cultural transformation projects, Andreza Araujo has built her authority around making safety decisions visible in the operation. The practical test is simple. If the team cannot show the control, explain its limits, and name the next action when it fails, the work is not ready to proceed.

Use the four checks before the next critical task, and turn a control from a written promise into a verified condition.