Building an HR Management System on Power Platform: A Practical Guide for UK HR Teams

A practical guide to building a bespoke HR Management System on Microsoft Power Platform, covering the Model-Driven App employee database, a React/TypeScript Code App mobile self-service app, Power Automate HR workflows, Power BI people analytics, and a head-to-head cost comparison against Workday, SAP SuccessFactors, Sage People, and BambooHR. Includes licensing requirements and a phased 18-week implementation plan.

What You Can Build on Power Platform

A full HR Management System built on Microsoft Power Platform typically comprises four components that work together as a single, integrated suite:

• Model-Driven App (HR Manager Desktop), the central HR database and case management tool used by HR managers and business partners. Built on Dataverse.
• Code App (Employee Self-Service Mobile App), a React/TypeScript application built natively within Power Platform, delivering a polished mobile-first experience employees actually want to use. Runs inside the Power Apps player on iOS and Android with no separate deployment.
• Power Automate Flows, automated workflows for onboarding, offboarding, absence approvals, performance review scheduling, and compliance reminders.
• Power BI Dashboard (People Analytics), real-time workforce dashboards covering headcount, absence rates, turnover, recruitment pipeline, and training compliance.

This guide walks through each component, the cost comparison against the major HR platforms, and a phased implementation plan.

How Power Platform Compares to Traditional HR Systems

Before building anything, your organisation needs to make a clear-eyed decision: build on Power Platform or buy a dedicated HR system? Here is the honest comparison.

Licence cost comparison (per employee per month)

3-year total cost of ownership (500 employees)

Against Sage People (the most realistic mid-market comparator for UK organisations with 200–1,000 employees) Power Platform delivers comparable HR functionality at a lower or equivalent 3-year cost, with significantly greater customisation headroom.

Against Workday, the saving is £750,000–1,700,000 over three years. Workday's value is in global multi-entity payroll, advanced workforce planning, and deep analytics at scale. For a single-entity UK organisation, that capability premium is rarely justified.

Where Power Platform wins

• Microsoft 365 organisations, incremental cost on existing infrastructure, not a new vendor
• Non-standard HR processes, complex shift patterns, sector-specific absence rules, regulated industries
• Tight Microsoft 365 integration, Teams, SharePoint, Outlook, Viva all work natively with no middleware
• Long-term ownership. You own the system, not rent access to it. No annual price increases from a vendor.
• Customisation without limits, any feature, any UI, any integration. If it can be built in software, it can be built in Power Platform.

Where dedicated HR platforms win

• Global payroll, Power Platform has no native payroll engine. You need a payroll integration.
• Out-of-the-box benchmarking, Workday and Sage People include salary surveys, compliance templates, and industry benchmarks
• Small businesses with no IT resource, BambooHR is self-configured and operational in days
• Speed to value, a SaaS platform is live in weeks; a Power Platform build takes 12–18 weeks

The Flexibility and Customisation Advantage

This is where Power Platform fundamentally outcompetes every HR SaaS platform on the market, and it is not a close contest.

Every SaaS platform has a ceiling

Sage People, HiBob, BambooHR, and even Workday are built around a fixed data model and a fixed set of features. You configure what they give you. When your business process does not fit the template (and it often does not) you have three options: change your process, pay for custom development at the vendor's rates, or live with the workaround.

UK organisations routinely encounter this ceiling with:

• Complex absence policies (rolling average holiday, enhanced compassionate leave, sickness trigger points that differ from Bradford Factor defaults)
• Non-standard contract types (zero-hours, annualised hours, term-time only)
• Sector-specific compliance requirements (DBS tracking for healthcare/education, SIA licence expiry for security, CSCS card management for construction)
• Unique performance frameworks that do not map to the vendor's review structure

Power Platform has no ceiling

Because the HR system is built on Dataverse (a fully programmable database) and the applications are built in React (Code App), Model-Driven framework, and Power Automate, every element is under your control:

• Add a new HR module in weeks, not months, a new TUPE tracking module, a restructure case management tool, a disciplinary and grievance workflow. These are new tables and forms in Dataverse, built by your implementation partner in days.
• Change the data model without rebuilding, add a new field to the employee record and it appears in every app, every flow, and every Power BI report automatically
• Build integrations that SaaS platforms cannot, direct API connections to niche payroll providers, occupational health systems, background screening services, or your ERP
• Own your data completely, employee data lives in your Dataverse environment, in your Microsoft tenant, under your GDPR controller obligations. No third-party SaaS vendor has access.

The mobile Code App is uniquely yours

Off-the-shelf HR platforms offer a mobile app. It is their mobile app, the same UI, the same features, the same limitations for every customer. Your employees use the same app as every other company on that platform.

