Workflow automation

Where a person must stay in the loop: 10 decisions not to fully automate

Workflow automationBy Fiona Wang8 November 20269 min read
Illustration for Singapore B2B provider matching and regulatory benchmarks
Public sources cited 2026 S$ Fee Benchmarks 1–5 Free Quotes
Illustration of an open book whose pages turn into signal waves

In short: Do not ask whether to automate or not. Ask which rung a step sits on: the software does it, the software drafts and a person approves, or a person still decides. Money, promises and access sit on the upper rungs until you can see a bad result before it leaves.

Owners do not usually ask for a philosophy of humans and machines. They ask where the line is, often after the line has already been crossed. A poster who described themselves as running lean said a quote went out on the wrong terms because nobody paused it, and asked where other people let systems decide. The same thread asked for moments that should never have been automated. Another self-described small business asked how to keep automation from sounding unlike them. A further self-described owner said an automated proposal reached a client it was not for. These are single reports. They were not investigated. They are enough to design a line you can explain to a new hire.

The line is not “AI versus a person”. It is three rungs, chosen per step.

Rung The software may A person must
Automate Do the step and record it Look only when the check fails
Draft and approve Prepare the record, the file or the message Accept this version before it counts
Keep manual Gather context, remind, file Decide

A step can move down the ladder after you have evidence, not because a demo looked smooth. Moving a step up the ladder, toward unattended, is a decision with a name on it.

Technology & cybersecurity illustration for Where a person must stay in the loop
1Tell us the needScope, budget, timing2Concierge callWe confirm requirements3Registry checksACRA, licences, fit41–5 introductionsCompare quotes free5You decideDecline any; nothing owed
How FYAdvisers matching works
Checklist before you hireEntity is live on ACRA BizFile+ (check the UEN)Certifications that fit the job: CREST/OSCP testers, CSA, ISO 27001Named lead and who actually deliversWritten scope, deliverables and retest or support termsPDPA handling, NDA and data locationFixed price vs day-rate, and change-request rules
Singapore B2B Vetting & Concierge WorkflowHow we verify and match 1 to 5 providers for your brief
01
Registry & Licence CheckACRA, MAS, CSRO, BCA, MOM & ISO status verified
02
Scope & 2026 Fee AuditItemised S$ benchmarks with hidden traps flagged
03
1 to 5 Vetted QuotesCompare proposals from matched Singapore firms
04
100% Free for BuyersZero obligation; providers fund the service

1. Quotes and commercial terms

Risk. A price, a date or a term leaves as if the company meant it.

Around it. Pull the last agreed price, the quantity and the open questions into a draft.

Approval. The person who may bind the company sees the draft and the source figures, and sends it. Quotation software on this site is built around that review. A quote that “went out because nobody paused it” is this rung ignored.

Failure mode. The workflow treats a template as consent. Timeout must not send.

2. Supplier bank details

Risk. The next payment goes to an account a fraudster named.

Around it. Store the request as pending. Do not let a pending number onto a payment screen.

Approval. Verify using a phone number or contact you already held, then a second person if you have decided the amount warrants it. The supplier guide is the control. This rung is “keep manual” for the verification itself. Filing the request can be automated.

Failure mode. The approver “corrects” a digit after verification. That edit has to void the check.

3. Releasing a payment

Risk. Money moves twice, or moves without an accepted bill.

Around it. Match the invoice, hold mismatches, record the approver. Invoice approval stops before the payment run on purpose.

Approval. The payment run has its own approver. The person who approved the invoice is not automatically that person.

Failure mode. A retry after a timeout creates a second payment. The business key has to make the second attempt a lookup, not a new transfer.

4. Messages during a dispute or a known hardship

Risk. A standard chaser lands on a customer you had promised to leave alone.

Around it. The overdue reminder can flag the invoice and suppress the draft while a hold is on.

Approval. A person writes or releases anything that interprets the dispute. The template does not.

Failure mode. The hold stops only the next stage, and a later stage still sends. The hold has to stop the sequence.

5. The list of people who will receive a bulk message

Risk. The right words go to the wrong segment. That is the shape of the irrelevant proposal email in the freelancer story.

Around it. Build the segment and show the count and a sample of names.

Approval. Approve the list, not only the template. A changed filter is a new approval.

Failure mode. “Everyone who is a customer” includes people who asked not to be written to, or people in a different company with a similar name.

6. Hiring and rejection

Risk. A score becomes a decision, and the person never sees the reason.

Around it. A workflow can collect documents and book a conversation. If a model scores candidates, the PDPC’s Advisory Guidelines on the use of personal data in AI recommendation and decision systems (1 March 2024) are about systems that recommend or decide using personal data. They are not a ruling on every chat box. Read them before you let a score reject someone. This article does not say a tool is lawful or unlawful.

Approval. A person makes the decision. The score, if you use one, is an input they can override, with the override recorded.

Failure mode. The lowest score is never shown to a human because the workflow already sent the rejection.

7. Granting or removing access

Risk. A joiner gets a copy of someone else’s permissions, or a leaver keeps a door open.

Around it. Tasks, role templates, and a log. The onboarding and offboarding guides split those jobs.

Approval. Someone confirms the role before activation, and someone confirms each system actually closed.

Failure mode. A tick on a checklist is treated as proof the application disabled the account.

8. Discounts and credit notes

Risk. A margin disappears because a rule was wider than anyone meant.

