Subcontracting is how the industry flexes - but every subcontracted load carries the subcontractor’s risk profile inside the principal’s reputation and balance sheet. When the subbie’s truck writes off a load or worse, the claimant sues everyone in the chain, and the operator at the top discovers whether their subcontractor vetting was a process or a hope. The insurance questions are the core of that vetting, and they belong in writing, on file, renewed annually.
The legal chain of a subcontracted movement does not protect the principal the way operators assume. The customer contracted with you: you are their carrier, and your conditions of carriage cap your liability to them - but they do not create your subcontractor’s liability to you, nor guarantee the subbie can pay it. If the subcontractor’s goods-in-transit cover is absent, exhausted or repudiated, the shortfall lands on the operator with the deepest pockets and the live policy: yours. The subbie vetting file is, in effect, part of your own insurance arrangements.
The vetting set is short and non-negotiable. The operator’s licence: the O-licence disc check first, because a subcontractor without a valid licence voids everything downstream - including, potentially, their own insurance. Goods in transit insurance: the policy schedule, not the broker’s verbal assurance - with the liability limit per load read against the loads you actually give them, the exclusions read for your freight types, and the territorial cover checked for your lanes. Public liability: the schedule again, with the limit - loading and unloading injuries are the subbie’s risk transferred to your site and your customer. Motor cover: fleet or vehicle, business use, the vehicles they will actually send. Employer liability where they employ drivers: the statutory cover, its certificate current. And increasingly, the evidence that it all stays paid: the mid-term lapse is the classic failure, and the renewal diary - documents re-collected annually, with expiry dates calendared - is what separates a vetting file from a vetting ritual.
Paper verifies better with conversation. Who loads and secures - because the loading negligence exclusions in GIT policies make the answer matter. What is the claims history - disclosed, and weighed against the premium it produced. Are they subcontracting onward - the cascade you did not approve is the risk you cannot see, and your terms should forbid it without consent. And does their cover match your conditions of carriage - the subcontractor trading on no terms who accepts your load accepts it on unbounded liability they cannot insure, which is your problem wearing their name.
Vet subcontractors like insurers: O-licence first, then schedules for goods-in-transit (limit versus your loads), public liability, motor and employer liability, re-collected every year against a calendar of expiry dates. When the subbie’s cover fails, the claim walks upstream - the file you keep is the wall it hits.
The documents only exist if the process demands them, and the working process is boringly simple: no subcontractor hauls until the file is complete - the licence check, the schedules, the signed subcontractor agreement putting them under your conditions of carriage - with the expiry dates logged in a calendar that chases renewals a month ahead. The fleets that run this as an office ritual find the awkward conversations disappear: the subbie who cannot produce a GIT schedule is filtered before the first load rather than after the first claim. The process’s quiet benefit is reputational: the customer who audits your subcontractor control - and the bigger ones do - finds a file instead of a shrug, and the audit question that sinks sloppy competitors becomes your sales line.
The vetting file’s hardest moment is the subbie who fails it: the keen, available haulier whose GIT limit is half your load value, whose policy excludes your freight type, or whose renewal lapsed in the summer. The temptation is the favour - ‘just this once, it’s only a short run’ - and the industry’s claims files are full of the once-only loads that wrote the loss. The working alternative is constructive: tell the subbie what the file needs, give them the broker conversation that fixes it, and add them to the panel when the documents arrive. The subcontractors worth having treat your vetting as a standard to meet, and the ones who resent it are telling you something the file was built to reveal.
Built properly, the vetted subcontractor panel becomes more than compliance - it is surge capacity with known risk: the vetted twenty the office can call at 4pm without a document chase, because the chase happened in January. The fleets with that panel quote peak work confidently, absorb vehicle breakdowns by substitution, and sleep through the season their unvetted competitors spend discovering what their overflow capacity was actually made of. The file cabinet, as usual in this industry, turns out to be a business tool.
Licence first, schedules not promises, GIT limit read against your real loads, expiries calendared and re-collected annually, and no loads before the file is complete. The subcontractor chain is only as strong as its least-insured link - and when a link fails, the claim does not stop to ask whose fault that was. It simply walks upstream to the operator who kept no file.