How to Prepare a Contractor Interface Review Before Mobilization in 14 Days

A contractor can arrive with a competent crew, current training records, and a signed scope of work, yet the job can still begin with an unsafe gap. The gap usually sits between organizations. One team controls the site, another controls the equipment, and neither has made the boundary explicit enough for a supervisor to act when conditions change.

A contractor interface review closes that boundary before mobilization. It is not a document-collection exercise. The review should show who owns each hazard, which controls must be present, how work will be coordinated, and what happens when the agreed conditions no longer exist. ISO 45001:2018 supports this approach by requiring organizations to control outsourced processes and coordinate with other parties that can affect occupational health and safety.

A contractor interface review is a structured check of the responsibilities, hazards, controls, communication routes, and decision rights shared by a host organization and a contractor before work starts. Its purpose is to expose boundary failures early, when the work plan can still be changed without placing a crew inside an untested arrangement.

What should be ready before the 14-day review starts?

Assign one host representative and one contractor representative with authority to resolve open questions. The host representative should understand site rules, simultaneous operations, emergency arrangements, and the permit system. The contractor representative should understand the actual method of work, crew composition, equipment, subcontractors, and production constraints that may influence the task.

Gather the current scope, schedule, site layout, method statement, risk assessment, equipment list, competency requirements, emergency contacts, and relevant permits. Do not treat these files as proof that the interface is controlled. They are inputs for a conversation that must reach the field. Andreza Araujo's safety leadership work repeatedly connects culture with the decisions people can see, so the review is complete only when the written agreement can guide a supervisor during real work.

Step 1: Define the work boundary

Write the boundary in operational language. Identify the exact area, assets, systems, shifts, access points, and dates covered by the contractor's work. Include the transitions where the contractor enters, performs the task, hands equipment back, or leaves the site.

Ask the host and contractor to mark the same boundary on a site plan. If their drawings show different isolation points, laydown areas, traffic routes, or exclusion zones, stop the review and reconcile the difference. A vague boundary becomes a practical excuse for assuming that another team is responsible.

Step 2: Map the interfaces that can change the risk

List every activity in which control passes between the host and contractor. Typical interfaces include energy isolation, line breaking, lifting, excavation, confined-space entry, traffic management, hot work, waste handling, and access to restricted systems.

For each interface, record the trigger that changes the risk. A shift change, a new subcontractor, a process start-up, a weather change, a simultaneous lift, or a change in equipment location can invalidate an earlier assumption. James Reason's work on latent failures is relevant here because a boundary that looks harmless on paper can align with other weaknesses during execution.

Step 3: Assign one owner to each critical control

Convert the risk assessment into a control ownership table. Name the person or role that must provide the control, the person who verifies it, the evidence that proves it exists, and the action required when it is absent. Avoid assigning ownership to a department without naming the decision-making role.

Separate provision from verification. The contractor may install a guard, while the host may verify that the guard fits the site arrangement and remains effective during simultaneous operations. When the same person provides and approves a control, document the independent challenge needed for high-consequence work.

Step 4: Reconcile the two work methods

Read the contractor's method beside the host's operating procedure, permit process, and isolation standard. Look for differences in terminology, sequence, acceptance criteria, and stop conditions. The most important question is not whether both documents mention the same hazard. It is whether both teams would take the same action when the hazard appears.

Resolve conflicts before approval. If the contractor's method assumes an isolation that the host cannot provide, revise the method or change the work window. If the host procedure requires a check that the contractor's sequence does not include, add it to the field plan and identify who will perform it. For work that depends on formal change control, compare this review with the site's safety-critical change review before startup.

Step 5: Test competence and supervision at the interface

Verify the competencies that matter for the actual task, not only the certificates attached to the procurement file. Check who will lead the crew, who can stop the job, who can authorize a restart, and who will supervise subcontractors. Confirm that the named people will be present during the shifts in which the highest-risk work occurs.

Ask the contractor supervisor to explain the work sequence in plain language while the host supervisor explains the site constraints. Their explanations should agree on the first critical control, the communication route, and the condition that requires a pause. If they do not, the gap is a readiness issue, not a training-record issue.

