A subcontractor can send an impressive safety folder without answering the question that matters: can this team carry out this particular job safely, with the people and resources it is proposing?
This subcontractor safety prequalification checklist helps you turn a document request into a practical evidence review. Use it before appointment or mobilisation, with the depth of review matched to the work and its risks.
Start with the job, then request the evidence
Define the activities, locations, equipment, interfaces and expected supervision. A ground-level delivery task and a roof installation package need different evidence. Asking both suppliers for the same large folder can hide the important questions.
HSE’s Using contractors guide covers selecting a suitable contractor alongside risk assessment, information sharing and supervision. Its contractor management principles also address resources, coordination and competence. These are Great Britain sources; verify local legal and client requirements separately for your project, including work in Saudi Arabia.
Subcontractor safety prequalification checklist
Use four evidence outcomes: verified, clarification required, not demonstrated or not applicable with a reason. A certificate received is not automatically a capability verified.
| Review area | Evidence to request | Question for the reviewer |
|---|---|---|
| Defined scope and interfaces | Proposed activities, exclusions, locations and other employers involved | Does everyone describe the same job? |
| Relevant experience | Comparable work examples and references that can be checked appropriately | Is the experience relevant to the proposed method and environment? |
| Named supervision | Proposed supervisor, responsibilities, availability and escalation arrangements | Who will direct the crew when work fronts change? |
| Worker competence | Role-specific training, experience and authorisation evidence where required | Does it cover the actual people, task and equipment? |
| Work planning | Relevant assessment and method examples, plus a plan for project-specific preparation | Can the subcontractor explain the critical controls? |
| Equipment readiness | Equipment list and applicable maintenance, inspection or examination records | Do records match the equipment proposed and its intended use? |
| Emergency arrangements | Task-specific emergency needs, response roles and coordination with the site | Are people, equipment and responsibilities realistically available? |
| Learning and improvement | Proportionate incident information, corrective-action examples and evidence of follow-up | What changed after a problem, and was the change checked? |
| Lower-tier subcontracting | Any proposed further subcontractors and how their work will be controlled | Will a different team arrive from the one assessed? |
| Mobilisation and monitoring | Induction plan, coordination meetings, reporting arrangements and inspection responsibilities | How will capability be checked in practice after appointment? |
Include licences, registrations, insurance or client approvals when they apply to the package. Check the relevant scope, validity and issuing evidence. Do not present one country’s certification scheme as a universal requirement.
How to review the submission
1. Check that the evidence belongs to the proposed team
Match names, roles, equipment identifiers and company details where relevant. Check dates and limitations. Keep only the information needed for the review, and restrict access to personal records. A generic company training matrix may not show whether the assigned crew meets the task requirements.
2. Ask for an explanation, not another attachment
Choose a realistic task interface and ask the proposed supervisor how it would be managed. For example: “A delivery blocks the planned access route while your team is working. Who coordinates the change, and what must be checked before you continue?” Assess the answer against the project’s arrangements.
3. Set conditions that can actually be closed
Replace “submit all documents ASAP” with a defined gap, owner, due point and acceptance evidence. Separate an administrative clarification from missing evidence about a critical work control. Do not let an overall score hide a serious unresolved issue.
Worked review example
Fictional procurement example: A roof-access installation subcontractor provides company policies, comparable experience and worker training records. However, the named supervisor is not confirmed and the proposed task-specific emergency arrangements are incomplete.
Review note: “Capability review remains open for this package. Subcontractor manager to confirm the assigned supervisor and submit the task-specific emergency arrangements for review before mobilisation release. Reviewer to verify that the proposed people and resources are available. No work-start authorisation issued by this review.”
The review does not invent a rescue method or assume that a training certificate resolves the missing plan. It identifies what must be demonstrated and when.
A simple decision and close-out record
| Field | Record |
|---|---|
| Package identity | Subcontractor, project, scope, assessment date and reviewer |
| Evidence reviewed | Document references, revisions, relevant dates and checks performed |
| Gaps and conditions | Specific concern, owner, due point and required evidence |
| Decision | Accepted for defined scope, pending clarification or not accepted, with reasons |
| Restrictions | Excluded activities and conditions that must be resolved before release |
| Verification | Who checked closure, what evidence was seen and when |
| Review trigger | Changed crew, equipment, scope, supervision or material performance concern |
What happens after prequalification?
Confirm project-specific planning and readiness before the affected work begins. On arrival, check that the crew and equipment match the reviewed proposal. Use our construction site safety induction checklist for the site briefing and understanding checks.
Continue supervision, coordination and monitoring while the work is underway. If the method, supervisor or subcontracting arrangement changes, review the relevant evidence again. A supplier’s earlier acceptance is not a permanent approval for every activity.
Common questions
Is an ISO certificate enough?
It may support the review, but it does not by itself demonstrate the competence of a particular crew or the suitability of a proposed work method. Verify relevance, scope and the task-specific evidence.
Should a small subcontractor provide the same documents as a large company?
Request proportionate evidence of safe capability. A concise, relevant explanation backed by records may be more useful than a large generic manual. Applicable requirements still need to be met.
Can a high checklist score override a critical gap?
No. Treat unresolved critical-control evidence as a decision issue in its own right. Record the restriction and the evidence needed before the relevant work is released.
Before signing the review: Can you explain why this subcontractor is suitable for this scope, what remains open and how the actual work will be monitored? Keep that reasoning with the record.