Travel Approval App on SharePoint with Teams Approvals
International law firm
In short
How can travel approvals move from email to Teams without a heavy custom build?
Travel approvals sent by email wait for someone to notice them, go to the wrong person when teams change and leave no clean record. We built a light solution on SharePoint and Teams Approvals that routes each request by team and writes the decision back, without a heavy custom build.
Results in numbers
- build effort
- 30 hrs
- SharePoint lists
- 2
At a glance
- Two SharePoint lists and one approval flow
- Approvals answered from Outlook or Teams
- Built in about 30 hours
The client
The client is an international law firm with offices worldwide. The solution serves its services company, where staff raise travel requests for themselves or a colleague on Microsoft 365.
What it was costing them
- Chasing approvers: a request sent by email sits until someone notices it, and nobody can see where it stands.
- Wrong recipient: without a maintained matrix, requests reach people who changed role or left the team.
- Weak record: decisions and comments sit in mailboxes, so an audit question means searching inboxes.
- Re-keying: details are copied by hand from a template into emails and trackers.
- Growth ceiling: each new team or country adds another variant of the same process.
What we built
We built a request list, an approval matrix list and one Power Automate flow that sends approvals to Teams and Outlook.
- One place for requests: a Travel Approvals list of about 15 columns, up to 20, mirrors the existing request template.
- The right approver every time: an Approval Matrix list maps each team to up to three approvers and can be edited without touching the flow.
- Fast decisions: any one approver answers from Outlook, Teams or mobile, with an optional comment.
- Nothing falls through: the requester and the traveller receive a confirmation and can cancel the request.
- A clean record: the flow writes the status, decision and comment back to the request.
- Works where staff already are: the lists embed in a Teams channel and open on desktop and mobile.
- Own items only: views limit each person to the requests they raised.
- Low licence footprint: standard Microsoft 365 licences cover the lists and approvals, and one technical account carries the premium licence the flow needs.
- Room to grow: a canvas app, a notification flow and automated audit exports are listed as later steps.
Results
- The solution uses 2 SharePoint lists, 2 flows at most, 1 technical account and 3 test accounts.
- Built in about 30 hours across a specialist and a senior consultant.
- Result: approvers answer from the email or Teams notification they already receive, which removes most manual chasing.
- Result: every request carries the same fields, so a complete record can be exported for audit on demand.
The risk most teams miss
A SharePoint based solution is quick, but at month three its limits show. Access by organisation structure, read-only audit views and back ups need extra work, and the flow depends on one technical account. The solution keeps the matrix in a list anyone authorised can edit, names a technical account and recommends regular automated exports. Dataverse is the route if security needs grow.
What we would add today
Improvements we would add on top of what is live.
- Move requests to Dataverse with row level security by region and a read-only audit role.
- Replace the single technical account with a service principal and connection references, deployed through a Power Platform pipeline.
- Add a canvas app or Power Pages form with policy checks, such as cost limits and travel class, before submission.
- Add multi-stage approvals with escalation after a set time, so a silent approver never blocks a trip.
- Add a Copilot Studio agent that answers who approves a trip and where a request stands, using the matrix.
Technology
SharePoint Online, Power Automate cloud flow, Microsoft Teams Approvals, Outlook, Microsoft 365.
Tell us how your teams approve travel today, and we will tell you which approval design fits and what it takes to run.
Products and capabilities
- Power Automate
- SharePoint
- Microsoft Teams
- approval workflow
- travel approval
- Teams approvals
The service behind this work
Power Platform development
Related use cases
HR and peopleLeave Management App: Accrual and Adjustable Leave Features
A leave app that applies one accrual type to every policy and cannot adjust a balance sends HR back to manual corrections. The client already ran a leave app built on Power Apps and SharePoint. We built two new features, hourly or daily accrual per policy and adjustable leave, in about 20 hours.
- 14
- tasks, two features
- 20 hrs
- for both features
Onboarding Solution Assessment and Action Plan
The onboarding solution is a global onboarding solution that people and culture teams rely on. It ran in a single production environment, so every hand edit added a hidden layer that blocked later updates. We assessed the whole solution and gave the client a clear action plan to bring it back under control.
- c. 30
- connection references
Overtime Management in Microsoft Teams
When overtime requests arrive by paper, mail, chat and phone, nobody can say with confidence who worked extra hours, and the data is too poor to report on. The client wanted to digitalise overtime requests but keep its formal PDF template. We delivered an app in Teams with multi-level approvals that prints each request on that template.
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.