Solutions Approvals
Contract renewals
Renewals that surface months before they lapse, with the decision already prepared.
01 / What it looks like running
Start to finish, and where a person still comes in.
- 01 / TriggerRenewal date approaches
- 02 / AutomatedOwner notified in good time
- 03 / AutomatedSpend and usage pulled together
- 04 / AutomatedDecision recorded
- 05 / Needs a personDeciding whether to renew
Automated Needs a person 3 of 5 run without anyone
02 / What stops happening
6 steps become 1.
The struck lines are the ones nobody performs after this is live.
- Someone keeps a spreadsheet of end dates
- They remember to look at it, or they do not
- They dig out what the contract costs and whether it is used
- They chase the owner for a decision
- The renewal auto-renews while they are chasing
- Deciding whether it is still worth having
03 / Built on
In your tenant, under your licences.
- Power Automate
- SharePoint
- 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.