Contractor Safety: 4 Procurement Decisions That Change Risk

A contractor can arrive with a signed scope, a clean prequalification file, and a serious exposure that procurement never tested. This article examines four procurement decisions that determine whether contractor risk is controlled before mobilization or merely documented after the fact.

The central argument is practical. Procurement does not own every field control, but it decides which risks enter the operation, which safeguards become contractual obligations, and which evidence is strong enough to stop a weak supplier from being treated as ready.

1. Define the work risk before comparing suppliers

The first procurement decision is whether the work package describes the real exposure instead of only the service to be purchased. A request for quotations that says “maintenance support” hides very different hazards when the job includes line breaking, energized equipment, confined space entry, lifting, or simultaneous operations.

ISO 45001:2018 requires organizations to consider procurement and contractors within the occupational health and safety management system. That requirement is often reduced to a questionnaire, although the harder question is whether the purchasing record identifies the conditions that can defeat a control.

Before a bid is released, the request should name task boundaries, energy sources, interfaces, competence requirements, emergency arrangements, and evidence that will be checked in the field. The contractor-heavy site signals matter here because paperwork can appear mature while the work interface remains undefined.

25+ years of executive EHS experience Andreza Araujo’s experience shows why this step belongs before the commercial comparison. When the risk is vague, the lowest price becomes the clearest selection criterion, even though the operation has not agreed on what “safe enough” means.

2. Separate legal eligibility from operational readiness

Legal eligibility proves that a contractor can participate in the market. Operational readiness proves that the contractor can perform this specific work under this site’s conditions, with its equipment, interfaces, and decision rights.

A current license, insurance certificate, training record, or injury-rate declaration may be necessary, but none of those documents proves that a supervisor can control a simultaneous operation at 2:00 a.m. The distinction also protects procurement from asking EHS to approve a supplier on evidence that was never designed to answer an operational question.

Use two gates. The first confirms legal, financial, and technical eligibility. The second tests task-specific readiness through a method statement review, competence interview, control verification, and a realistic emergency question. The new procurement manager guide helps build the governance rhythm, but the second gate must remain tied to the work package.

In projects supported by Andreza Araujo, this separation prevents a familiar failure. A contractor is approved because the file is complete, then the site discovers that the named competent person is unavailable, the equipment differs from the bid, or the escalation path was never agreed.

3. Buy control capability, not only labor capacity

The third decision is whether the contract buys a contractor’s ability to maintain critical controls, rather than only hours, headcount, or production output. A supplier that can provide 20 workers may still lack the planning discipline, supervision depth, or equipment assurance needed for high-consequence work.

Procurement should ask what the contractor will control, how that control will be verified, and what happens when the control cannot be maintained. For lifting, evidence may include lift planning, equipment certification, exclusion-zone design, and a named lift director. For isolation work, it may include energy identification, lock ownership, verification, and handback criteria.

This is where a critical-control walkdown changes the commercial conversation. The team can inspect whether the promised barrier exists, whether the owner understands its purpose, and whether the contractor’s method survives contact with the work area.

The market often treats “more supervision” as the answer. That is incomplete because supervision helps only when the supervisor has authority, time, competence, and a control model that can be tested. A contract that pays for attendance without defining those conditions has purchased visibility, not assurance.

4. Make bid evaluation expose the cheapest unsafe assumption

The fourth decision is how the bid is scored. A procurement model that rewards price while treating safety as pass or fail encourages suppliers to keep safeguards outside the quoted scope, where they can later appear as variations, delays, or field improvisations.

Use a weighted evaluation that makes safety evidence visible before award. The exact weights should reflect the hazard, but a practical model can test four dimensions: task competence, control design, supervision capacity, and evidence of previous control performance. Price remains relevant because a solution that cannot be funded will not remain reliable, yet price should not erase a material control gap.

Ask each bidder to explain one credible failure mode, one control that prevents it, one control that limits harm if prevention fails, and one piece of evidence that proves the control is working. This exercise is more revealing than asking whether the company “takes safety seriously,” because it requires a decision trail rather than a declaration.

Andreza Araujo’s book The Illusion of Compliance provides the right warning for this stage. A compliant file can create false confidence when the selection process rewards documents that are easy to submit instead of controls that are difficult to maintain.

5. Contract the right to stop, change, and escalate

