# Approval workflow: what it is, types, examples and how to build one

> A practical approval workflow guide: the five main types, eight examples by department, a step-by-step design method and the mistakes that slow approvals.

Published 2026-07-08 by Easyflow team. Category: Process management.

Someone wants to buy software, take a week off, give a customer a discount, or get admin access to the billing system. Each of those needs a yes from someone before it happens.

In most small and mid-sized teams, that yes travels through email, chat or a hallway conversation. It works while the team is small. Then requests start getting lost, the same question gets asked twice, approvals wait for a week because one person is traveling, and nobody can find out who approved the $9,000 contract last spring.

An **approval workflow** fixes that by giving every request the same path: the same information, the right approvers, deadlines, and a record of every decision. This guide covers the main types, eight examples you can adapt, and a method to design your own.

> **Key takeaways**
>
> - An approval workflow is a fixed path a request follows to get a decision from the right people before anything happens.
> - Five types cover nearly every case: single, sequential, parallel, by amount and conditional.
> - Design from the approver's point of view: what do they need to see to decide in under a minute?
> - Reasons on rejection, deadlines, delegates and an automatic audit trail matter more than the tool you pick.

## What is an approval workflow?

An approval workflow is the defined path a request follows from "I'd like to do this" to a recorded yes or no, before the thing actually happens. It has three parts:

1. **The request.** What is being asked, with the information an approver needs.
2. **The decision.** One or more people approve, reject or send it back, according to rules written in advance.
3. **The outcome and the record.** Someone acts on the decision (orders, books, grants access), and the whole history is kept.

The key words are *before* and *in advance*. An approval that happens after the purchase is just a notification, and an approver chosen by the requester on the spot is a favor, not a control.

## Types of approval workflows

### Single approval

One person decides, such as the direct manager on a vacation request. This is the right choice for most low-risk, high-volume requests. Add a second approver only if that person checks something different.

### Sequential (multi-level) approval

Approvers decide one after another: manager, then department head, then CFO. Each one sees what the previous approvers decided, and senior people only review requests that already passed the first check. This is the most common pattern for anything involving money.

### Parallel approval

Several people receive the request at the same time and all of them must approve. It is faster when the approvers check different things, for example finance checking the budget while legal reviews the contract terms. The cost is that senior people may review something the manager will reject anyway.

### Approval by amount (tiered)

