Direct answer
Automate a spreadsheet workflow first when it repeats, has an owner, observable rules, a verifiable output, and a clear exception path. Do not start with the most visible table or the most impressive demo. Start with a bounded slice where you can see whether state was updated correctly.
Who it is for and when it does not apply
This page is for an owner choosing among candidates such as reporting, intake, reconciliation, CRM updates, or document preparation. It is not a universal ranking. If you cannot identify the outcome, lawful access, or owner, pause automation and clarify the workflow.
Prioritisation criteria
Evaluate every candidate with the same internal scale, such as “low”, “medium”, or “high”. Do not add points to simulate precision:
Swipe or scroll to compare the columns.
| Criterion | Question | Positive signal |
|---|---|---|
| Repetition | Does it occur often enough to observe? | Stable cycle with representative examples |
| Clarity | Are input, rule, and output known? | Explicit fields and acceptance criterion |
| Coordination cost | Is context lost between people or systems? | Visible handoff and status |
| Controllable risk | Can the result be stopped and checked? | Defined reconciliation and approval |
| Access | Can data and integrations be used legitimately? | Owner and permissions clarified |
| Learning value | Can the first release be limited? | One path and user group |
Method and definitions
- List candidates without changing their description to make them look more suitable.
- For each one, write the input event, accepted outcome, and most operationally costly exception.
- Mark what is observed, assumed, and still to be checked.
- Choose the best balance of operational value and controllability, not the highest score in one dimension.
- Define a stop condition: missing data, ambiguous rule, or unavailable integration sends the case to a person.
“First” means the first path approved for learning and operation, not a promise of a financial result. A good pilot path is not automatically the company’s most important process.
Reusable prioritisation matrix
Swipe or scroll to compare the columns.
| Candidate workflow | Input / output | Owner | Stable rules | Exception and control | Safe first slice |
|---|---|---|---|---|---|
| Form request → CRM queue | Complete before workshop | To complete | To check | To complete | One request type |
| Sheet → finance register reconciliation | Complete before workshop | To complete | To check | To complete | One period in read-only mode |
| Delivery status → internal report | Complete before workshop | To complete | To check | To complete | One team and a few states |
This table is a working instrument, not evidence of results. Replace “To complete” only after observation and owner agreement. Do not add customer data, production files, or credentials.
Recommendation by workflow type
- If the work is rare or the workflow is not stable, document it before automating it. An existing product may be enough for a common list, approval, or report.
- If transfer between systems is the problem, start with an integration. Use deterministic rules for explicit transformations, deduplication, synchronisation, and calculations.
- Use bounded AI for extraction or classification from variable text only when a threshold and human review are in place.
- Consider an operational application when configuration cannot safely model the required state, exceptions, roles, and interface. Approvals, ambiguous cases, and important external outputs remain with a person.
For the full comparison, see Automation or operational application?.
Limitations
Frequency alone does not determine priority. A frequent workflow may involve data that cannot be used for the stated purpose, high risk, or unstable rules. A less frequent workflow may still justify an interface when errors are difficult to recover. This method does not calculate ROI or claim savings, rankings, or client outcomes.
Related AutomateFlow pages
Material history
Initial public version or material revision.
Suggest a correction
Include the page and the source supporting the proposed change.