Operations
The booking spreadsheet breaks at about six vehicles, and not for the reason you think
September 15, 2026 · Max · 8 min read

A shared booking spreadsheet stops working somewhere between five and eight vehicles, and it fails on concurrency rather than on volume. It is not that you have too many bookings. It is that too many people now need to write to the same rows on the same morning, and a spreadsheet has no idea who is allowed to change what, or who needs to be told when something changes.
Call it the concurrency wall. The useful part is that you can tell whether you have hit it without counting anything.
Why vehicles and not bookings
Follow the writers rather than the rows.
At one or two vehicles, the owner takes the enquiry, sends the price, drives the trip and updates the sheet. There is exactly one writer, and a spreadsheet with one writer is an excellent piece of software. It is free, it is already installed, and it will do anything you ask it to.
At three or four, a driver appears and somebody starts helping with the phone. Two writers, occasionally three. Still survivable, because the overlap is small and the owner is usually in the room.
At five to eight, the shape changes. There is a person answering enquiries, a person building tomorrow morning, drivers who need today's plan before they leave the house, and an owner who is in a van and unreachable for six hours. That is four writers who all need the same rows, and at least one of them is on a phone. Volume did not break the sheet. Simultaneity did.
The number is five to eight rather than a single figure because it moves with how many people touch the day, not with how many vehicles are on the driveway. A three-van operator with three office staff hits the wall early. An eight-van operator where one person does every quote hits it late.
The five failures that mean you are there
Each of these is a symptom of the same thing: the sheet cannot enforce anything and cannot notify anyone.
- The same row, edited twice. Two people open the file, both change Saturday, and the second save quietly wins. Nobody finds out until a customer arrives at the wrong time.
- A vehicle double-booked. A walk-in or a phone booking goes into a slot that was already taken, because nothing in a grid of cells knows that one van cannot be in two places at 9am.
- The driver never got the change. The pickup moved at 8pm and the message went into a group chat with forty other messages in it. The driver is working from the version they screenshotted yesterday.
- The deposit nobody chased. There is a column for it. There is no mechanism behind the column, so it is only accurate for the bookings somebody remembered to update, which is not the ones that matter.
- The booking that lived in one person's phone. It was agreed over WhatsApp, it never reached the sheet, and it exists only in the memory of somebody who is currently driving.
One of these in a season is bad luck. Two of them in a month is the wall.
What a spreadsheet can and cannot do
| Shared spreadsheet | Dispatch software | |
|---|---|---|
| Cost | Free, and already installed | A monthly subscription |
| Flexibility | Total. Any column you can imagine | Whatever the product decided for you |
| Two people editing at once | Last save wins, silently | One record, one current state |
| Booking the same van twice | Nothing stops it | The conflict is visible on the board |
| Telling the driver about a change | You, by message, by hand | The driver's link shows the current version |
| Knowing what is still owed | A column somebody has to maintain | Derived from what has been paid |
| Chasing a balance before a trip | You remember, or you do not | Sent automatically before the date |
| Setup effort | None. It already matches how you think | An evening of entering your tours and vehicles |
| Getting your data out | It is already a file you own | Depends entirely on the vendor. Ask first |
Two of those rows favour the spreadsheet outright, and no software product should pretend otherwise. A spreadsheet costs nothing, it fits your business perfectly because you shaped it yourself, and nobody can take it away from you or put the price up.
You do not need software yet if
This list is here because being recommended to somebody who then churns in six weeks helps nobody.
- One person takes every booking. If the same human quotes, confirms, dispatches and drives, the sheet has one writer and the wall is a long way off.
- One or two vehicles, and you are in one of them. You are the source of truth. Writing it down twice is the only cost.
- Your season is short. A subscription charges you the same in February as in July. Four quiet months of a $99 plan is $396 for software nobody opened, and a spreadsheet charges nothing for a quiet month.
- You have never had one of the five failures. Not "you fixed it quickly". Never had it. Then the system you have is working, and the correct move is to keep using it.
The moment to change is not a vehicle count. It is the second time in a month you rebuild a day by hand because nobody could tell you what the truth was.
What to do this week, whichever side you land on
- Make one place the truth and say so out loud. Most spreadsheet failures are really two-systems failures: a sheet and a group chat that disagree. Pick one, and make the other one a pointer to it.
- Give tomorrow a single owner. One named person builds the next day and nobody else edits it after a fixed hour.
- Send the driver a dated plan, not a message. Whatever the format, it should carry the time it was produced so the driver knows whether they are holding the current one.
- Put the deposit somewhere that cannot be forgotten. A calendar reminder per booking is crude and works better than a column.
Those four cost nothing and buy back most of the risk. If you do them and the day still falls over, the problem is the tool.
Where FleetDesk fits
FleetDesk, dispatch software for tour operators, is what the four habits above look like when the software enforces them instead of you. One record per booking, a board whose columns are your vehicles, a tokenised run sheet link the driver opens on a phone with no app and no login, and an automatic email before the trip carrying whatever balance is still owed.
It is built for the quote-first end of the business: somebody asks, you price the group, a deposit lands, you run the day. It does not process payments and it does not sell seats to the public, so if what you need is a checkout on your website, this is the wrong tool and a booking platform is the right one.
If you are still on one van and one writer, keep the spreadsheet. It is winning.