Why Contractor Safety Management Often Stops at Document Compliance
Most contractor files are complete. Far fewer show that the person at the task can perform it safely.
Ask a site to show its contractor safety management records and you will usually see a well-organised folder: prequalification questionnaires, insurance certificates, safety statistics, induction attendance sheets and training certificates for every worker on the gate list. Then ask a different question: For the crew on the high-risk job in Unit 3 right now, who confirmed that each person can actually do that task safely, and how? On many sites, the answer is a stack of certificates, not a record of anyone observing the work.
This matters because contractors often carry out the work with the highest exposure: turnarounds, confined space entry, lifting, hot work, line breaking, scaffolding and commissioning. When the evidence behind a contract worker’s authorisation is a document check alone, the organisation is relying on a training provider’s assessment that may be months or years old and may have been made at a different site, with different equipment and different procedures.
Document compliance is necessary. It confirms that a contractor is legally entitled to work, insured, trained and inducted. What it does not confirm, on its own, is that a particular person can perform a particular high-risk task, on this site, under these conditions, today.
Contractor safety programmes are usually built around procurement and mobilisation. A contractor is prequalified, a contract is awarded, workers are registered, documents are uploaded, an induction is delivered and a gate pass is issued.
Field competency is harder to evidence. It requires a competent person to observe a worker performing the task against defined criteria and to record the result. It takes supervisor time when schedules are tightest, so it is often the first step to be compressed.
The result is a system that measures what is easy to collect. Dashboards report the percentage of workers with valid certificates and completed inductions. They rarely report the percentage of workers performing safety-critical tasks who have been verified in the field for those tasks.
The consequences extend beyond audit findings. The International Labour Organization estimates that around 2.93 million people died from work-related accidents and diseases in 2019. [1] That figure is not specific to contractors, and no single statistic isolates competency failures. But contractor work is concentrated in high-hazard activities, and when an investigation finds that a worker held the required certificate but lacked the practical capability for the task, the same gap is exposed: the paperwork was in order, but performance was never verified.
Why a Valid Certificate Is Not the Same as Field Competency
Four recurring patterns can create a gap between a complete contractor file and a competent worker at the task.
Certificates describe training, not task performance
A certificate shows that a person attended a course and met the provider’s assessment criteria on a given date. It does not show how recently they performed the task, or whether they understand your site-specific procedures, permit requirements and emergency arrangements. Some certificates are expired, issued for a narrower scope than the work requires, or not genuine, and a document review that does not check the issuing body’s records may not detect this.
Prequalification assesses the company, not the crew on shift
Prequalification typically reviews a contractor’s safety management system, past performance, insurance and policies. That is a sound basis for selecting a company. It says little about the specific supervisor and crew who arrive on the night shift during a turnaround, particularly when the contractor relies on subcontractors or short-term labour to meet peak demand.
Mobilisation pressure compresses verification
Turnarounds and project peaks can bring hundreds of contract workers to site within days. Inductions are delivered to large groups, document checks are prioritised to clear gate access, and field verification is deferred to the expectation that supervisors will monitor performance. The first days of a turnaround are often when verification is thinnest.
Competence is assumed to transfer between sites and roles
A rigger who has worked safely on one site is not automatically competent on another with different cranes, lift plans, communication protocols and ground conditions. A worker competent as a confined space entrant is not automatically competent as a standby attendant or gas tester. Competence is specific to the role and the task, and the evidence needs to match.
What Regulations and Standards Already Expect
The expectation that contractor competence should be verified, not just documented, is not new. Several regulatory and standards sources already point beyond document collection. The summary below is not exhaustive; organisations should consult the current text of each source and the requirements of their own jurisdiction.
Source | Applicability | What it expects |
OSHA 29 CFR 1910.119(h) | Mandatory in the U.S. for processes covered by the PSM standard. Paragraph (h) applies to contractors performing maintenance, repair, turnaround, major renovation or specialty work on or adjacent to a covered process, not to incidental services such as janitorial, food or delivery services. | The host employer must evaluate a contractor’s safety performance and programmes when selecting contractors and periodically evaluate their performance. The contract employer must train each contract employee and document the training, including the means used to verify that the employee understood it. [2] |
ISO 45001:2018, clauses 7.2 and 8.1.4.2 | Voluntary management system standard. It becomes a requirement where an organisation is certified to it or has committed to it contractually. | Determine the necessary competence of workers, ensure they are competent on the basis of education, training or experience, and retain evidence. Coordinate procurement with contractors to identify hazards and control risks arising from contractor activities. [3] |
CDM 2015, regulation 8 | Legal requirement for construction projects in Great Britain. | Anyone appointing a designer or contractor must take reasonable steps to satisfy themselves that the appointee has the skills, knowledge and experience, and, for an organisation, the organisational capability, to fulfil the role. [4] |
HSE UK, HSG159 | HSE guidance, not law. Following HSE guidance is normally enough to comply with the law in Great Britain. | Addresses planning, selection, site induction, supervision, monitoring and review of contractor work. [5] |
ILO Convention 155, Article 17 | Binding on states that have ratified it and applied through national law. It does not place duties directly on companies. | Where two or more undertakings work simultaneously at one workplace, they shall collaborate in applying the Convention’s requirements. [6] |
CCPS, Risk Based Process Safety | Industry good-practice guidance for process safety. Not a regulation. | Treats contractor management and training and performance assurance as separate elements, recognising that training alone does not establish that personnel can perform as required. [7] |
Read the OSHA requirement carefully. Paragraph (h)(3)(iii) does not ask only for a training record. It requires the contract employer to record the means used to verify that each contract employee understood the training. A signed attendance sheet records presence; it does not, by itself, record verification. The standard applies to covered PSM processes, but the principle is useful well beyond them. [2]
OSHA’s multi-employer citation policy also makes clear that responsibility on a shared worksite does not sit with one party alone. Depending on its role and the reasonableness of its actions, a controlling employer may be cited for hazardous conditions to which other employers’ workers are exposed. [8]
The policy is an enforcement directive for federal OSHA; state-plan states may apply their own equivalent policies. This summary is not legal advice. Which requirements apply depends on jurisdiction, industry, the type of work and contract terms.
The Contractor Competency Gates: Four Gates From Prequalified to Proven in the Field
The Contractor Competency Gates is a proposed practical framework for asking how much evidence exists that a contract worker can safely perform a specific high-risk task. It is not a model prescribed by OSHA, ISO, HSE or CCPS. Each gate builds on the previous one. In practice, most contractor programmes are strongest at Gates 1 and 2 and weakest at Gates 3 and 4.
Gate | What it means | Example evidence |
1 Company capability | The contracting company has been assessed as capable of managing the risks of the work it will perform. | Prequalification review, safety programme evaluation, past performance, references and contract HSE requirements. |
2 Individual credentials | The individual holds the qualifications, certificates, fitness for work and site induction required for the role. | Certificates validated against the issuer, scope checked against the assigned tasks, induction and fitness-for-work records. |
3 Task verification | A competent person has observed the individual performing the specific high-risk task, on this site, against defined criteria, before unsupervised work. | Gate 3 verification record with the mandatory fields listed in section 4.3. |
4 Sustained performance | Performance is monitored during the work, and authorisation is reviewed when observations, incidents or changes indicate a concern. | PTW audits, field observations, Near Miss and incident links, CAPA records, suspension, reassessment and reinstatement records. |
Gate 3 is where document compliance becomes field competency
Gate 3 is the step most often missing. It does not require a full reassessment of every worker for every activity. It requires the organisation to identify the tasks where a competency failure could cause serious harm, define what competent performance looks like for each, and verify it in the field before a worker performs that task without close supervision.
Practical assessment criteria
Criteria should be written so that two competent assessors observing the same performance would reach the same result. In practice, that means criteria that are:
Task-specific: tied to a defined role, such as standby attendant, gas tester or rigger, rather than a general trade.
Observable: written as actions the worker performs or explains, such as “checks each isolation point against the isolation certificate before signing,” not “understands isolation.”
Site-specific: covering local procedures, permit requirements, communication methods and emergency arrangements.
Inclusive of abnormal conditions: covering what the worker does when an alarm activates, conditions change or a step cannot be completed as planned.
Assessed with the actual equipment: the gas monitor, rescue equipment or lifting gear the worker will use on this site.
Some criteria should be designated critical. For a confined space standby attendant, these would typically include the response to a gas monitor alarm, the conditions for ordering evacuation and how to initiate the site’s rescue arrangements. Not meeting a critical criterion should result in a fail, whatever the rest of the performance looks like.
Mandatory evidence fields for a Gate 3 record
A verification that cannot be reconstructed later is difficult to rely on. Each Gate 3 record should capture, at minimum:
Field | What to record |
Worker and employer | Full name, unique ID, direct employer and the contracting chain (main contractor, subcontractor or labour agency). |
Task and role | The specific safety-critical task verified, such as “standby attendant, vessel entry,” not a general trade title. |
Location and equipment | Site, unit or area, and the equipment models used during the assessment. |
Criteria reference | The assessment checklist used, including its version, and the result against each critical criterion. |
Assessor | Name, role and the basis of the assessor’s own competence to verify this task. |
Method | Observation of live work, practical demonstration, simulation or structured questioning, alone or in combination. |
Outcome and conditions | Pass, conditional approval, fail or reassessment required, with any restrictions and close-out dates. |
Dates and validity | Assessment date, expiry or revalidation date, and the events that would trigger earlier reassessment. |
Competency assessment decision matrix
Every Gate 3 assessment should end in one of four defined outcomes, each with a clear authorisation status. The thresholds below are illustrative; organisations should define their own in their contractor management procedure.
Outcome | When it applies | Authorisation status | Required action |
Pass | All criteria met, including every critical criterion. | Authorised for the verified task, within any stated limits. | Record the result, set the revalidation date and make the status visible to permit issuers. |
Conditional approval | All critical criteria met, with minor gaps in non-critical criteria. | Authorised only under defined conditions, such as direct supervision, reduced scope or a set period. | Record the conditions and a close-out date. Reassess before conditions are lifted. Authorisation lapses if conditions are not closed out. |
Fail | Any critical criterion not met, or several non-critical gaps. | Not authorised for the task. | Record the gaps, assign training or coaching through a CAPA and schedule reassessment. |
Reassessment required | Verification expired, or triggered by change, extended absence, a Gate 4 concern or return after suspension. | Paused or restricted, as defined in the procedure, until reassessed. | Reassess against current criteria before the worker resumes the task without close supervision. |
Gate 4: suspension, corrective action, reassessment and reinstatement
Verification is a point-in-time judgement. Gate 4 connects it to what happens next. When field evidence raises a concern about a worker’s competence for a task, the response should follow a defined workflow rather than an informal conversation. Suspension in this sense is a safety measure, not a disciplinary one, and it should be communicated that way.
Step | What happens | Evidence |
1. Trigger | A PTW audit finding, field observation, Near Miss, incident, failed verification or relevant change raises a concern about competence for a specific task. | Trigger record linked to the worker and the task. |
2. Suspend or restrict | The authorisation for the affected task is suspended or restricted immediately, in proportion to the concern, and permit issuers are informed. Other authorisations are reviewed, not suspended automatically. | Scope of suspension, reason, decision-maker and effective time. |
3. Investigate and CAPA | The cause is established proportionately, with an RCA where warranted. The CAPA may address the individual, the criteria, the procedure or the contractor’s arrangements; not every gap is an individual failing. | Investigation notes; CAPA with owner, actions and due date. |
4. Reassess | Once the CAPA is complete, a competent assessor re-verifies the task against current criteria, preferably someone not involved in the original finding. | New Gate 3 record. |
5. Reinstate or remove | An authorised person reinstates the authorisation, fully or conditionally, or confirms that the worker remains unauthorised for that task. The full history is retained. | Reinstatement decision with name, date and any conditions. |
Applying the gates to subcontractor tiers
Many contract workers are not employed by the contractor the organisation selected. Turnaround and EPC workforces often include second- and third-tier subcontractors and labour supplied through agencies, some of which never pass through the host’s prequalification. The gates should apply to every worker who performs a safety-critical task, whatever the employer tier:
Flow-down: contracts require the main contractor to apply equivalent Gate 1 to Gate 3 controls to its subcontractors and to declare each subcontractor before mobilisation.
Worker-level visibility: each worker’s record shows the actual employer and the contracting chain, not only the main contractor.
Host sampling: the host independently checks a sample of subcontractor Gate 3 verifications, weighted toward safety-critical tasks and newly engaged subcontractors.
Records follow the person: when a worker moves between contractors, their verification and suspension history moves with them rather than resetting.
A proposed rule for task authorisation
For tasks an organisation designates as safety-critical, this framework recommends that a contract worker be authorised to perform them without close supervision only when a current Gate 3 pass or conditional approval exists and there is no unresolved Gate 4 suspension. This is a proposed governance rule, not a requirement stated by any regulator or standard. Organisations should adopt it through their own contractor management and permit-to-work procedures, including a clear definition of who is competent to verify.
This is the gap the Soapbox Contractor Management module is intended to address: bringing each contract worker’s credentials, field verifications and permit records together so that authorisation reflects what has been demonstrated, not just what has been uploaded.
Three Field Scenarios Where the Documents Were Valid but the Competency Was Not
The following are illustrative scenarios, not claims about a specific site or incident. Each shows how a complete contractor file can coexist with a gap in field competency.
Turnaround confined space entry
Field scenario
A certified attendant who cannot initiate the rescue
During a refinery turnaround, a contractor supplies standby attendants for vessel entries. Every attendant holds a current confined space certificate, and the permit names the attendant. On the second night shift, the area authority asks the attendant at a column entry to show how the four-gas monitor alarm is acknowledged and what happens if an entrant becomes unresponsive.
The attendant has not used that monitor model before and is unsure how to call the rescue team, because the site’s arrangements differ from those at the attendant’s previous site. The certificate was valid. The site-specific capability had never been verified.
The entry is paused until the attendant is briefed and verified on the equipment and rescue arrangements. The lasting correction is a Gate 3 verification for every attendant before their first entry, with rescue initiation as a critical criterion, visible to the permit issuer before entry is authorised.
Lifting operations on an EPC site
Field scenario
A genuine rigger card with the wrong scope
A subcontractor rigger with a third-party certification card is assigned to rig a fabricated spool for a mobile crane lift. The lift supervisor notices that the rigger has selected slings without accounting for the sling angle in the approved lift plan, which would increase the load on each leg beyond what the plan assumed.
A check with the card issuer shows that the card is genuine but covers a lower category of rigging than the lift requires. The document check at mobilisation confirmed that a card existed; it did not compare the card’s scope with the tasks the worker would be assigned.
The correction is to map each rigging role to the required certification scope, validate cards with the issuer, and add a Gate 3 practical check of sling selection and load calculation for critical lifts.
The auditor’s request
Field scenario
Twelve months of hot work roles
An auditor asks for every contract worker who acted as fire watch or gas tester for hot work in the previous 12 months and, for each, evidence that they were competent for that role on the date of the permit.
The team spends several days matching permit records to gate access lists, training matrices and contractor submissions. Training certificates exist for most workers. Field verification records exist for few, and where they do, they are paper forms filed by contractor rather than by worker. Some workers moved between contractors during the year, and their records did not follow them.
The central finding is not that the workers were incompetent. It is that the organisation cannot demonstrate whether they were competent for the role on the day. For an auditor, an investigator or a regulator, that gap is itself the finding.
Measuring Field Competency as a Leading Indicator
Contractor safety performance is often measured through lagging indicators such as recordable injury rates by contractor. These have value, but they arrive after harm. API RP 754 distinguishes process safety indicators suitable for public reporting (Tiers 1 and 2) from those intended for internal use (Tiers 3 and 4), and its fourth edition was published in August 2026. [9] The competency measures below are proposals that can complement internal indicators; they are not API RP 754 metrics.
The Field Verification Rate
The primary measure proposed here is the Field Verification Rate: the percentage of contractor authorisations for designated safety-critical tasks that are supported by a current Gate 3 pass or conditional approval for that specific task.
Field Verification Rate = (Safety-critical task authorisations with current field verification ÷ Total safety-critical task authorisations) × 100
The denominator should count task authorisations rather than workers, because one worker may hold several. Reporting by contractor, subcontractor tier, task type and shift shows where verification is weakest, which is often the night shift and the first days of mobilisation.
Supporting competency KPIs
A single rate can be met on paper. These supporting measures show whether the verification behind it is timely, consistent and acted upon:
KPI | Definition | What it reveals |
Verified before first task | Percentage of safety-critical authorisations where Gate 3 was completed before the worker first performed the task. | Whether verification happens before exposure or after it. |
First-time pass rate | Percentage of Gate 3 assessments passed at the first attempt, by contractor and task. | Quality of contractor training and pre-mobilisation preparation. A rate close to 100% may also signal weak assessments. |
Conditional approvals closed on time | Percentage of conditional approvals closed out by their due date. | Whether conditions are managed or forgotten. |
Subcontractor verification coverage | Field Verification Rate calculated for subcontractor and agency workers only. | Whether lower tiers are verified to the same standard as the main contractor. |
Competency suspensions | Suspensions per 100 safety-critical authorisations, with average time to reinstatement or removal. | Where performance gaps cluster and whether CAPA closes them. |
Assessment consistency | Percentage agreement when a sample of verifications is independently reassessed. | Whether assessors apply the criteria consistently. |
These measures should be read together. Targets that reward a high Field Verification Rate on their own can encourage rushed sign-offs; a rising rate with falling assessment consistency is not progress.
Three operating rules
Verification is tied to the task, not the badge. A worker verified as a gas tester is not automatically verified as a fire watch or standby attendant. Authorisation records should name the task.
Field findings reach the individual record. When a PTW audit, observation, Near Miss or RCA identifies a competency gap, it is linked to the person and the authorisation and handled through the Gate 4 workflow.
Change triggers review. New equipment, procedures revised through MOC, a change of employer or a long gap since the task was last performed should prompt reassessment where the existing verification may no longer be valid.
What Mature Organisations Do Differently
Organisations with strong contractor safety performance treat contractor management as part of operations rather than a purely procurement or administrative function. They define a list of safety-critical tasks that require field verification, rather than attempting to verify everything. They describe competent performance for each task in observable terms, and they designate and train the people who are competent to verify it.
They plan verification capacity into turnaround and project schedules, including the first days of mobilisation and night shifts, instead of expecting supervisors to absorb it. They hold contractor supervisors accountable for verifying their own crews and audit a sample of those verifications themselves.
They also connect contractor records to the operational processes that reveal performance: permits, SIMOPS reviews, inspections, observations, Near Miss reports, incident investigations and CAPA. When a worker’s competency is questioned, the people issuing permits can see it. When a contractor’s crews repeatedly show the same gap, the finding reaches the contract owner and the contractor’s management, not just the individual.
The Question a Document-Based Contractor Register Struggles to Answer
That question is this:
The question
“For every contract worker on site today, which safety-critical tasks are they authorised to perform, what field evidence shows they were verified for each task on this site, and is any of that evidence expired, restricted or linked to an open CAPA?”
A spreadsheet can hold the gate list, training matrix, certificate expiry dates and permit log. With careful design, it can also cross-reference them. The difficulty arises when contractors submit records in different formats, workers move between employers, field verifications are recorded on paper, and permit issuers cannot see a worker’s verification status at the point of authorisation. Manual reconciliation then becomes slow and error-prone, usually when the answer is needed most.
An integrated HSE platform can support a stronger process when it links each contract worker to their credentials, task-specific verifications, permits, observations and corrective actions, and makes that status visible to the people authorising work. The technology does not replace competent assessors or management follow-through. It makes their work traceable and usable at the point of decision.
If your team can answer the question quickly and reliably, your contractor safety management is measuring competency. If it takes days, it is measuring documents.
About the author
Hasan Ahmed Sayed is an HSE professional with more than 12 years of experience across construction, EPC, industrial, shutdown and turnaround projects. As an HSE SME at SoapBox Software Solutions LLP, he brings field experience into the design of digital HSE requirements, workflows and assurance practices.
Continue reading
Explore the platform: Contractor Management module
Get involved early: SoapBox Early Adopters Programme (EAP)
References
The links below support the factual statements and standards references in this article. Always consult the applicable current edition of a standard or regulation when establishing compliance requirements.
[1] International Labour Organization (2023), A Call for Safer and Healthier Working Environments. https://www.ilo.org/publications/call-safer-and-healthier-working-environments
[2] OSHA, 29 CFR 1910.119 — Process safety management of highly hazardous chemicals. See paragraph (h), Contractors, including (h)(2) and (h)(3)(iii). https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.119
[3] ISO 45001:2018, Occupational health and safety management systems. See clauses 7.2 (Competence) and 8.1.4.2 (Contractors). https://www.iso.org/standard/63787.html
[4] The Construction (Design and Management) Regulations 2015, Regulation 8 — General duties. https://www.legislation.gov.uk/uksi/2015/51/regulation/8
[5] Health and Safety Executive (2011), HSG159: Managing contractors — A guide for employers. https://www.hse.gov.uk/pubns/books/hsg159.htm
[6] International Labour Organization, C155 — Occupational Safety and Health Convention, 1981, Article 17. https://normlex.ilo.org/dyn/nrmlx_en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:C155
[7] Center for Chemical Process Safety / AIChE (2007), Guidelines for Risk Based Process Safety. https://www.aiche.org/ccps/resources/publications/books/guidelines-risk-based-process-safety
[8] OSHA, CPL 02-00-124 — Multi-Employer Citation Policy. https://www.osha.gov/enforcement/directives/cpl-02-00-124
[9] American Petroleum Institute (6 August 2026), API Publishes Fourth Edition of Process Safety Performance Indicators Standard (API RP 754). https://www.api.org/news-policy-and-issues/news/2026/08/06/api-publishes-fourth-edition-process-safety-performance-indicators-standard
