Build an internal request system with Power Apps
IT tickets, equipment, leave, expenses, facilities, change requests — most internal requests still travel by email. A Power App gives you one front door, with routing and tracking built in.
What is the operational problem?
When requests arrive as emails and live in spreadsheets, there is no structured intake, no clear ownership and no audit trail. Things fall through the cracks, the same questions get asked twice, and nobody can report on volume or turnaround.
Requests buried in inboxes
No single intake point — requests arrive any way, anywhere, and get lost.
Spreadsheets doing the wrong job
A shared tracker that needs manual updates, breaks under load and tells you nothing in real time.
No ownership or SLA
Without routing, requests sit unassigned and turnaround is invisible.
What does the manual process cost?
A clear, conservative worked example — adjust the inputs to your own numbers.
Worked example: routing 40 requests a week by hand
| Requests per week | 40 |
| Admin time to log & route each | 6 minutes |
| Hours per year (×52) | ≈ 208 hours |
| Blended hourly cost | £20 |
| Direct admin cost per year | ≈ £4,160 |
This counts only the logging and routing. It excludes rework from lost requests and the frustration cost of poor turnaround.
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.
How would the Microsoft 365 solution work?
Built on tools you already own — Power Automate, SharePoint, Teams and the wider Microsoft 365 stack.
Power Apps form
FlowOps logicright owner, SLA set
status + reporting
- Staff submit through a single Power App — on web, Teams or mobile — with the fields you actually need.
- Power Automate routes each request to the correct owner and triggers Approvals where needed.
- Status, owner and SLA are tracked automatically; requesters can see where their request is.
- A simple dashboard shows volume, turnaround and bottlenecks — no manual reporting.
What licences might be required?
We confirm exact licensing at scoping — and design to avoid premium licences where we sensibly can.
Stay within Microsoft 365 (SharePoint-backed)
A Power App using SharePoint lists and standard connectors is covered by your existing Microsoft 365 Business licence — no premium add-on.
included in M365 Business
Best-value option for most internal request systems.
Power Apps Premium (if you need Dataverse)
Needed for a standalone app on Dataverse, premium connectors, or richer security and scale beyond what SharePoint lists give you.
~£16.40 per user
A deliberate cost/scale trade-off we size with you — not a default.
Indicative UK list prices, per user per month, ex-VAT, mid-2026. Microsoft is changing some Microsoft 365 and Copilot prices from 1 July 2026 — exact licensing is confirmed at scoping, never assumed.
What risks or governance checks are needed?
Automation without governance is a liability. This is the BCS-disciplined checklist we work through.
- Choose the data store deliberately: SharePoint (no premium) vs Dataverse (premium, more robust)
- Use a managed environment and a clear environment strategy
- Apply DLP policies to control which connectors the app can use
- Define ownership and an Application Lifecycle Management (ALM) plan
- Set role-based access so people see only what they should
- Plan for support and handover so the app is not orphaned
What result should the business expect?
Requests arrive in one structured place, route themselves to the right owner, and are tracked to completion. Staff stop chasing, managers get visibility, and you can finally report on volume and turnaround.
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.