Solutions Approvals

Approval routing

Requests that route themselves, chase themselves, and record who decided what.

01 / What it looks like running

Start to finish, and where a person still comes in.

  1. 01 / TriggerRequest arrives
  2. 02 / AutomatedRouted to the right approver
  3. 03 / AutomatedChased on a schedule
  4. 04 / AutomatedDecision recorded
  5. 05 / Needs a personEdge cases

Automated Needs a person 3 of 5 run without anyone

02 / What stops happening

8 steps become 1.

The struck lines are the ones nobody performs after this is live.

  1. Request arrives by email or in a form
  2. Someone reads it and works out who should approve it
  3. They forward it on
  4. It sits in an inbox
  5. Someone remembers to chase it
  6. The decision comes back by reply
  7. Someone records it somewhere
  8. Exceptions and edge cases, decided by a person

03 / Built on

In your tenant, under your licences.

  • Power Automate
  • SharePoint

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.

Book a call Next: Contract renewals