The Spreadsheet That Keeps a Department Running: When Should It Be Replaced?
In almost every business we start, one department runs on a single spreadsheet. Service schedules, request tracking, time off, supplier orders, equipment inventory. It works, it cost nothing, and no one ever decided that this spreadsheet would become a management tool—it just happened on its own.
The question isn't whether it's right or wrong. It's about determining at what point the file costs more than it brings in —and that point can be identified.
The Five Signals
Only one person knows how to use it. This is the most serious—and most common—sign. The file contains formulas, hidden tabs, and macros written years ago. The person who created it has become a single point of failure for the company, and they are rarely aware of it.
We work with copies. “Final version,” “final corrected version”—one file per site, one file per month. As soon as there are multiple copies of the data, someone ends up working on the wrong one—and no one notices until it becomes apparent to a client.
The data has to be re-entered elsewhere. Whatever is entered into the file ends up being retyped into an invoice, a web CRM , or an email. This double entry means time is paid for twice, and it creates a constant discrepancy between the two systems.
No one can access it from the field. A technician who jots things down on paper and re-enters the data in the evening, a sales representative who calls the office to check inventory: the system dictates a specific location, and the organization has complied with this constraint without questioning it.
There’s no way to know who changed what. When data is incorrect, the only possible answer is “I don’t know.” For scheduling, that’s just annoying; for billable hours, quality control, or personnel data, it’s a whole different kind of problem.
Note: Three out of five signs indicate a problem. Just one doesn't necessarily mean there is one: a well-maintained spreadsheet that someone uses for their own work is an excellent tool.
What Not to Replace
It's just as important as the rest, and it helps avoid unnecessary projects.
A spreadsheet used for calculating, simulating, and comparing is still just a spreadsheet. An analysis, a projected budget, a pricing model—these are use cases where the flexibility of a spreadsheet is exactly what’s needed, and where an application would be more rigid without being more accurate.
The line is clear: a spreadsheet that answers a question belongs there. A spreadsheet that records what the company does no longer belongs there.
What Does This Mean in Practice?
A business application doesn't do what the file does any better. It does three things that the file cannot do:
- a single piece of data that multiple people can modify without interfering with each other;
- permissions, so that everyone can view and edit only what concerns them, and nothing else;
- a log that shows who entered what and when.
Added to that, almost always, is the ability to access it from a phone—and that’s often what wins teams over, long before governance considerations come into play.
The effort—and it's less than you might think
An initial tool that replicates the scope of the file—the same fields, the same rules, the same people—can be built in a matter of weeks, not months. That’s actually the right way to start: don’t try to improve the process at the same time you’re building the tool. Attempts to tackle both projects simultaneously almost always fail, because no one knows what’s causing the problem anymore.
What drives up costs are the things we add along the way. A project that starts with a plan and ends with “while we’re at it, we might as well handle the billing too” has doubled in scope without anyone deciding to do so.
What to Do
- List the files that store data rather than compute it. Usually three to five.
- For each one, count the number of people who use it and the number of people who know how to repair it.
- Identify the duplicate entries it causes downstream.
- Choose just one—the most painful one—and address it while keeping the scope of the analysis constant.
- Take a look at how it turned out before you start on the second one.
Lambert Consulting builds these tools on the platform you’re already paying for and integrates them with your other systems rather than creating yet another one. When it comes to quality technical support, it’s worth considering the distinction between an application at Power Apps and a solution developed at Azure before getting started, and the actual cost of the licenses should be calculated at the same time.
Microsoft Sources
What an article Can't Know
An article describes what applies to everyone. What varies from one organization to another is the inventory: which applications, which accounts, and which pieces of equipment are actually involved in your organization. The inventory determines the scope of the effort, and it cannot be summarized on a single page.
You'll be speaking directly with the engineers who will be doing the work, not with a middleman. We'll respond within 24 business hours.
Check what is still true
Announced dates are sometimes postponed, products are renamed, and conditions change. The blog tracks these topics over time: when a rule changes, a new post announces it.
Search for a topic in the blogIn the same issue
Three articles on the same topic. The blog has 149 articles, all of which are freely accessible.