Approval workflow: how to design one that does not get lost in email
SynaptaGrid9 min read
In short
An approval workflow is a defined path a request follows until someone with the right authority approves or rejects it, with the decision recorded. A workflow that holds up has five parts: a request that arrives in one place, automatic checks before a person is asked, a clear rule for who approves, a decision saved on the item itself, and a visible history of what each step did. Email fails because it has none of these: the request is scattered, nobody is named, and the outcome is a reply in someone’s inbox. Design the approver rule first, because it decides who is asked and what counts as approved.
Read the transcript
This is the workflow. Purchases of 1,000 or more go to a manager. Smaller ones are approved automatically.
Each step and each route is defined here, so anyone can see how a request travels.
A purchase request is submitted: 4,800 for laptops.
The workflow starts on its own and waits for a person.
The run is waiting on a decision.
The amount is 1,000 or more, so the rule sent it to Manager approval.
The approval task is waiting for its approver.
The approver claims the task.
Then chooses a decision and gives a reason.
The decision is saved with the task.
The run continues by itself and the outcome stays with the run.
Every step, the route taken and who decided are kept in the run history.
The five parts of an approval workflow
Whatever you approve (a new supplier, a purchase, a leave request), the same five parts decide whether the process works.
- One place for the request
- The request arrives as a record with its details, not as a forwarded message, so every approver sees the same facts.
- Checks before a person
- Anything a machine can check (a field is filled, a number is under a limit, a company exists in a register) runs first, so people are only asked about what needs judgment.
- A rule for who approves
- The workflow states who decides: one named person, anyone in a role, or a group that must agree. A request that waits for “whoever sees it” waits forever.
- The decision on the item
- Approved or rejected is saved on the record, with who decided and why, so the answer is where the next person looks.
- A history of the steps
- Each run shows what every step did, so a stuck or failed request can be found and fixed.
An approval with a check
Choosing who approves: seven rules
The approver rule is the design decision that matters most. These are the rules a workflow can use, from simplest to most flexible.
| Rule | Who is asked | When it fits |
|---|---|---|
| One person | A single named user | A budget owner who alone can sign off |
| A list of people | A short list of named users | A small team where any listed person can pick it up |
| A role | Everyone who holds a role, such as Finance manager | Approval belongs to a job, not a person, so holidays and job changes do not stall it |
| Quorum | A pool of voters, with a number of identical votes required | A committee: three of five must approve |
| Weighted | Voters whose votes carry different weights, with a total weight required | A board where some members count for more |
| Any of | A group where the first decision wins | Speed matters and any one of several people can decide |
| All of | A group where every person must approve | Sign-off that needs each department, such as legal and finance |
The old way and the new way
The table compares an approval that runs by email with one that runs as a workflow on a record.
- The request
- The old way: Details forwarded between inboxes, so each person sees a different version
- The new way: One record that everyone opens
- Checks
- The old way: Someone looks up the registry or the limit by hand
- The new way: A step runs the check and shows the result
- Who decides
- The old way: Whoever replies first, or whoever the sender remembers
- The new way: A stated rule: one person, a role, a quorum or all of a group
- The outcome
- The old way: A reply buried in a thread
- The new way: The decision, saved on the record
- When something breaks
- The old way: The request is lost and nobody knows
- The new way: The failed step is visible, the item is not approved, and the run can be repeated after the fix
- Evidence
- The old way: Search inboxes and rebuild the story
- The new way: A run history with each step’s result
Common design mistakes
- Asking a person to do a machine’s job
- If the approver spends the time checking that a form is complete, the check belongs in an earlier step.
- Naming people, not roles
- A workflow that names one person stops the day that person is away. Use a role when the authority belongs to the job.
- No rule for failure
- Decide what happens when a check cannot run. The safe answer is that the item is not approved and someone can see why.
- Approval without a record of why
- A bare “approved” cannot be explained later. Save who decided and, for a rejection, the reason.
- Too many approvers
- Every extra approver adds waiting time. Ask only the people whose judgment changes the outcome.
How we decided
In SynaptaGrid Automation a workflow is a set of steps. A step can run a check, call another system, or ask a person. When it asks a person, the workflow uses one of the seven approver rules above, and the rule is part of the step.
We chose to make the approver rule explicit and one of a fixed set, not free text. The cost is that a very unusual rule needs a workflow step of its own. The benefit is that every approval says who may decide and what counts as approved.
We chose that a failed step does not approve the item. In the example we built and ran in our own workspace, a company check failed with a service error: the run showed the failed step and the record was not approved. After the record was corrected and saved, a new run passed the same step. The recovery in that example was a new run, not a rewind of the first.
We save the outcome on the record and keep a run history with each step’s result, so the answer to “what happened to this request” is in two places a person already looks.
Standards and accepted practice behind this
These are the practices we build against. We align with them. This page does not claim a certification.
- Segregation of duties
- The person who raises a request should not be the only person who approves it. A role or a quorum makes that rule easy to keep.
- Source: NIST glossary: separation of duty (opens in a new tab)
- Least privilege
- Approval authority goes to the roles that need it and no wider.
- Source: NIST glossary: least privilege (opens in a new tab)
- BPMN 2.0 vocabulary
- The common notation for drawing process steps, gateways and tasks. It is a useful way to sketch a process before building it, even when you do not build in BPMN.
- Source: OMG: BPMN 2.0 specification (opens in a new tab)
- Audit trail
- Accepted practice for approvals that matter: who decided, when, and on what information.
- Source: NIST glossary: audit trail (opens in a new tab)
Where SynaptaGrid fits
SynaptaGrid Automation runs approvals like the one above: a request arrives as a record, a step checks it, a person decides, and the outcome is saved on the record. Each run keeps its history with the result of every step.
The supplier approval example on the site was built and run in our own workspace. A person can also decide from an AI assistant connected to the workspace: in our live run in November the assistant listed the signed-in person’s open task and recorded the decision with a reason code, and the run moved to Published. The decision is recorded under the person, not under the assistant.
Frequently asked questions
- What is an approval workflow?
- It is a defined path a request follows until someone with the right authority approves or rejects it. The path states the steps, who decides at each one, and where the decision is recorded.
- How do I design an approval workflow?
- Start with the approver rule, then add the automatic checks that should run before a person is asked, then decide where the decision is saved and what happens when a step fails.
- What is the difference between an approval workflow and an approval process?
- The process is how the business wants approvals to work. The workflow is that process made explicit as steps a system runs, so it behaves the same way every time.
- Can several people have to approve?
- Yes. A workflow can require every person in a group, a number of votes from a pool, or votes that carry different weights. It can also accept the first decision from any of several people.
SynaptaGrid
Run one approval end to end
Walk through your own approval with us and see the check, the decision and the history.