Most service companies run on a spreadsheet long before they run on anything else. One tab for the schedule, one for customer rates, one for invoices, and a person in the office who knows how all of it fits together.
That is not a mistake. For a company with three trucks and a dozen customers, Excel is often the right tool. The trouble starts later, quietly, as the company grows and the spreadsheet is asked to do jobs it was never built for.
This article is a fair look at Excel as a way to run jobs, crews and invoices: why people choose it, where it starts to cost you, and what an Excel alternative for job scheduling and invoicing actually changes.
Why Excel is where most companies start
There are good reasons the spreadsheet wins early on.
- You already have it. It came with the computer or the office subscription. There is nothing new to buy.
- Everyone knows it. Your office manager, your bookkeeper and your accountant can all open the file without training.
- It bends to fit. Need a column for AFE numbers or a tab for trailer rentals? Add one. No vendor to ask, no feature request to wait on.
- It is yours. The data sits in a file you control, and nobody can change the price on you.
For a small operation where the owner dispatches, invoices and answers the phone, a well-kept spreadsheet is fast and good enough. If that describes you today, there is no rush.
Where the spreadsheet starts to break
Errors are normal, not careless
The research on spreadsheet errors is old, consistent and a little uncomfortable. Raymond Panko at the University of Hawaii reviewed fifteen years of studies and noted that human error rates on complex mental tasks tend to sit around 2% to 5%. Across field audits of real business spreadsheets, the more recent audits, which used better methods, found errors in at least 86% of the spreadsheets they checked.1
A later audit by Stephen Powell, Kenneth Baker and Barry Lawson at Dartmouth looked at 50 working spreadsheets from real organizations and found errors in 0.9% to 1.8% of all formula cells, depending on how strictly an error was defined.2 That sounds small until you apply it. A rate and invoicing workbook with 500 formulas would, at those rates, carry somewhere around 4 to 9 wrong cells. Nobody knows which ones.
Excel can also change your data without being asked. A team of researchers found that Excel’s default settings convert some gene names to dates, turning “SEPT2” into “2-Sep”, and that about one fifth of genomics papers with supplementary Excel gene lists contained these errors.3 Service companies see the same thing with job numbers, part numbers and unit numbers that happen to look like dates or very large numbers.
We go deeper on this in our post on what the research says about spreadsheet errors.
Every job gets typed more than once
In a spreadsheet setup, the same job is usually entered several times: once on the schedule, once in the hours log, once on the invoice. Each copy is a chance to get something wrong, and the usual safeguard is someone glancing over the invoice before it goes out.
That safeguard is weaker than it feels. In a controlled study, Kimberly Barchard and Larry Pace assigned 195 people to enter data using different methods. Visually checking the work produced 2,958% more errors than double entry, and was not significantly better than doing no check at all.4 A quick look over an invoice catches the obvious mistakes. It rarely catches the wrong rate in row 14.
One file, many people
As soon as two people need the schedule, the spreadsheet gets shared, copied or emailed. Cloud versions of Excel help, with co-editing and version history, and they are a real improvement over “Schedule_FINAL_v3.xlsx” on someone’s desktop. But a spreadsheet still does not know that a job has moved from scheduled to finished to invoiced, or stop someone from invoicing the same ticket twice, or tell you who changed a customer’s rate last Tuesday and why.
The crew cannot use it
A spreadsheet is built for a desk and a keyboard. On a phone in a truck cab it is close to unusable. So the crew gets their jobs some other way, a text or a call, and sends hours and notes back the same way. The spreadsheet becomes a copy of information that lives somewhere else, kept up to date by whoever has time to retype it.
Records have to last
The Canada Revenue Agency generally requires businesses to keep their records and supporting documents for six years from the end of the last tax year they relate to.5 A spreadsheet that gets edited, re-sorted and overwritten every week is a poor record of what was actually billed and why. When a customer disputes an invoice from last spring, you want the ticket, the hours and the rate as they were then, not as they are now.
Signs you have outgrown the spreadsheet
You do not need to switch the day you hire your second dispatcher. These are the signs it is time:
- Only one person really understands the file, and things stall when they are away.
- You have found an invoice with the wrong rate or a missed charge more than once this year.
- Jobs are getting invoiced days or weeks after they are done.
- You keep separate copies of the schedule for the office, the shop and the field.
- Crews are texting photos and hours that someone then retypes.
- You cannot easily answer “which jobs are finished but not invoiced?”
If three or more of those sound familiar, the spreadsheet is costing you more than it saves.
What a job system changes
The main difference is that a job becomes one record that moves through stages, instead of a row copied between tabs.
| Task | In a spreadsheet | In a job system like Dispatch |
|---|---|---|
| Scheduling | A tab someone updates by hand | One schedule board everyone sees |
| Sending jobs to crews | A text or a call | A text with a link to the job |
| Recording hours and photos | Sent back by text, retyped | Added by the crew on the job itself |
| Customer rates | Looked up in another tab | Applied automatically from the client’s pricing |
| Invoicing | Copied from the hours log | Built from the finished ticket |
| Who changed what | Unknown | Kept in an audit trail |
None of this is magic. It is the same work you do today, with the copying taken out.
Moving off Excel without losing your history
The biggest worry about leaving Excel is losing what is in it. A careful switch looks like this:
- Start with clients and rates. These are the most valuable parts of the spreadsheet. Get them into the new system first and check them line by line.
- Keep the old file as a read-only record. Do not delete it. Save a copy, lock it, and keep it with your other records.
- Run new jobs in the new system. Finish the jobs already in progress the old way. Start every new job the new way.
- Pick a cut-off date for invoicing. From that date on, every invoice comes from the new system.
- Give it two weeks before judging. The first few days always feel slower. By the second week, you will know.
Our guide to moving off spreadsheets covers this in more detail.
Where Dispatch fits
Dispatch is a job and billing system for trucking, equipment rental, oilfield and field-service companies. The office works in a browser. Crews get a text when they are assigned a job and open a link on their phone to see the details, update the status and add photos and notes, with nothing to install. When the job is done, the office turns one or more finished tickets into an invoice with the client’s rates already applied, and sends it with a link to pay by card.
It is not accounting software, and it does not try to replace your bookkeeper’s tools. It replaces the spreadsheet that sits between the work and the books. If that spreadsheet has started to feel fragile, book a demo and bring it along. We will show you what it looks like in Dispatch.
Footnotes
-
Raymond R. Panko, “Spreadsheet Errors: What We Know. What We Think We Can Do,” Proceedings of the European Spreadsheet Risks Interest Group (EuSpRIG) Symposium, 2000. https://arxiv.org/abs/0802.3457 ↩
-
Stephen G. Powell, Kenneth R. Baker and Barry Lawson, “Errors in Operational Spreadsheets,” Journal of Organizational and End User Computing 21(3), 2009. https://mba.tuck.dartmouth.edu/spreadsheet/product_pubs_files/Errors.pdf ↩
-
Mark Ziemann, Yotam Eren and Assam El-Osta, “Gene name errors are widespread in the scientific literature,” Genome Biology 17:177, 2016. https://doi.org/10.1186/s13059-016-1044-7 ↩
-
Kimberly A. Barchard and Larry A. Pace, “Preventing human error: The impact of data entry methods on data accuracy and statistical results,” Computers in Human Behavior 27(5), 2011. https://doi.org/10.1016/j.chb.2011.04.004 ↩
-
Canada Revenue Agency, “Where to keep your records, for how long and how to request permission to destroy them early,” Government of Canada. https://www.canada.ca/en/revenue-agency/services/tax/businesses/topics/keeping-records/where-keep-your-records-long-request-permission-destroy-them-early.html ↩
