How to Run a 12-Minute Pre-Task Risk Reset

A pre-task risk reset is the short review that tells a supervisor whether today's job still matches today's field, today's control set, and today's decision rights before the crew starts work. It matters because a task that changed after the briefing can keep moving under yesterday's assumptions unless someone interrupts it on purpose.

Across 25+ years of executive EHS work and more than 250 cultural transformation projects supported by Andreza Araujo, the same failure keeps appearing. The team knows the hazard, but the control picture has already moved. In A Ilusao da Conformidade, that is the trap. Paper can look current while the field has moved on.

This guide is for supervisors, area owners, maintenance leads, and EHS managers who need a fast reset that changes the next decision. If the task changed during planning, pair this routine with scope-change risk review. If the work crosses a shift boundary, use permit-to-work handover audit and critical control handover so the reset does not stop at the meeting room.

What you need before starting

Bring the live job brief, the current field condition, the permit or task card if one exists, the isolation list, and one person who can stop the work if the answer is not clear. If the crew cannot explain the task in one plain sentence, the reset is already behind the field.

Use the reset only when the job is real, not when someone wants another talking point. The point is to compare the approved plan with the work as it exists now, then decide whether the crew can continue or whether the job needs a new review. That is why this article sits next to temporary deviation risk review and safety decision trail.

Step 1: Name the job as it exists today

Start with a sentence that describes the job the crew is about to do, not the job that was approved yesterday. Name the location, the equipment, the exposure, the shift, and any change that matters to the control set. If those facts are still fuzzy, the team is working from memory instead of evidence.

James Reason's work on latent conditions helps here because a visible mistake is often only the last link in a longer chain. The reset is valuable when it exposes the hidden change, such as a new access route, a different contractor, a missing guard, or a workface that no longer matches the plan.

Step 2: Compare the approved plan with the field

Put the approved plan on one side and the field condition on the other. Then mark every place where the sequence, the access, the isolation, the tools, or the crew no longer match. The comparison should be simple enough that the supervisor can explain it without reading from a screen.

The useful question is not whether the document looks complete. The useful question is whether the plan and the field still describe the same job. If they do not, the reset is not a formality. It is the point where the job either gets re-controlled or gets paused.

Step 3: Test the control that would fail first

Do not start with the easiest item to check. Start with the control that would fail first if the work keeps going under pressure. In one job that may be isolation. In another it may be ventilation, traffic separation, line-of-fire distance, or rescue readiness. The first weak barrier tells you more than the last one.

Andreza Araujo learned this pattern in programs where results had to move, including the PepsiCo South America case in which the accident ratio fell 50% in six months. The lesson was not that people became perfect. The lesson was that leaders changed what they verified before work continued, and that changed the odds.

Step 4: Ask who can stop the job

A risk reset is weak if nobody can stop the work without asking permission from three other people. Name the person who can pause the task, the person who can change the brief, and the person who can clear a restart. If the answer depends on who is nearby, the control is too fragile.

This step matters because decision rights are part of the barrier set. A crew that keeps moving while everyone waits for approval is not being disciplined. It is being under-controlled. The reset should make authority visible before the job touches energy, motion, height, or pressure.

Step 5: Rebrief the crew in plain language

Explain the delta, not the whole history. Say what changed, why the change matters, what control now carries the most risk, and what the crew must do if the field stops matching the brief. The best brief is the one that the crew can repeat under pressure without losing the point.

As Andreza Araujo argues in Safety Culture: From Theory to Practice, repeated decisions define the real operating model. A reset that the crew cannot repeat is not yet part of that model. It may have been heard, but it has not been absorbed into the way work is actually done.

Step 6: Write the stop condition

Every reset needs a clear trigger that cancels the current approval and forces a new one. Name the event that changes the risk picture enough to stop the task, such as a new leak, a broken isolation, a changed access route, an unexpected atmosphere, or the loss of rescue readiness. If the stop condition is vague, the crew will keep working too long.

Sorte ou Capacidade is useful here because luck is not a control strategy. A team that keeps relying on the last safe outcome eventually runs into the one event the old approval cannot cover. The stop condition is how the supervisor keeps a small change from becoming a serious one.

Step 7: Verify the reset in the field

Walk the workface. Check the control. Ask one worker to explain what changed and what the crew will do if the condition changes again. If the answer is not immediate, the reset is not complete. Verification belongs in the field because that is where the barrier must actually exist.

This is also where critical control handover matters. If the crew can name the hazard but cannot point to the live control, the task is still too dependent on memory. The same logic applies to permit-to-work handover audit, where the file must still match the work face.

Step 8: Close the loop after the shift

Do not treat the reset as finished the moment the crew says yes. Give the job a short exposure window, then check whether the new control held under normal pressure. Night shift, fatigue, interruptions, and production pressure often reveal the weak point that the meeting did not see.

In more than 250 cultural transformation projects, Andreza Araujo has seen that the most durable change comes when leaders review what happened after the reset, not just what was said during it. That is the operating difference between a quick conversation and a real control routine.

• The current job was described in plain language, not in yesterday's terms.
• The approved plan and the field condition were compared side by side.
• The first failing control was tested before work continued.
• The stop authority and restart authority were explicit.
• The crew received a delta brief and could repeat it under pressure.

If your operation needs stronger field discipline, Andreza Araujo's books and diagnostics can help turn this reset into a routine. Start with the book Safety Culture: From Theory to Practice or return to Andreza Araujo for leadership support that keeps the control set alive in the field.