A contractor safety clause should define decision rights before pressure arrives. If a worker identifies a failed isolation, a changed lift path, or a missing rescue resource, the agreement must make clear who can stop the work, who must be notified, who pays for the delay, and what evidence is required before restart.

Without those terms, the operational message is contradictory. Leaders say stop-work authority exists, while the commercial system signals that delay is a contractor problem. That conflict makes escalation personal, which is why a technically correct concern can remain unraised until the exposure becomes an event.

Include a change-control trigger for altered scope, crew, equipment, sequence, shift, or interface. Require a documented review when any of those conditions changes the assumptions behind the original award. The contract should also preserve the client’s right to audit critical controls and reject work that no longer matches the agreed method.

This is not an attempt to transfer every safety duty to procurement. It is a way to ensure that accountability follows the decision that created the exposure, while field leaders retain the authority to protect people when conditions change.

6. Test the contractor’s evidence before mobilization

Documents should be sampled against reality before the first shift, because a certificate is evidence of a past condition, not proof of present capability. The test can be small, but it must be specific enough to reveal whether the contractor understands the work it is about to perform.

Use three evidence levels. First, verify identity and validity, including the person, equipment, date, and issuing body. Second, test understanding through a scenario-based interview or practical demonstration. Third, observe the control in the work area or in a realistic simulation whose assumptions are recorded.

A contractor may provide a rescue plan that lists equipment and phone numbers. The readiness test should ask who reaches the casualty first, what happens if normal access is blocked, how long the team can sustain the response, and which condition allows work to restart. Those questions expose operational gaps that a document review misses.

The critical-control verification gaps are relevant because procurement dashboards often report completion rates rather than evidence quality. A green status is weak when nobody can show what was tested.

7. Measure contractor performance through control evidence

Contractor performance should be reviewed through the controls that matter to the work, not through injury counts alone. A low recordable rate can coexist with poor isolation discipline, overdue equipment inspection, repeated permit deviations, or weak reporting of changed conditions.

Choose a small set of indicators that connect the commercial promise to field behavior. Examples include the percentage of critical controls verified before start, the age of open high-risk actions, the proportion of scope changes reviewed before execution, and the number of stop-work interventions that received a documented response.

Each indicator needs a definition, owner, evidence source, review cadence, and escalation threshold. Otherwise the number becomes a reporting ritual that cannot guide a decision. The risk criteria discussion helps leadership set those boundaries, especially when a contractor’s performance is acceptable in routine work but weak in a high-consequence task.

250+ cultural transformation projects Across these projects, Andreza Araujo has seen that measurement changes behavior only when leaders use it to change capacity, sequence, or permission. A dashboard that only ranks contractors does not improve the control that caused the ranking.

8. Decide when the contract should not be awarded

The final decision is the one procurement teams often avoid: whether the supplier should not be awarded the work. A clear no-award threshold protects the operation from treating an unresolved control gap as a negotiation detail.

Set the threshold before bids are scored. It may include missing competence for a critical task, inability to demonstrate a required barrier, refusal to accept stop-work terms, material mismatch between the bid and the method, or a commercial price that depends on removing a necessary safeguard.

Use a documented exception process when the business believes the work must proceed. The exception should name the residual exposure, the temporary controls, the accountable executive, the expiry date, and the evidence required to return to the normal standard. A senior signature does not make an unsafe assumption safe, but it does make the decision visible enough to challenge.

That discipline reflects the lesson behind Safety Culture: From Theory to Practice. Culture is not the language used in a supplier meeting. It is the pattern of decisions that remains stable when delivery pressure, cost pressure, and schedule pressure arrive together.

Procurement paperwork versus contractor control

A contractor decision becomes harder to reverse after mobilization, because sunk cost and schedule pressure make weak evidence look more acceptable than it was during the bid.

Conclusion: procurement sets the first safety boundary

Contractor safety improves when procurement defines the exposure, separates eligibility from readiness, buys control capability, tests evidence, and sets a real no-award threshold before mobilization.

Andreza Araujo’s work across 19 countries and her documented 50% reduction in accident ratio over six months at PepsiCo South America show why governance and field execution must stay connected. If your supplier process still measures paperwork more carefully than control capability, start by rewriting one high-risk work package and test every promise before the first shift.