When spreadsheets stop coping with the traffic office
A practical comparison of spreadsheets and TMS for UK haulage firms handling jobs, PODs, driver briefings and invoicing.
A spreadsheet is fine until the traffic office starts depending on memory, phone calls and luck to make it work. If you are running a handful of repeat jobs, with one person who knows every customer, every driver and every collection point, you can get by for a while. The problem is not that spreadsheets are wrong. It is that they do not run the day. People do.
That is the point where we see firms start looking for haulage software for a transport manager doing jobs on spreadsheet. Not because they want a big system, but because the office is losing time on the same avoidable jobs every day. Chasing POD. Re-keying the same details. Ringing drivers for updates that should already be visible. Missing demurrage because nobody wrote the times down properly. Finishing the work on Tuesday and invoicing it the following week, or later.
Where spreadsheets still work and where they start costing you
A spreadsheet still works when the operation is genuinely small and stable. Three vehicles on regular work. The same customers every week. The same collection and delivery points. One person planning, speaking to drivers and doing the paperwork. If the jobs are straightforward and there are not many changes during the day, a spreadsheet can remain a decent diary and billing list.
It also works better where the work is simple general haulage rather than container work. Container traffic creates more moving parts. Booking references, pin numbers, port times, VBS slots, quay collections, empty returns, deadlines, detention risk, demurrage risk and container turnaround all create more opportunities for a line on a spreadsheet to stop being enough.
The break point is usually not fleet size on its own. It is volume, change and handoffs.
A spreadsheet starts costing you when any of these become normal:
- Jobs are added or changed after the drivers have left the yard
- Drivers are briefed by phone calls, WhatsApp and screenshots
- You need to know where a vehicle is without ringing the driver
- POD comes back in paper form, late in the day or days later
- More than one person updates the same sheet
- You are copying job details from one place to another
- Customers want status updates before you have had time to ask the driver
- You use subcontractor cover often enough that rates and POD need tracking separately
- Container jobs need timed events recorded properly for demurrage or container turnaround
- Invoices are being held because one detail is missing
That is the real issue. A spreadsheet stores data, but it does not control the flow of work. It does not brief the driver. It does not prompt for missing references. It does not collect ePOD. It does not tell the office that a job is ready to invoice. It does not stop two people from working off two different versions of the truth.
In a UK haulage business, that matters because the traffic office is usually lean. The owner may still be driving some weeks. The transport manager may also be dealing with maintenance bookings, customer calls and O-licence responsibilities. There is no spare admin layer to absorb mistakes. A missed POD is not a minor inconvenience. It is a late invoice. A late invoice is cash held back for no good reason.
We often hear, “The spreadsheet itself is not the problem.” That is true. The problem is everything built around it. The notebook beside it. The phone calls. The whiteboard. The driver text. The paper in the cab. The invoice list someone meant to update on Friday and did not.
How a TMS changes the working day for a transport manager
A good TMS should remove repeat admin from the day, not add another system to feed. The practical difference starts in planning.
With a spreadsheet, planning often means entering the job, finding a vehicle, messaging the driver, then updating the sheet again if anything changes. With a TMS, the job and the allocation sit in one place. The traffic office can see what is assigned, what is still open and what has changed since the morning. That is the first gain. Less mental load.
Driver briefing is the next one. In a spreadsheet-led office, the driver’s actual brief may be spread across a line on the sheet, a WhatsApp message, a photo of a booking form and a follow-up phone call. In a TMS, the job details can go straight to the driver in a usable form, with addresses, references, timing and notes together. If the collection reference changes at 08:40, the brief changes there, not in three different places.
That matters more than it sounds. A lot of avoidable mistakes are not planning mistakes. They are briefing mistakes.
Progress tracking also changes. Not in the glossy sense of “full visibility”, but in the practical sense that the office stops ringing round to ask the same questions. Has the collection happened. Is the container loaded. Has the empty been tipped. Has the delivery gone in. If the job status is being updated as the day moves on, the transport manager can manage exceptions rather than chasing routine progress.
For firms doing container work, this is where proper event recording starts paying for itself. If the key times are captured against the job, the office can see whether demurrage needs to be raised, whether waiting time needs discussing, and whether container turnaround is drifting into a problem before the customer argues about it.
POD is usually the biggest change of all. On spreadsheets, the work often feels finished when the vehicle is empty again. Commercially, it is not finished until the POD is back and the invoice can go. A TMS with ePOD closes that gap. The office does not need to wait for paper to return to the yard, or for someone to remember to photograph it that evening. The job can move towards invoice while it is still fresh, not after a pile has built up on a desk.
That is why we built Logivo around the daily sequence of plan, brief, run, capture POD and invoice. If you want a closer look at how planning alone stops work falling through the cracks, this piece on keeping jobs from slipping during the day covers the practical side.
The final difference is invoicing readiness. In a spreadsheet office, invoicing is often a separate clean-up exercise. Someone has to check whether the POD is back, whether the rate is confirmed, whether the extra waiting time should be added, whether the subcontractor cost is noted, whether the customer reference is there. In a TMS, those checks can happen as part of the job flow. The office is not hunting around after the event to complete the record.
Spreadsheet versus TMS on the jobs that usually go wrong
The easiest way to judge the difference is to look at the jobs that regularly go wrong.
Missed POD is the obvious one. In a spreadsheet setup, the sheet may show the job as done, but the POD is in a cab, in a tray, in a WhatsApp photo thread, or nowhere anyone can find quickly. Then invoicing waits. In a TMS with ePOD, the proof is attached to the job record and visible to the office straight away. That does not just save filing time. It stops revenue being delayed by paperwork.
Demurrage is another common weak spot. A spreadsheet can hold a note saying “2 hrs wait”, but it depends on somebody recording it properly and somebody else remembering to bill it. A TMS can keep the waiting event with the job so it is not lost between operations and accounts. The same applies to detention-related issues around container work. If the times are not captured at the point they happen, it becomes an argument later.
Container turnaround is where manual systems often become guesswork. You may know in broad terms which boxes are out, but not have a clean view of which jobs are still open, which empties need returning, or which deadlines are getting tight. A TMS makes that visible as live work, not a memory test for the traffic office.
Backload changes are a daily reality for many operators. A vehicle tips earlier than expected. A collection moves. A better-paying backload appears. On a spreadsheet, that often means deleting, overwriting or adding comments, then making sure the driver has the latest version by phone. In a TMS, the plan can be adjusted and the driver brief updated from the same place. Less room for crossed wires.
Subcontractor jobs are another area where spreadsheets become messy quickly. You need to know who covered the job, what rate was agreed, whether the POD has come back, whether the customer has been billed and whether the supplier can be approved for payment. A spreadsheet can hold all of that, but only if someone is disciplined enough to update every field every time. In practice, the gaps show up when the invoice is late or when a supplier chases payment before the customer has been billed.
Invoice delays are usually the result of all of the above. The work was done, but one thing is missing. The POD. The waiting time. The customer reference. The rate. The subcontractor cost. The spreadsheet did not fail in a technical sense. It simply did not drive the process far enough.
That is why we focus on shortening the time between job completion and invoice. We have written more about getting invoices out faster from completed transport jobs and about sending the invoice the same day the POD lands, because for many operators that is where the return shows up first.
What to check before you move off spreadsheets
The right time to move is before the office is drowning, not after. But it is still worth checking a few basics so you do not swap one problem for another.
First, look at setup effort. Many smaller operators have been put off by software vendors quoting an implementation project, consultancy days and a long onboarding process. For a three to fifty vehicle haulage business, that is often the wrong fit. If your current system is a spreadsheet, paper POD and WhatsApp, you do not need a six-month project. You need to start running live jobs without weeks of prep.
Second, check whether the software suits your actual fleet size and traffic office structure. Some systems are built for larger operations with separate planning, customer service, compliance and accounts teams. If your transport manager also answers the phone and covers a vehicle now and then, the system needs to be quick to use and forgiving under pressure. It should help one busy person make fewer mistakes, not force them through layers of workflow that belong in a much larger business.
Third, be clear about the jobs you need it to handle. General haulage and container work do not create exactly the same demands. Container operators need proper handling of timed events, references, status changes and return legs. If your business lives on quay work, empty returns and turnarounds, make sure the software understands that shape of work rather than treating every load as a simple A to B delivery.
Fourth, look at the invoicing path. A surprising number of systems are decent at planning but weak at getting completed work commercially closed. Ask a simple question: once the driver has finished and the POD is in, how many steps remain before the job is invoice-ready? If the answer is still “quite a few”, you are only moving the bottleneck.
Fifth, consider cost risk honestly. For a small or mid-size operator, the biggest risk is not usually licence cost alone. It is paying for software that takes too long to start, needs outside help to configure, or only makes sense once the whole business has changed around it. We built Logivo to avoid that. No implementation project, no consultant, no minimum fleet size. If you want to see what that looks like in practice, this article on starting haulage software without an implementation project sets it out plainly.
Finally, keep UK-specific reality in mind. If you operate in Great Britain, your day-to-day transport admin, customer expectations and O-licence responsibilities are not the same thing as a generic European logistics workflow. A lot of software is sold in broad EU terms. The actual traffic office work in a UK haulage firm is more specific than that, especially where container work, paper trails and customer references drive whether you get paid.
Who should stay on spreadsheets for now and who should switch
Some operators should stay on spreadsheets for now.
If you have a very small fleet, low daily job count, repeat work with little change, and one person who can still control the whole day without jobs slipping, a spreadsheet may still be good enough. That is especially true if POD comes back promptly, invoices go out on time, and the office is not spending every afternoon chasing information that should already be to hand.
Stay where you are, for now, if all of this is true:
- The daily plan rarely changes after first allocation
- Drivers do not need frequent updates during the day
- POD is returned consistently without delay
- Invoices go out promptly, without a weekly catch-up session
- You are not losing extras such as waiting time or demurrage
- One person can still see the whole board without relying on memory
But many firms reading this will recognise that they are already past that point.
You should switch when the spreadsheet has become the centre of a manual system that depends on constant chasing. That usually shows up in workload before it shows up in any formal report. The owner is still doing traffic at night. The transport manager starts the day with yesterday’s paperwork still open. Drivers ring because they cannot find the latest instruction. A subcontractor POD is missing. A customer asks for an update and the office has to make three calls to answer a simple question. The invoice run drifts because completed jobs are not commercially complete.
As a rule of thumb, switch when these become normal:
- The office is planning tomorrow while still fixing yesterday
- Jobs change during the day and the latest version is hard to control
- POD delays are holding back invoices
- Container jobs need better timing records for demurrage or container turnaround
- Backload opportunities are being missed because replanning is too clumsy
- Subcontractor work is increasing and the paperwork trail is getting messy
- The transport manager is carrying too much of the system in their head
That is the real decision framework. Not “Are we big enough for software?” but “Is the current way of working making the day harder than it needs to be?”
If the answer is yes, then moving off spreadsheets is not about becoming more sophisticated. It is about getting the traffic office under control. The right TMS should let you plan the job once, brief the driver properly, see progress without a chain of phone calls, capture POD as part of the job, and get the work ready to invoice while it is still current.
That is exactly the gap we built Logivo to close for UK haulage and container operators. Not with a big project, and not with features you will never use, but with software that fits the way a three to fifty vehicle traffic office actually works.
Can a spreadsheet still be enough for a small haulage firm?
Yes, if job volume is low, the same people handle the work every day, and PODs and invoicing are not slipping. The problem usually starts when the office relies on memory, calls and WhatsApp to fill the gaps.
What does a TMS do that a spreadsheet cannot?
A TMS keeps the job, driver brief, status, POD and invoice trail in one place. A spreadsheet can list jobs, but it does not manage the handover between planning, execution and billing very well.
Will moving to a TMS save time straight away?
It can, but the biggest early gain is often fewer missed steps rather than dramatic time savings. Firms usually notice faster POD collection, less chasing and invoices going out sooner.
Is a TMS only worth it for larger fleets?
No. Small operators often feel the pain earlier because the owner or transport manager is doing traffic, customer calls and sometimes driving as well. One missing POD can hold up cash just as badly in a five-vehicle fleet.
What should a transport manager ask on a demo?
Ask how jobs are entered, how drivers are briefed, how POD is captured, what happens when a job changes midday, and how quickly completed work becomes ready to invoice.