A Power Platform Code App built in React is a bespoke mobile application designed around your organisation's workflows, your branding, and your employees' actual needs. The Manager Hub shows the exact information your line managers need. The Leave Request screen enforces your specific leave policy. The Company Directory integrates with your org structure.

It runs inside the standard Power Apps player on iOS and Android, so there is no App Store submission, no separate MDM deployment, no additional infrastructure. It is a fully custom mobile application delivered within your existing Microsoft platform investment.

Component 1: Model-Driven App, HR Manager Desktop

The Model-Driven App is built on Microsoft Dataverse and gives HR managers a structured, form-driven interface for managing the full employee lifecycle.

Core modules to build

Employee Records

• Personal details, emergency contacts, right-to-work documentation
• Employment history, contract type, probation tracking
• Salary history with effective dates
• Custom fields for role-specific attributes

Onboarding Management

• Pre-start task checklist (IT setup, payroll, access requests)
• New starter documents collection with status tracking
• Automated welcome communications via Power Automate
• 30/60/90-day review scheduling

Absence Management

• Annual leave requests with calendar integration
• Bradford Factor calculation for absence monitoring
• Medical certificate tracking
• Absence pattern reporting linked to Power BI

Performance & Development

• Objective setting with mid-year and year-end reviews
• 360-degree feedback collection
• Training record and CPD tracking
• Succession planning flags

Offboarding

• Exit interview scheduling
• Asset return checklist
• System access revocation tasks routed to IT via Power Automate
• Leaver documentation automation

Dataverse table design

Core tables to create:

• Employees (extends the standard Dataverse Contact table)
• Contracts (one-to-many with Employees)
• Absence Requests (with approval workflow)
• Performance Reviews (linked to review periods)
• Training Records
• Onboarding Checklists (template-based, cloned per new starter)

Use Business Rules in Dataverse to enforce data validation (e.g., end date cannot precede start date, salary changes require justification notes). This keeps validation logic in the data layer, not scattered across apps.

Component 2: Code App, Employee Self-Service Mobile App

Why Code App, not Canvas App?

Power Apps Code Apps let you build full React and TypeScript applications that run natively within the Power Platform ecosystem, same Power Apps player, same Dataverse connection, same Power Platform licensing. The difference is the development approach and the output quality.

Canvas apps are excellent for internal tools and quick HR team workflows. For an employee-facing mobile app (one that 500 people open every day to request leave, check balances, and view their payslip) the experience needs to feel like a proper mobile application. A Code App delivers that without leaving the Power Platform or adding a separate deployment pipeline.

What you get with a Code App that canvas cannot match:

• Full responsive layout control with CSS grid and flexbox, screens that genuinely adapt to any phone size
• Smooth animations and transitions using standard React libraries
• Custom UI components (e.g., a swipe-to-approve gesture for managers, a pull-to-refresh absence calendar)
• No formula-language constraints, standard TypeScript for all logic
• Accessibility compliance (WCAG 2.1 AA) achievable through standard ARIA practices

What stays the same as any Power Platform app:

• Deployed and distributed through the Power Apps mobile player (iOS and Android)
• Connects directly to Dataverse, SharePoint, and all Power Platform connectors
• Covered by the same Power Apps Premium licence, no additional per-user cost
• Governed by the same DLP policies and environment strategy as the rest of your Power Platform estate
• Managed and updated from the Power Platform admin centre

Screens to include

Home screen

• Leave balance summary (days remaining, pending requests) with animated ring charts
• Upcoming review dates and company announcements
• Quick-action cards: Request Leave, Report Absence, Update My Details
• Manager view: team absences this week, pending approvals badge

Leave Request

• Swipe-based calendar date picker showing team availability to avoid conflicts
• Leave type selection (annual, TOIL, compassionate, study)
• Manager approval notification triggered on submission
• Push notification when approved or declined

My Profile

• View and update personal details, emergency contacts, bank details
• Document access: payslips, contract, HR policies
• Training record and certifications view

Absence Reporting

• Same-day absence logging with reason codes
• Phased return tracking
• Manager notified automatically via Power Automate

Company Directory

• Searchable employee directory with profile photos
• Org chart view
• One-tap Teams call or message integration

Manager Hub (role-based screen, only visible to line managers)

• Team absence calendar
• Pending approval queue with approve/decline swipe gestures
• Direct reports' probation and review dates

Mobile-first design principles for Code Apps

Because you are writing React, you have full control over responsive behaviour. Key practices:

• Design at 375px width first. This is the effective width of most modern phones in portrait
• Use viewport units for full-screen layouts, not fixed pixel heights
• Implement a bottom navigation bar rather than a hamburger menu, thumbs reach the bottom of a phone, not the top
• Test gesture interactions (swipe, pull-to-refresh) on actual devices, not emulators
• Follow Apple Human Interface Guidelines and Material Design patterns for platform-native feel

