Direct answer
A team has outgrown a spreadsheet when process control depends on people, copies, and hard-to-check formulas, not merely when the file has many rows. Important signs include changes without history, unclear ownership, manual reconciliation, and exceptions with no safe place to go.
Who it is for and when it does not apply
Use this page to decide whether the problem is process governance or simply spreadsheet organisation. Do not conclude that you need a custom application from one sign. A well-structured table, correct permissions, and a simple procedure may be enough.
Signs and checks
Swipe or scroll to compare the columns.
| Observed sign | What it may mean | Owner check |
|---|---|---|
| Several “final” copies | There is no system of record | Which version drives today’s decision? |
| Formulas overwritten | The rule is not protected or tested | Who can change the formula, and how do we know? |
| Copying between sheet, CRM, and email | Integration is missing or the contract is unclear | Which field is authoritative in each system? |
| Statuses written differently | State has no controlled vocabulary | Which states and transitions are allowed? |
| Reports rebuilt manually | Output is not reproducible | Can another operator verify the same period? |
| Exceptions in comments or chat | There is no queue or accountable owner | Who takes the case, and by when? |
| Broad data access | Permissions follow the file, not the role | What can each role see and change? |
Method and definitions
Count observed incidents over a period chosen by the team, without inventing universal thresholds. Distinguish:
- editing friction: formatting, filters, formulas, or versions that spreadsheet design can repair;
- coordination dependency: steps between people and tools where integration or a work queue may help;
- operational risk: inability to show who changed what, recover a state, or limit access;
- decision problem: data is available, but approval and exception handling need a human owner.
The signal is stronger when it recurs across cycles and affects a verifiable output. Do not turn an observation into a performance or cost claim without a definition, period, and source.
Spreadsheet maturity sheet
Complete with “yes”, “partial”, or “no”, then discuss every “no” with the owner:
- One place is declared the system of record for each important field.
- Read, edit, and approval roles are differentiated.
- Formulas, state conventions, and validations are documented.
- Version history and a tested recovery path exist.
- Duplicates and incomplete rows can be identified.
- Handoffs are visible, not only communicated verbally.
- Data is retained and shared according to company policy.
- Reports can be reproduced without hidden operations.
Interpretation: a few “partial” answers call for standardisation and spreadsheet discipline first. More “no” answers, together with a repeatable process and active owner, justify analysis for an integration or operational system. This is not a universal score and does not make a commercial recommendation on its own.
What to do after the diagnosis
- Repair the spreadsheet and working rules first when the problem is formatting, a missing convention, or unclear ownership.
- Integrate systems or automate stable rules when the same data is repeatedly copied, validated, or recalculated.
- Consider an operational application when the team needs its own states, roles, queues, and exceptions. Keep sensitive or hard-to-reverse decisions with a person.
These signs show where to investigate, not which product to buy. For the full framework, see Automation or operational application?.
Limitations
A large file is not automatically a risk, and a small file is not automatically safe. Size, user count, and sheet count are clues, not evidence. Also check access, retention, backup, and integration policies. Examples are generic and do not describe a client or measured implementation.
Related AutomateFlow pages
Material history
Initial public version or material revision.
Suggest a correction
Include the page and the source supporting the proposed change.