Approval points that don’t become the new bottleneck
Keeping a person in the loop only works if the loop is fast. How to design approvals people can clear in one view.
“Human in the loop” is easy to promise and easy to get wrong. If every item waits for someone who has to open three systems before saying yes, the bottleneck has moved, not gone. In finance and healthcare the approval is the point: recording, paying, scheduling and anything clinical stay with people. So the approval deserves as much design as the automation around it.
These are the rules we build to.
One approval, one decision
Each card asks one question: record this entry, send this follow-up, mark this referral ready to schedule. If a reviewer has to make two decisions, it’s two cards.
Bring the evidence to the decision
The card carries what’s needed to decide: the invoice, the purchase order and the difference; the referral and the fields that are missing; the draft message and who it’s going to. The reviewer shouldn’t need another tab.
Decide in writing what needs a person
Not everything does, and pretending otherwise floods the queue. Agree on the line before go-live. An invoice that matches its PO within tolerance can wait in a batch for one approval; a mismatch gets its own card. A complete referral goes to the scheduling queue; one that’s missing insurance details goes back to the referring practice with a drafted request, for your team to send. Review the line after the pilot, with the exceptions in front of you.
Name the approver, and the backup
An approval assigned to “finance” waits. One assigned to the AP lead, with a named backup for the days they’re out, gets cleared.
Put it where people already work
Teams, Outlook, the intake queue. A new dashboard is one more place to check, and usually the last one checked.
Keep the record
Who approved, when, and what they saw. That record is what lets a controller or a practice manager trust the workflow, and it’s what you need when someone asks why.
In healthcare, some decisions never reach the workflow
Clinical triage, care decisions, coding changes and the rules for contacting patients stay with qualified staff. The workflow handles the administrative routing around them: collecting the referral, checking the required fields, drafting the follow-up for review.
Designing approvals this way is how control stays with your team without your team becoming the slowest step. How we handle financial and patient data covers the rest: access, logging, and the agreements we work under.