SharePoint & Approvals

SharePoint document approval workflows

Policies, contracts, quotes, content — anything that needs sign-off before it goes out. SharePoint and Power Automate Approvals turn manual chasing into a controlled, auditable workflow.

1 · The problem

What is the operational problem?

Document approval by email is a governance gap. The wrong version gets signed off, there is no record of who approved what, and the document sits in an inbox waiting while someone forgets to reply. For regulated or contractual documents, that is a real risk.

Approvals lost in email

Sign-off requests sit unread; the author chases manually and the document stalls.

Version confusion

No single controlled copy — people approve the wrong draft and changes get lost.

No audit trail

When someone asks "who approved this and when?", there is no reliable answer.

2 · The cost

What does the manual process cost?

A clear, conservative worked example — adjust the inputs to your own numbers.

Worked example: 25 document approvals a week

Approvals per week 25
Chasing & version admin each 8 minutes
Hours per year (×52) ≈ 173 hours
Blended hourly cost £24
Direct admin cost per year ≈ £4,150

Illustrative inputs — substitute your own, and measure the minutes rather than estimating them. The bigger exposure is governance: an unapproved or wrong-version document going out can cost far more than the admin time.

Want the number for your business first?

The free Quick Win Identifier ranks your manual processes and estimates the annual saving in about 5 minutes.

Find your first automation
3 · The solution

How would the Microsoft 365 solution work?

Built on tools you already own — Power Automate, SharePoint, Teams and the wider Microsoft 365 stack.

Document ready
uploaded to SharePoint
FlowOps logic
Approval routed
sequential / parallel
Locked & logged
version + audit trail
  • A document added to (or updated in) a SharePoint library triggers a Power Automate approval flow.
  • The right approver(s) get a Teams/Outlook Approvals card — sequential or parallel, with reminders.
  • On approval the version is captured and the document moves to a published/approved state.
  • Every decision, comment and timestamp is recorded, giving a complete audit trail.
In detail

Do you even need a workflow?

Most guides jump straight to building a flow. The useful questions come earlier: whether you need one at all, what design decisions determine if it survives contact with real users, and what happens the first time something goes wrong.

If approvals are currently tracked in a spreadsheet, that is worth recognising for what it is first — a spreadsheet quietly running a live process. SharePoint has a built-in content approval setting on document libraries. Turn it on and a document stays in a Pending state, invisible to most readers, until someone with the right permission approves it. No Power Automate, no flow to maintain, no licence question. For a small team approving a handful of documents against a simple rule, that can be the whole answer — and it is the option most vendor guides never mention, because they are selling something else.

A Power Automate document approval workflow earns its place when the routing needs to be conditional, when more than one person signs in a defined order, when the request has to reach someone in Teams or Outlook rather than waiting to be noticed, or when you need reminders and escalation. Below that threshold, the flow is overhead.

Start here before building anything

What you needBuilt-in content approvalPower Automate approval flow
One approver, simple ruleUsually enoughOverhead
Sequential or parallel approversNot supportedYes
Routing that depends on value, type or departmentNot supportedYes
Request pushed to Teams or OutlookNo — approver must lookYes
Reminders and escalation on silenceNoYes
Audit record of comments and timestampsVersion history onlyApproval record plus history
Ongoing maintenanceNoneA flow someone must own

The five decisions that determine whether it works

Before any of this, the process needs to be written down with numbers against it — how many approvals, how long each takes, and who is involved. Documenting a process properly before automating it is what makes the cost figures above yours rather than ours.

Approval workflows rarely fail on the technology. They fail because a decision was never made, and the flow does something unhelpful by default.

Settle these before the build, not during it

DecisionWhy it bites later
Sequential or parallel?Parallel is faster but nobody sees the others’ comments before deciding. Sequential is slower and stalls entirely on the first unavailable person.
Who approves, by rule not by name?Hard-coding individuals means the flow breaks the week someone changes role. Route to a SharePoint group or a lookup, not a person.
What happens on rejection?Most builds send a notification and stop. The author then has no defined route back in, so the process quietly reverts to email.
What happens on silence?Without a reminder and an escalation path, an approval can sit indefinitely and the failure is invisible — which is the exact problem you were trying to solve.
Where does the approved version live?If the approved copy stays editable in the same place, you have an audit trail pointing at a document that may have changed since.

What breaks in the first month

