Pre-task planning is the short, on-the-spot safety briefing a crew runs right before non-routine work: they pause at the job, name the hazards and controls for the task in front of them, confirm who does what, and only then start. It also goes by pre-job brief, job safety briefing, tailboard talk, Take 5, or Take 2. It is planning at the point of work, not at a desk.

Pre-task planning fills the gap between the formal safety paperwork and the moment a wrench actually turns. A written procedure describes the job in general; the pre-task plan checks whether today's version of the job, with this crew, this equipment, and these conditions, still matches. Most serious incidents happen on non-routine work, at the exact moment when conditions changed and nobody stopped to notice. This post covers how to run one, how it differs from a formal analysis, and how to make it a fast habit instead of another form. It is educational, not legal advice.

What is the difference between pre-task planning and a JSA?

They operate at different scales and different moments. A job safety analysis (JSA) is a formal, written document developed once for a recurring job, reviewed and approved, and reused; it is the reference. Pre-task planning happens at the job site, minutes before the work, and checks the reference against today's reality. Think of the JSA as the map and the pre-task plan as the driver looking up from the map to see that the bridge is out.

Job safety analysis versus point-of-work pre-task planningTwo tools, two momentsJOB SAFETY ANALYSISPRE-TASK PLANWHENonce, before the job existsWHENminutes before this taskWHOsafety lead + operatorWHOthe crew doing the workFORMformal, approved, reusedFORMshort card, one-timeCAPTURESthe job as designedCAPTURESthe job as it is todayThe pre-task plan catches what changed since the JSA was written
A JSA describes the job as designed; a pre-task plan checks it against the job as it stands today, with this crew and these conditions.

The two are not rivals. The best pre-task plans start from the JSA or written procedure and spend their thirty seconds on the delta: what is different today. Is the weather different? Is a guard removed? Is someone new on the crew? Is a second job happening overhead? A pre-task plan that just re-reads the JSA wastes the crew's time; one that hunts for the change earns its keep.

There is a scope difference too. A JSA covers a whole recurring job in general terms, so it has to be a little abstract to stay reusable. A pre-task plan is concrete: this pump, this shift, this crew, this weather, this adjacent job. Because it is concrete, it can catch the specific combination the general document never anticipated, the crane lift happening at the same time as the line-break, the trench that filled with water overnight, the lockout that a different crew already applied. Those combinations are where people get hurt, and they are invisible to a document written weeks ago. The pre-task plan is the only tool that looks at them.

Is pre-task planning required by OSHA?

There is no single OSHA standard called "pre-task planning," but the idea is baked into the law and required outright in some standards. OSHA's general duty clause requires employers to keep the workplace free of recognized serious hazards, and you cannot control a hazard nobody paused to recognize. Specific standards go further: the electric power generation, transmission, and distribution standard requires a job briefing before each job, covering hazards, procedures, special precautions, energy-source controls, and PPE. Confined space entry and lockout/tagout both build a point-of-work planning step into their procedures. So even where "pre-task plan" is not the exact phrase, the pause-and-plan behavior is often mandatory, and it is always good practice.

How do you run a pre-task plan? The steps

Keep it short and keep it at the job. A pre-task plan that takes twenty minutes will get skipped; one that takes two minutes and actually finds the day's hazard will get used. Here is the sequence.

  1. Stop at the job, with the whole crew. Not at the morning meeting, not in the break room. At the location, looking at the actual equipment, with everyone who will touch the task present.
  2. State the task and the scope. One or two sentences: what are we doing, and where does it start and stop. Vague scope is where extra, unplanned work sneaks in.
  3. Name the hazards you can see and the ones you cannot. Walk the task in your head, step by step, and call out the mechanisms of injury: stored energy, overhead loads, traffic, chemicals, heat, dropped objects, pinch points. Look up, look down, look for the change since last time.
  4. Assign a control to each hazard and confirm roles. Who isolates the energy, who spots, who holds the permit, who stops the job if something changes. Every hazard gets a named control and every control gets a named person.
  5. Confirm the stop-work trigger and go. Agree out loud on what would make you stop, and confirm everyone has the authority to call it. Then start the work, and re-run the plan if conditions change mid-task.

The whole thing lives on a small card or a tablet field, not a three-page form. The goal is a habit, not a document.

What goes on a pre-task planning card?

A pre-task card is deliberately small. It has room for the task and scope, the hazards, the control for each, the crew and their roles, the required permits and PPE, and the stop-work trigger. That is enough. If the card grows to a full page, it stops being a point-of-work tool and becomes paperwork, and paperwork gets filled out in the truck instead of at the job.

Layout of a compact pre-task planning cardA pre-task card fits on one small pageTASK & SCOPE: what we are doing, where it starts and stopsHAZARDS (look up / down / around)CONTROL FOR EACH HAZARD1. ______________________2. ______________________3. ______________________1. ______________________2. ______________________3. ______________________CREW & ROLESPERMITS / PPE REQUIREDSTOP-WORK TRIGGER: if this happens, we stop and re-planSmall enough to fill out at the job, not back in the truck
A compact pre-task card: task and scope, hazards paired with controls, crew and roles, permits and PPE, and an explicit stop-work trigger.

What are the common mistakes that kill a pre-task plan?

The failures are predictable. The plan gets filled out in the break room instead of at the job, so nobody sees the condition that actually changed. It gets done by one person and read to the crew, so the crew never engages and treats it as the supervisor's homework. It grows into a long form, so people fill it in from memory to save time. The hazards are written vaguely, "be careful of the equipment", so no real control follows. Or the stop-work trigger is theoretical, because the last person who stopped a job got chewed out, so nobody will stop this one either. Each of these turns the pause into theater. The fix for all of them is the same: keep it at the job, keep it short, keep it owned by the crew, and make stopping the work a normal, respected act rather than a career risk.

How do you make it a habit instead of a chore?

Three things separate a living pre-task program from a box-ticking one. First, the crew fills it out, not a supervisor at a desk; the people doing the work own the plan. Second, it stays short, so the cost of doing it honestly is low. Third, the stop-work authority is real: if a worker calls a stop because the plan no longer matches reality, the response is thanks, not friction. Feed the day's findings back into the system. A hazard that keeps showing up on pre-task cards is a candidate for a toolbox talk or a permanent engineering fix, and any close call caught during the pause belongs in your near-miss reporting so the next crew benefits.

What do the numbers say?

The case for pausing before non-routine work, from primary sources:

The pattern behind most of those fatals is not ignorance of the hazard in general; it is a crew that started work before anyone checked whether today's conditions had changed. That check is the entire job of the pre-task plan.

The practical weakness of paper pre-task cards is that they vanish the moment they are filled out: the recurring hazard on card after card never gets counted, because the cards live in a truck and a bin. Harmony is an AI-native layer that connects machines, software, and paperwork into one operational layer, with no rip-and-replace. Pre-task cards captured on a tablet become structured, searchable data, and AI search returns cited answers across them, so "what hazards keep coming up on this line's pre-task plans" becomes a question you can answer instead of a stack you cannot read. It is the everyday shape of connected worker technology and it is not a safety-compliance product. Harmony's digital workflows move those cards and handoffs into that structure; the CLS case study shows the pattern. Where the work is high-hazard and formalized, the same pause feeds bigger programs like process safety management where a documented pre-startup check is the law.