What not to automate: when a person should still approve the next step

Business automation

The short answer

Do not automate a consequential decision just because its preparation is repetitive. Keep a person involved when the rules are unclear, information is incomplete, the action is difficult to reverse or the decision changes a commitment to a customer. Automation can still gather details, prepare a draft and highlight exceptions. Put approval before the consequential action, tie it to the version being reviewed and stop if important facts change before execution.

The choice is rarely all manual or fully automatic. A useful workflow can remove copying and chasing while leaving the decision with someone who understands its consequences.

Judge the consequence, not how easy the button is to automate

Ask what happens if the action is wrong, repeated, late or based on old information. Creating an internal reminder is different from confirming a service date, changing an accepted price or sharing private records. A technically simple action can carry a substantial business consequence.

Consider reversibility. Can the result be corrected quietly, or would it require a customer explanation, a refund or recovery of information already disclosed? The harder it is to undo, the more deliberate the permission and review should be.

Frequency is not enough to settle the question. A repeated decision can still depend on context that has never been written down. If experienced people disagree about what should happen, clarify the policy before encoding either person's answer into a workflow.

Automate preparation without automating the decision

Separate gathering, checking, drafting, approving and executing. Often the first three can be improved without granting the connection permission to perform the final action. A draft record or review summary may remove most of the repetitive work.

Illustrative boundaries between preparation and commitment
TaskPossible automatic preparationReason to retain review
Unusual service requestCollect details and flag missing informationSuitability and capacity may need judgment
Revised quotePrepare changes and show the differencePrice and scope commitments may have changed
Customer complaintCollect the relevant historyContext, tone and an appropriate response matter
Invoice preparationAssemble a draft from agreed workExceptions and unapproved additions need checking
Record cleanupSuggest possible duplicatesA wrong merge or deletion may be difficult to reverse

Choose the boundary for the actual task. Keeping review does not mean keeping every manual copying step around it.

Make approval a real stop, not a notification

A message saying something happened is not approval. The workflow must wait before the consequential action, and the reviewer needs enough information to make the decision. Show the proposed action, relevant details, changes from the earlier version and any unresolved uncertainty.

Microsoft's approval workflow documentation demonstrates a wait-for-approval step and recording the decision. Your business still needs to define who can approve and what that approval permits.

Provide a way to decline or request correction. Do not make the fastest click the only workable path. If nobody responds, keep the item pending or route it through an agreed escalation. Silence should not quietly become permission to send, delete or commit.

An illustrative example: a request changes after review

Imagine a service request where staff approve a particular scope and proposed date. Before confirmation is sent, the customer adds a new requirement. This illustrative example shows why a remembered yes is not enough.

  1. Keep the reviewed version of the request identifiable.
  2. Show the reviewer the proposed confirmation, scope and date together.
  3. Record approval for that version and permitted action.
  4. Before executing, check whether relevant facts have changed.
  5. If scope, price, capacity or another material detail changed, stop and request fresh review.
  6. Record the completed action so a repeated event cannot send another confirmation.

A spelling correction may not need the same treatment as extra work, but agree that distinction in advance. The workflow should not decide that a change is harmless simply because it can still fill every required field.

Keep context-sensitive and sensitive-data decisions with a person

Personal disputes, serious complaints, safety concerns and unusual contractual commitments are poor places to start with unattended decisions. A person may need to understand information that is not in the form, ask a follow-up question or recognize when specialist help is appropriate.

Access to sensitive information also deserves a deliberate boundary. Collecting a file does not mean every connected tool or reviewer should receive it. Decide which details are necessary for the task and what access the connection actually requires.

If a tool generates a summary or suggested reply, the reviewer should be able to inspect the original information. A fluent suggestion is not proof that the facts are complete. Ordinary rule-based automation may be enough for the preparation, and there is no need to add generation to a task that simply moves structured details.

Avoid turning every task into an approval queue

Too much review can recreate the delay you wanted to remove. Separate routine actions with stable rules from meaningful exceptions. An internal reminder may run automatically while a changed customer commitment waits for review.

Watch pending items and whether reviewers have time to inspect them. If everything is approved without reading, the safeguard is not working. Improve the information presented, narrow the decisions or reconsider what genuinely needs approval. Adding more notifications does not create more attention.

Our automation work can include drafts, review steps and internal notifications, with the permitted actions agreed before implementation. Bring a task where you want less admin but still need control. We can discuss the automatic steps and the point where a person should decide.

A few follow-up questions

Can a routine action ever run without individual approval?

Yes, when the business has agreed clear rules, suitable access and proportionate checks for the consequence. Test exceptions and recovery first. The decision should be explicit rather than an accidental result of the software's default setting.

What if the approver is away?

Define an appropriate alternative reviewer or keep the action pending. Check that the alternative has the knowledge and permission to decide. An overdue approval should not automatically become acceptance just because a deadline passed.

Do approvals remove the need for failure recovery?

No. An approved action can still fail, partly finish or be repeated. Keep the approval record connected to the action and verify what completed before retrying. Approval controls permission; recovery controls unfinished or uncertain execution.

Sources and further reading

Remove the admin without handing over every decision

Tell us what you want prepared automatically and which commitments still need your review. We can discuss a workflow with practical approval boundaries and a clear response to exceptions.

Discuss approval-based automation See what our business automation service includes
Website by TelosOps