Offline capability

For employees in low-connectivity environments (warehouses, field sites, manufacturing floors), implement offline data sync using the Power Apps offline API. Critical actions (logging an absence, submitting a timesheet) queue locally and sync to Dataverse when connectivity is restored. The Code App TypeScript layer handles the sync queue logic cleanly, which is significantly more straightforward than canvas offline collections.

Component 3: Power Automate, HR Workflow Automation

Power Automate orchestrates the processes that connect the Model-Driven App, the Code App, payroll systems, and Microsoft 365.

Priority flows to build

New Starter Onboarding Flow Triggered when a new employee record is created with a future start date. Automatically:

1. Sends welcome email with onboarding portal link
2. Creates IT access request in ServiceNow or equivalent
3. Schedules 30/60/90-day review meetings in Outlook
4. Assigns onboarding checklist and notifies line manager

Absence Approval Flow Triggered by a leave request submission. Routes to line manager for approval. On approval: updates leave balance, notifies payroll integration, confirms to employee. On rejection: notifies employee with reason.

Probation Review Reminder Scheduled flow running daily. Identifies employees with probation end dates within 14 days. Notifies line manager and HR partner. Creates review task in the Model-Driven App.

Contract Expiry Alert Notifies HR 60 and 30 days before fixed-term contract expiry. Triggers renewal or termination process in the HR app.

Offboarding Orchestration Triggered when an employee's termination date is set. Creates and assigns tasks across IT, payroll, facilities, and the line manager. Tracks completion. Escalates overdue tasks to HR.

Component 4: Power BI, People Analytics Dashboard

Embed Power BI reports directly in the Model-Driven App so HR managers see live analytics without leaving their workspace.

Key reports to build

• Headcount & Attrition, headcount by department/location, monthly leavers vs joiners, voluntary vs involuntary attrition rate
• Absence Dashboard, absence rate by department, Bradford Factor distribution, rolling 12-month absence trend
• Recruitment Pipeline, open roles by department, time-to-hire, offer acceptance rate
• Training Compliance, mandatory training completion by team, overdue certifications, CPD hours by individual
• Salary & Pay Equity, average salary by band and gender (anonymised for compliance), salary range penetration

Use Row-Level Security in Power BI so line managers only see their own team data when the report is embedded in Teams or SharePoint.

Licensing Requirements

Why only 1–2 Power Automate Premium licences?

Power Automate flows that use premium connectors (Dataverse, custom payroll connectors, ServiceNow) must be owned by a licensed user, but that is the account the flow runs under, not every employee who triggers it. In practice this means:

• The HR system administrator account that owns the onboarding, offboarding, and absence flows needs Power Automate Premium (£12.50/month)
• A second service account is recommended as a backup owner (£12.50/month)
• Employees who submit leave requests or trigger flows via the Code App do not need a separate Power Automate licence, their interaction is covered by their Power Apps Premium licence
• HR managers who build and edit flows in their own environment need Power Automate Premium only if they own flows using premium connectors independently of the system admin account

For an organisation with 500 employees and 5 HR staff:

• 505 x Power Apps Premium: £7,777/month (£93,324/year)
• 2 x Power Automate Premium (flow owners): £25/month (£300/year)
• 10 x Power BI Pro (HR managers + senior leaders): £84/month (£1,008/year)
• Total running cost: approximately £94,632/year

Phased Implementation Plan

Phase 1, Foundation (Weeks 1–6)

• Dataverse schema design and employee data migration
• Model-Driven App: Employee Records and Absence Management modules
• Basic absence approval flow
• HR Manager desktop app go-live

Phase 2, Self-Service (Weeks 7–12)

• Code App build: Home, Leave Request, My Profile, Absence Reporting screens
• Manager Hub screen with approval workflows
• Onboarding and offboarding automation flows
• Employee self-service go-live

Phase 3, Intelligence (Weeks 13–18)

• Power BI people analytics dashboards
• Performance and development module
• Advanced automation (probation tracking, contract alerts)
• Full suite go-live

Implementation Checklist

• Dataverse environment provisioned (production + sandbox)
• DLP policies configured before development begins
• Existing HR data cleansed and mapped to Dataverse schema
• Integration with payroll system identified (connector or API)
• GDPR Data Processing Agreement with Microsoft confirmed
• Right-to-work and sensitive data fields classified and access-controlled
• Code App tested on iOS and Android on actual devices
• Offline sync tested in low-connectivity conditions
• Line manager training completed before go-live
• HR team trained on Model-Driven App and Power BI
• Hypercare support plan in place for first 4 weeks post-launch