How to Verify Contractor Competence Before High-Risk Mobilization in 10 Steps

F2 practical guide

Contractor mobilization often begins with a document exchange. The host receives a training matrix, a list of certificates, and a declaration that the crew is ready. The weakness appears when the first task requires a judgment that none of those documents tested.

Competence is not the same as course completion. It is the ability to recognize the exposure, use the control in the right sequence, communicate with the people who own the interface, and stop or escalate when the work no longer matches the plan. The following ten steps give a plant manager, contractor manager, or site safety leader a practical way to test that ability before high-risk work starts.

What to prepare before the verification

Start with the work, the exposure, and the decisions that can prevent serious harm, then ask the contractor to provide evidence against those requirements.

The review should not begin with a folder of certificates. Begin with the scope of work, the equipment involved, the critical controls, the interfaces with host personnel, and the conditions that would require a pause. ISO 45001:2018 places contractor control inside the management system, which means the verification should connect to operational planning and control. If workload, fatigue, conflict, or communication barriers can affect performance, ISO 45003:2021 provides a useful reference for examining psychosocial conditions that may weaken execution.

James Reason’s work on latent failures also matters here. A worker can be individually capable and still be placed in a system that makes the safe action difficult. The review therefore tests both personal capability and the conditions that the host must make reliable.

Step 1: Define the task-specific competence profile

Translate the work scope into observable capabilities before asking for names or certificates.

Write down what each role must be able to do, not only what training each role must have. A confined-space entrant may need to interpret atmospheric readings, maintain communication, recognize a change in conditions, and leave without waiting for a supervisor. A lifting supervisor may need to reject an unstable setup, confirm exclusion zones, and resolve conflicting signals.

Separate routine knowledge from high-consequence decisions. This distinction prevents a large training matrix from hiding one missing capability that can defeat several controls.

Step 2: Map the critical decisions and boundaries

Identify who can authorize, pause, change, and escalate the work when conditions differ from the plan.

Competence includes knowing the limits of one’s authority. Create a simple decision map that identifies the person who can release the job, the person who can isolate equipment, the person who can stop the work, and the person who must be called when a control is unavailable.

Ask the contractor supervisor to explain these boundaries without reading from the procedure. If the answer depends on “someone from the client,” the interface is not yet controlled. The host should name the responsible role and the response route before the crew mobilizes.

Step 3: Check credentials against the actual assignment

Match each credential to the equipment, task, jurisdiction, and level of responsibility that the assignment requires.

Review licenses, authorizations, medical or fitness requirements where applicable, and recent task-specific training. Then test the match. A credential for operating one class of equipment does not automatically prove competence on a different model, attachment, energy source, or site layout.

Record gaps rather than averaging them away. A crew can have a high percentage of completed courses and still lack the one authorization required for isolation, rescue, or final release.

Step 4: Test recency and experience without accepting vague claims

Ask for recent, relevant evidence that shows the person has performed the same type of work under comparable conditions.

“Ten years of experience” is not precise enough by itself. Ask when the person last performed the task, which equipment was used, what unusual condition was managed, and which decision required escalation. The purpose is not to reward storytelling. It is to determine whether experience is current and relevant to the exposure now being introduced.

Where the assignment is unusual or infrequent, treat the absence of recent practice as a verification need. A simulation, supervised demonstration, or additional competent person may be necessary before work begins.

Step 5: Observe a practical demonstration

Watch the crew perform the critical sequence in a controlled setting, because practical behavior reveals gaps that paperwork cannot.

Choose a demonstration that represents the highest-value control rather than the easiest task to stage. Observe preparation, communication, equipment checks, control use, response to an abnormal condition, and closeout. Ask the worker to explain what would cause a stop, but do not turn the exercise into a memory test.

The evaluator should record observable evidence, including skipped steps, unclear signals, unsafe assumptions, and appropriate pauses. A demonstration is useful only when the criteria are defined before the observation and applied consistently across crews.

Step 6: Introduce one realistic change in conditions

Change one material condition and see whether the crew recognizes that the original plan no longer applies.

Examples include a change in weather, a conflicting simultaneous operation, a failed communication channel, an unexpected energy source, or a missing control. The scenario must remain controlled and proportionate to the task. Its purpose is to reveal judgment, not to surprise people with a theatrical test.

Strong performance includes noticing the change, explaining its significance, protecting people from exposure, and using the agreed escalation route. Weak performance includes continuing because the schedule is tight or waiting for someone else to notice.

Step 7: Verify communication at the host interface

Confirm that the contractor and host team share the same words, signals, handover points, and escalation expectations.

Many failures occur at the boundary between organizations. Ask both sides to describe the same job, the same isolation status, and the same stop-work trigger. Compare the answers. Differences may show a translation problem, an ownership gap, or a local workaround that has not been approved.

Include shift handover and language needs in the check. A crew that understands a control in the morning may lose the protection when a different supervisor, subcontractor, or host operator takes over.

Step 8: Confirm supervision capacity, not just supervisor credentials

Check whether the named supervisor can actually see, influence, and respond to the work throughout the exposure.

A qualified supervisor who is responsible for several distant crews may not provide effective control. Ask how often the supervisor will be present, how the crew will request support, what decisions can be made remotely, and what happens when two jobs compete for attention.

The answer should match the risk. High-risk work needs a supervision arrangement that can detect drift early enough to matter, particularly when the crew is unfamiliar with the site or the task has limited recovery time.

Step 9: Record gaps with an owner and a decision date

Turn every gap into an explicit decision, because an undocumented exception becomes an invisible assumption during execution.

Use a short register with the requirement, evidence reviewed, gap, interim protection, owner, decision date, and mobilization status. Do not label a gap “to be addressed” without stating who must act and what evidence will close it.

Some gaps require the contractor to provide a qualified person. Others require the host to change the work plan, add supervision, improve an interface, or delay the activity. The register makes that distinction visible to the manager who controls the schedule.

Step 10: Release, restrict, or stop the mobilization

Make the mobilization decision from verified evidence, not from the cost of delaying the job.

Release the work when critical capabilities are demonstrated, the interface is understood, and unresolved items do not expose people beyond the approved controls. Restrict the scope when only part of the assignment is verified. Stop the mobilization when a critical gap remains and no credible interim protection exists.

The final decision should state what was verified, what was not verified, who owns the remaining risk, and what event will trigger a new review. This creates a traceable boundary between readiness and assumption.

Final checklist for the mobilization gate

A contractor is ready when the evidence connects the person, the task, the control, the interface, and the decision route.

• The task-specific competence profile is defined for every critical role.
• Credentials match the actual equipment, jurisdiction, and responsibility.
• Recent relevant experience has been checked without relying on vague claims.
• A practical demonstration has been observed against pre-defined criteria.
• The crew has responded to one realistic change in conditions.
• Host and contractor teams agree on communication, handover, and stop-work expectations.
• Supervision capacity matches the exposure and work arrangement.
• Every gap has an owner, a decision date, and a mobilization status.

Across 25+ years of executive EHS work, Andreza Araujo’s central lesson is consistent with this method: safety performance improves when leadership turns expectations into decisions that can be seen in the work. A contractor gate is valuable for the same reason. It does not ask whether a folder looks complete. It asks whether the next high-risk decision can be made by a prepared person, with a usable control, inside a reliable operating system.

If your organization needs to strengthen contractor governance before exposure reaches the field, Andreza Araujo helps leaders connect safety culture, risk management, and practical execution.