These are the failure modes worth designing for up front. None of them are exotic; all of them are common enough that a build which ignores them tends to be abandoned.

  • The approver is on leave. Needs a delegate or an escalation after a set period, or the document stops.
  • The document is edited mid-approval. Decide whether that restarts the approval. If it does not, the approval record refers to a version nobody reviewed.
  • Rejection loops. A document rejected, amended and resubmitted should produce a new approval record, not overwrite the old one — the rejection is part of the evidence.
  • The flow itself fails. Flows error on permissions, throttling and deleted items. Without failure alerting to a named owner, it can stop silently and nobody notices for weeks.
  • Bulk uploads. Migrating a library can trigger an approval per document. Guard the trigger, or somebody receives four hundred cards.
  • Someone approves the wrong thing. Include the version number and a direct link in the approval request, so the approver can see what they are signing.

The audit trail an auditor actually asks for

If the reason for the project is a certification, an insurer or a contractual obligation, the test is not whether approvals happen — it is whether you can evidence them afterwards. In practice that means being able to produce, for any given document: who approved it, when, which version they saw, what they said, and what happened to anything rejected along the way.

SharePoint version history and the Power Automate approval record can together cover this, but only if retention is set deliberately. Approval history is not kept forever by default, and a flow deleted a year later can take its run history with it. Decide the retention period against what your sector requires, and keep the approval evidence somewhere it survives the flow being rebuilt.

4 · Licensing

What licences might be required?

We confirm exact licensing at scoping — and design to avoid premium licences where we sensibly can.

Microsoft 365 Business Standard or Premium

SharePoint, Teams and standard Power Automate capabilities may support a contained approval design; confirm current tenant rights and service limits. See what Business Premium can cover.

from ~£10.80 (Standard) / ~£16.90 (Premium)

Premium capability (if required)

May apply when approvals integrate with an external line-of-business system via a premium connector, use Dataverse or require another premium capability.

confirm current terms

We validate the exact licence position before the fixed-price build scope.

Indicative UK list prices, per user per month, ex-VAT, where shown. Microsoft pricing, packaging and entitlements change — exact current UK licensing is confirmed at scoping, never assumed.

5 · Governance

What risks or governance checks are needed?

Automation without governance is a liability. This is the disciplined checklist we work through.

  • Define the approval matrix: who approves what, in what order
  • Use SharePoint version control and content approval settings
  • Run the flow from a service account with least-privilege access
  • Retain approval records for the period your sector requires
  • Set escalation and reminders so approvals cannot stall silently
  • Apply DLP and sensitivity labels to controlled documents
6 · The result

What result should the business expect?

Controlled versions, one source
Complete approval audit trail
No manual chasing

Documents can move through sign-off automatically, with the correct version controlled and approvals recorded. Manual chasing can be reduced, governance can improve, and the configured audit trail can show who approved what, when.

Questions

Frequently asked questions

What is a document approval workflow?

A defined route a document takes before it can be treated as final: who reviews it, in what order, what happens if it is rejected, and where the record of that decision is kept. It can be a built-in library setting, an automated flow, or a manual process written down — the automation is a way of enforcing it, not the thing itself.

Do I need Power Automate for document approval in SharePoint?

Not always. SharePoint document libraries include a content approval setting that holds a document in a pending state until it is approved, which can be sufficient for a single approver and a simple rule. Power Automate becomes worthwhile when routing is conditional, several people approve in a defined order, requests need to reach people in Teams or Outlook, or you need reminders and escalation.

How do I set up an approval workflow in Power Automate?

In outline: a SharePoint trigger on the library, a Start and wait for an approval action, a condition branching on the outcome, and actions that update the document’s status and notify the author. Microsoft documents the click-by-click well. The part worth spending time on is not the build — it is deciding routing, rejection handling, escalation on silence and where the approved version lives, because those are what determine whether it is still in use six months later.

What licence does a SharePoint approval workflow need?

A contained design using SharePoint, Teams and standard Power Automate capabilities may be supported by Microsoft 365 Business Standard or Premium, subject to your tenant rights and service limits. Premium capability may apply if approvals integrate with an external system through a premium connector or use Dataverse. Entitlements and pricing change — confirm current UK terms with Microsoft before committing to a design.

Can approvals happen in Teams?

Yes. Approval requests can appear as a card in Teams or Outlook, so the approver acts where they already work rather than having to visit the document library. This tends to matter more than anything else for adoption: approvals that require someone to remember to go and look are the ones that stall.

How long does a build like this take?

A contained approval workflow over one library is usually a matter of days rather than weeks, and the discovery beforehand is often the longer part — mapping who approves what, agreeing the exception routes and confirming the licence position. Complexity grows with the number of routing rules and the number of systems involved.

What if an approver leaves or is on holiday?

Route to a group or a lookup rather than a named individual, and set an escalation so an unanswered request moves on after a defined period. A flow that points at one person is a flow with a single point of failure, and it will usually be discovered at the least convenient moment.

Ready to see what this is worth for your team?

Book a free 30-minute automation review and we will turn your version of this process into a costed plan — the seventh question, answered for your business.