Solutions Approvals
Leave and absence
Requests approved in the chat window they were asked in, with the team calendar and the morning digest updated behind them.
01 / What it looks like running
Start to finish, and where a person still comes in.
01 / Trigger Leave requested
02 / Automated Balance and clashes checked
03 / Decision Balance available, no clash?
Clear
04 / Automated Sent to the manager to confirm
Clash or no balance
05 / Automated Requester told why, before anyone is asked
06 / Automated Alternative dates offered
07 / Automated Calendar and team availability updated
08 / Automated Who is out today posted each morning
09 / Needs a person Approving, in one click
Automated Needs a person 7 of 9 run without anyone
02 / What stops happening
7 steps become 1.
The struck lines are the ones nobody performs after this is live.
- Someone emails or messages their manager
- The manager checks the balance somewhere
- They check whether anyone else is off that week
- They reply yes, and mean to update the calendar
- The calendar is updated later, or not
- The team finds out who is off by noticing
- The decision itself, in one click
03 / Built on
In your tenant, under your licences.
- Power Automate
- Microsoft 365
- Power Apps
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.