Worknano

Approval workflows: five patterns that do not slow people down

Updated 2026-11-15

An approval workflow is a fixed route that a request takes to the people who must say yes to it. The request can be an expense, a holiday or a discount for a customer. The workflow also keeps a note of who decided what. It slows people down when every request takes the longest route. The five patterns below give each request the shortest route that is still safe.

Where the time really goes

Saying yes or no takes seconds. Waiting takes days. A request waits because the boss is on holiday. Or it sits behind a step that adds nothing. Or one missing detail sends it back to the start. Each pattern removes one of these waits.

The five patterns

  1. A limit for small requests. Not every request needs every signature. A small expense needs the team lead only. A large one also goes to the person who looks after the money. Most requests are small, so most are finished after one step.
  2. A stand-in with a time limit. Give each step a time limit and name a stand-in. If the first person has not answered in time, the request moves on by itself. Nobody has to notice that a colleague is away.
  3. Ask two people at once. Sometimes two people must agree and neither needs the other's answer. Ask both at the same time. Two steps of two days each then take two days, not four.
  4. Send it back, do not refuse it. A plain no makes the person start again from the beginning. Offer a third answer next to yes and no: "please change this". The person corrects the one detail, and the request returns to the same step.
  5. Agree the rule once. Some requests fit a rule so clearly that a person adds nothing. Travel inside the agreed budget is one example. Agree the rule once and let matching requests pass. Only the exceptions go to a person.

The five patterns at a glance

PatternUse it whenWatch out for
Limit for small requestsMost requests are smallRequests split in two to stay under the limit
Stand-in with time limitAlwaysA stand-in who is away at the same time
Two people at onceEach can decide aloneTwo answers that contradict each other
Send it backRequests often lack one detailEndless back and forth: allow two rounds
Agree the rule onceA written rule existsA rule nobody looks at again

How many people should approve one request?

Each step should answer a question that nobody before it could answer. If two people check the same thing, remove one. Three steps is a sensible upper limit for a small company. Beyond that, people stop reading and simply click yes.

What to write down for every decision

Who asked, who decided, when, and with which comment. With that record you can see how long each step takes. The slowest step is the one to improve first.

How Worknano handles this

The Approvals module in Worknano lets you set, for each type of request, who approves it and in which order. You can name roles or individual people. Each step can have a time limit, after which the request passes to the next level. A step can also be skipped by a rule, for example finance only above €1,000. Approvers can approve, ask for changes or reject, and add comments. Everyone finds the decisions waiting for them under Pending and their own requests under Requests, both sortable by age. Every action is logged with the time and the person, and the history can be exported as a PDF.

Create a free workspace and set up your first approval with a limit for small requests.