Mid-afternoon, and the customer wants to know where their delivery is. If it is on one of your own vehicles, the office can see the job, the driver’s current position and the latest ETA. If it is on a subcontracted leg, the answer often becomes a phone call: your office calls the subcontractor, they contact their driver, and the customer waits for an update.
That is the shape of the subcontractor tracking problem for operations that flex capacity with sub-hauliers: visibility ends at the yard gate. The moment a job leaves on someone else’s truck, the operation is back to phones and promises. The customer, meanwhile, neither knows nor cares whose truck it is. They bought a delivery from you.
Why subcontractor tracking breaks
The gap is structural, not a people problem, which is why it has survived so long.
You cannot fit your telematics to their trucks. Hardware belongs to a vehicle and a contract. A sub-haulier who works for six operators cannot carry six trackers, and nobody pays to fit hardware to a truck they use eight days a month.
Software licences make casual capacity expensive. If seeing a subcontractor means buying them a licence on your system, the sums stop working for exactly the flexible, occasional relationships subcontracting exists for.
So the updates go informal. A message at collection. A call at delivery, if you are lucky. A POD that arrives as a photograph days later, if it arrives at all. Every update is a person interrupting another person. Every quiet hour in between is a gap the office fills with guesswork.
And the invoice can wait for the paperwork. For operators that invoice once proof of delivery is received, a late subcontractor POD can delay the billing process too, so the informal channel does not just cost visibility. It can stretch your own cash cycle, one late photograph at a time.
What the gap costs
The direct cost is office time: the calling, the chasing, the calling back. The larger cost is commercial. UK haulage runs on thin margins, around 2% according to the RHA’s 2025 Annual Cost Movement Survey, and at margins that thin, service failures are expensive wherever they land. Subcontracting exists to protect service on work you cannot cover. A subbed leg the office cannot see can end up doing the opposite, quietly, on the jobs where your name is most exposed.
There is a record-keeping edge to it too. The delivery record on a subbed job is only as good as the paperwork that eventually comes back. A photographed POD in a message thread is evidence of a sort. A signed, time-stamped ePOD attached to the job record gives the office a clearer record to answer delivery queries and support disputes.
What good subcontractor tracking looks like
Whatever system you evaluate, ours included, the requirements are the same five. Test each one live, on a subbed job, in the demo.
| Stage | How it runs today | What to require |
|---|---|---|
| Assigning the job | An email or call to the subbie’s office, often re-keyed into another system or managed outside the main transport plan | same screen — Subcontracted legs planned on the same screen as your own fleet, one plan for the whole job |
| The driver’s copy | Forwarded messages; the driver works from a screenshot | own phone — The sub driver gets the job on an app on their own phone, no hardware fitted, nothing to install in the truck |
| En route | Silence, then a call when someone worries | live position — Where mobile tracking is enabled, position and current ETA visible to the office alongside your own work |
| At delivery | A POD photo in a message thread, days later, if it arrives | epod at delivery — Signed ePOD captured at delivery, attached to the job and synced to the office when connected |
| The commercial loop | Invoice waits on paperwork; the customer waits on you | low friction — Low-friction access for occasional subcontractor drivers, without fitting vehicle hardware, so the job completes and bills like any other |
HaulierMagic can keep subcontracted work inside the same operational flow as your own jobs. Subcontracted legs are planned alongside your own fleet, and subcontractor drivers can use the Driver App on their own phones to receive work and capture proof of delivery, without specialist hardware in the vehicle. Where mobile tracking is enabled, the office can follow progress alongside its own work. The ePOD is captured against the job and syncs back to the office when connected, reducing the chasing of separate POD photos and message threads. If customer self-service is part of the requirement, ask to see the Client Portal and the customer view separately in the demo, and confirm exactly what the customer can see. For a Transport Manager consolidating a fragmented operation, this is one of the joins that matters most; our case to the consolidation-minded TM sets out the rest.
Testing it before you buy
Subcontractor tracking is exactly the kind of claim that survives a standard demo and fails on real work, so script it yourself. Bring a genuine multi-leg job with a subbed middle leg. Make the system plan it, dispatch it to a phone that is not on your account, track it, capture the POD and invoice it, live. Watch where the workflow needs a workaround: a subbie set up as a fake driver, a licence quietly required, a POD that arrives somewhere other than the job record.
Ask the commercial questions on the same paper. What does a subcontractor cost to add, and to remove? Who supports their driver when the app misbehaves at a delivery point? What does the customer see of a subbed leg, and can you control it? Written answers, filed with the quotes.
The yard gate does not have to be where subcontractor tracking ends. The fix is not more hardware. It is the subbed leg on the same screen, the same app and the same POD flow as everything else, so a customer’s question has one answer whoever’s truck is carrying the load. That is the operational gap to close, and it is straightforward to test in a live demo using one real subcontracted job.
Subcontractor tracking: what operators ask
What happens if a subcontractor driver has no signal?
The Driver App works offline. The job details already on the phone stay available, the proof of delivery is captured at the delivery point regardless of signal, and it syncs back to the office when connectivity returns. The practical difference from the message-thread alternative: nothing depends on the driver remembering to send anything. The record is captured against the job at the time, and the office receives it as soon as the app reconnects.
What does the customer see on a subbed leg?
It depends on the customer-facing setup, so treat it as its own demo question rather than an assumption. Where the Client Portal or customer tracking is part of your configuration, the subcontracted leg sits in the same job flow as your own work. What the customer is shown is controlled the same way as on your own vehicles. Ask to see the customer view separately in the demo, on a subcontracted job, and confirm exactly what appears before you commit anything to a customer.