Step 6: Build the communication and escalation route

Define how routine coordination, urgent warnings, and stop-work decisions will travel across the interface. Name the channel, the receiving role, the backup role, and the expected response when the primary contact is unavailable. Include shift handover because an agreement that exists only during daytime planning will not protect night work.

Use a short escalation drill before mobilization. Present a realistic change, such as an unexpected process release or a missing isolation, and ask each party to state who calls whom, who has authority to stop, and what evidence is required before restart. The drill should expose hesitation while there is still time to change the plan. The host can also use the site's emergency response readiness tests to challenge shared rescue and escalation assumptions.

Step 7: Walk the worksite before approving mobilization

Take the agreed documents to the actual work area. Check access, lighting, housekeeping, emergency equipment, isolation points, traffic separation, communication coverage, muster arrangements, and space for the planned equipment. Include the people who will supervise the work because they can identify constraints that a planning meeting misses.

Record field discrepancies with an owner and a due date. Do not close an item because someone promises to fix it after the crew arrives. Mobilization should be approved only when the remaining actions have a clear temporary control, an accountable decision-maker, and a defined review point that does not leave workers carrying unexamined exposure. If lifting or vehicle movement is part of the scope, verify the site's lift exclusion zones during this walk.

Step 8: Approve, brief, and verify the first shift

Issue one interface agreement that consolidates the boundary, control owners, communication route, emergency arrangements, and stop conditions. Keep the document short enough for supervisors to use, while linking it to the detailed method statement and permit records. Both organizations should approve the same version.

At the first-shift briefing, ask the crew to explain the boundary and the response to the most important change condition. Then verify the controls in the field during the opening task rather than treating the briefing as the final evidence. A signed attendance sheet proves participation. It does not prove that the arrangement works.

What should the final review record show?

The record should make the decision traceable. It should show the work boundary, critical interfaces, control owners, verification evidence, unresolved items, escalation contacts, emergency assumptions, approval roles, and the first verification date. If the job runs across several shifts or phases, define when the review must be repeated.

Use the record to improve contractor governance, not to create another archive. After the first shift, compare the plan with what supervisors actually had to clarify. Repeated questions about access, isolation, handover, or authority reveal a design weakness that should be corrected before the next contractor mobilizes.

Final mobilization checklist

• The host and contractor have marked the same work boundary and transition points.
• Each critical control has a provider, verifier, evidence source, and response if absent.
• The method statement, permit process, isolation standard, and emergency plan agree.
• Supervisors know who can stop the work and who can authorize a restart.
• The first-shift verification date and owner are recorded before mobilization approval.

For a broader view of how management choices shape safety culture, explore Andreza Araujo's books and practical safety resources.

The contractor interface is ready when both organizations can describe the same work boundary, point to the same control owners, and act on the same stop conditions. That standard is more demanding than collecting documents, yet it gives supervisors a workable basis for protecting people when the plan meets the site.

Frequently asked questions

What is the main purpose of a contractor interface review?

The main purpose is to identify and close gaps between the host organization and contractor before work begins. The review clarifies who controls each hazard, who verifies the control, how changes are escalated, and which conditions require work to stop or be redesigned.

When should the review take place?

Start the review before mobilization and allow enough time to resolve differences between the scope, work method, site controls, and emergency arrangements. Repeat it when the work boundary, crew, equipment, phase, shift pattern, or operating conditions change materially.

Does a signed contractor risk assessment prove readiness?

No. A signed assessment proves that a document was reviewed or accepted. Readiness also requires field verification, clear control ownership, aligned work methods, competent supervision, and a tested route for stopping and restarting work when conditions change.

Who should lead the review?

The host organization should appoint a representative who understands the site and can resolve operational constraints, while the contractor should appoint a representative who understands the real work method and crew. The review works best when both representatives can make or obtain timely decisions.

How can a small site keep the process practical?

Use one short interface agreement, one control ownership table, one site walk, and one first-shift verification. Small sites still need clear boundaries and escalation authority, but they can keep the evidence compact when the work is straightforward and the decision roles are explicit.