In a company of eight people, approvals happen across the desk. The owner hears about the new laptop, the day off and the customer discount before anyone thinks of writing it down. Then the team grows past the point where everyone sits together, and the same questions start arriving by text, email and chat, often all three.
An approval workflow for a small business is not a bureaucracy. It is a short list of decisions that need a yes before they happen, the person who gives that yes, and a record of it. Done well, it takes work off the owner's plate instead of adding forms to everyone else's.
This guide covers what to put under approval, who should decide as the company grows, the few controls worth keeping even when you are small, and how to choose a way to run it.
Key takeaways
- Approve the decisions that commit money, access or the company's word. Leave routine work to checklists and policies.
- The owner approves everything at first. The goal of the workflow is to hand most of those decisions to managers, with an amount rule that keeps the big ones with the owner.
- Two controls are worth keeping at any size: the person who asks for a payment is not the only one who approves it, and every decision is recorded.
- Choose a tool that people can use from email or a phone in under a minute, or they will keep approving in chat.
What a small business should put under approval
Not everything needs an approval. Approvals are for decisions that are hard to undo or that commit something on the company's behalf. A useful test: if this went wrong, would the owner want to know who decided it?
| Area | Typical requests | Why it needs a yes first |
|---|---|---|
| Spending | Purchases, software subscriptions, travel, budget changes | Money leaves the company and subscriptions keep charging |
| Payments | Supplier invoices, refunds, payroll changes | Paying the wrong bill, or the same bill twice, is hard to reverse |
| People | New hires, time off, overtime, salary changes | They affect cost, coverage and fairness |
| Access | Admin rights, shared passwords, bank and payroll systems | Access is easy to grant and easy to forget to remove |
| Customer commitments | Discounts, contracts, special terms | They bind the company and set expectations for the next deal |
Things that usually don't need an approval: routine tasks with a clear owner, spending below a small limit that people can cover on a company card, and anything already decided by a written policy. For recurring work, such as opening and closing routines, a checklist with proof that it was done works better than an approval.
Who approves, as the company grows
The workflow should change as the team does. The pattern below is a starting point, not a rule.
| Team size | Who approves most requests | What stays with the owner | How it usually runs |
|---|---|---|---|
| About 5 to 15 people | The owner | Everything, but in one place instead of five | A shared form or a simple tool, with the owner approving from a phone |
| About 15 to 50 people | Each person's manager | Spending above an amount, new hires, payments to new suppliers | A tool that routes by manager and applies one amount rule |
| About 50 to 150 people | Managers, with finance for spending | Large commitments and exceptions | Rules by amount and type, delegates, and reports on how long approvals take |
The step that matters most is the middle one: moving from "the owner approves everything" to "managers approve, with an amount rule". It frees the owner's time without losing sight of the big decisions. Write the rule in one sentence, such as "purchases above $2,500 also need the owner", and adjust the amount after a few months. Our approval matrix guide covers rules with several levels.
Controls worth keeping, even when you are small
Large companies have internal audit teams. A small business can get most of the protection with a few habits:
- Requester and approver are different people. The person who asks for a payment or a refund should not be the only one who approves it. This is the core of what accountants call segregation of duties, and it is the cheapest fraud and error control there is.
- Approval comes before the action. An approval given after the purchase is a notification. If things regularly happen first and get approved later, the workflow is too slow, not too strict.
- Every decision is recorded. Who approved, when, and what they saw. You will need it for a dispute with a supplier, a question from your accountant, or an employee asking why their request was turned down.
- Amounts are checked again when they change. A request approved at $900 that becomes $1,400 should be approved again at the new amount.
- Someone covers when the approver is away. A named delegate keeps requests moving during vacations.
- Access is removed when people leave. Approving access is half the job. An offboarding checklist is the other half.
None of these needs a large tool. They need the same path for every request and a record that doesn't live in someone's inbox.
How to set it up in a week
- List the requests. Ask the team what they ask permission for, and the owner what they get asked. You will usually find five to ten request types.
- Pick the first two. Start with the ones that come up most often or cost the most, typically purchases and time off.
- Write each one as three parts: the form (what the approver needs to see), the default approver (by role), and one rule for the exception. Our guide to the simple approval workflow walks through it with examples.
- Run it for a month. Look at what got sent back, what took longest, and what still went through chat.
- Add the next requests. Expenses, invoices, access and discounts follow the same pattern.
Choosing how to run it
Small businesses typically choose between three options:
- Email or chat with a template. Free and familiar. It works for a handful of people, but the record is scattered and nobody gets reminded. See the signs you've outgrown email approvals.
- Forms and spreadsheets. Better structure and a single list, but routing, reminders and amount rules depend on someone remembering them.
- A workflow tool. Requests route themselves, rules apply automatically and the record keeps itself.
If you look at tools, check these points before price:
- Deciding is quick. Approvers can approve from an email or a phone without logging in to a dashboard first.
- Rules are simple to set. An amount threshold and a manager-based approver should not need a consultant.
- People outside the company are free. Suppliers, customers and candidates often take part, and they shouldn't count as paid users.
- The record is yours. You can export the requests and decisions at any time.
- Pricing is published. You can see what the team will cost as it grows.
Our comparison of approval workflow software for small teams looks at several options in more detail.
Common mistakes
- Copying a large company's workflow. Three approval levels on a $200 purchase teach people to work around the process.
- The owner as the only approver forever. It works at ten people and becomes the bottleneck at thirty.
- No reason on rejections. Requesters guess what went wrong and send the same request again.
- Approvals in chat "just this once". Once becomes the norm, and the record disappears.
- Never revisiting the amounts. A limit that made sense at ten people is too low at fifty.
Frequently asked questions
Does a small business need an approval workflow?
Once more than a few people can spend money, grant access or make promises to customers, yes. It doesn't have to be formal: a short form, one approver and a record are enough to start.
What should require approval in a small business?
Decisions that commit money, access or the company's word: purchases and subscriptions, payments and refunds, hires and time off, admin access, and discounts or contracts. Routine work with a clear owner usually doesn't.
Who should approve purchases in a small company?
At first the owner, then each person's manager, with purchases above a set amount also going to the owner or to finance. The amount depends on your margins and cash, and should be reviewed as the company grows.
How do I stop the owner from being the bottleneck?
Give managers approval for routine requests and keep only the exceptions with the owner, using an amount or a request type as the rule. Add a delegate for when the owner is away, and let approvals happen from a phone.
Running it in Easyflow
Easyflow is made for this stage: processes are straight lists of steps that anyone can read, approvals go to roles such as the requester's manager, and an approval limit by amount keeps the large requests with the owner or finance. Approvers decide from the email (a confirmation page opens first) or their phone, delegates take over during time off, deadlines come with reminders, and every request keeps a tamper-evident record you can export. People outside the company take part without an account and never count as users. The gallery has ready-made Purchase request, Expense reimbursement, Invoice approval, Vacation request, Access request and Discount approval processes, there is one published price, and the trial is free for 14 days without a card.