In the first article in this series, we looked at who should help develop a Job Hazard Analysis.
The people closest to the work often hold information that never appears in a procedure, drawing, or schedule. Bringing that knowledge into JHA development makes the analysis stronger.
But development is only the first step.
Eventually, the JHA reaches the crew that is about to perform the work. At that point, many organizations shift from planning to communication. The foreman explains the document, answers questions, and collects signatures.
The crew has received the plan.
The more important question is whether they have had a chance to test it.
What if the crew were expected to find what the JHA got wrong before anyone signed it?
That changes the conversation from presentation to validation.
A Completed JHA Can Still Need Correction
A foreman may arrive at the pre-task meeting with a JHA that has already received considerable attention. The sequence has been developed, hazards and controls have been identified, and the appropriate people may have reviewed the document.
That work matters.
It also represents the best understanding of the task available up to that point.
The crew now brings another source of information: direct knowledge of the work they are about to perform in the area where they are about to perform it.
That final comparison matters because a well-developed plan can still contain an incorrect assumption. Equipment may need to be positioned differently than expected. The proposed sequence may create an access problem. A control that appeared practical during planning may be awkward once the crew looks at the actual setup.
Finding one of those issues during the pre-task discussion does not diminish the planning that came before it.
It improves the plan before someone depends on it.
Review and Validation Are Different
We frequently say that workers should review the JHA before beginning work.
A review may confirm that the crew has seen the document, understands the planned sequence, and has heard the hazards and controls discussed.
Validation goes further.
Review asks whether the crew received the plan. Validation asks whether the plan survives contact with the crew’s knowledge of the work.
The crew is being asked to compare what is written with what they expect to encounter.
Perhaps the proposed lift location interferes with access. Maybe a connection shown late in the sequence will become difficult to reach if another step happens first. Material staging that looked reasonable during planning may create a problem once the crew considers how people and equipment will move through the area.
These are the kinds of details a JHA can miss even when the people who developed it did good work.
Validation provides another chance to find them before exposure occurs.
“Do You Understand?” Is Only Part of the Conversation
There is nothing wrong with asking workers whether they understand the JHA.
Understanding matters.
The limitation is that the question focuses on whether information moved successfully from the person presenting the plan to the people receiving it.
A different question requires more from the crew:
What did we miss?
Now workers have to evaluate the plan rather than simply confirm that they heard it.
A foreman might ask whether the sequence reflects how the crew expects to perform the task, where the proposed method is likely to become difficult, and whether any control looks workable on paper but questionable in the field.
That is enough to start a different kind of discussion.
A worker may say, “We won’t be able to set up there.”
Another may point out that the planned sequence creates a problem later in the task.
The most useful response from the foreman may simply be:
“Show me.”
At that point, nobody is defending the document. They are examining the work.
Field Input Has to Be Able to Affect the Plan
Workers quickly learn whether a request for input is genuine.
If the JHA is already considered finished, asking the crew for comments has limited value. They may speak, but everyone in the meeting understands that the real decisions have already been made.
Validation requires room for legitimate field knowledge to influence what happens next.
That does not give every suggestion equal weight or turn the pre-task meeting into a vote. A proposed change may conflict with a regulatory requirement, manufacturer instruction, engineering decision, or established control. Some issues require a competent person, qualified person, safety professional, engineer, or another technical resource.
The value lies in taking the concern seriously enough to examine it.
If the crew identifies a real gap, the appropriate people can resolve it and revise the JHA where necessary.
That response teaches workers something important about participation. Their knowledge is useful because it can improve the work, not simply because management wants them to speak during a meeting.
The Signature Comes After the Conversation
The signature has a legitimate place in the process.
Its value depends heavily on what happened before the pen reached the paper.
A signed JHA can document that a discussion occurred. The quality of that discussion determines whether the signature represents meaningful participation or little more than acknowledgment that the document was presented.
The better sequence is to discuss the proposed work, give the crew an opportunity to identify concerns, resolve legitimate issues, and make needed corrections before documenting participation.
In practical terms, the signature should represent something closer to this understanding:
We discussed how this work is intended to be performed, had an opportunity to raise concerns, and are starting with a plan that reflects the work as we currently understand it.
That gives the signature context.
The important work happened in the conversation that produced it.
Validation Also Develops Judgment
There is a workforce-development benefit here as well.
When workers are asked to evaluate a JHA, they have to use hazard-recognition and planning skills rather than wait for someone else to provide the answer.
A newer employee gets to hear why an experienced worker is concerned about a particular step. The foreman can explain how a sequencing decision affects exposure. Safety can introduce a technical consideration that the crew had not recognized.
People learn how others think about risk while working through a real task.
Over time, those discussions can build a crew that is more comfortable examining plans rather than simply following them.
The difference between “Do you understand?” and “What did we miss?” may seem small.
From a workforce-development standpoint, it is significant.
One asks the worker to receive information.
The other asks the worker to use judgment.
Validation Is the Middle of the Process
The JHA series follows a simple framework:
Develop. Validate. Adapt.
Development brings the right knowledge into the initial analysis.
Validation puts that proposed plan in front of the people who will perform the work and gives them an opportunity to test its assumptions before execution.
Then the work begins.
That last point matters because even a thoroughly developed and validated JHA reflects conditions at a particular moment. Construction keeps moving after the signatures are collected.
For now, the objective is simpler: begin with a plan the crew recognizes as accurate, workable, and appropriately controlled.
The JHA should reach the workforce as something worth examining, not merely something waiting for signatures.
Ask the crew to test the plan.
Listen when the field sees something the document missed.
Make the necessary correction while there is still time to make it before exposure occurs.
Then document the conversation and begin the work.
Because once the work starts, another question takes over:
What happens when the plan was right this morning, but the job is different this afternoon?
That is where adaptation begins.
Develop. Validate. Adapt.
