When the file becomes the process: fix, replace or retire a spreadsheet
People blame the spreadsheet. But replace it before you know what it's quietly doing and you can lose the only complete view of the process.
- Theme
- Systems and workflow
- Published
- 12 February 2026
The file may be carrying decisions nobody designed
A workbook can start as a list and grow into a register, calculator, approval queue, reporting layer and the company's memory. The risk is the rules nobody wrote down.
Before choosing a replacement, map what goes into the file, who changes it, which decisions depend on it and what comes out. That shows whether the problem is the tool, the process around it or both.
A drawing or RFI register that has quietly become the approval queue for design changes is a common example: replace it without understanding that role, and the only visible record of who approved what disappears with it.
Treat control and inconvenience as different problems
A slow spreadsheet is annoying. An uncontrolled spreadsheet used to evidence inspection, payment, competence or compliance is a different category of problem.
Fix what affects traceability, access, accuracy and continuity before you improve how it looks or automate it.
- 01 Can the current version be identified?
- 02 Is it clear who looks after it when the author is away?
- 03 Can an important change be traced?
- 04 Are calculations and source data understood?
- 05 Does access match the sensitivity of the information?
When to improve, replace or leave it alone
Improve the file when the task is narrow, someone is clearly responsible for it and better validation, protection or guidance can control the real risks. Replace it when several people need to work in it at once, with permissions, dependable integration or an auditable record the file cannot provide.
Leave it alone when the work is low-consequence, well understood and a new system would add more overhead than control. "Leave alone" is still a decision: record who looks after the file, what it is for and what would trigger another review.
Finding the file's hidden rules first
If replacement is justified, write the hidden rules down before the old file is retired. Test the new flow on real scenarios with the people who understand the exceptions.