Every organisation has one.
Sometimes it's called the tracker. Sometimes it's the master sheet. Sometimes it lives in someone's personal OneDrive with a name like Final_v3_ACTUAL_USE_THIS_ONE.xlsx.
Whatever it's called, it's doing a job it was never designed to do.
How it starts
Nobody plans to run a critical business process on a spreadsheet.
It usually begins with a reasonable decision. A new process needs tracking. Someone creates a sheet. It's quick, it works, everyone can access it.
Then the process grows. More columns get added. Conditional formatting appears. A second tab is created for historical data. A macro someone wrote in 2019 is still running, and nobody is entirely sure what it does.
By the time the problem becomes visible, the spreadsheet is load-bearing.
What we kept seeing
When we started working with organisations on workflow automation, we expected to find outdated technology.
What we actually found was spreadsheets doing things spreadsheets were never built for:
- Tracking document approvals across departments
- Managing employee time across multiple projects
- Monitoring support requests for contracted clients
- Generating compliance reports for audits
In each case, someone had been maintaining the sheet manually. Updating rows. Sending emails to chase approvals. Exporting data to create reports.
The spreadsheet wasn't the problem. The process built around it was.
The real cost
The hours spent maintaining these systems are rarely counted.
They sit in the background: the person who updates the tracker every morning, the manager who exports data to build the weekly report, the administrator who reconciles two versions of the same file.
We've seen organisations where a significant portion of a team's working week is spent not on the work itself, but on managing the system that tracks the work.
That's the cost nobody puts in a budget.
What replacing it actually looks like
We've learned to be cautious about the word "replace."
The spreadsheet is usually a symptom, not the cause. The underlying process, whether approvals, time recording or support tracking, still needs to exist. It just needs to exist in a system that was designed for it.
There's a second difference that's easy to miss. A spreadsheet stores things. It has no idea what any of them are. The approval sits in one cell, the contract sits in a folder, and the connection between the two lives in someone's head.
A system built for the process can read the document, file it against the right record and keep its history. That's the idea we describe APDocs with: Your documents, understood, not just stored.
When we work with a new customer, the first question isn't "what software do you need?" It's "what does this process actually need to do?"
The answer to that question shapes everything that comes after.
A small observation
The organisations that get the most from automation aren't the ones with the most sophisticated technology requirements.
They're the ones who are honest about where their processes are fragile.
The spreadsheet that runs the business is often the most honest map of where that fragility lives.