New Contractor Safety Coordinator in 60 Days: Build Control Ownership Before Mobilization Pressure Wins

A new contractor safety coordinator can inherit hundreds of forms and still lack one essential fact: who owns the control when the work changes. The gap appears during mobilization, when contract language, schedule pressure, local conditions, and contractor methods meet for the first time.

The first 60 days should therefore produce more than a compliance calendar. They should establish a visible operating system in which the host organization, contractor management, and field supervisors know what they own, how the control is checked, and who can stop the task when the agreed method no longer fits.

Andreza Araujo's published professional biography describes more than 25 years in executive EHS work across multinational operations, while her professional work includes more than 250 cultural transformation projects. That experience supports a practical test for this role, which is whether the organization can protect a control when mobilization pressure makes shortcuts attractive.

What does a new contractor safety coordinator need to understand before starting?

Contractor safety is not a separate system that sits beside operations. It is a temporary operating relationship whose risks change when scope, crew, equipment, access, supervision, or sequence changes. A contractor may arrive with a strong method statement, yet the site can still invalidate it through an unavailable isolation point, a congested route, an altered lifting plan, or a supervisor who has never worked in that area.

ISO 45001:2018 requires organizations to control procurement, outsourced processes, operational changes, and competence. Those requirements do not mean the coordinator should personally approve every task. They mean the organization needs a reliable way to decide which conditions must be known before work begins and which changes require a fresh review.

James Reason's work on latent failures adds an important distinction. A field error can be shaped by decisions made earlier, including a contract that rewards speed without defining stop-work authority, a scope that omits interface risks, or a handoff that assumes another team owns the barrier. The coordinator's first responsibility is to make those hidden conditions discussable.

First week: Where does contractor risk become invisible?

Spend the first week in the work areas, not only in the contractor office. Observe mobilization meetings, pre-job briefings, equipment arrival, permit preparation, access control, and the first execution of routine work. Ask supervisors to show where the control exists, who checks it, and what happens when the check fails.

Use the observations to build a simple interface map. Record the host owner, contractor owner, field verifier, decision that can pause work, and evidence expected before restart. Do not begin with a large scorecard, because a scorecard can hide the specific boundary where responsibility is being passed without acceptance.

At the end of the week, select three work interfaces for deeper review. Choose activities that cross organizational boundaries, because those are where ownership is most likely to become ambiguous.

Days 8 to 15: Turn contract promises into field conditions

Review the contract, prequalification evidence, risk assessments, insurance documents, competence records, and mobilization checklist together. The purpose is not to find a missing signature. It is to identify promises that cannot yet be tested in the actual work environment.

A contractor may promise competent supervision, but the site needs a named supervisor with authority, local access, and enough time to observe the work. A method statement may require exclusion zones, but the coordinator must confirm that the route, layout, and adjacent activities allow those zones to exist. A rescue plan may name equipment that is not available on the shift when the work occurs.

Create a field-readiness register with one line for each critical condition. Give every line an owner, due date, verification method, and escalation route. Keep the register short enough for a supervisor to use during a pre-job review, because a control that cannot be discussed at the workface will not remain reliable for long.

Days 16 to 30: Define ownership for critical controls

By day 30, move from general contractor accountability to control-level ownership. The contractor company can own the work method, while the host organization may own isolation, access, traffic segregation, or simultaneous-operations coordination. A field supervisor may verify the control, but verification does not automatically transfer ownership of the condition.

For each critical activity, answer five questions in plain language. What can cause serious harm? Which control must be present? Who has authority to provide it? Who verifies it before work starts? What decision follows if the verification fails?

This structure prevents a familiar failure. The host assumes the contractor owns everything because the contractor performs the task, while the contractor assumes the host controls the site conditions. When both assumptions remain unspoken, the worker receives a permit that looks complete but does not explain who resolves the conflict.

Use the existing contractor safety process as the backbone, then add only the ownership fields that change decisions. A useful internal reference is the contractor-safety article on procurement decisions, which shows why risk can be shaped before a crew reaches the gate. The coordinator's role is to connect that early decision to field verification rather than treating procurement and execution as separate worlds.

Days 31 to 45: Test whether supervisors can demonstrate the control

Induction confirms that information was presented. It does not confirm that a supervisor can control the job under local conditions. During this phase, require short demonstrations in the work area. Ask the supervisor to show the isolation boundary, identify the exclusion zone, explain the communication route, or point out the condition that would stop the task.

Use demonstrations selectively. The goal is not to create another inspection ritual. The goal is to test the decisions that matter when the work is ready to start and the schedule is already under pressure.

• Confirm that the control exists where the task will occur.
• Ask the supervisor to explain the verification step without reading the document.
• Introduce one realistic change and observe whether the team escalates or improvises.
• Record the decision owner and the evidence required before restart.

When a demonstration fails, avoid treating the finding as a contractor personality problem. Check whether the work pack was unclear, whether the supervisor had the authority assumed by the contract, and whether the host created a condition that made the planned control impossible.

Days 46 to 60: Make the system survive pressure

The final phase should test the system during the conditions most likely to weaken it. Review a delayed job, a shift handover, a temporary deviation, a subcontractor change, and a task that requires coordination with operations or maintenance. These situations reveal whether the control system works only when the plan is stable.

Ask leaders to review decisions, not only outcomes. Did the team identify the change early? Did the named owner respond? Was the temporary control clear and time-bound? Did the restart require evidence, or did the schedule itself become the authorization?

By day 60, produce a short assurance report with three parts. First, list the controls whose ownership is now clear. Second, identify the interfaces that still depend on personal relationships or informal memory. Third, define the next management decision, including the resource, authority, or contract change needed to close the remaining gap.

Which mistakes weaken a contractor safety coordinator's first 60 days?

The first mistake is treating contractor safety as document completeness. Documents matter, but they are only useful when they describe conditions that can be verified. A signed risk assessment cannot compensate for an unavailable isolation or an unclear work boundary.

The second mistake is making the coordinator the owner of every control. That creates dependence on one safety professional and teaches operations and contractors to wait for approval. The coordinator should clarify ownership, test evidence, and escalate unresolved conditions, while accountable leaders retain the decisions assigned to them.

The third mistake is measuring activity instead of control reliability. The number of inductions, inspections, and meetings may increase while serious exposure remains unchanged. A stronger question is whether the person who owns the barrier can demonstrate it before work starts and respond when the conditions change.

The fourth mistake is separating contractor performance from host performance. Contractor work occurs inside host decisions about planning, access, schedule, equipment, interfaces, and supervision. If those conditions are ignored, the review will blame the visible gap while leaving the system that produced it untouched.

What should the coordinator carry into the next quarter?

A successful first 60 days leaves the organization with a repeatable decision rhythm. New contractors can enter through the same readiness gate, supervisors can identify their control boundaries, and leaders can see which unresolved interface requires intervention before the next job begins.

Keep the operating model practical. Every critical control needs an owner, a verifier, a decision rule, and evidence that remains credible across shifts. When those four elements are visible, the coordinator becomes more than a compliance checkpoint. The role becomes a bridge between what the organization bought, what the contractor planned, and what the field can safely execute.

If your operation is redesigning contractor governance, explore Andreza Araujo's work on safety culture and leadership at Andreza Araujo.