Build a contractor document requirements matrix by work package
One generic “contractor documents” checklist can under-ask a high-risk trade and over-ask a low-risk service provider. A document requirements matrix starts with the work and records what each evidence request is meant to establish, who reviews it and when it must be accepted. It gives the supplier a clear request and the buyer a defensible decision trail.
The matrix is a procurement and operational tool, not a statutory schedule of universal documents. Requirements vary with the legal entity, trade, site, contract and activity. HSE's Using contractors guidance says the buyer should identify the job and satisfy itself that the contractor can do it safely; the degree of competence and supporting evidence depends on the work.
Start with tasks, not file types
Define the work packages separately: for example, routine cleaning, electrical installation, roof access, lifting, design services or maintenance in an occupied building. For each package, record who the supplier will be, whether it will subcontract, the site, work dates, foreseeable hazards and any role it will hold under the contract or law.
Next write the decision the evidence will support. A certificate may show an organisation's assessed status; it does not by itself show that a named worker can perform this task. An insurance certificate may show a policy exists; it may not prove a particular activity is covered. A RAMS document may exist; the site team must still check that it fits current conditions. Request the item that addresses the specific question, not every PDF the organisation has ever uploaded.
Use a compact matrix
| Work-package question | Possible evidence | Reviewer and stage | What the record must say |
|---|---|---|---|
| Is this the supplier that will contract and work? | Legal-entity details, trading-name explanation | Procurement, before selection | Entity accepted and matched to contract. |
| Does relevant insurance meet this contract? | Policy schedule, certificate or broker clarification | Procurement/insurance reviewer, before award or mobilisation | Insured entity, work, limits, dates and unresolved exclusions. |
| Can this firm manage the proposed work? | Relevant experience, current assessed status, references | Commercial and H&S reviewer, before award | Scope and limits of the evidence. |
| Can named people perform the task? | Role-specific qualifications, training, experience or authorisation | Site/project reviewer, before the task starts | Which people and activities were checked. |
| Is the method suitable for this location? | Task/site RAMS, permit or specific plan where required | Competent site reviewer, before the task starts | Version, conditions and briefing decision. |
These are examples, not an instruction to require every item for every contractor. Add a column for source of requirement: law, buyer policy, contract, client specification or site risk assessment. If a request cannot be explained, reconsider whether it is proportionate. If a legal or contractual requirement applies, do not quietly drop it merely to shorten the form.
Separate the two review stages
Organisation-level prequalification asks whether the supplier is suitable to appoint. A start-work check asks whether the current people, method, site arrangements and documents are ready for the particular activity. SSIP client guidance makes this distinction for health and safety assessments: an initial scheme check leaves work-specific experience, trained people and resources to verify. HSE's construction planning guidance likewise places planning and coordination before the construction phase.
Put the required stage in the matrix. A buyer might review financial standing before selection, then inspect site-specific RAMS only when the scope is sufficiently defined. But an essential condition must still be closed before the activity it controls. The conditional contractor approval guide explains how to record a missing item without silently releasing work.
Keep the supplier request intelligible
Send the supplier the work package, exact item, accepted alternatives, reference period or expiry requirement, due date and a person who can answer questions. Avoid vague requests such as “all compliance documents”. For group companies, say which legal entity must hold the policy or accreditation. For multiple sites, say whether one organisation-level document may be reused and which site-specific additions remain necessary.
When an item arrives, record accepted, clarification required or rejected for this package, with the document version and reviewer reason. If the work changes materially, revisit only the affected rows. Do not let an old generic approval override the requirements of a new high-risk activity.
The general subcontractor prequalification checklist describes common request categories. This matrix has a narrower job: decide why, when and by whom an item is required. If evaluating contractor prequalification software, ask the vendor to show how work-package requirements, evidence versions and review decisions are represented. Complys does not itself define your legal requirements or guarantee that a file proves competence.
Primary sources and owner gate
- HSE — Using contractors: job definition, proportionate selection evidence and contractor coordination.
- HSE — Planning for construction work: information and arrangements before work begins.
- SSIP — Clients: organisation assessment and separate project-specific checks.
Before integration: Compare the whole current prequalification checklist, onboarding checklist and sector trade checklists. If one already serves the buyer's work-package matrix task fully, merge this material into that owner and do not create another generic checklist result.
Organise the records this involves
Complys gives you one place to store, track and share the compliance records and evidence described here. Legal and assessment decisions stay with you and the relevant authority.
Explore Contractor Prequalification Software →