How to Verify a New Work Package Before the First Shift in 8 Readiness Tests

A new work package can be approved before anyone has proved that the job is ready to run. The documents may be signed, the contractor may be mobilized, and the first shift may still inherit unresolved exposure at the point where planning meets production.

This guide gives EHS practitioners, supervisors, and work-package owners a practical way to test readiness before the first shift. The central idea is simple, although it is often missed in control-of-work systems: a package is ready only when the people doing the work can show how the planned controls will operate under the conditions they will actually face.

Work-package readiness is the evidence-based decision that a defined job can start because its scope, hazards, controls, resources, interfaces, and escalation boundaries are understood and usable by the team that will execute it. Approval alone is not readiness, since paperwork can confirm intent without proving field control.

What you need before starting

Use one work package that is about to enter execution. Bring the current scope, drawings or task instructions, risk assessment, permit requirements, contractor plan, equipment list, emergency arrangements, and the names of the people who will control the work. Include the supervisor and at least one person who will perform the task, because a readiness decision made only by planners can miss the friction that appears at the workface.

ISO 45001:2018 gives organizations a management-system framework for identifying hazards, controlling risks, and evaluating operational planning. The review below turns that expectation into a short field decision. It does not replace a permit, a formal risk assessment, or a competent technical review.

Step 1: Freeze the work scope

Write down what the package includes and what it does not include. State the equipment, location, work sequence, shift window, contractor boundaries, and expected handoffs. If the package says "replace the valve," clarify whether isolation, draining, line breaking, testing, reinstatement, and startup are included.

Ask the supervisor to describe the job without reading the document, then compare that explanation with the package. A mismatch shows that the approved scope has not become a shared operating picture. Record every difference as an action or a stop condition instead of allowing the crew to solve an unclear boundary after tools are in position.

The scope should also state what would force a new review. A change in equipment, energy state, work area, or sequence is not a minor administrative update when it changes the conditions under which the controls must work.

Step 2: Name the serious exposures

List the exposures that could cause a fatality, permanent harm, or a major release if control fails. Keep the list specific to the task. "Mechanical risk" is too broad to guide a decision; stored pressure between a closed valve and a flange is specific enough to test.

Use James Reason's distinction between active failures and latent conditions as a practical reminder. A worker's action may be the final visible event while design assumptions, isolation quality, staffing, or supervision have already shaped the conditions in which that action occurs.

For each serious exposure, identify the control that must work before the job starts. If the team cannot name the control and the evidence that will prove it, the package is not ready.

Step 3: Match each control to proof

Convert every important control into a verification statement. "Use a barricade" becomes "the barricade prevents entry into the dropped-object zone and remains intact during the work." "Confirm isolation" becomes "the authorized person has tested the isolation at the point of work and recorded the result."

Choose proof that can be seen, heard, measured, or demonstrated. A signature can confirm participation, but it cannot by itself prove that a valve is depressurized, a rescue route is open, or a lifting plan matches the actual load.

Where the proof depends on a specialist, name that person before the shift. Where the proof must be repeated after a change, state the trigger. Control verification is stronger when the team knows what evidence is required and when that evidence stops being valid.

Step 4: Test the work sequence in the field

Walk the planned sequence in the actual work area. Follow the route from staging to the point of work, then trace the return route for people, materials, waste, and emergency response. Look for blocked access, conflicting work, poor lighting, weather exposure, communication dead zones, and places where the team would need to improvise.

Ask the person who will perform each critical action to demonstrate the first move without starting the job. This often reveals that a tool is missing, the isolation point is not visible, the lifting position is wrong, or the procedure assumes a space that the field does not provide.

Resolve physical conflicts before approval. A work package that is technically correct but physically unusable transfers the design problem to the crew, which is where schedule pressure can make weak controls look normal.

Step 5: Confirm people, competence, and authority

Identify who owns the work, who controls the permit or authorization, who verifies the critical controls, who can stop the job, and who decides whether work may restart. Use names and roles rather than department labels, because a department cannot make a time-sensitive decision at the workface.

Check that the people assigned to critical tasks have the required competence, briefing, access conditions, and language support. Competence is not only a training record; it includes the ability to recognize a changed condition and act within a clear escalation boundary.

Andreza Araujo makes this practical leadership point in the book Make The Difference: Be a Leader in Health & Safety. Supervisors create control through decisions close to the work, not through the distance between the field and the management system.

Step 6: Stress the interfaces

Most work packages do not operate alone. They share space, energy, equipment, permits, access routes, or information with another team. List every interface that could change the exposure, including operations, maintenance, contractors, logistics, laboratories, security, and emergency response.

For each interface, state what must be communicated, who receives it, and what happens if the other party does not respond. A message sent to a group mailbox is not an interface control if no one is accountable for the decision.

Run one change scenario. Ask what the team would do if production needs the area, a second contractor arrives, weather changes the plan, or the isolation boundary moves. The answer should identify a person, a pause point, and a restart condition.

Step 7: Rehearse the abnormal condition

Select the most credible abnormal condition and rehearse the first response. The scenario might involve loss of communication, unexpected energy, a dropped object, a chemical release, a medical event, or a failed control. Keep the rehearsal close to the actual job instead of using a generic emergency script.

Check whether the team can reach the right equipment, contact the right responder, protect uninvolved people, and preserve the scene without creating a second exposure. If the response depends on a route, radio, rescue device, or specialist, verify that resource at the worksite.

A rehearsal is not a performance contest. Its purpose is to expose an assumption while the job can still be redesigned, before the team has invested time and reputation in defending the original plan.

Step 8: Set the release and restart decision

End the review with a clear decision. Release the work only when the scope is understood, serious exposures have named controls, field proof is available, people and authority are confirmed, interfaces are controlled, and the abnormal response is workable.

If one condition remains open, classify it as a hold, an action with an owner and deadline, or an accepted residual risk approved by the role defined in site governance. Do not hide an unresolved control inside meeting notes. A decision that cannot be found cannot protect the next shift.

Set the restart trigger before the first shift begins. The package must return for review when scope, personnel, equipment, isolation, weather, sequence, or interface conditions change beyond the limits defined by the team.

Final readiness checklist

• The scope and exclusions are understood by the supervisor and work crew.
• Serious exposures are specific, with a named control for each one.
• Each critical control has field evidence that can be checked.
• The planned sequence has been walked in the actual work area.
• People, competence, stop authority, and restart authority are identified.
• Interfaces have owners, response expectations, and pause conditions.
• An abnormal condition has been rehearsed with real resources.
• The release decision and change triggers are recorded where the next shift can find them.

Why this review changes the quality of the first shift

The first shift is often treated as the beginning of execution, although it is really the first test of the design. When the work package reaches the field with vague boundaries, unverified controls, or weak interfaces, the crew must compensate through improvisation. When the package is tested before release, the organization can correct the design while correction is still inexpensive and before pressure rewards silent adaptation.

Readiness is not another approval layer. It is the point at which the organization proves that its planned controls can survive contact with the work. That proof gives the supervisor a defensible release decision and gives the crew a clear boundary for stopping, escalating, and restarting the job.

Explore more practical safety leadership guidance from Headline Podcast.