
Contractor preparation checklist
Select a trade, review the relevant preparation points and download your checklist.
Explore →
SOURCING FORCE ONSITE · BME CONSULTING
Build contractor checks around the company, contract and actual UK work. Separate identity and tax verification from insurance, competence and site preparation, and retain evidence of what was checked.
01 · YOUR PROJECT
A UK contractor file should be built around the service and contracting parties, rather than the value of the latest invoice. France’s €5,000 excluding-VAT vigilance threshold is not a UK contractor-checking threshold. Determine the work, who appoints and pays the company, the jurisdiction and any construction tax requirements before deciding what evidence and checks are needed.
For an occasional intervention, link the accepted quotation, known variations and service scope to the order. For an evolving contract, review the scope and calendar at each extension. Following the contractual relationship is more reliable than treating a small monthly invoice as proof that no checks are needed. It also reveals when a short assignment becomes a recurring service.
Illustrative example, unrelated to a client reference: a £6,000 service paid in three £2,000 instalments is still a £6,000 contractual requirement. That total is relevant to the purchase, but is not a universal UK legal trigger. Assess whether the actual work and payer fall within CIS and what site, competence and insurance checks are required.
02 · YOUR PROJECT
Identify the legal entity named in the contract and its business form. For a UK limited company, company details can be checked through Companies House; a sole trader does not have the same incorporation file. Where CIS applies, the responsible contractor considers registration and HMRC verification. These checks serve different purposes and should not be described as a British URSSAF certificate.
Build the file around the actual contracting identity. A trading name, former establishment or group logo is not enough to identify the counterparty. Following a company change, merger or replacement subcontractor, reconcile documents with the new relationship. For an overseas company working in the UK, assess the applicable registration, tax and local requirements rather than mechanically copying a UK company checklist.
03 · YOUR PROJECT
A received document and a completed verification are distinct records. Check identity information against the appropriate official source and assess whether a certificate or policy document belongs to the company engaged. If CIS applies, HMRC verification establishes the relevant payment treatment; it does not certify technical competence or health and safety.
A useful circuit holds both the evidence received and a record of the action taken. Record the date, checker, entity and result. Route anomalies to a queue visible to purchasing. An unreadable document, mismatched registration number or unresolved verification requires an explicit action rather than a default approved status.
For several sites, define who carries out checks and who can see the result. The user site needs the file’s status before receiving the company; finance needs to distinguish a payment issue from a missing technical acceptance. A shared record helps teams work from the same information rather than circulate divergent copies by email.
04 · YOUR PROJECT
Do not import France’s statutory six-month vigilance cycle as a blanket UK rule. Set reviews according to the actual requirements, document validity, contract duration and changes. Where CIS applies, HMRC requires verification of a new subcontractor and certain previously used subcontractors; its specific rules should guide that check rather than an invented universal expiry.
The schedule should follow operational reality. Update the end date when work is extended and document closure when it is finished. When several sites use one company, identify which contracts remain active. Avoid a single supplier expiry date that obscures policy renewals, changing teams or task-specific evidence for separate interventions.
A proposed organisation is for purchasing to follow contract dates, a document manager to chase missing evidence and a designated specialist to resolve anomalies. Define when to inform the site, contact the company or request legal or tax review. This is a working method, not a new legal threshold or a substitute for the rules applicable to the relationship.
05 · YOUR PROJECT
Failures can create contractual, tax or regulatory exposure according to the facts and applicable rules. A missing file item does not automatically mean the same fine or consequence in every case. Explain which check is outstanding, why it matters and who must decide the next step instead of promising that use of a document platform removes all risk.
Identity and tax verification do not approve the technical intervention. They do not establish that insurance covers the ordered trade, workers have the necessary competence or overlapping activities are safely prepared. Keep those topics as separate parts of the file. A correctly identified company may still require substantial site and safety preparation.
06 · YOUR PROJECT
OnSite organises document collection, review dates and traceability within the agreed scope, including through Vigilegal. The contract identifies the counterparties, who performs each check and which records are available to the client. The client retains obligations linked to its role and site; platform follow-up does not remove those responsibilities.
For a selected company, OnSite offers administrative onboarding within 24 hours with an actionable file and the necessary approvals. Sourcing depends on the specification. The administrative or sourcing fee is 3–12% excluding VAT according to scope. These commercial conditions do not waive checks needed before an intervention or payment under the actual arrangement.
YOUR NEXT PROJECT
Describe the trade, UK site and dates. Jonathan Morris discusses onboarding or sourcing with you.
Discuss my project