How to Run a Task Authorization Conversation Before High-Risk Work in 8 Checks

A crew can sign a job briefing, repeat the hazard list, and still be unprepared to start. The question is not whether everyone heard the plan. The question is whether the team can explain how the work will remain controlled when the field does not match the paperwork.

A task authorization conversation creates that decision point. It is a short, deliberate exchange before high-risk work in which the supervisor tests scope, competence, control ownership, changing conditions, and stop-work authority. The aim is not to make the meeting longer. The aim is to prevent a signature from being mistaken for readiness.

Across more than 25 years of EHS leadership, Andreza Araujo has worked across multinational operations where the quality of a safety conversation depended on what leaders did with the answer. Her practical leadership model treats care as an operating discipline, which means the conversation must change the release decision when the evidence is weak.

What you need before starting

Bring the current work scope, the applicable risk assessment, the permit or isolation record when one is required, and the names of the people who own the critical controls. The supervisor also needs enough time to pause the release if the team cannot demonstrate readiness.

Use the conversation for work such as line breaking, energized activity, confined-space entry, lifting, work at height, hot work, or a temporary deviation that changes the normal risk profile. OSHA 1910.147 provides a useful anchor for energy-control verification, although the same decision logic applies to other high-risk tasks.

Step 1: Name the exact task and release boundary

State what the team is authorized to do, where the work begins, where it ends, and what is outside the release. Ask the work leader to repeat the scope without reading it from the form.

This check prevents scope drift, which occurs when a team starts with one job and gradually absorbs adjacent work because the equipment is already open or the crew is already in position. If the boundary cannot be stated clearly, the task is not ready for release.

Step 2: Confirm who is competent for each critical activity

Match each critical activity to the person who is qualified and authorized to perform it. Do not accept a general statement that the crew is experienced, because experience with routine work does not prove competence for an unusual configuration or a changed energy state.

Ask the person performing the activity to describe the first critical decision and the condition that would require a pause. A task authorization conversation becomes useful when competence is demonstrated through explanation, not inferred from a badge, job title, or attendance record.

Step 3: Ask the team to describe the failure that matters most

Invite the team to identify the credible high-consequence failure in plain language. The answer should describe what could happen, where exposure would occur, and which part of the job could allow the event to develop.

James Reason's work on latent failures supports this discipline because serious events rarely depend on one isolated action. The question directs attention toward the conditions and barriers that make the event possible, rather than turning the conversation into a search for a careless person.

Step 4: Verify the critical controls where the work will occur

Walk through each critical control and ask how the team knows it is present and functioning. A control is not verified because it appears on a risk assessment. It is verified when someone can point to its physical or procedural evidence.

For an isolation, that evidence may include the approved isolation record and the test of zero energy. For work at height, it may include the access system, anchorage, rescue arrangement, and exclusion zone. If the control depends on another team, name that dependency before the task is released.

Step 5: Assign an owner to every control

Ask who will install, check, maintain, and remove each critical control. The same person does not need to perform every action, but the ownership chain must be visible to the supervisor and the work team.

Ownership prevents the common trap in which everyone believes someone else checked the condition. Andreza Araujo's book Make The Difference: Be a Leader in Health & Safety emphasizes operational leadership, and this check converts that principle into a specific release decision.

Step 6: Test what has changed since the plan was written

Ask what is different today. Look for weather, simultaneous operations, staffing changes, equipment condition, access restrictions, contractor interfaces, production pressure, or a change in the sequence.

When the answer is nothing, do not close the question immediately. Ask which observation supports that conclusion. A credible authorization accounts for the present worksite, because a correct plan can become unsafe when the conditions around it move.

Step 7: Rehearse the stop and escalation route

Ask each role what would make the person stop, who must be informed, and who has authority to restart the work. Use a realistic trigger such as a missing barrier, an unexpected energy source, a loss of communication, or a change in the work boundary.

The route must work without permission from the person creating the pressure. If a worker can stop the task but cannot reach a decision-maker, the organization has announced authority without creating a usable system.

Step 8: Make and record the release decision

End with one of three decisions: release the task, release it with a named condition and owner, or do not release it. Avoid vague language such as proceed carefully, because it hides the difference between acceptance and unresolved exposure.

Record the task, the people involved, the controls checked, the conditions attached to the release, and the next verification point. The record should help the next supervisor understand what was decided and why, which is especially important when work continues across shifts.

Final checklist for supervisors

• The task scope and release boundary are stated in the team's own words.
• Each critical activity has a competent and authorized person.
• The team can describe the failure that matters most.
• Critical controls are verified with evidence at the worksite.
• Every control has a named owner and a verification method.
• Changes in conditions and simultaneous operations are discussed.
• The stop and escalation route is practical and understood.
• The release decision, conditions, owners, and next check are recorded.

Frequently asked questions

What is a task authorization conversation?

It is a short, structured discussion before high-risk work in which the supervisor and work team confirm the scope, competence, hazards, critical controls, changing conditions, and authority to stop or escalate the task.

How is it different from a toolbox talk?

A toolbox talk usually transfers information to a group. A task authorization conversation tests whether a specific job can proceed under the conditions that exist now and identifies what must change before work starts.

Who should lead the conversation?

The person accountable for releasing the task should lead it, usually the supervisor or area owner, while the people performing the work explain the sequence, controls, and uncertainties in their own words.

What should happen when a worker cannot explain a critical control?

Pause the authorization, clarify the control, confirm competence, and involve the responsible technical or operational owner before the task proceeds. Do not treat silence as agreement.

Should the conversation be documented?

Document the task, the people involved, the critical controls, unresolved conditions, agreed owners, and the release decision. Record only information that supports safe execution and follow-up.

A task authorization conversation earns its place in the workday when it can change the release decision. For more practical guidance on safety leadership, safe behavior, and cultural transformation, explore Andreza Araujo's books and resources.