Job Safety Analysis That Crews Actually Use

Every morning on a rig, a crew gathers and someone reads a job safety analysis. The JSA breaks the job into steps, names the hazard in each step, and states the control. It is the most common safety document in the oil field, and the least respected, because most JSAs are signed at the tailgate and lost by nightfall.

The paper JSA problem

A JSA written on a generic form, signed by a crew that changes every tour, and filed in a folder nobody opens is not a safety document. It is a liability with a signature on it. When an incident happens, the investigator pulls the JSA and finds a template that describes a different day, a different crew, and a different job.

The crews know this. That is why the tailgate reading is a mumble. A document that cannot answer the question "what is different about today" is not worth reading out loud.

What makes a JSA usable

• Written in the words the crew uses, not the safety manual's words.
• Specific to the location and the day: the well, the weather, the crew, the equipment.
• Updated when conditions change, not just when the sun comes up.
• Tied to the work order or the permit, so the right JSA reaches the right job.
• Referenced during the work, not only at the start.

The test of a good JSA is simple: can a crew member who missed the tailgate pick it up and know the hazards? If the answer is no, the document is decoration.

What always gets missed

The hazards that get skipped are the ones that became routine. Making a connection, rigging up, walking the pipe rack: these steps happen a hundred times, and the crew has done them a hundred times, which is exactly when the JSA goes blank. The H2S article on this site covers the same trap for gas detection drills, and the site access article covers it for visitors. Routine is where the risk hides.

New crew members and simultaneous operations get missed the same way. A green hand on the tongs, a frac spread working next to the rig: the JSA written last week did not know about either one.

The record after the incident

When something does happen, the JSA is the first document the investigator asks for. A dated version that matches the day, with the crew named and the hazards specific, answers questions. A blank template starts them. The difference is not effort in the moment. It is whether the document was built to be used or to be filed.

Write it as a crew, not as a safety department

The JSA that works is the one the crew writes for itself. The safety department's template has the right boxes, but the crew's version has the right words: the actual steps, the actual tools, the actual ground conditions. OSHA 3071 makes the same point: the people who do the job know the job, and the analysis starts with them.

This is also the fix for the routine-hazard gap. When the crew writes the JSA, making a connection gets written down, because the crew knows where the pinch points are. When a safety department writes it, the generic hazards get covered and the real ones do not. The supervisor's job is to ask the questions. The crew's job is to answer them in their own words.

If your JSAs are a paper ritual, book a working session with the OpsFlo operations team. Book a call here to run JSAs from a tablet, versioned, tied to the job, and searchable when the auditor or the investigator asks.

For the other side of the same coin, read the guide on incident reporting on the rig.