New Control-of-Work Coordinator in 60 Days: What to Do Before High-Risk Work Starts

F6 role profile for a new control-of-work coordinator

A new control-of-work coordinator usually arrives when permits, isolations, contractor interfaces, and change reviews exist in separate folders, yet no one can explain how they protect the same job. The role is not another approval desk. It is the person who makes the conditions for high-risk work visible before production pressure turns a gap into an accepted exposure.

In the first 60 days, the coordinator should build a small operating rhythm that connects the work package, the responsible supervisor, the people exposed, and the decision to continue, pause, or redesign the job. The sequence below is designed for a coordinator entering a plant, project, shutdown, or maintenance organization where authority already exists but the handoffs are unreliable.

What a control-of-work coordinator needs to understand before starting

A control-of-work coordinator tests whether the organization has enough information, authority, and time to perform high-risk work safely. The coordinator does not own every permit or replace the supervisor. The role makes the operating boundary clear, then routes weak conditions to the person who can change them.

That distinction prevents two predictable failures. If the coordinator becomes the final approver for every task, operations stop owning the work. If the coordinator only checks signatures, the system creates administrative evidence without proving that isolation, competence, rescue, and simultaneous-operations controls are usable.

Andreza Araujo makes a related point in Muito Além do Zero, where safety is treated as a question of clarity and practicality rather than bureaucracy. The coordinator should therefore ask what a supervisor and crew can understand at the point of work, not how impressive the control manual looks in an audit.

First week: map the decisions that protect the work

Start with a short listening tour. Meet the operations manager, maintenance planner, permit issuer, isolation authority, contractor representative, emergency lead, and two supervisors who regularly run high-risk work. Ask each person where a job usually slows down, where information arrives late, and which decision nobody wants to own.

Build a one-page flow from scope definition to closeout. Mark where the job changes hands, where the hazard review is repeated, and where the crew can stop the work. A control-of-work map should include permit-to-work, energy isolation, confined-space entry, lifting, line breaking, hot work, contractor interfaces, and management of change only when those elements are actually relevant to the site.

Use the existing permit revalidation triggers as a practical test. If a change in scope, crew, weather, isolation, or neighboring work does not force a deliberate review, the coordinator has found a decision gap rather than a paperwork gap.

First 30 days: define the minimum evidence for high-risk work

Choose three to five work types that carry the greatest consequence at the site. For each one, define the minimum evidence needed before the job starts, the person who verifies it, and the condition that requires a pause. The list should be short enough for supervisors to use during a pressured shift.

For an isolation, the evidence may include the correct energy source, an identifiable lock, a documented release boundary, and an independent verification. For confined-space entry, it may include current atmospheric testing, rescue readiness, communication, and a clear response to a failed reading. These are examples, not a universal checklist, because the correct evidence depends on the equipment and exposure.

Write each control as an observable condition. “The permit is complete” is weak because completion does not prove understanding. “The supervisor can explain the isolation boundary and the crew can identify the same boundary at the equipment” is stronger because it connects the record to the worksite.

Link the coordinator’s work to the contractor interface before mobilization, because contractors often receive the most complex work while operating with the least context about local decisions. A Headline Podcast guest described the ethical answer clearly, there is no durable “us and them” boundary when the client controls the conditions of work.

Days 31 to 60: test the system during real work

Do not launch a large audit campaign. Follow a small number of live jobs from planning through closeout, and compare what the work package says with what the supervisor and crew believe they are authorized to do. Record where the two versions diverge, who noticed the divergence, and what decision followed.

Run one field conversation with the supervisor before the job starts, one check during the highest-exposure phase, and one closeout review after the work changes or ends. The purpose is not to catch people out. It is to see whether the control remains usable when access, sequence, staffing, or production conditions shift.

The coordinator should classify evidence as confirmed, uncertain, or failed. Confirmed means the control is present and explainable. Uncertain means the evidence is incomplete or inconsistent, so the job needs a decision before exposure increases. Failed means the control is absent, ineffective, or contradicted by the worksite.

When findings repeat, route them to the owner of the work design. A repeated isolation error may point to equipment labeling, planning time, or authority boundaries rather than a need for another reminder. James Reason’s work on latent failures helps keep that diagnosis precise, because the visible mistake may be the final layer in a chain of conditions.

Month 2 onward: make handoffs carry responsibility

After the initial 60 days, the coordinator should stop being the only person who can explain the control-of-work process. Supervisors should be able to state what evidence they need, workers should know how to challenge a changed condition, and planners should see how late scope changes affect the work package.

Create a weekly review of unresolved control decisions. Keep it focused on age, owner, temporary protection, and next decision date. Do not turn the meeting into a list of every open action, because volume hides the few conditions that can change the consequence of the work.

Use risk-owner reviews when a control depends on several departments. The coordinator supplies the evidence and convenes the conversation, while the accountable manager decides whether to resource, reschedule, redesign, or formally accept the remaining exposure.

Common mistakes that weaken the role

The first mistake is treating permit quality as a writing contest. A short permit that captures the real boundary is safer than a long form that nobody reads. The second is reviewing only the first shift, even though the risk changes when a contractor crew rotates, a temporary repair remains in place, or another team starts nearby.

The third mistake is escalating every uncertainty in the same way. A missing signature and a missing isolation are not equivalent, so the response must reflect consequence and control strength. The fourth is using the coordinator to compensate for unclear line management. The role can expose an authority gap, but it cannot permanently carry a decision that belongs to operations.

A final mistake is measuring activity instead of control. Visits, permits reviewed, and meetings held can show effort, although they do not prove that high-risk work became more predictable. Review repeated control failures, time from discovery to decision, and whether the next supervisor can explain the protection without the coordinator standing beside them.

Control-of-work before and after the first 60 days

Resources to deepen the coordinator’s practice

Begin with Sorte ou Capacidade by Andreza Araujo for the distinction between relying on luck and building the capability to manage exposure deliberately. On the Headline Podcast, Andreza Araujo and Dr. Megan Tranter repeatedly bring safety back to the decisions that shape real work, which is the right editorial lens for this role.

For daily application, pair the coordinator’s map with a review of competence drift. A current training record does not establish that a person can recognize a changed condition, use the control, or stop the job when the original assumption no longer holds.

Headline Podcast is a useful place to continue the conversation because the show connects leadership, safety, and risk without separating the human decision from the technical control. The coordinator’s job is to make that connection operational.

What the coordinator should leave behind

After 60 days, the strongest sign of progress is not that the coordinator has reviewed more permits. It is that supervisors can describe the work boundary, crews can challenge a changed condition, contractors know how to escalate, and managers can see which unresolved decision is holding up safe execution.

That is the standard for a control-of-work coordinator. Build enough clarity for the safe decision to be made before exposure rises, then keep responsibility with the person who has authority to change the work. Explore Headline Podcast for more conversations that connect safety leadership with the conditions in which people actually work.