How to Run a Contractor Interface Review Before Simultaneous Operations Start

When two employers control the same work area, each permit can be complete while the combined exposure remains unmanaged. This guide gives supervisors and EHS managers an eight-step method for reviewing contractor interfaces before simultaneous operations begin.

The central question is not whether every contractor has a safety document. It is whether the host, contractor, and affected operations have agreed on who controls each interaction, what can change, and which decision stops the work when the plan no longer matches the field.

What you need before starting

A contractor interface review is a short, evidence-based meeting that maps shared boundaries, confirms control ownership, tests conflicts between tasks, and records the decisions that must be visible before work starts.

Collect the current work scope, site layout, contractor method statements, isolation plans, lifting plans, permits, emergency arrangements, and names of the people who can authorize a change. Do not treat the contractor induction as a substitute for this review, because induction transfers information while interface review assigns decisions.

OSHA addresses communication and coordination between host employers, contractors, and staffing agencies, while 29 CFR 1910.119(h) adds specific contractor duties for covered highly hazardous chemical operations. ISO 45001:2018 also expects organizations to control procurement, contractors, and outsourced processes in a way that protects workers. These anchors support the review, but they do not replace a site-specific decision about the work in front of you.

Step 1: Define the work boundary

Write the physical, operational, and time boundary of the work before discussing controls, because an unclear boundary lets each party plan against a different job.

Mark the area on a current drawing and state what is inside the review. Include access routes, laydown zones, energy sources, temporary structures, adjacent production, emergency routes, and the shifts that will overlap. If the work crosses a battery limit or changes the status of a shared system, include that interface explicitly rather than leaving it to the permit issuer.

The boundary should name what is excluded as well. A contractor may control scaffold erection, while the host retains control of process isolation, traffic routes, and emergency communications. That division is useful only when it is written in language that the person leading the task can apply without interpretation.

Use the site drawing as a decision tool, not as an attachment that nobody opens. The drawing which shows a crane swing, a live line, and a pedestrian route can expose a conflict earlier than a long narrative method statement.

Step 2: Name the control owners

Assign one accountable owner to each critical control, including the person who verifies it and the person who can stop the interaction.

Create an ownership table with four fields: control, accountable owner, verification method, and stop-work authority. Cover isolation, access, line breaking, lifting exclusion, atmospheric testing, fire protection, dropped-object prevention, traffic separation, and emergency notification when they apply.

A company name is not an owner. The owner must be a role or named person who will be present or reachable during the work. If a control depends on a permit issuer, area authority, contractor supervisor, and operations coordinator, record how those people confirm the same status.

Andreza Araujo describes this principle in Safety Culture: From Theory to Practice, where responsibility becomes credible only when management behavior makes the expected decision visible. In a contractor review, that means replacing statements such as “the contractor is responsible for safety” with a precise answer to who controls each interface.

Step 3: Map simultaneous operations

List every task that can overlap in place or time, then test whether one task can change the exposure faced by another.

Start with the schedule rather than the contractor list. Put maintenance, production, testing, lifting, vehicle movement, electrical work, cleaning, commissioning, and emergency drills on the same timeline. An operation that is safe in isolation can create a different risk when it shares a boundary with hot work, pressure testing, mobile equipment, or an energized system.

For each overlap, ask what changes first. Does one crew remove a guard that another crew assumes is in place? Does a lift cross an access route? Does a test release energy into an area where another contractor is working? Does a shift change occur before the control is rechecked?

Do not hide uncertainty by adding another generic permit. The useful output is a short list of interactions that need a decision, a timing restriction, a physical separation, or a single coordinating authority.

Step 4: Test the handoffs

Rehearse each handoff in the order it will occur, including what information must be confirmed before the next person accepts control.

Choose the moments where control moves between the host and contractor, between shifts, or between work phases. Common examples include isolation release, equipment handback, area release, permit suspension, simultaneous work approval, and emergency escalation. At each point, name the evidence that proves the handoff happened.

A signature alone does not prove transfer. The receiving person should be able to state the current equipment status, open restrictions, people still exposed, barriers that remain temporary, and the condition that would require the work to stop.

