Almost every team we onboard arrives with a "master" spreadsheet, and a quiet anxiety about it.
It started as a simple tracker. Then it grew, tab by tab, into the backbone of the whole program. The problem is not the spreadsheet itself. It is using it as the system of record for a regulated funding process.
That is where it starts to fail:
- It breaks the moment two people edit it at once.
- Version history disappears, so no one can say which figure is current.
- Formulas get overwritten by accident, and no one notices until a number looks wrong months later.
And the hardest gap of all: when an auditor or a board member asks "who decided to fund this, and on what basis?", the spreadsheet cannot answer. The decision happened in an email thread that has since been buried.
There is usually a single person who understands the whole file. That makes the program fragile. When they are on leave, the program effectively pauses.
Moving intake, eligibility checks, scoring and decisions into one configured workflow does not mean abandoning structure. It means the structure is finally enforced, logged and shareable. The spreadsheet can stay as a personal scratchpad. It just stops being the place the program lives.