Measure reconciliation cost, not row count
Team size alone does not decide when to change. Procedure revision frequency, number of owners, different validity periods and time spent identifying the current copy matter more.
If a report requires comparing messages, folders and several files, the organization already pays a reconciliation cost even with a small team.
Recognize signs that the boundary has been crossed
The boundary is crossed when a source revision does not create a reliable action list, overdue items have no owner or a record can be overwritten without history.
Dependence on one person who understands every formula, colour and exception is another signal. It is a continuity risk, not just administrative inconvenience.
- multiple copies and manual reconciliation
- no record change history
- no connection to a procedure version
- reminders sent manually
- reporting depends on one person's knowledge
Migrate in stages and preserve decision sources
Start by cleaning active requirements, people and source versions. Do not transfer every historical column without deciding what it means and whether it is still needed.
After migration, compare results for a selected procedure and team. Keep the old spreadsheet as a restricted, dated archive under the retention rules, not as a parallel register for further editing.
Questions worth asking
Must Excel be removed completely?
No. A spreadsheet remains useful for one-off analysis and exports. It should not be maintained manually as a second source of current status.
How many employees justify a system?
There is no universal threshold. Change frequency, risk, number of requirements and reconciliation cost matter more than headcount alone.