When a spreadsheet becomes the system of record
How operations teams know a spreadsheet has outgrown its job, and what to replace it with before the next hire depends on it.
APPSOLN® Editorial · 2026-09-28 · 2 min read
How do you tell a working spreadsheet from a hidden system of record?
A spreadsheet is fine when one person tracks a list. It becomes the system of record when other people make decisions from it, when it is the only copy of a status, or when a missed row changes a customer outcome. At that point the file is no longer a convenience. It is the application.
Which signals mean the sheet should be replaced?
Look for these before you fund a build:
- More than one person edits the same file, and nobody can say which version is current.
- Status lives in color, comments, or a column that only one person understands.
- The same customer, order, or ticket is typed into the sheet and into another tool.
- A new hire cannot run the process without a walkthrough of the file.
- Leadership asks for a number the sheet cannot produce without a manual cleanup.
Any two of those are enough to scope a replacement. Waiting for a crisis usually means the next hire inherits the file.
What should the replacement actually do?
Do not start with a feature list. Start with the workflow the sheet is carrying: who updates it, which systems already hold the source data, and which decision the sheet is supposed to support. A useful first application usually does four things:
- Stores one current record for each item the team tracks.
- Shows the status an operator needs without a private column legend.
- Writes back to the system that already owns the customer, order, or document.
- Leaves a place for testing, release, and later automation.
The build is successful when people stop keeping a shadow copy.
What should you leave out of the first version?
Leave out reporting that leadership can already get from the system of record, extra roles nobody will use, and any AI step that assumes clean data the sheet never had. A smaller application that operators trust beats a broad portal they avoid.
Checklist
- Named owner for the workflow
- One source of truth named, even if it is still the sheet today
- Users who will stop using the sheet
- Acceptance criteria the next release can be tested against
- A non-goal list so the first build stays small