Keep a process manual when the business cannot define a safe decision boundary or recover from likely errors. Automation can still prepare evidence or organise work without taking the final consequential action.
Suitability depends on consequence and uncertainty
Automation suitability asks whether inputs, rules, authority, outcomes, and recovery are sufficiently defined for the proposed scope. Repetition alone does not make a task appropriate. A frequent ambiguous decision can remain difficult to automate safely.
For a proposed assessment, examine input quality, policy stability, exception frequency, effect reversibility, permission requirements, and available supervision. Identify which parts are deterministic and which require contextual judgment or accountable approval.
Do not treat human review as a magic fix. Reviewers need usable evidence, authority, time, and a real ability to reject. A rushed approval queue can transfer responsibility without improving the decision.
Compare fictional service processes
Collecting a callback number and issue description can be a bounded intake task with clear validation. Deciding compensation for a disputed visit may require investigation, policy interpretation, and authorised judgment. The assistant can prepare the complaint packet while leaving the decision with staff.
A third process involves an irreversible external action with weak identifiers and no reconciliation support. Even if the API is easy to call, the integration may not support an acceptable failure mode. Keep that effect manual or redesign the process first.
| Process property | Scope implication |
|---|---|
| Clear inputs and stable rules | Candidate for tested automation |
| Ambiguous evidence | Human clarification or review needed |
| High-impact irreversible effect | Stronger authority and control boundary |
| Frequent undocumented exceptions | Clarify the business process first |
| No accountable owner | Do not deploy unsupported autonomous operation |
Use a fictional failure exercise to test the decision. Ask who notices the error, what evidence remains, and how the customer outcome can be repaired.
Automate preparation before authority
A useful first scope may gather approved facts, validate completeness, draft a proposal, or route an item. Staff then make the consequential decision. Measure whether that preparation reduces work without creating misleading recommendations or hidden data exposure.
Manual work also has error and capacity limits. Compare actual alternatives rather than assuming people are infallible. The goal is a supported process with clear ownership, not automation for its own sake or permanent refusal to improve.
This assessment is proposed. The HVAC case study explicitly keeps saved intake separate from appointment confirmation and dispatch. Pair it with external approval design.
Manual-process FAQ
Should every repetitive task be automated?
No. Consider ambiguity, authority, consequence, and recovery as well as frequency.
Can a manual final decision coexist with automation?
Yes. Preparation, validation, and routing can be useful bounded scopes.
What should change before expanding autonomy?
Establish clearer rules, better evidence, tested controls, accountable ownership, and a supported recovery path.