Around it. Calculate the discount and show it against the original. Do not post it.

Approval. Under a ceiling you write down, a named role. Above it, a second role. The ceiling is yours, not a figure from a software tutorial.

Failure mode. An edited draft keeps the old approval. A new amount needs a new decision.

9. Anything you send in your own voice to a long-standing client

Risk. The relationship hears a template at the moment it needed a person.

Around it. Remind the owner. Draft from the file if it helps.

Approval. They send. The authenticity question in that thread is this rung. You do not solve it by making the template warmer.

Failure mode. A “small” automation, such as a renewal note, carries a price the file no longer supports.

10. Anything the workflow cannot classify

Risk. The unsure item is forced into the nearest folder and treated as done.

Around it. A queue with the original file and the reason it was unsure.

Approval. A named person, with a deadline on the queue, not on the customer. If they do not act, the item stays. It does not default to send.

Failure mode. The queue is nobody’s job, so the oldest items are the dangerous ones.

What is reasonable to automate outright

Internal notifications to a named person. Filing a document that passed a type check into a folder that same person can open. Reminding staff of a date that already exists in a system you trust. Copying a validated field from one record to another when a duplicate check has run. These are the high-catchability items in what to automate first. They are not a moral category. They are steps where a bad output is visible before it matters.

How to design the approval so it is real

The approver must see the version they are approving: the file, the amount, the recipient list, and what will happen if they accept. A mobile ping that says “approve?” without the document is how rubber stamps happen. If the queue is so long that people stop reading, narrow the rule that enters the queue. That is a design change. It is not a reason to remove the person.

Write the timeout down. A timeout may escalate to a deputy or it may expire the request. It must not perform the customer-facing or money-moving step. Power Automate’s cloud-flow run limit, including steps that are waiting, is a separate constraint. The long-running approval guide is about storing the decision somewhere that outlives the run. Other platforms have their own limits. Check them. Do not borrow Microsoft’s number for a different product.

Keep the decision in a record you can export: who, when, which version, and the rejection reason. The retention guide explains why the platform’s own history is the wrong archive. An approval log is a business record. A run log is not, once the vendor deletes it.

If you are comparing this with an “agent” that takes actions, the agent versus workflow guide is the place those permissions are questioned. An agent does not get a higher rung than a workflow. It gets a lower one until you have seen it be wrong safely.

What the approver’s screen has to show

If the screen is thinner than the decision, people approve the screen and not the decision. Minimum contents, for any rung that says draft-and-approve:

On the screen Why
The exact version, with a version id So a later edit cannot reuse this approval
The amount, date or recipient that will be acted on Not a summary that hides the field
What will happen on accept: send, post, pay, or only file The verb matters
What will happen on reject, and where the item goes Reject must be a real state
The timeout and the deputy So absence is not an accidental send
A link to the source document So the approver is not trusting a paraphrase

A timeout table you can copy into the design, and then change:

If the approver does nothing Internal reminder Customer message or payment
Four working hours Escalate to the deputy Do not send or pay
They reject Close this version Do not send or pay
They edit the amount Treat as a new version The old approval dies
The platform run expires The business record stays pending Still do not send or pay

The last row is why the Power Automate guide exists. A 30-day platform limit is not permission to auto-approve on day 31. Other products do not inherit Microsoft’s number. Ask them what their wait step does at the end.

Illustrative scenario

Illustrative scenario, not a client. A professional-services firm wants renewal quotes to go out without a partner opening each one. Four steps, four rungs.

Step Rung Why
Notice that a renewal date is 45 days away Automate Internal, checkable, no promise
Draft the quote from last year’s scope and this year’s rate card Draft and approve The partner sees scope and price
Send the quote Draft and approve Same person sends, or a deputy under a ceiling
Apply a discount the client asked for on the phone Keep manual The reason is not in the file

The firm does not measure a faster renewal cycle in this scenario. It measures whether a wrong rate can leave. It cannot, unless the approver chooses it.

Limits

The ten items are the decisions that show up when money, access or a relationship can be harmed. They are not a legal standard of care. The stories are single posts, mostly from outside Singapore, from people who described their role themselves. No share of businesses is claimed.

The same review rule belongs in an AI brief: questions to ask an AI agency and the AI pilot acceptance checklist.

To place one step on the ladder, use the workflow service or WhatsApp +65 9071 3976 (chat).

Frequently asked questions

Does keeping an approval cancel the benefit?

It cancels unattended speed on that step. It keeps the benefit of gathering the file, checking for duplicates and putting the right context in front of one person. If the approval is rubber-stamped because fifty items arrive at once, the design has failed and the batch is too wide, not because approval is a foolish idea.

Can approvals happen in WhatsApp?

Only if the tool you use can record who approved which version, and the approver can see the document rather than a one-line summary. Do not assume a chat reply is an approval record. This site does not promise a WhatsApp approval feature.

How do follow-ups stay personal?

Let the workflow remind you, and sometimes draft from facts you already hold. A person sends anything that interprets a relationship. A poster who described automating email and a notes tool asked how to keep that balance. The draft is the practical answer. An auto-send is the thing they were worried about.

Who approves when I am away?

A named deputy, set before the leave, with a ceiling. An out-of-office reply is not a deputy. If nobody is delegated, the item waits. It does not fall through to send.

Chat on WhatsAppConcierge · +65 9071 3976
Get Free QuotesWhatsApp Us