The brittleness of Pre-Task Plans: Why good processes still fail

Pre-Task Plans (PTPs) are widely recognized as an effective tool for preventing incidents at the front line. When done well, they align crews around the work, associated hazards, and establish the controls needed to perform tasks safely. Despite their widespread adoption, PTPs often fail in subtle but predictable ways.

This fragility—or brittleness—does not mean pre-task planning is ineffective. It means the process is highly dependent on experience, judgment, and how the conversation is framed. When those elements are weak or misaligned, PTPs can create a false sense of security rather than meaningful risk reduction. Understanding where PTPs break down is essential to strengthening them.

You don’t know what you don’t know

One of the most common failure points in pre-task planning is experience (or lack thereof). Seasoned supervisors and craft workers often anticipate hazards instinctively. Years of exposure allow them to recognize subtle warning signs, understand how tasks interact, and select effective controls almost automatically.

Less experienced supervisors and crews do not yet have that depth of situational awareness. Todd Hohn, Vice President of EHS&Q at ONE Gas, refers to this as the “juniorocity” problem—situations where newer supervisors are leading newer workers without the benefit of accumulated experience. In these environments, PTPs can appear complete on paper while critical hazards remain unrecognized.

The result is not negligence, but blind spots. Crews cannot plan for hazards they do not know exist. Without access to historical insight, prior ‘lessons learned’, or guidance beyond personal experience, pre-task planning becomes limited to what the group can collectively recall in that moment.

Identifying hazards without connecting the controls

Another common weakness occurs when hazards are identified, but controls are not clearly or explicitly coupled with those hazards.

Many PTPs list hazards in one section and controls in another, without making the relationship between the two unmistakable. This separation can leave room for assumptions: workers may believe control applies broadly, while others may not recognize which hazards it is intended to mitigate.

Effective pre-task planning requires more than hazard recognition. It requires deliberate pairing—this hazard exists; therefore this specific control must be in place. When that linkage is missing, controls may be applied inconsistently or overlooked entirely, especially as work progresses and conditions change.

Planning at the day level instead of the task level

Pre-task plans are most effective when they are built around the task, not simply the day.

In practice, many PTPs are created once per shift and remain static, even though crews may perform multiple, distinct tasks throughout the day. Each task can introduce new hazards, different energy sources, and unique control requirements. A single, generalized PTP often becomes too broad to meaningfully address the real risks associated with each activity.

When PTPs are framed at a high level— “today’s work”—they tend to rely on generic hazards and controls that may not fully apply as the scope of work evolves. This task-level mismatch increases the likelihood that workers proceed under assumptions that no longer reflect the actual conditions they are facing.

When PTPs become a compliance exercise

Perhaps the most damaging source of brittleness is cultural. In some organizations, PTPs are viewed primarily as a compliance requirement rather than a risk management tool.

When pre-task plans are only referenced after an incident—often to determine whether they were completed correctly—they can quickly become associated with blame rather than protection. This punitive perception discourages honest discussion, minimizes hazard identification, and incentivizes crews to complete the form rather than engage in the conversation.

In these environments, the PTP may be technically complete, but functionally hollow. Workers focus on checking boxes instead of thinking critically about how the work could fail.

Planning without a clear “Safe to Start” gGate

Another subtle but critical weakness occurs when hazards and controls are identified yet work begins without verifying that essential controls are in place.

In many cases, the PTP conversation happens as intended. Hazards are discussed. Controls are mentioned. Everyone agrees on what should be done. However, there is often no explicit pause point that confirms conditions are truly safe to begin work. The plan exists, but the transition from planning to execution is informal and assumed.