Use a short verbal read-back when the consequence of misunderstanding is high. The read-back should be recorded in the permit or control log, whose purpose is to preserve the decision trail rather than create another administrative task.

Step 5: Challenge the method against field conditions

Compare the approved method with the actual work area and change the method when the field contains constraints that the planning documents did not address.

Walk the boundary with the contractor supervisor, host representative, and the person who owns the affected operation. Check access, lighting, weather exposure, noise, congestion, temporary supports, stored energy, communication coverage, and the location of emergency equipment.

Ask the crew to show how the critical control will work at the point of use. A document may require a barricade, but the field may offer no stable surface for it. A method may assume radio contact, while the work area may contain a dead zone. These are not small housekeeping issues when they change whether a control can be used.

In more than 250 cultural transformation projects, Andreza Araujo has treated the gap between declared practice and operated practice as a management problem, not a worker attitude problem. The interface review should apply the same test by changing the plan before production pressure turns an obvious mismatch into a late improvisation.

Step 6: Set conflict rules

Write the conditions under which simultaneous work is allowed, restricted, paused, or prohibited, and give one role authority to make the call.

Use plain rules that match the interaction. For example, lifting over occupied work is prohibited; pressure testing excludes nonessential people; hot work requires an agreed fire watch and combustible-material check; and any unexpected energy indication suspends the task until the isolation owner reassesses it.

Conflict rules should also cover changes in sequence. If a contractor finishes early, another crew may be tempted to enter the area before the host has verified status. If the sequence changes, require a new interface check rather than allowing the original approval to follow the work automatically.

The rule must identify the trigger, the immediate action, the authority, and the evidence needed to restart. A vague instruction to “coordinate closely” fails because it describes a wish rather than a decision path.

Step 7: Verify emergency coordination

Test whether the host and contractor can identify the same alarm, evacuation route, first response, emergency contact, and accountability method.

Ask what happens if the contractor supervisor is unavailable, the normal radio channel fails, or the incident affects more than one work group. Confirm who contacts site emergency response, who controls the area, who accounts for contractor personnel, and who communicates the initial status to operations.

A rescue plan should be practical for the actual work, not merely attached to the method statement. Check access for responders, equipment compatibility, language needs, weather limits, and the time required to reach the person at risk. When the task involves confined space, lifting, line breaking, or work at height, verify that the rescue arrangement addresses the specific exposure rather than naming emergency response in general terms.

OSHA's communication and coordination guidance emphasizes that host and contractor arrangements must be understood before and during the work. The review should therefore include a short question-and-answer test, where each person explains the first action they would take and the person they would contact.

Step 8: Record the release decision

Release the work only after unresolved interfaces have an owner, a due time, an interim control, or an explicit decision that the work cannot start.

End the review with three lists: controls confirmed, controls requiring action, and conditions that prohibit release. Record the evidence reviewed, the people present, the next verification point, and the person who will close each open item.

Do not close an open interface because the meeting ended. The work is ready only when the agreed control exists in the field and the responsible person can explain how it will be checked during the shift. A decision log that contains no owner or verification method is a record of discussion, not a control.

Set a recheck when the work is long, unusual, or exposed to changing conditions. The trigger may be a shift change, a new contractor, a change in sequence, weather deterioration, an unexpected process condition, or a control that was temporarily removed.

Comparison: paperwork review versus interface control

Use a paperwork review to establish minimum requirements, but use an interface review to decide whether the combined work is ready. That distinction is especially important when contractors share space, energy sources, emergency routes, or production constraints.

Conclusion: release the interaction, not just the job

A contractor interface review prevents simultaneous operations from being treated as separate jobs when the exposure is created by their interaction. Define the boundary, assign control owners, map overlaps, test handoffs, challenge the field method, set conflict rules, verify emergency coordination, and release only what has evidence.

Headline Podcast explores how safety leaders turn technical expectations into decisions people can see and use. For broader work on safety culture and leadership, visit Andreza Araujo's official site, and compare this guide with stored-energy control during maintenance isolation, the difference between a pre-job briefing, toolbox talk, and shift handover, and a line-of-fire review before maintenance starts.