The HR director reports a 14% attrition rate to the board. Finance has 19% in its spreadsheet. Both teams insist they used the same employee data.
This disagreement is common in UK organisations. One team may count resignations only, while another includes redundancies and retirements. One may divide leavers by opening headcount, while another uses average headcount. A third may use a payroll extract covering the financial year and compare it with an HR report covering the calendar year.
A reliable attrition rate calculation starts before the formula. You need agreed definitions, a fixed reporting period, clean employee records and a denominator that reflects the workforce during that period. The standard UK approach provides the foundation, but the quality of the result depends on how carefully your organisation applies it.
Why Your Attrition Numbers Might Be Wrong
The boardroom disagreement usually isn't caused by arithmetic. It comes from two reports answering different questions while using the same label.
The HR report might count 28 resignations from a population of permanent employees. Finance might count 38 people whose employment records ended, including fixed-term contract expiries, redundancies, dismissals and retirements. If HR divides by average headcount and finance divides by opening headcount, the difference widens again.
Start with the leaver definition
The UK crude wastage method treats labour turnover as leavers divided by average employees over a defined period. The historical CIPD turnover methodology describes leavers as including voluntary departures, involuntary severance, redundancies and retirements, while excluding internal transfers.
That definition is useful for whole-organisation turnover, but it isn't automatically the right definition for every management question. A voluntary attrition report should isolate resignations and employee-led departures. A restructuring report should show redundancies separately. An internal mobility report should track transfers as movement within the organisation, not as external loss.
Time periods create silent differences
A report covering April to March won't reconcile with one covering January to December unless the dates are aligned. Payroll may use the termination date, HR may use the employee's final working day, and a manager's spreadsheet may use the date the resignation was submitted.
Ask these questions before accepting a rate:
- Who counts as a leaver? Include resignations, redundancies, dismissals and retirements, or only selected categories?
- What is the period? Are all records inside the same start and end dates?
- What is the population? Permanent employees only, or also fixed-term staff and other worker groups?
- How is headcount calculated? Opening headcount, closing headcount or an average?
- Are internal transfers excluded? An employee moving between departments hasn't left the organisation.
- Are duplicate or corrected records removed? A rehire or amended termination can otherwise become two departures.
A wrong rate can direct retention funding towards a stable team while missing a genuine hotspot. It can also make a restructuring look like a voluntary-retention problem, producing the wrong response from managers and finance.
Practical rule: Never approve an attrition figure until its numerator, denominator, population and dates appear beside it.
The UK Crude Wastage Formula Explained
The standard UK formula is straightforward:
Labour turnover = Number of leavers in a set period × 100 ÷ Average number employed in the same period
The formula is set out in CIPD benchmarking guidance and remains the clearest starting point for a consistent UK attrition rate calculation.
Step one, fix the period
Choose a month, quarter or year, then apply that choice consistently. The numerator must contain only leavers whose relevant leaving date falls within the selected period.
For a whole-organisation rate, include voluntary exits, redundancies, dismissals and retirements. Internal transfers and promotions shouldn't be counted as leavers because the employee remains employed by the organisation. If you want voluntary attrition, use a narrower numerator and label it clearly.
Step two, calculate average headcount
The usual practical calculation is:
Average headcount = (Opening headcount + Closing headcount) ÷ 2
Average headcount is preferable to opening headcount because it reflects workforce movement during the period. The UK staff turnover calculation guidance uses this mechanics-based approach.
Consider a UK organisation with 200 employees at the start of a twelve-month period and 28 leavers. If the organisation ends with 190 employees, average headcount is:
(200 + 190) ÷ 2 = 195
The rate is therefore:
28 ÷ 195 × 100 = 14.4%
Using opening headcount instead produces 14.0%. The difference may look modest in this example, but it becomes more material when a business is growing quickly, shrinking sharply or experiencing major hiring activity.
The same issue appears in the practical example cited in UK turnover benchmark guidance. A business moving from 100 to 95 staff with 12 leavers reports 12.3% using average headcount, rather than 12.0% using opening headcount.
Step three, match cadence to purpose
Monthly reporting is useful for identifying emerging issues, but a small workforce can produce volatile results because a few departures have a noticeable effect. Quarterly reporting gives managers more observations while retaining operational relevance. Annual reporting is more stable and useful for board comparisons, workforce planning and external benchmarking.
Don't add monthly percentages together to create an annual rate. Calculate the annual numerator and annual average headcount across the complete period instead.
The ONS redundancy series provides a separate UK measure, reported as redundancies per 1,000 employees. It should sit alongside turnover when you need to understand involuntary exits, rather than being folded into a voluntary attrition measure.
Attrition Versus Turnover and When to Use Each
The words attrition and turnover often describe different management questions. Attrition commonly refers to employees leaving and roles remaining open or disappearing, so it reflects a reduction in workforce capacity. Turnover generally counts all leavers, whether the organisation replaces them or not.
The distinction matters during restructuring. A business can experience high turnover because redundancies and replacement hiring occur in the same period, while its permanent workforce plan remains stable. If the board sees only one number, it may mistake planned workforce movement for a retention failure.
Attrition vs Turnover Comparison
| Criteria | Attrition | Turnover |
|---|---|---|
| Primary meaning | Employees leave without immediate replacement or the role remains open | All employees leaving during the period |
| Numerator | Departures that reduce or remove workforce capacity | Voluntary exits, redundancies, dismissals and retirements, according to the agreed definition |
| Internal transfers | Usually excluded from organisation-wide attrition, but may be tracked for team-level capacity | Excluded when measuring employees leaving the organisation |
| Best use | Workforce planning, vacancy risk and capacity analysis | Overall labour movement and year-on-year comparison |
| Typical response | Recruitment planning, succession and workload management | Retention, restructuring, workforce design and recruitment analysis |
| Main risk | Understates employee movement when roles are backfilled | Overstates voluntary retention risk during planned restructuring |
A UK logistics firm might report a rise in turnover after closing one depot and opening another. If the HR team uses that figure to justify a broad retention programme, it may spend money addressing a problem that isn't primarily caused by employee dissatisfaction. The more useful report would separate voluntary resignations, redundancies and internal moves, then show whether critical roles remain vacant.
For board reporting, put the measures together. Show total turnover, voluntary exits, involuntary exits, internal mobility and open roles. That gives directors enough context to decide whether the priority is manager support, recruitment capacity, succession planning or organisational redesign.
For a concise treatment of audit-ready metric definitions, the HelpWithMetrics audit-ready metrics guide is a useful supporting resource. UK teams can also compare terminology with DynamicsHub's rate of turnover guidance, while keeping their own agreed definitions visible in every dashboard.
Building the Calculation in Excel and Power BI
Spreadsheets can produce a sound result when the input structure is controlled. They become unreliable when each department creates its own leaver categories, date filters and headcount assumptions.
A dependable Excel structure
Set up a table named EmployeeData with fields such as:
- Employee ID: A stable identifier that remains unchanged through corrections.
- Start Date: The employee's employment start date.
- Leaving Date: Blank for active employees and populated for leavers.
- Employment Status: Active or exited, with agreed status rules.
- Leaving Reason: Resignation, redundancy, dismissal, retirement or another approved category.
- Department: The organisational unit used for reporting.
With named cells for PeriodStart and PeriodEnd, a whole-organisation leaver count can use:
=COUNTIFS(EmployeeData[Leaving Date],">="&PeriodStart,EmployeeData[Leaving Date],"<="&PeriodEnd)
If opening and closing headcounts sit in named cells called OpeningHC and ClosingHC, the rate is:
=Leavers/AVERAGE(OpeningHC,ClosingHC)*100
For a department view, add the department criterion to the COUNTIFS expression and calculate the matching opening and closing populations. Don't use one company-wide denominator for a department numerator.
A practical Power BI measure
A proper model should include a Date table, an employee table and a leaver date relationship. A basic measure can be written as:
Attrition Rate = DIVIDE([Leavers], [Average Headcount], 0)
The supporting measures might be:
Leavers = CALCULATE(DISTINCTCOUNT(Employee[Employee ID]), Employee[Leaving Date] <> BLANK())
Average Headcount = DIVIDE([Opening Headcount] + [Closing Headcount], 2)
The exact filter logic depends on how your Dataverse tables store employment periods. If employees can have multiple employment records, DISTINCTCOUNT alone won't resolve overlapping records or rehires. The model must define whether a person leaving and rejoining is one event, two events or a separate employment spell.
Connect the model to reporting
Power BI should filter by period, department, location, manager, tenure and leaving reason without requiring manual exports. The HR KPI dashboard guidance shows how KPI reporting can give managers a more consistent view of workforce measures.
The denominator trap remains the main issue. A beautiful visual using opening headcount is still a weak attrition report if the organisation is changing size quickly. Store the calculation rules in the model, not in a note on someone's spreadsheet.
Data-Cleaning Rules and Edge Cases That Distort Your Rate
A perfect formula can't repair poor records. In mid-market UK organisations, the biggest errors usually arise when HR, payroll, recruitment and line managers maintain different versions of an employee's employment history.
Five rules that protect the numerator
Deduplicate employment events. A leaver may have a termination record, a payroll correction and a rehire record. Count the exit event once, using the stable employee ID, relevant leaving date and approved event type.
Separate internal movement. An employee transferred from one depot to another hasn't left the organisation. Excluding internal transfers protects the company-wide rate, while a separate internal mobility measure can show the impact on the original team.
Classify contract expiry deliberately. A fixed-term contract ending may be expected workforce movement, but it may also represent a genuine capacity loss. Decide whether it belongs in whole-organisation turnover, voluntary attrition or a separate contract-end category.
Handle garden leave consistently. Garden leave can create a difference between the contractual end date and the last active working day. Choose one date rule and apply it across every period.
Use period headcount. A point-in-time snapshot can misrepresent a workforce that hired heavily, reduced staffing or operated with seasonal workers. Use the average for the same period as the leaver count.
Restructuring needs its own view
Redundancies can make total turnover rise even when voluntary exits remain stable. Brightmine's UK attrition guidance highlights how results change depending on whether redundancies are included, and reports UK attrition at 19% in 2025, up 11% year on year, compared with a European average of 17.4%.
Those figures aren't a substitute for your internal definition. They show why a UK dashboard should contain separate fields for resignation, redundancy, dismissal, retirement, contract expiry and other exits. During a restructure, present total turnover and voluntary turnover side by side instead of hiding the distinction inside a single percentage.
A validation checklist for your data team
- Identity: Every employment record has one stable employee identifier.
- Dates: Start and leaving dates are valid, ordered and inside the reporting logic.
- Status: Active and exited statuses agree with payroll and employment records.
- Reasons: Termination codes map to a controlled list.
- Population: Contractors, temporary workers and employees on leave follow an explicit rule.
- Movement: Internal transfers don't appear as external leavers.
- Rehires: Rejoining employees follow a documented event policy.
- Reconciliation: Closing headcount reconciles with opening headcount, joiners and exits.
- Restructuring: Redundancies are visible separately from voluntary departures.
- Text quality: Clean imported fields before matching or categorising records. The OnRoute guide to cleaning Excel data is useful for removing hidden formatting issues that can interfere with consistent values.
Automating Attrition Insights with Dynamics 365 and Hubdrive
Manual spreadsheets fail when several teams edit the same population, especially when corrections arrive after the monthly report has been circulated. A Dataverse-based HR model gives the organisation one employee record, one employment history and one controlled set of exit reasons.
Hubdrive's HR Management for Microsoft Dynamics 365 supports a hire-to-retire structure in which recruitment, onboarding, employment changes, absence, performance and exit information can sit within the same Microsoft business environment. When a leaver is recorded at the point of exit, the leaving date and reason can feed Power BI without repeated copy-and-paste work.
What changes operationally
A structured system can apply the same rules across departments:
- Controlled exit data: Resignation, redundancy, dismissal, retirement and contract expiry can remain distinct categories.
- Connected reporting: Dataverse records can supply Power BI dashboards without manual exports.
- Manager visibility: Teams and Microsoft 365 workflows can bring alerts and actions into the tools managers already use.
- Compliance support: UK Right to Work integration, GDPR-aligned data retention and Microsoft Entra ID security can support controlled HR operations.
- Tenant control: Data can reside in the organisation's own Microsoft 365 tenant, subject to the implemented architecture and governance.
AI-assisted features may help identify patterns for review, but they shouldn't replace HR judgement. A risk flag should prompt a conversation or data check, not automatically label an employee as likely to leave.
The practical benefit is consistency. HR can define the numerator once, calculate average headcount from the same employment population and let managers investigate changes by department, tenure or exit reason. The Dynamics 365 HR overview provides further context on the wider platform approach.
DynamicsHub delivers implementations of Hubdrive's HR Management for Microsoft Dynamics 365 for UK organisations, alongside configuration, integration and ongoing optimisation. The product should be assessed against your data model, reporting controls and governance requirements, rather than treated as a shortcut around definition work.
Benchmarking Your Rate and Setting a Reporting Cadence
A rate has meaning only when the comparison is fair. CIPD's UK benchmarking data reports average workforce turnover of 34%, split between 27.4% of workers moving to a new employer and 6.6% who weren't working one year later, as shown in its UK turnover benchmarking analysis. That isn't directly interchangeable with a company attrition measure because the populations and definitions differ.
Sector context matters too. CIPD reports turnover variation from 25% in public administration and defence to 52% in hospitality. Use those figures as context, not as automatic targets. Your own baseline, workforce model, location, job mix and exit definitions still determine whether a change is concerning.
A useful reporting rhythm is:
- Monthly: Monitor total, voluntary and involuntary exits, then investigate unusual movement in critical teams.
- Quarterly: Present trends, department comparisons, tenure patterns, vacancies and agreed actions to senior leadership.
- Annually: Reconfirm definitions, review the full-year calculation and compare with suitable UK sector benchmarks.
Every board report should show the rate, numerator, denominator, period, population and split by leaving reason. Add one sentence explaining the management action attached to the result. That turns a dashboard from a historical record into a workforce decision tool.
Organisations ready to replace manual reconciliation can use DynamicsHub's UK implementation support and Hubdrive's HR Management for Microsoft Dynamics 365 to connect employee records, Dataverse and Power BI. Experience HR transformation built around your business. Hubdrive's HR Management for Microsoft Dynamics 365 is a hire-to-retire solution designed to provide more powerful, flexible and future-ready HR capability than Microsoft Dynamics 365 HR.
DynamicsHub can help you define a reliable attrition model, clean the underlying employee data and build Dynamics 365, Dataverse and Power BI reporting around your UK workforce. Call 01522 508096 today to discuss your requirements, or visit DynamicsHub and send a message through the contact page.
