Website

Designing Approval Workflows in Business Software: Rules, Limits and the Cases Everyone Forgets

November 11, 2026 · 7 min read · Etzal Group Team

A company introduces purchase approvals in its new system: the requester's manager approves, then finance. On paper it is perfect. In the third week the operations manager goes on leave for ten days. Forty requests wait in his queue. Urgent purchases are made by phone and "regularised later". A supervisor requests a purchase and discovers the system routes it to himself. Someone edits a request after it was approved, raising the amount. None of these was a bug. Each was a question nobody asked when the flow was drawn. Approval workflows are simple in the normal case and are defined by their exceptions.

What an approval is for

Before designing, be clear what each approval step is meant to achieve. There are four legitimate purposes.

  • Authority. Someone entitled to commit the company's money or name agrees.
  • Budget. There is money for this.
  • Correctness. Someone who knows checks that the request is right.
  • Separation of duties. The person who asks is not the only one who decides.

A step that serves none of these is a delay with a signature. Ask of each proposed approver: what, specifically, are they checking? If the answer is "they should be aware", send them a notification, not an approval.

The basic decisions

1. What needs approval

List the request types: purchases, expenses, leave, discounts, new customers or suppliers, payments, price changes, access rights, journal entries. Each may have its own flow.

2. Who approves, by rule

Define approvers by role and relationship, not by name.

  • The requester's line manager.
  • The owner of the budget or cost centre.
  • A functional specialist: finance, IT, legal.
  • A senior role above a value limit.

Named individuals in a workflow break every time someone changes job.

3. Thresholds

Scale the control to the risk.

AmountApproval
Up to a small limitNone, or line manager only
Up to a middle limitLine manager, then budget owner
Above thatAdd finance head
Above a high limitAdd director

Set the lowest threshold so that most everyday requests need one approval or none. If everything needs three signatures, people will find ways round all three.

4. Sequence or parallel

  • Sequential: one after another. Needed when a later approver relies on an earlier check.
  • Parallel: several at once. Faster, when the checks are independent.

Use parallel wherever the order does not matter.

5. All, any, or a number

When a step has several possible approvers:

  • Any one of a group, for example anyone in the finance team.
  • All of them.
  • A minimum number, such as two of three directors.

"Any one of a group" avoids dependence on a single person and is often the right default for functional checks.

Eight cases everyone forgets

1. The approver is away

  • Delegation: an approver names a deputy for a date range. The record shows who actually approved and on whose behalf.
  • Escalation: after a set time with no action, the request moves up, or to a backup.
  • Reminders before escalation.

Decide the waiting times per request type. A leave request can wait two days. A payment to a supplier with a due date cannot.

2. The requester is the approver

A manager's own request must not route to themselves. The rule: nobody approves their own request, and it goes to their manager or a peer instead. The same applies when a deputy would be approving something they requested.

3. The request changes after approval

If the amount, supplier or items change after approval, what happens?

  • Small changes within a tolerance, such as a few percent, may proceed.
  • Anything beyond that returns for re-approval.
  • The system records what changed and who changed it.

An approval that survives any later edit approves nothing.

4. Rejection

  • Is a reason required? It should be.
  • Does the request return to the requester for correction, or end?
  • After correction, does it restart from the first approver or return to the one who rejected it?

5. Sending back for more information

Different from rejection. The approver has a question. The request should return to the requester, keep its history, and come back to the same approver.

6. Withdrawal and cancellation

Can the requester withdraw a pending request? What about one already approved and not yet acted on? What happens downstream, for example to a purchase order already sent?

7. Urgent requests

There will be real emergencies. If the system has no path for them, people will act outside it.

  • An urgent flag that shortens waiting times and alerts approvers by phone or message.
  • An emergency path: a named senior person may approve alone, with a mandatory reason and an after-the-fact review.
  • A count of how often it is used. An emergency path used daily is the normal process in disguise.

