Pre-Task Risk Assessment: 7 Supervisor Checks

Most serious field events do not begin with an absent form, because they begin with a form that was signed while the real task had already changed. This guide shows supervisors how to audit a Pre-Task Risk Assessment before the first tool moves, after a pre-mortem safety review has tested planning assumptions, with checks that expose weak controls and line of fire body-positioning gaps rather than decorate compliance.

If the same weak assessment appears across crews, the corrective action may need work redesign or supervisor coaching because training alone will not repair the routine.

Why a Pre-Task Risk Assessment fails when it becomes a signature

A Pre-Task Risk Assessment, often called PTRA, should translate the actual job into current hazards, credible consequences, and verified controls. It fails when the crew treats it as a permission slip, because a signature does not prove that energy sources, weather, simultaneous operations, access, tools, and rescue arrangements were understood. When contractors are involved, procurement safety clauses often decide whether those basics were funded before mobilization.

When the task reveals a deeper technical uncertainty, the supervisor should escalate beyond the PTRA and ask whether HAZOP, FMEA or Bow-Tie is the better method for the decision.

The weak point is rarely the template itself. Across 25+ years leading EHS at multinationals, Andreza Araujo has observed that field risk rises when supervisors audit completion but not quality, which means the paper looks clean while the task remains exposed.

For a supervisor, the practical question is not whether the PTRA exists. The useful question is whether the document would still make sense if the job stopped for two hours, the crew changed, or a contractor started another activity nearby.

1. Confirm the task is described as work, not as a department

A useful PTRA starts with a task description narrow enough to expose the work sequence. "Maintenance" or "line intervention" is too broad, while "remove jammed material from conveyor discharge after isolation" gives the supervisor something to challenge.

What many checklists hide is the difference between activity and exposure. As Andreza Araujo argues in Safety Culture: From Theory to Practice, culture becomes visible in the gap between what the organization says and what people do under pressure, and the first line of that gap appears in how the task is named.

The supervisor should ask the crew to state the first three physical actions, in order. If the answer does not match the PTRA, the document belongs back on the toolbox, because the assessment is describing a generic job rather than the job that will happen.

A strong PTRA should also define when the crew must use stop-work authority. If changed field conditions are identified but no one knows which trigger requires pause, the assessment becomes a document rather than a working control.

2. Separate routine hazards from task-changing conditions

A Pre-Task Risk Assessment should capture what changed today, because stable hazards already belong in the JSA, procedure, training, and engineering design. Wet ground, a missing scaffold tag, a substitute technician, nearby hot work, or a late production request can change the risk profile even when the planned task is familiar.

This is where many PTRA systems become theater. They repeat the same boxes every morning, although the real decision is whether today's conditions have invalidated yesterday's controls.

The supervisor should ask one field question: "What is different from the last time we did this job?" If the crew cannot name one difference, the supervisor should verify the site personally, because familiarity often hides the drift that a form will not catch.

3. Test whether high-energy hazards have named controls

High-energy hazards deserve named controls, not broad promises. A PTRA that lists "mechanical energy" but does not name isolation points, stored energy release, verification method, and restart authority is not controlling the hazard.

This check connects directly with LOTO verification before restart, because the paper assessment is only credible when the crew can prove that energy has been isolated and verified at the point of work. In serious events, the missing control is often earlier than PPE, buried in isolation, permit flow, supervision, or design.

The supervisor should mark any high-energy hazard with a specific barrier owner. If no person owns the control, the control is a hope. In field work, hope is not a barrier.

4. Require a control stronger than PPE for credible SIF exposure

PPE is not enough when the credible consequence is a SIF, a Serious Injury or Fatality. If a PTRA identifies fall exposure, line-of-fire exposure, confined space entry, lifting, energized work, or mobile equipment interaction, the supervisor should expect elimination, substitution, engineering control, isolation, or procedural control before relying on PPE.

During the PepsiCo South America tenure, where the accident ratio fell 50% in six months, Andreza Araujo learned that visible improvement came from changing how leaders controlled work, not from asking teams to sign more documents. That lesson matters because PTRA quality depends on the hierarchy of controls being real at the work face.

For work at height, this means the PTRA should connect with the working-at-height rescue plan, anchor points, fall clearance, rescue timing, and equipment inspection. A harness without rescue capability is an incomplete control, because suspension trauma can turn a fall arrest into a second emergency.

5. Look for simultaneous operations before approving the job

Simultaneous operations create risk that the original crew may not see, because the hazard comes from another team, contractor, vehicle route, crane lift, cleaning activity, or production change. A good PTRA names those interfaces and states who has coordination authority.

In more than 250 cultural-transformation projects supported by Andreza Araujo's team, one recurring weakness is the assumption that every crew sees the same job boundary. They do not, especially when contractors and production teams share the same space under schedule pressure.

The supervisor should walk the boundary before approval. The fastest test is to ask, "Who can hurt this crew even if this crew follows its own plan?" A credible answer moves the assessment from individual caution to operational coordination.

6. Verify that the residual risk is accepted at the right level

Residual risk after controls must be accepted by someone whose authority matches the consequence. A supervisor can approve ordinary field variation, but credible fatality exposure, failed critical control, or major deviation from procedure should move to the plant manager, EHS manager, permit issuer, or another defined authority.

The common failure is hiding escalation inside a risk matrix. A color change from red to yellow means little if the listed controls are not verified, because the matrix is only a decision aid and not proof that risk is tolerable.

The supervisor should write one sentence on the PTRA stating why the remaining risk is acceptable. If that sentence sounds political, vague, or dependent on luck, the job is not ready.

7. Turn PTRA quality into a leading indicator

PTRA quality can become a leading indicator when supervisors score evidence, not paperwork volume. Counting completed forms only proves activity, while scoring task specificity, changed conditions, critical-control verification, and escalation quality reveals whether the organization is learning before harm occurs.

This is the same logic behind leading indicators that TRIR will never show. A low incident rate can coexist with weak controls, underreporting, and quiet drift, which is why serious-risk exposure needs its own measurement.

The supervisor can use a simple five-point weekly audit: task specificity, change recognition, named critical controls, correct escalation, and crew participation. When those scores fall, the response should be coaching and redesign, not another campaign telling people to be careful.

Comparison: paper PTRA vs field-ready PTRA

The difference between paper compliance and field readiness appears in the evidence a supervisor can observe before work starts.

How to connect PTRA with incident investigation

A PTRA should become evidence during incident investigation, because it shows what the organization believed before the task started. When the document names generic hazards and the incident involves a specific unverified control, the gap helps investigators find latent weaknesses in planning, supervision, permit flow, or procedure design.

James Reason's work on latent failures helps explain why this matters. The question is not whether the operator signed the assessment, but which organizational conditions made a weak assessment look acceptable.

That is why RCA should avoid the operator-error trap. If the PTRA was poor and everyone accepted it as normal, the finding belongs to the system of work, not only to the person who held the pen.

Each week without a PTRA quality audit leaves supervisors approving work from paperwork confidence, while the real exposure accumulates in changed conditions, weak escalation, and unverified critical controls.

Conclusion: the supervisor is the quality gate

A Pre-Task Risk Assessment protects people only when the supervisor treats it as a field decision, not as a document to collect. The best test is whether the crew can explain the work, the changed condition, the high-energy hazard, the named control, and the escalation rule without reading from the form.

For practitioners ready to build that discipline into daily operations, Safety Culture Diagnosis and ACS Global Ventures consulting can help connect culture, leadership, and risk management. Start with a diagnostic at Andreza Araujo and make the PTRA a control that helps people come home.