When spreadsheets stop working in freight

Excel is not a bad tool. For your first twenty trips there is nothing better: it costs nothing, everyone can use it, a new column takes a minute, and you do not have to ask anyone’s permission. Building a system instead of using a spreadsheet in a company’s first year is usually just a waste of money.

The problem is not the spreadsheet itself. The problem is where it stops — and that point arrives sooner than people expect.

Almost every company that comes to us says a version of the same sentence: “Everything works, it just takes far too long.” There is something specific behind that sentence, and it is not the size of the file.

One trip, two routes

By hand

Typed 4 times · 3 people

1. The customer calls
2. The dispatcher types it into Excel
3. It goes to the driver over WhatsApp
4. The driver photographs the delivery note
5. Accounts type it in again
6. At month end the report is assembled

With a system

Typed once

1. The order lands in the system
2. The driver sees it on a phone and confirms
3. The report is already there

The dashed steps are the points where information is carried from one person to another by hand.

The difference is not the number of steps. The difference is how many times the same thing is written down: the same trip is recorded four times in four places — heard on a call, typed into a spreadsheet, copied into a chat, reassembled in a report.

Every one of those is a chance to get it wrong. Worse, none of the four copies knows about the others. When the driver confirms a corrected address in the chat, the row in the spreadsheet stays as it was. At month end, somebody has to work out by hand which version is true.

Seven signs

1. 1

   The same figure is typed in two places. Once into the spreadsheet, once into accounting or onto a delivery note. Which one is right is now something you have to remember.

2. 2

   Someone asks which file is the latest. If file names carry dates, "final", "new" or "fixed", what you really have is a versioning problem.

3. 3

   Putting a report together takes a day. You already hold the numbers. If gathering them takes a day, the problem is not the arithmetic — it is where the numbers live.

4. 4

   A question has to wait for an answer. If "where is that truck now?" or "what does this customer owe?" needs somebody to make a call, the information is in people, not in a system.

5. 5

   The work stops when one person is away. If only one person understands the file, that is not a process — it is a risk.

6. 6

   Mistakes surface at month end. A wrong rate, a forgotten trip or a payment entered twice shows up a month later instead of on the day it happened.

7. 7

   Training someone new takes weeks. The process is not in the file, it is in people’s heads — so every new hire learns the same thing from scratch.

Three of these and you can live with it. Five, and you are already paying the cost — it simply never appears as a line in any report, because the cost is people’s time.

What a system actually changes

Let us deal with the most common wrong expectation first: a system does not give you new information. You already have the information — in the spreadsheet, in the chat, on a paper delivery note, in the driver’s memory.

What a system changes is this: how many times the same thing gets written down, and by whom.

• Written once, where it happens. The driver confirms the delivery on their own phone, so the dispatcher never retypes it.
• The report is not assembled, it is already there — because the numbers sit in one place rather than in four files.
• A question does not wait. The answer to “where is that truck” is on a screen, not at the other end of a phone call.
• A mistake shows up on the day. If a rate does not match the contract, the system says so then, not at month end.

When a spreadsheet is still the right answer

To be straight about it — we build systems for a living, and there are cases where doing so is a waste of money:

• When the volume is low. Ten or fifteen trips a month is work one person handles comfortably in a spreadsheet.
• When the process has not settled. If the company changes how it works every month, a system will slow those changes down. Let the process settle first.
• When it is a one-person job. If the problem is information passing from hand to hand and there is only one pair of hands, there is no problem.

	Spreadsheet	System
Cost to start	Effectively none	A project, delivered in phases
Making a change	Immediately, yourself	Planned — but it reaches everyone at once
As the team grows	Every new person means another copy	Every new person reads the same source
When mistakes surface	At month end	As they happen
Reporting	Assembled by hand	Already there

Where to start

The most expensive and most dangerous route is moving the whole company onto a system at once. Those projects tend to stall halfway, because every department has to change how it works on the same day.

Start instead with the one process that hurts most. In freight that is usually the trip itself: an order arrives, it reaches the driver, delivery is confirmed, the paperwork closes. Once that chain works, everything else — rating, debts, reporting — can be set on top of it, because the information is already in one place.

Which process to start with is something we can tell you after one conversation. If the answer is “you do not need a system yet”, we say that too.