Solutions Approvals
Spend approval
Requests that approve themselves under the limit, and route to the right person over it.
01 / What it looks like running
Start to finish, and where a person still comes in.
01 / Trigger Request submitted
02 / Automated Budget and cost centre checked
03 / Decision Within the requester’s limit?
Within limit
04 / Automated Approved and logged automatically
Over limit
05 / Automated Routed to the budget holder
06 / Automated Chased until answered
07 / Automated Requester told either way
08 / Needs a person Deciding on anything over the limit
Automated Needs a person 6 of 8 run without anyone
02 / What stops happening
8 steps become 1.
The struck lines are the ones nobody performs after this is live.
- Someone emails a request to whoever they think approves it
- That person checks whether there is budget
- They work out whether it is theirs to approve
- They forward it on if it is not
- It waits in a second inbox
- Someone chases
- The answer is recorded in an email thread and nowhere else
- Deciding on the spend that is genuinely a decision
03 / Built on
In your tenant, under your licences.
- Power Automate
- Power Apps
- Dataverse
Yours may differ. What a process runs on is decided by what it touches, not by what we prefer building with.
Does yours run like this?
It probably runs nearly like this, with two steps that are entirely your own. Those two are the interesting part.