Somebody on your team needs a new laptop. They email their manager. The manager forgets, gets a follow-up, replies "sure, ask Dave about budget." Dave is on vacation. Two weeks later the request is buried under forty other threads and the employee is still working on a machine that takes ten minutes to boot. Nothing about this is unusual. Most small businesses run every approval this way: purchases, time off, discounts, contracts, new hires. Email is where those requests go to stall.
An approval workflow fixes this by making the request a thing that exists in one place, with a status, an owner, and a clock. Instead of a message in someone's inbox, it's an item in a system: submitted on this date, waiting on this person, approved or rejected with a reason attached. Nobody has to search their email for "the yes." The yes is right there.
What an approval workflow actually is
Strip away the vendor language and it's four parts:
- A form. The requester fills in what they need, how much it costs, and why. Structured fields, not a free-form email, so the approver has everything up front instead of asking three clarifying questions.
- A routing rule. Purchases under $500 go to the direct manager. Over $500, they also go to the owner. Time off goes to whoever runs the schedule. The system decides who sees it, not the requester.
- A decision with a record. Approve or reject, with a comment. Timestamped. Attached to the request forever.
- Notifications. The approver gets pinged when something needs them. The requester gets pinged when it's decided. Nobody follows up manually.
That last part is where the real time savings live. In an email chain, the requester does the chasing. In a workflow, the system does.
Escalation and delegation
Two features separate a workflow that works from one that just moves the bottleneck.
Escalation means a request that sits untouched for a set time, say three business days, automatically bumps to the next person up or fires a reminder. Approvers are busy people. Without escalation, your fancy new system stalls exactly like email did, just in a different inbox.
Delegation means an approver going on vacation can hand their queue to someone else for a week. Requests keep moving. When Dave is out, Dave's approvals don't wait for Dave. We see companies skip this setting and then wonder why everything freezes every time a manager takes a Friday off.
The audit trail is not optional
Six months from now, someone will ask "who approved this?" Maybe it's a $4,000 charge nobody remembers. Maybe it's your accountant at tax time. Maybe it's a dispute about whether a discount was authorized. With email, you're hoping the thread still exists and that you can find it. With a workflow, you pull up the request and the answer is on the screen: who asked, who approved, when, and what they said. If you're in an industry with any compliance requirements, this stops being nice-to-have and becomes the whole point.
What tools to use
You almost certainly don't need to buy anything new. Approval workflows come bundled with software you probably already pay for:
- Microsoft 365: the Approvals app in Teams handles basic request-and-approve out of the box. Power Automate handles routing rules, multi-step approvals, and escalation when you outgrow the basic app.
- Google Workspace: Google Forms feeding a Sheet gets you surprisingly far, and AppSheet can add real routing on top if you need it.
- Purpose-built tools: if approvals are core to your business, tools like Jotform, Kissflow, or the approval features inside your accounting or HR software may fit better than a general platform.
Start with what's in your existing subscription. The tool matters far less than the discipline of using one path for requests instead of five.
How to roll it out without a revolt
Pick one approval type, not all of them. Purchase requests are usually the best first candidate: high pain, clear rules, easy to define. Build the form, set the routing, set an escalation timer, and test it with two or three real requests before announcing anything. Then tell the team the email path is closed as of a specific date. If people can still email their manager for approval, they will, and the system dies quietly. One path, enforced.
After the first type runs smoothly for a month, add the next one. Time off, then expense reimbursement, then whatever else generates chase-me email threads.
How you know it's done right
Three signs. First, when someone asks "did that get approved?" the answer takes ten seconds to find, not a search through email. Second, requests don't stall silently: anything sitting too long pings someone automatically. Third, and this is the real test, people stop routing around the system. If employees are still texting the owner for a quick yes, the workflow is too slow or too complicated, and that's a fixable problem, not a reason to go back to email.
We set these up regularly, usually inside Microsoft 365 or Google Workspace a client already pays for. Most take an afternoon to build and a couple weeks of tuning. Cheap fix for a problem that wastes hours every single week.
Stuck on this, or want it done for you? That's the job.
Email us →