In July 2025, hauliers collecting from London Gateway were waiting five hours or more for a box. Some operators told their customers that gave hauliers the right to add a surcharge, and some added £150 a collection. (The Loadstar, Xeneta Bridge)
Some of those charges stuck. Plenty didn’t. The difference was rarely the wait itself. It was whether anyone could show it.
This month has opened the same gap again. Empties refused at Felixstowe and London Gateway, trucks queuing, collections moved at short notice. The delay starts at the port. The cost lands on the haulier. And the proof of what happened sits with the driver, in a cab, on a phone or on a scrap of paper, a long way from the person sending the invoice.
This piece covers how to close that gap: what counts as evidence for waiting time and failed jobs, how to capture it at the moment it happens, and how to get it onto the invoice before the customer’s version of events is the only one left. The cash follows the proof.
Three versions of one wait

Take one collection from a busy port this month. The booking says 10:00. The driver reaches the queue at 09:40, gets to the stack at 13:10 and leaves loaded at 14:30.
Three systems will tell three stories about that morning. The port’s records show when the box was released and when the truck went through the gate. The customer’s system shows a booking at 10:00 and a delivery that arrived late. The haulier’s own records, if they exist at all, often show a job started and a job finished.
The only person who saw the whole morning was the driver. Their version usually lives in a phone call to the traffic office, a WhatsApp message or a note on the back of a delivery note.
When the waiting charge reaches the invoice three weeks later, the customer’s version is the one in a system. The driver’s version is the one that has to be argued for. That’s why so many waiting charges get written off. The wait happened. The haulier just can’t show it in a form the customer will accept.
What counts as proof
A waiting charge holds up when it answers four questions without anyone having to remember anything.
| QUESTION | WHAT ANSWERS IT? |
| When did the truck arrive? | Arrival at the gate or the queue, recorded at the time |
| When could the job actually start? | Release, slot or gate-in time |
| What changed, and who changed it? | The original instruction, the new one, and who sent it |
| What did it cost | The gap between when the job could have run and when it did |
Two things make that record count. It has to be made at the time, not rebuilt later from memory. And it has to sit against the job the customer recognises: their booking reference, their container number, their collection.
The same four questions cover more than waiting. A failed collection because the box wasn’t released. A redelivery because the customer moved the time. A run to an inland depot because the port wouldn’t take an empty. Each is a change someone else made, and each costs the haulier a driver’s hours.
Capture it when it happens
Most hauliers already have the information. The driver knows when they arrived. The traffic office knows when the instruction changed. It’s just captured in the wrong place, at the wrong time, by the wrong person.
Three habits close most of the gap:
- The driver records the moment, not the summary. Arrival, gate-in, loaded, departed. An update on a phone against the job takes seconds. A note at the end of the shift takes longer and is worth less.
- Changes are logged against the job, not in the inbox. When the customer or the line moves a time, the new instruction and who sent it sit with the job. An email chain is hard to find three weeks later, and harder to use.
- The traffic office sees the clock while it’s running. If waiting is building at 11:30, someone can tell the customer at 11:30. A charge the customer heard about on the day is far easier to collect than one they first see on an invoice.
None of this needs the driver to do more paperwork. It needs the job to be the place where everything lands.
Getting it onto the invoice
Proof only pays if it reaches the person raising the invoice, in time, in a form the customer recognises.

That means the waiting time, the failed collection or the changed instruction travels with the job, from the cab to the office and from the office to the invoice, without being retyped. The charge goes out with the job, not in a separate batch at the end of the month. And when the customer queries it, the answer is already attached: the times, the instruction, who changed it.
In Fargo Tops, drivers, including third-party and subcontract drivers, receive work and send status changes through a simple browser-based app, and ePODs are captured against the job. Tops compares the live operation with the plan, flags exceptions as they happen, and tracks storage, demurrage and
detention against the job as charges build. Commercial and operational data stay together from booking to invoice, so the record of what happened and the charge for it sit in the same place. For owner-drivers and small fleets working for larger operators, Fargo Move covers the smaller end: jobs received, milestones updated as the job moves, and electronic proof of delivery returned against the job.
Where the margin goes when you can’t
An unprovable wait never shows up as one loss. It shows up as a driver’s afternoon with nothing to bill, a second collection that didn’t happen, a disputed invoice that sits unpaid for another month, and a customer who learns that waiting is free.
The delay starts at the port. The cost lands on the haulier. The proof is in the cab. Getting that proof onto the invoice is the difference between a bad week and a bad week you were paid for.
Start with last week. Count the hours your drivers waited, and how many of those hours you were paid for. If the gap is bigger than you expected, talk to Fargo and we’ll show you how Tops keeps the record against every job.