The approvers depend on the amount. Up to $1,000 the manager approves alone. Above that, the department head joins. Above $10,000, the CFO. This keeps small requests fast and puts more eyes on large ones. The table that defines the tiers is called an approval matrix, and we cover how to set the limits in our guide to [approval matrices and approval limits](https://easy.wf/blog/approval-matrix-approval-limits).

### Conditional approval

A rule decides whether an approval step happens at all. A purchase of software might need an IT security review, while office supplies skip it. A refund over a certain amount goes to finance, while small ones do not. Conditions keep one workflow for the whole request type instead of five nearly identical ones.

| Type | Use it when | Watch out for |
|---|---|---|
| Single | Low risk, high volume | Becoming a bottleneck if the approver is often away |
| Sequential | Money, contracts, anything escalating in risk | Too many levels for small amounts |
| Parallel | Approvers check different things | Wasted reviews on requests that will be rejected |
| By amount | The risk grows with the value | Split requests to stay under a limit |
| Conditional | Some requests need an extra check | Too many conditions nobody can explain |

## Anatomy of an approval request

A good approval request lets the approver decide in under a minute without asking anything back. It contains:

- **What is being asked**, in structured fields, not a paragraph. Item, dates, system, customer.
- **The amount or impact**, calculated when possible. A total should come from quantity times price, not be typed.
- **The reason.** One or two sentences. It is the first thing every approver asks.
- **Supporting files.** Quotes, receipts, the contract draft.
- **Who is asking and for whom.** Requester, department, cost center.
- **When it is needed.** Separates urgent from "whenever".
- **The decision options.** Approve, reject with a reason, or send back for changes.
- **The history.** Who already approved, with comments.

If approvers keep replying with questions, a field is missing.

## Approval workflow examples

The amounts and roles below are examples. Adapt them to your size and risk.

| Area | Request | Who approves | Rule |
|---|---|---|---|
| Finance | Purchase request | Manager; department head above $1,000; CFO above $10,000 | Approved before the purchase order is issued |
| Finance | Expense report | Manager, then finance | A receipt for every line; finance checks the travel and expense policy |
| Finance | Supplier invoice | Budget owner of the cost center | Matched to the purchase order and receipt before it is scheduled for payment |
| HR | Vacation request | Direct manager | Decided within two business days; checked against team coverage |
| HR | Job opening | Department head, then finance, then HR | Finance confirms the role is in the headcount budget |
| IT | Access to a system | Manager, then the system owner | Least privilege; access is reviewed periodically |
| Sales | Discount on a quote | Sales manager up to 10%; sales director above | Approved before the quote reaches the customer |
| Operations | Customer refund | Support lead up to $250; finance above | Reason and order number required; refund issued only after approval |

A few of these deserve their own guide. The [purchase approval workflow](https://easy.wf/blog/purchase-approval-workflow) covers requests, ordering and receiving. The [expense report approval process](https://easy.wf/blog/expense-approval-process) covers receipts and policy checks, and the [invoice approval workflow](https://easy.wf/blog/invoice-approval-workflow) covers matching invoices before payment.

## How to design an approval workflow, step by step

1. **Pick one request type.** Start with the one that causes the most follow-ups. Purchases and time off are common first choices.
2. **List what the approver needs to decide.** Ask the current approvers: "What do you always have to ask about?" Each answer becomes a field.
3. **Name the approvers as roles.** "Requester's manager", "cost center owner", "CFO". Never a specific name in the rule itself.
4. **Choose the type.** Single if the risk is low, by amount if it involves money, conditional if only some requests need an extra check.
5. **Set a deadline for each approval.** Decide what happens when it passes: a reminder first, then escalation to someone else.
6. **Define what happens after the decision.** Who acts on a yes (orders, books, grants access)? What does the requester get on a no?
7. **Plan for absence.** Each approver has a delegate, with dates, recorded in the history.
8. **Run it for a month, then review.** Look at how long approvals take, where they wait, and how often requests are sent back.

Keep the first version linear. Request, approvals, action, confirmation. Add a condition when a real, repeated case needs it, not for every hypothetical.

## Approval workflow best practices

- **Require a reason on every rejection.** "No" without a reason produces the same request tomorrow. A short reason teaches the team what is acceptable.
- **Send back instead of rejecting** when something small is missing, like a second quote. The requester fixes it and the request continues from where it was.
- **Set deadlines and escalate.** A request waiting three days for a $200 approval teaches people to skip the process.
- **Use delegates for absence.** Vacations should not stop approvals, and the record should show who approved on whose behalf.
- **Approve before acting.** The next step (ordering, granting access, issuing the refund) should only open after the approval.
- **Never approve your own request.** If the requester is also the approver for that level, the request goes one level up.
- **Make approving easy.** Approvers who decide twice a month should not need to learn a system. An email with the summary and approve/reject buttons, leading to a confirmation page, removes most of the delay.
- **Keep the audit trail automatic.** Who decided, when, with what comment, and what the request looked like at that moment. Nobody should have to remember to save an email.

## Common mistakes

- **Too many approvers "just in case".** Each one adds a delay. If an approver never rejects anything, ask what they are checking.
- **Approving in chat.** It is fast, but the record is gone the day someone searches for it.
- **One person approves everything.** It creates a queue and a single point of failure.
- **Thresholds nobody remembers.** If the limits live in a policy PDF, people guess. The workflow should pick the approvers from the amount.
- **Not re-approving when the amount changes.** A $900 request that becomes $1,400 should be approved again at the new amount.

## Frequently asked questions

### What is the difference between an approval process and an approval workflow?

The approval process is the rule: who must approve what, and under which conditions. The approval workflow is how that rule is carried out in practice, meaning the form, the routing, the deadlines and the record. You can have a written approval process with no workflow, which usually means it is applied inconsistently.

### What is a multi-level approval workflow?

It is a workflow where a request needs more than one approval, usually in sequence, such as manager and then department head. Many teams make the number of levels depend on the amount, so small requests need one approval and large ones need two or three.

### How many approval levels should a request have?

As few as the risk allows. For most routine requests one level is enough, and two or three levels are usually reserved for large amounts or long commitments. If you find yourself adding a fourth level, check whether each approver actually reviews something different.

### How long should an approval take?

For routine requests, the same or the next business day is a reasonable target. If approvals regularly take longer, people start acting first and asking later. Deadlines with reminders, delegates and approvals from email or a phone keep most requests within a day.

## Running it in Easyflow

Easyflow runs approval workflows as a linear list of steps. The request is a form with structured fields, calculated totals and attachments, and each approval step goes to a role: a person, a group, the requester's manager, or someone picked in an earlier field. Conditions can skip an approval step, approval limits by amount pick the approvers from tiers and recalculate them when the amount changes, and there are no parallel branches, on purpose. Approvers can approve, reject or send back from the email (a confirmation page opens first), out-of-office delegates take over automatically, and the task center allows bulk approval. Every step has a deadline with reminders and escalation, and every request keeps a tamper-evident timeline. The gallery has ready-made **Purchase request**, **Expense reimbursement**, **Invoice approval**, **Vacation request**, **Job opening request**, **Access request**, **Discount approval** and **Customer refund** processes.

If your approvals still live in inboxes, read the [7 signs your team has outgrown email approvals](https://easy.wf/blog/outgrown-email-approvals).

Page: https://easy.wf/blog/approval-workflow