Automation & Orchestration
Approval workflows: a decision with an owner, a deadline and the evidence
Approvals don't belong in an inbox
Most approvals are a message: “can I give them 15%?” It sits in someone's inbox with half the context, nobody else can see it's waiting, and when the approver is on a job or on holiday, the work behind it simply stops.
An approval workflow turns the question into a saved state with an owner, a deadline and the evidence attached. The work it holds up waits visibly. Reminders and delegation are part of the rule. And the decision, with who made it and why, is recorded where the work continues.
Who approves what
Every decision is recorded
Q-240 · discount request
- done
Request created
T6, 15% off
- done
Evidence attached
repeat customer, competing quote
- done
Operations manager decides
approved 09:40
- done
Quote sent
15% off
Approved as asked. The quote went out with the decision and the approver recorded on it.
Q-240 · discount request
- done
Request created
T6, 15% off
- skipped
Operations manager decides
away until Monday
- done
Delegated to office lead
after 2 h with no answer
- done
Office lead decides
approved at 12%
- done
Quote sent
12% off
The approver being away didn't stop the work. The delegate's change is recorded beside the original request.
Q-240 · discount request
- done
Request created
T6, 15% off
- done
Operations manager decides
rejected: margin below the floor
- skipped
Quote sent
back to T6
- done
T6 told
with the reason
A no is a decision too. T6 sees the reason and can offer the customer something else.
Five parts of every approval
01
Owner
Who decides
One named approver, chosen by the rule, not whoever happens to see the message.
02
Evidence
What they need
The request, the numbers and the attachments that justify it, in one place.
03
Deadline
How long it may wait
When the reminder goes, and when waiting becomes a problem.
04
Delegate
Who decides instead
The backup when the approver is away or doesn't answer, named in advance.
05
Record
What was decided
Who decided, when, what changed and why, kept with the work.
What approval workflows hand off
In
Out
Worth building when work waits on someone's yes
Good fit
- The same kinds of decisions come up every week.
- Work stops when the approver is busy or away.
- You need to know later who approved what, and why.
Not the right fit
- Approvals are rare and the approver is always at hand.
- The rules for who may approve haven't been agreed. Settle them first.
Questions about approval workflows
Can approvers decide from their phone?
Yes. The notification carries the evidence and the decision buttons. Anything that needs a closer look opens the full request.
What if two people need to approve?
The rule says whether it's one after the other or both at once. Each decision is recorded separately.
What happens when the approver is away?
The rule names a delegate, either while they're marked away or after a set time without an answer. Nothing waits on a holiday.
Can we see everything that's waiting?
Yes. Open approvals are listed with their age and their owner, so a stuck one is visible before a customer asks about it.