8. The organisation changes

  • An approver leaves or changes role while requests are pending. Their queue must be reassigned.
  • Thresholds and rules change. Do pending requests follow the old rule or the new one?
  • A new department has no manager assigned. Where do its requests go?

A default route, to a named administrator or role, catches whatever the rules did not anticipate.

Keep it fast

The control only works if people use it, and they only use it if it is quick.

  • Approve where people are. On a phone, from a notification or a message, in one or two taps.
  • Show what is needed to decide on one screen: who, what, how much, why, budget remaining, attachments. An approver who has to open three screens will approve without looking.
  • Batch small items. Let an approver handle ten routine requests at once.
  • Measure waiting time per step and per approver, and show it.
  • Auto-approve the trivial, with a record and periodic review.
  • Remove steps that never reject. If an approver has approved 500 requests in a row without a question, the step is either unnecessary or not being done.

Make it honest

  • A complete trail. Who requested, who approved or rejected, when, with what comment, and on whose behalf.
  • No silent overrides. An administrator who can force a request through must leave a visible record.
  • Approval of what was actually seen. The record should preserve the version approved.
  • Segregation enforced by the system, not by good intentions: the requester cannot approve, and the person who approves a supplier cannot also pay them.
  • Visibility for the requester. They can see where their request is and who has it. This alone removes most "any news?" messages.

Notifications

  • Tell the approver when something arrives, by the channel they will see.
  • Do not flood. A daily digest for low-priority items, immediate alerts for urgent ones.
  • Tell the requester at each decision.
  • Remind before escalation.

Specify it before building

Give a developer this, for each request type:

  1. Who may raise it.
  2. What information it must contain.
  3. The approval steps, with roles, thresholds and whether sequential or parallel.
  4. Waiting times, reminders and escalation.
  5. Delegation rules.
  6. What happens on rejection, on a request for information, on withdrawal.
  7. What changes require re-approval.
  8. The urgent and emergency paths.
  9. What happens after final approval.
  10. Who can change the rules, and how changes are recorded.

Then walk through it with real examples from last month, including the awkward ones. If the flow cannot handle what actually happened, fix it on paper.

Configurable, within reason

Rules change: thresholds rise, departments are reorganised. Thresholds and approvers by role should be settings, changeable by an administrator with a record, not code that needs a developer. Resist making everything configurable. A workflow engine in which anything is possible is one nobody can audit.

Common mistakes

  • Approvers named as individuals.
  • Too many levels.
  • No thresholds.
  • No delegation or escalation.
  • Self-approval possible.
  • Edits after approval.
  • No emergency path, so emergencies bypass the system.
  • Approval screens without the information needed to decide.
  • Approval used where a notification would do.
  • No measurement of waiting time.

We map approval rules with clients before building, using their real cases from recent months, as part of Enterprise Software. If approvals in your current system are slow or routinely bypassed, contact us.

Summary

Give each approval step a purpose: authority, budget, correctness or separation of duties. Define approvers by role, scale levels with value thresholds and run independent checks in parallel. Decide in advance how the flow handles absence, self-approval, later changes, rejection, questions, withdrawal, emergencies and reorganisation. Make approving quick and informed, record everything, measure waiting times and remove steps that add nothing.

Frequently asked questions

What is an approval workflow?

It is the defined route a request follows before it is acted on: who must approve it, in what order, under what conditions, and what happens when it is rejected or left waiting. In software, it replaces signatures on paper and messages asking "can I go ahead?" with a recorded, enforced sequence.

How many approval levels should a process have?

As few as control genuinely requires, usually one or two for routine requests and more only above significant value limits. Each added level adds delay and reduces each approver's sense of responsibility, because everyone assumes someone else has checked. Use value thresholds so that small requests pass quickly.

What happens when an approver is unavailable?

The workflow should provide for it: delegation to a named deputy for a date range, and escalation to the approver's manager after a set waiting time. Without these, requests queue behind one person's holiday, and people start working around the system.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Website Development

Fast, SEO-ready websites that turn visitors into customers.