How to Run a Pre-Task Control Review in 8 Decision Checks

F2 practical guide for shift supervisors, maintenance coordinators, and EHS leaders

Non-routine work rarely becomes dangerous because nobody wrote a risk assessment. It becomes dangerous when the approved plan no longer matches the task, the control owner is unclear, or the team starts under production pressure before anyone tests the gap.

A pre-task control review is a short, evidence-based check that confirms the task, exposure, critical controls, responsible people, and restart conditions still match the work about to begin. It is not a second generic risk assessment. It is the final decision point between a document that looks complete and a control arrangement that the crew can actually use.

The guide below is designed for work such as an unplanned repair, a temporary process change, a first-time contractor activity, or a maintenance task whose conditions have shifted since planning. James Reason's work on latent conditions is useful here because the visible hazard is often preceded by weak planning, unclear interfaces, or assumptions that nobody has tested. Andreza Araujo's The Illusion of Compliance makes the complementary point that a completed form is not evidence of a controlled task.

Step 1: Define the work boundary

Start by naming exactly what the team will do, where the work begins and ends, and what is outside the review. A phrase such as “repair the pump” is too broad because it can hide isolation, draining, access, lifting, testing, and restart decisions that involve different exposures.

Write the task as a sequence with a clear start condition and finish condition. Include simultaneous work nearby, contractor interfaces, temporary equipment, and any handover that could transfer risk between groups. If the boundary cannot be stated in plain language, the review is not ready to proceed.

Step 2: Confirm what changed since planning

Ask what is different from the plan that was originally approved. The change may involve the asset, the crew, the weather, the production state, the sequence, the access route, or the time available. A small change matters when it invalidates an assumption that a control depends on.

Use the existing temporary change risk review when the work has become an exception that the operation expects to repeat. The purpose is not to punish deviation. It is to stop an exception from becoming an undocumented operating condition.

Step 3: Map the exposure path

Describe how a person could be harmed if the task goes wrong. Identify the energy, material, movement, pressure, height, chemical, vehicle, or environmental condition involved, then connect it to the people and equipment that could enter the exposure path.

This step prevents the review from becoming a list of hazards without a decision. The team should be able to say what can reach whom, through which route, during which part of the sequence. If the exposure path is uncertain, pause the work and gather the missing information before selecting controls.

Step 4: Test the critical controls

List the controls that must work for the task to remain acceptable, then test their condition rather than merely confirming that they appear in the paperwork. For hazardous energy, that may include isolation, dissipation, verification, and protection from re-energization. For lifting, it may include equipment suitability, ground condition, exclusion, and communication.

Use the control availability model to distinguish a control that is documented from one that is available, usable, and dependable in this task. A permit, training record, or inspection sticker supports the decision, but none of them proves that the barrier will hold under the current conditions.

Step 5: Assign one owner to each control

Every critical control needs a named owner who can confirm its condition, respond when it fails, and communicate the decision to the crew. Avoid assigning ownership to a department alone because “maintenance” or “operations” cannot answer a question at the workface.

The owner does not need to perform every action personally. The owner does need enough authority and competence to verify the barrier, stop the sequence when evidence is missing, and escalate a conflict that cannot be resolved locally. This is where safety leadership becomes operational rather than ceremonial.

Step 6: Check competence and communication

Confirm that the people performing, supervising, isolating, and authorizing the work understand their specific roles. Generic training is not enough when the task depends on a local line-up, an unusual interface, or a recovery action that the crew has not practiced.

Ask one person to explain the sequence and the main failure response in their own words. This simple check reveals whether the team is relying on a document that nobody has translated into action. It also gives the supervisor a chance to correct ambiguity before exposure begins.

Step 7: Set stop and restart conditions

Define what will stop the task and what evidence is required before it can restart. Stop conditions may include a lost isolation, a changed weather condition, an unexpected person entering the exclusion zone, a control that becomes unavailable, or a sequence that no longer matches the approved method.

Restart conditions should be observable. “Everyone is comfortable” is not enough. Specify the verification, authorization, inspection, or communication that must occur, and identify who can release the work. A pause without a restart path creates pressure to continue; a restart without evidence turns the pause into theater.

Step 8: Record the decision and verify the first move

Record the material decisions, unresolved assumptions, control owners, stop conditions, and the person who authorized the start. Keep the record short enough to use at the workface, while preserving the evidence that a later reviewer would need to understand why the task was allowed to proceed.

Then observe the first meaningful step in the field. The review is only credible if the team starts in the way it described. When the first move reveals a mismatch, correct the plan before the mismatch becomes normal. Andreza Araujo's safety-culture work repeatedly returns to this principle: culture is visible in the choices leaders make when the written plan meets operational pressure.

How to know the review worked

A useful review produces a controlled start, not a longer form. The supervisor should be able to point to the exposure path, show the critical controls, name the owners, explain the stop conditions, and demonstrate that the first move followed the agreed sequence.

Review the process after a material change, a near miss, a control failure, or a serious delay that increased pressure on the crew. Track whether reviews identify real changes, whether unresolved items are escalated, and whether restart decisions are supported by evidence. Do not judge the process by the number of forms completed because a high completion rate can coexist with weak field verification.

For a broader task-start method, compare this guide with the four decision questions in a job safety analysis. The two tools serve different moments. The job safety analysis structures the work, while the pre-task control review confirms that the structure still fits the conditions that exist now.

FAQ

When should a pre-task control review be required?

Require it when work is non-routine, conditions have changed, several groups share the exposure, a temporary control is being used, or the consequence of a failed barrier is high. The trigger should be tied to decision risk rather than the job title of the person performing the task.

Is this the same as a job safety analysis?

No. A job safety analysis usually structures the task and identifies hazards before work begins. A pre-task control review checks whether the planned controls, owners, and restart conditions still match the actual work at the point of execution.

Who should lead the review?

The person responsible for the work should lead it with the control owners and the people who will perform the task. EHS can facilitate or challenge the decision, but the operational owner must retain responsibility for the start and the stop.

What if the team cannot verify one critical control?

Do not authorize the exposure while treating the missing verification as an administrative action. Contain the task, identify the evidence needed, assign an owner, and escalate when the control cannot be restored within the local decision authority.

How long should the review take?

The duration should match the complexity and consequence of the work. A simple review may take a few minutes, while a complex maintenance interface may require a longer field discussion. Speed is useful only when it preserves the decisions that keep the exposure controlled.

A pre-task control review earns its place when it changes the decision to start, pause, modify, or restart work. If it only confirms that paperwork exists, it has not added a barrier. For more on turning safety systems into dependable operating choices, explore Andreza Araujo's books and methods at the Andreza Araujo store.