CR CONSULTING · SMALL-BUSINESS GUIDE
Where should a person stay in an automated workflow?
A practical guide for small-business owners to spot human-review points, handle exceptions, and set clear workflow boundaries.
Start with the consequence of getting a step wrong. Routine work with clear inputs may be a candidate for automation planning; decisions involving uncertainty, customer judgment, or meaningful consequences need a person in the loop.
01 · DECIDE WHERE TO REVIEW
Four signals that a person should step in
Walk through each step in the process. If one of these signals applies, write down the review rule before considering how that step might be automated.
A mistake could matter
Keep a person responsible when a step could affect safety, money, privacy, eligibility, or a promise made to a customer. Require approval before any consequential or hard-to-reverse action.
The information is unclear
Pause when details are missing, conflicting, duplicated, stale, or outside the cases you have defined. A workflow should not guess which version is right.
Context or judgment matters
Complaints, sensitive requests, negotiations, unusual customer needs, and decisions that call for empathy or business discretion belong with a person.
A step changes something outside the draft
Sending a custom response, changing a customer record, confirming a commitment, or taking another external action deserves a clear owner and an approval rule matched to its impact.
02 · PLAN FOR EXCEPTIONS
Make the unusual case clear before it happens
An exception is any case the workflow cannot safely handle using its written rules. For each one, define what triggers a pause and who owns the next decision.
- 01
Name the trigger
Write down observable conditions: for example, a missing required detail, a duplicate request, a disputed charge, or a question outside the services you have described.
- 02
Say what must stop
Specify which later steps must wait. Preserve the original request and its context; do not silently guess, send a final answer, or keep retrying an action that failed.
- 03
Assign a person and a backup
Name the role that reviews the case and who covers when that person is unavailable. Give the reviewer the information needed to decide, not just an error label.
- 04
Set a response and escalation path
Choose a response window that fits the urgency. If the reviewer cannot resolve the case in that window, say who receives it next and what safe fallback the customer will see.
- 05
Record the outcome
Capture the decision, who made it, and whether the workflow may continue. If the same exception keeps appearing, update the process instead of adding a one-off guess.
03 · SET THE BOUNDARIES
Separate routine steps from human decisions
Put the limits in plain language so the business owner, reviewer, and anyone implementing the process share the same expectations.
Possible routine steps
After a process is mapped and tested, predictable internal preparation—such as organizing known request types or preparing a draft—may be suitable for a later workflow.
Approval before action
Keep a person as the decision-maker for unusual cases, customer-specific advice, quotes or commitments, sensitive information, and actions that are difficult to undo.
Stop rather than guess
Define the cases a workflow must never handle on its own. When a request falls outside those limits, pause and send it to the named person with the reason it stopped.
A PRACTICAL NEXT STEP
Send one task for a written review.
Free written workflow review. No call required. Send one task you’d like to simplify, how your team handles it today, and the software you use. You’ll get a one-page recommendation. No purchase required. Please do not send customer or patient records.
Submitting the form starts a conversation; it does not connect tools or start automation.