Approval workflows that don't slow people down: a small business guide
Approvals protect money and quality but often become bottlenecks. Learn to sort decisions by risk, set limits and delegates, separate duties where it matters, set response times and use automation to route requests.

Every small business has an approval story. A purchase request sits in someone's inbox for a week. A discount needs the owner's sign-off while the customer waits. A time-off request gets lost in a chat thread. Approvals exist for good reasons, such as controlling spending, catching errors and preventing fraud, but badly designed ones turn into bottlenecks that frustrate everyone and encourage people to work around the process.
The goal is not fewer controls. It is controls that fit the risk: quick for small, routine things and careful for large or unusual ones. This guide shows how to design approval workflows for a small team that protect the business without stalling the work. It is general information, not legal or accounting advice; if you handle significant money, ask your accountant to review your controls.
What an approval is for
An approval does one of three jobs:
- Authorize: someone with the right authority agrees that something should happen, such as a purchase or a discount.
- Check: a second person reviews the work for mistakes before it goes out, such as an invoice or a contract.
- Record: the decision is documented so you can show who agreed to what and when.
If an approval does none of these, it is just a delay. Cut it.
Cornell University's finance office describes the ideal as a setup where no one person initiates, authorizes, records and reconciles the same transaction, and says approval covers both pre-approval and review after the entry is made. That second part is useful for small teams: you can sometimes approve after the fact instead of before, as long as someone reviews.
Step 1: Sort decisions by risk
Start by listing the decisions in your business that currently need a signature or a "yes". Then group them.
| Risk level | Examples | Approval style | |---|---|---| | Low | Small supplies, routine time off within allowance, standard reports | No approval, or review after the fact | | Medium | Purchases within a set limit, discounts within a set percentage, new supplier setup | One approver, quick turnaround | | High | Large spend, contracts, payments to new payees, changes to bank details, firing or hiring | Named approver plus a second check |
Most delays come from treating low-risk items like high-risk ones. Moving them down a level frees up your attention for the decisions that matter.
Step 2: Set limits and delegate
Give people a spending or discount limit within which they can act without asking. For example, a team lead can approve up to $250, a manager up to $2,000, and anything above that goes to the owner.
Write down who can approve what
An approval policy can fit on one page. For each type of decision, list:
- Who requests it
- Who approves it, and who is the backup
- The dollar or percentage limit
- How quickly the approver should respond
- Where the request and decision are recorded
The University of Pennsylvania's audit office suggests, in its internal-controls guidance on delegation, that you list the time period, the person, the transaction types, the dollar limits and the scope, and that you review delegations at least annually. For a small business, an annual review is a sensible habit even if you do not formalize more.
Step 3: Keep the people separate where it counts
Segregation of duties sounds like big-company jargon, but the idea is simple: the person who asks for money should not be the only one who approves it, and the person who pays should not be the only one who checks the bank statement.
When you only have a handful of people, you cannot separate everything. Cornell's guidance says that where separation is not practical you should use alternative controls, such as more management review and oversight of that activity, and it suggests rotating key tasks such as bank reconciliations or approvals to help test controls and cross-train staff. In practice:
- The owner or an outside bookkeeper reviews the bank statement monthly, even if someone else enters the transactions.
- Anything the owner buys is reviewed by someone else, or by the accountant.
- Changes to bank details for a supplier are confirmed by phone with a known number.
Step 4: Make the approval easy to give
Slow approvals are often slow because the approver lacks information or has to hunt for the request. Design the request so a decision takes one minute.
- One place. Requests go to a single queue, not email, chat and paper.
- Complete requests. The form asks for amount, reason, supplier and budget line, so the approver does not need to ask follow-up questions.
- Clear status. The requester can see "pending", "approved" or "declined" without asking.
- Mobile friendly. Approvers should be able to say yes from a phone.
- Reminder and escalation. If nobody responds in a set time, the system nudges the approver and then the backup.
- A reason when declining. A short note prevents repeat requests and resentment.
Step 5: Set service levels for approvers
Agree how fast approvals should happen and measure it. A reasonable standard for a small business might be one business day for routine requests and same day for urgent ones. Review the numbers monthly: how many requests, how long they waited, which approver is the bottleneck. If one person is always the delay, raise their limit, add a delegate or remove the approval entirely.
Step 6: Use automation to route, not to decide
Automation is excellent at routing an approval to the right person based on the amount or type, sending reminders and recording the outcome. It should not make the decision for risky items. The US Chamber of Commerce advises keeping human review and approval for sensitive tasks such as financial transactions and confidential customer data. The same principle applies to AI tools: let them prepare a recommendation, and let a person approve. Our guide on AI agents and human approval explains how to keep control.
A routing rule might read: "If the amount is under $250, approve automatically and notify the manager. If it is between $250 and $2,000, send to the manager. If it is above $2,000, send to the owner and the bookkeeper."
A checklist for a new approval workflow
- Name the decision and why it needs approval (authorize, check or record).
- Rate the risk: low, medium or high.
- Set the limit and the approver, plus a backup.
- Design the request form so it is complete the first time.
- Set a response time and an escalation rule.
- Decide where the decision is recorded.
- Test with a real example, including an out-of-office approver.
- Review after one month: volume, delays and any workarounds.
Common mistakes
- Approving everything. When every request needs sign-off, people stop reading what they approve.
- One approver for everything. Add limits, delegates and backups.
- No backup. A holiday should not stop the business.
- Approvals by chat message. Decisions get buried and cannot be found later.
- Rubber-stamping. An approver who never asks a question is not controlling anything. Spot-check a sample each month.
- Letting the requester approve their own request. Even when you are small, route it to someone else.
- Never reviewing the rules. Limits that suited a three-person team may be wrong for ten.
For help deciding who should see and do what in your systems, see our guide on roles and permissions in a small company. For thinking through large purchases, try the cost-benefit check before you hire, buy or expand.
Where WorkBOS fits
WorkBOS includes roles and permissions, so you can decide who may request, approve or view something, and an audit log that records who did what and when. Its automations can route work to the right person, and its AI agents act only after a human approves. Time-off requests live alongside attendance and leave, and spending can be compared with project budgets and actuals. The pricing page shows plan differences, the docs describe how to set approvals up and the Academy has short lessons. You can apply every idea above with a shared form and a clear one-page policy if you are not using a platform yet.
Frequently asked questions
Q: How many approvals does a small business need? A: As few as the risk allows. Require approval for money leaving the business, contracts, changes to payee details and anything hard to undo. Let routine, low-value items go through with review afterwards.
Q: What if I am a solo owner with one employee? A: Separate what you can: have someone else, such as a bookkeeper or accountant, review bank statements and unusual transactions. Keep a simple log of decisions.
Q: Should approvals happen before or after the action? A: High-risk items need approval before. Low-risk items can be approved afterwards through a regular review, which keeps work moving while still catching errors.
Q: How do I stop approvals piling up while I am away? A: Name a backup approver with a limit, and set reminders and escalation. Never let one person's absence block the whole process.
Q: Can an AI agent approve things for me? A: Let it draft, summarize or flag, but keep a person as the approver for anything involving money, confidential data or customers.
Sources are linked in the text above: Cornell University Finance and the US Chamber of Commerce.
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →