How to design a digital approval workflow
Define who decides, when a substitute takes over and what changes require a fresh decision.

In short
- For a purchase, show the amount, supplier and budget code together.
- Give each stage an owner, a substitute and a deadline.
- Try a request just above a spending threshold, a correction after approval and a decision by a substitute.
- Next steps
On this page
Define what the decision covers
For a purchase, show the amount, supplier and budget code together. Decide which later changes invalidate approval, such as a different supplier or a higher amount. Keep the information the approver actually saw.
Assign the next action
Give each stage an owner, a substitute and a deadline. Tell requesters where their application stands and why a decision was declined. A reminder is often enough when a deadline passes. Automatic approval needs an explicit rule.
Test the awkward cases
Try a request just above a spending threshold, a correction after approval and a decision by a substitute. Two clicks or duplicate notifications should record one decision. Keep the request, decision and confirmation attached to the same record.
Next steps
Creagrid / actie
Practical checklist
Describe the problem and intended outcome.
Involve the people who use the process every day.
Test the riskiest assumption with a small prototype.
Define tests, ownership and maintenance up front.

