Keeping subcontractor work visible from job to invoice
A practical guide to subcontractor management for UK haulage firms, covering booking, POD, rates, delays and getting invoices out on time.
If you use subcontractors every week, the problem is rarely finding someone with a truck. The problem is keeping the job visible once it leaves your own fleet. You need to know what was agreed, whether the load is moving, whether anything has changed on site, where the POD is, what the final cost is, and whether the sales invoice can go out today or will sit for another week while somebody chases paperwork.
That is what good subcontractor management looks like in practice. It is not a policy document. It is a working method that keeps the office, the customer, the subcontractor and the invoice tied to the same job record from first call to final billing.
What subcontractor management means in a small haulage office
In a small UK haulage office, subcontractor management means controlling work that is carried out by somebody outside your own fleet, without losing sight of the job. It covers the point where you decide to pass a load out, the rate you agree, the brief you send, the updates you receive, the POD you collect, and the purchase and sales invoices that follow.
For most operators with three to fifty vehicles, this does not break down because people do not care. It breaks down because the day is busy and the process lives in too many places. The customer job is in one spreadsheet. The agreed rate is in a text message. The delivery instruction is in WhatsApp. The POD is in the driver’s cab or on somebody’s phone. The extra waiting time is mentioned on a call at half six, then forgotten by the time the invoice is raised.
That creates three direct problems.
First, you lose operational control. You cannot answer a customer confidently because you are waiting for somebody else to reply.
Second, you lose margin. Waiting time, redelivery, failed delivery, demurrage, or a change of collection point may be real costs, but if they are not captured against the job, they are easy to miss.
Third, you lose billing time. Jobs get delivered on Tuesday and invoiced next Thursday because nobody has the POD, nobody has confirmed the final cost, or nobody is sure whether the job is complete.
For UK operators, this matters even more where container work is involved. container turnaround, quay cut-offs, VBS slots, detention risk, and customer pressure all make timing tighter. If the office is relying on memory and message history, a subcontracted container move can become expensive very quickly.
Where subcontractor jobs usually go wrong
Most subcontractor jobs do not go wrong in one dramatic moment. They go wrong through small gaps.
A common one is an unclear brief. The collection postcode is right, but the booking reference is missing. The delivery is booked, but nobody has passed on the site contact. The driver arrives at a warehouse that requires PPE, a booking number, and a side curtain, and only finds out on the gate.
Another is the agreed rate not being clear enough. If the office says "£x for the move" but does not state what happens if the driver waits two hours, tips the next morning, or has to return the box because the site rejects it, the dispute starts before the truck has even left. The argument later is usually not about the base rate. It is about the exceptions.
POD is another regular failure point. The job is done, but the POD is missing, illegible, or sent to the wrong person. Sometimes the load delivered fine, but the office still cannot invoice because the customer requires a signed POD or a timestamped ePOD before they will accept the charge.
Then there are changes during the job. A delivery slot moves. A container is not grounded. The customer adds a second drop. The haulier rings to say there is heavy waiting time and asks for authorisation. If those changes are not recorded against the job, the office ends up with three versions of events and no reliable basis for recharging the customer.
Jobs also go wrong after completion. This is the quiet leak in many businesses. The subcontractor sends their invoice. The customer has not yet been billed. Or the customer is billed at the original amount, but the extra costs never make it on because the person raising invoices was not on the phone when the issue happened.
If that sounds familiar, it is because the weak point is not the transport itself. It is the handover between operations and accounts, and between one person’s memory and another person’s paperwork. We covered that practical link in more detail in our guide to keeping subcontractor paperwork tied to the right haulage job.
What information you need before you hand a job over
Before a subcontractor starts, we need one complete job record. Not a rough outline, not a screenshot of the customer email, and not "I’ve sent him the details". One record.
At minimum, that record should include:
- customer name
- collection and delivery addresses
- postcode and site name
- booking references
- contact names and phone numbers
- collection date and time
- delivery date and time
- load type
- vehicle or trailer requirements
- weight, unit count, or container details
- whether it is import, export, domestic, or a backload
- any port, line, or terminal reference where relevant
- any restrictions such as FORS, PPE, Moffett, tail-lift, or timed booking
For container work, the brief usually needs more. Container number, size, whether the box is empty or laden, port or depot, cut-off, last free day if known, and any detail affecting container turnaround. If there is likely demurrage or detention exposure, the office needs to know that before the move starts, not after the customer asks why there is an extra charge.
Then there is the commercial side. This is where many firms stay too vague. We should have:
- the agreed buy rate
- whether the rate is all-in or subject to extras
- waiting time rules
- redelivery or failed delivery rules
- out-of-hours rules
- cancellation terms
- who must authorise extra cost
- how POD must be returned
- when the subcontractor can invoice us
If the job needs a same-day POD photo, say so. If the customer will not pay without a signed POD, say so. If waiting time is only chargeable after a certain period, record that threshold clearly. If a port booking change is chargeable, put that in the notes.
This is where software helps, not because the information is complicated, but because it needs to be in one place and visible to the next person. A proper transport management system for haulage planning and job control should let us build that brief once and send it out without retyping it into three different apps.
How to keep control while the job is running
Once the job is out with a subcontractor, the office still owns the customer relationship. That means we need updates without spending the whole day chasing them.
In practice, control comes from setting expectations early. If the subcontractor knows we need collection confirmed, arrival on site, delays, and delivery confirmed, we can manage by exception instead of ringing for every stage. The issue is not whether the driver has moved. The issue is whether the office can see what matters.
For a small operator, this does not need a control tower. It needs a live job status, a clear audit trail, and one place where changes are logged. If the delivery slot moves from 10:00 to 14:00, we record the change against the job. If the site refuses the load, we record who said so and when. If the haulier reports two hours waiting, we log that while it is happening, not two days later when the invoice arrives.
Consistent customer updates matter here as well. Many customer relationships are damaged not by delay, but by silence. If we know a truck is waiting, we can tell the customer. If we know the driver has delivered but the POD is still pending, we can say that too. What customers dislike is hearing three different stories from three different people.
This is especially important where the transport manager is also driving some weeks, or where the owner is still taking calls out of hours. In those businesses, jobs often rely on one person knowing everything. The moment that person is in a cab, under a trailer, or dealing with a breakdown, visibility disappears. A TMS should reduce that dependency by keeping the live state of the job visible to the office, not locked in one phone.
Where you use subcontractors regularly, tracking matters too, but only if it is practical. You do not need theatre. You need to know whether the load has been collected, whether it is likely to miss a slot, and whether the customer needs an update. We set out the useful, day-to-day side of that in our article on tracking subcontracted loads without constant phone chasing.
How POD, costs and invoice timing fit together
This is where margin is either protected or quietly lost.
A job is not commercially complete just because the truck has tipped. To invoice properly, we need proof of completion, final cost, and any chargeable exceptions tied back to the same movement. If those pieces are late or disconnected, the sales invoice waits.
POD is the obvious part. If the customer requires a signed POD, we need it attached to the job as soon as possible. If a digital proof is acceptable, ePOD shortens the gap between delivery and invoice because the document is already in the record. There is no need to wait for paper to come back to the yard or for somebody to photograph it later.
But POD is only one part of the billing picture. We also need to capture extras while they are still fresh and evidenced. That includes waiting time, failed delivery, extra drop, rebooking, redelivery, and demurrage where applicable. In container work, those costs can be the difference between a worthwhile move and one that barely covers itself. If the office learns about them only when the subcontractor invoice arrives, there is a good chance the customer has already been billed too low, or not at all.
That means the commercial workflow should run in this order:
- Job is completed.
- POD or ePOD is attached.
- Exceptions and extras are recorded.
- Final buy cost is confirmed.
- Sales invoice is raised promptly, with supporting documents ready.
Where firms struggle, the steps happen in the wrong order or in different systems. Accounts raises the invoice before operations has finished the job. Or operations closes the job but never passes on the waiting time. Or the subcontractor invoice arrives first, and everyone realises the customer invoice is still sitting in draft.
In the UK, that delay also affects cash flow in a very direct way. If your customer terms run from invoice date, a fortnight lost between delivery and billing is a fortnight lost on payment. For smaller operators, that matters more than any dashboard ever will.
If your accounts package is already in place, the best setup is usually not replacing it. It is making sure the transport side feeds it cleanly, with the right job value and paperwork attached. That is why many operators look for a straightforward link between operations and accounts, such as a QuickBooks workflow for transport invoicing.
What to look for in a TMS if you use subcontractor regularly
If you subcontract regularly, the right TMS should solve everyday visibility problems, not give you a bigger admin job.
Start with the basics. You need to create a job once, assign it to a subcontractor, and keep the original customer movement, the buy rate, and the sell rate tied together. If the system makes you duplicate jobs or maintain separate records manually, it will create work instead of removing it.
The next requirement is a proper job brief. The system should let us send clear instructions with addresses, times, references, site notes, and rate rules. Ideally, the brief the subcontractor receives should be the same one the office sees later when checking disputes.
Status updates matter as well. We need to see whether the job is allocated, in progress, delayed, delivered, or awaiting POD. That can come from app updates, links, or simple response methods, but it needs to land back on the job automatically enough that the office is not retyping every event.
Document handling is another must. A TMS should attach POD, ePOD, delivery notes, photos, and exception evidence to the right job. Not in a separate email chain and not in a downloads folder somebody has to search later.
Cost capture is where many generic systems fall short. For haulage, we need to record waiting time, extra mileage, redelivery, demurrage, and other non-standard charges against the movement that caused them. If that cannot be done easily, those costs will stay in someone’s head until they disappear.
For container operators, look for fields and workflows that reflect real container work. Port references, box details, depot moves, quay deadlines, and container turnaround are not edge cases. They are the job. If a system assumes every movement is a simple A to B pallet delivery, the office will end up back on spreadsheets for the work that actually hurts.
You also want a system that is realistic for a small operator. No implementation project. No consultant. No minimum fleet size. No requirement to spend weeks configuring something before the first job goes through it. If the software cannot be used by a transport manager who is also answering the phone and covering a vehicle now and then, it is too heavy.
Finally, look at how the job closes. That is often the most valuable part. Can the system show which delivered jobs are still missing POD? Which ones are ready to invoice? Which have a cost discrepancy? Which subcontractor jobs are complete operationally but not commercially? If it cannot answer those questions quickly, the same old gap between delivery and invoice will remain.
Good subcontractor management is not about creating more process for its own sake. It is about keeping one clear thread from the customer booking, to the subcontracted move, to the proof of completion, to the invoice. When that thread breaks, the office chases. When it holds, the work is calmer, the margin is clearer, and the invoice goes out while the job is still fresh.
What is subcontractor management in haulage?
It is the day-to-day control of work given to a subcontractor: the brief, the agreed rate, updates during the job, POD, extra charges and making sure the customer invoice is not held up.
Why do subcontractor jobs often get invoiced late?
Usually because the office is waiting for POD, a delivery time, a signed note for waiting time, or confirmation of the agreed charge. The job is done, but the paperwork is not together.
What should be on a subcontractor job brief?
Collection and delivery details, times, reference numbers, load or container information, site rules, contact names, agreed rate and what to do if there is waiting time, refusal or a failed delivery.
Can a small haulier manage subcontractor work without a big system?
Yes, but only if the key details are kept in one place. If the brief is in WhatsApp, the rate is in email and the POD is on paper, jobs will be missed and invoices will slip.
How does ePOD help with subcontractor management?
ePOD shortens the gap between the job finishing and the office having proof it is complete. That makes it easier to check extras, answer customer queries and raise the invoice sooner.