You're probably dealing with the same mess most mid-market HR teams are facing right now, a Monday calendar full of live law changes, managers asking what still applies, and a payroll team that can't afford to guess. The trap isn't ignorance of uk employment law updates, it's treating them as a policy tidy-up when the breakage happens inside absence logic, probation templates, leave requests, and dismissal evidence.
The dates matter. 6 April 2026 is when Statutory Sick Pay changes again, and 1 January 2027 is when unfair dismissal protection shifts to six months' continuous service in Great Britain, with the compensatory award cap removed for those claims (ACAS guidance on the Employment Rights Act 2025). If you're still running old forms and manual checks, you're already behind.
Where UK HR Stands Right Now
If you opened a Teams stand-up this morning and found three separate questions on your desk, that is the reality for a lot of HR teams right now. Payroll wants a clear rule for day-one SSP, managers want to know how paternity and unpaid parental leave are handled from the start date, and Legal wants evidence retention tightened because tribunal timing has shifted.
From 6 April 2026, Statutory Sick Pay becomes a day-one entitlement with no lower earnings limit and no waiting period, paid at the lower of the statutory rate of £123.25 per week or 80% of normal weekly earnings (JDSupra legal update). That needs to be built into payroll logic, absence workflows, and manager guidance before the first case lands, because a manual workaround will fail the moment someone reports sick leave.
The other risk sits in the background and causes real trouble later. The tribunal limitation period has moved from three months to six months, so weak grievance handling and poor retention now stay exposed for much longer (Pinsent Masons timeline overview). Keep the evidence trail clean, and use the employment verification guide as a reminder that records need to support decisions, not just satisfy filing habits.
Practical rule: if a policy change affects payroll, leave eligibility, or dismissal risk, it needs a system change, not just a PDF update.
For the wider control picture, the briefing on human resources compliance is the right companion piece. It shows why 2026 is an execution year, and why HR teams that wait for a policy refresh will find the system has already drifted out of compliance.
The Policy Story Behind the 2026 Changes
A mid-market HR team that treated 2024 as a tidy compliance refresh is already behind. The direction was clear then, because day-one flexible working rights returned from 6 April 2024, the request window no longer needed 26 weeks' service, and employer response time dropped from three months to two months (CM Murray summary of 2024 changes).
The same shift showed up in pay and leave. The National Living Wage widened to cover workers aged 21 and over from 1 April 2024, down from the older 23-and-over threshold, and the package also added one week of unpaid Carer's Leave from 6 April 2024. The message is blunt. UK employment law has been pushing toward earlier access, wider eligibility, and less room for informal handling.
What changed again in late 2024
By 1 October 2024, the Employment (Allocation of Tips) Act 2023 required employers to pass tips on to workers and keep a tipping policy where tips are left more than occasionally (Gateley summary of 2024 developments). Then on 26 October 2024, the Worker Protection (Amendment of Equality Act 2010) Act imposed a positive duty on all employers to take reasonable steps to prevent sexual harassment, with tribunals able to uplift compensation by up to 25% when the code is unreasonably ignored.
That is the pattern. Workers gained more direct rights, employers inherited tighter duties, and non-compliance became more expensive.
If you are reviewing automation in recruitment, the debate around regulations for AI in hiring sits in the same compliance bucket. HR now has to show fairness, consistency, and traceability, not just good intent.
The Employment Rights Act 2025 sits over that shift. Read against the last two years, it does not look like a grab bag of reforms. It looks like a staged move toward stronger worker protection, stronger transparency, and stronger enforcement.
The Phased Timeline You Need on One Page
Stop treating 2026 and 2027 as one blended “update cycle”. They're not. 2026 is about operational changes already in motion, while 2027 is where the deeper dismissal and status reforms hit the business model (Pinsent Masons timeline overview).
Live or imminent in 2026
Payroll owns the first hard stop, because day-one SSP is live from 6 April 2026 (JDSupra legal update). The artefact you need is a reconfigured absence engine that can calculate entitlement on day zero and stop waiting for the old trigger.
HR Operations owns paternity and unpaid parental leave rules because those rights are now part of the day-one experience. The artefact is a leave catalogue that presents the correct options from the first day of employment, not after probation.
Legal and HR case management own the tribunal window shift, because the move from three months to six months gives weak evidence more time to come back and bite you (Pinsent Masons timeline overview). The artefact is a retention schedule and grievance triage process that gets used.
Structural reforms coming in 2027
1 January 2027 is the date that should be sitting on your board pack now. Unfair dismissal protection moves to six months' continuous service and the compensatory award cap is removed for those claims (ACAS guidance on the Employment Rights Act 2025). The owner here is HR, with Legal and line managers in the loop, because probation design and exit decision-making need to be tighter before that date, not after it.
Fire-and-rehire restrictions and guaranteed-hours style reforms also sit in the 2027 phase, which means contract templates, consultation playbooks, and rostering logic all need a review. If you're on a mid-market HR stack, this is the point where the gap between “we know the law” and “the system enforces it” turns into real operational risk.
If a date changes payroll, probation, or dismissal, don't wait for the next policy cycle. Put it in the project plan now.
Pay and Leave Mechanics That Change Payroll
Payroll teams need the rules hard-coded before the first affected absence or leave request arrives. Statutory Sick Pay changes are the first test, because the payroll engine either handles them cleanly or creates underpayments on day one.
What the payroll engine has to do
From 6 April 2026, SSP is payable from day one of absence, with no lower earnings limit and no waiting period, at the lower of £123.25 per week or 80% of normal weekly earnings (JDSupra legal update). Absence coding has to trigger immediately, eligibility logic has to stop filtering out lower-paid staff, and payroll has to stop assuming there is a qualifying wait.
The same day-one logic applies to paternity leave and unpaid parental leave. Those entitlements need to appear in the employee journey from the start, because if the self-service portal hides them until after a service threshold, managers will make ad hoc promises and HR will end up reconciling the records later.
The new Fair Work Agency raises the stakes again. Once enforcement is more centralised, inconsistent approvals, bad coding, and underpayments are harder to bury in spreadsheets or explain away after the fact.
Where teams usually break it
The failure points are familiar.
- Absence rules still use the old waiting period, so the first eligible claim is underpaid.
- Eligibility checks still rely on the old lower earnings threshold, so support staff get excluded by mistake.
- Manager approvals do not show the new leave types at the right time, so people take informal time off instead of recorded leave.
For the system side of this, payroll integration matters because entitlement logic fails when absence, HR records, and payroll sit in separate tools and never reconcile properly.
NewsletterAsAService for lawyers (NewsletterAsAService for lawyers) is a good example of why structured updates beat ad hoc messages. HR needs the same discipline internally, especially where leave, pay, and approval logic overlap.
The right response is direct. Rebuild the rules in the system, test them against live employee records, and switch off the old logic before the change date lands.
Dismissal Risk, Probation and Redundancy Discipline
A weak dismissal file will hurt you faster once the new unfair dismissal rules bite. From 1 January 2027, Great Britain moves to six months' continuous service for unfair dismissal protection, and the compensatory award cap disappears for unfair dismissal claims (ACAS guidance on the Employment Rights Act 2025). That changes how you handle probation exits, capability concerns, and redundancy selections for anyone with short service.
A seven-month employee is no longer a casual risk. If the manager wants them out for poor performance, the record cannot stop at a few vague Teams messages and one missed deadline. You need a clear probation plan, formal feedback, repeated review points, and a paper trail that shows the decision was reasonable when it lands in tribunal.
A proper probation policy now sits inside dismissal discipline. Leave it informal, and HR will spend the next year reconstructing expectations from scraps of email and calendar invites.
For legal teams that need to keep staff informed without flooding them with one-off messages, NewsletterAsAService for lawyers is a good example of why structured updates beat ad hoc comms. HR should apply the same discipline internally.
What to tighten before January 2027
- Probation templates need review dates, success criteria, and named sign-off owners.
- Grievance triage needs a named owner and a deadline for escalation.
- Evidence retention should keep the record available long enough to survive the longer tribunal window.
- Redundancy planning should assume dismissal exposure is no longer buffered by the old two-year threshold.
The tribunal limitation period also moves from three months to six months, so weak paper trails stay alive for longer and get more expensive to defend (Pinsent Masons timeline overview). Inbox-based case handling will not cut it. Use a structured case file with versioned documents and audit trails, because memory will not protect you.
For a closer look at how probation should work in practice, the internal guide on probationary period in employment is the right companion read.
Configuring Microsoft Dynamics 365 HR by Hubdrive for Compliance
The cleanest way to survive these changes is to make the HR platform enforce them. Microsoft Dynamics 365 HR by Hubdrive, built on Dataverse, is where the policy becomes executable rather than interpretive.
Build the law into the data model
Start with absence and leave entities. SSP day-one entitlement should be triggered by a Power Automate flow that evaluates absence from day zero, not after a waiting period. The rule set must also stop applying the old lower earnings threshold, because that threshold no longer belongs in eligibility logic.
Add leave types for paternity leave and unpaid parental leave so they appear in employee self-service from the first day of employment. Don't hide them behind a service gate if the law doesn't.
Fix scheduling, reporting and audit controls
If you employ zero-hours staff, your configuration needs to support guaranteed-hours calculations and predictable scheduling decisions. That means the system should store the relevant working pattern, surface the available hours, and keep a defensible audit trail when a manager changes a rota.
Flexible working should be configured as a day-one default in employee self-service, with the approval workflow tied to a documented reason if it's refused. That's not just user experience. It's evidence.
Use the platform for compliance, not just admin
The integrated UK Right to Work module should sit alongside retention rules so starter documents don't drift outside GDPR-aligned storage periods. Power BI dashboards can also support ethnicity and disability pay-gap reporting once the data fields are clean and consistent.
Configuring the process beats training people to remember the process. Managers forget. Systems don't, if you set them up properly.
That's the point of a compliant HR platform. It doesn't just store records. It reduces the number of decisions that can go wrong in the first place.
Why Configuration Beats Policy Documentation
A policy folder won't stop an underpayment. A slide deck won't stop a bad dismissal. A configured system will at least force the right logic to run before a manager clicks approve.
Cost of Inaction Versus Cost of Configuration
| Risk Area | Maximum Exposure | Dynamics 365 HR by Hubdrive Configuration |
|---|---|---|
| Redundancy and dismissal | £21,000 maximum basic award or statutory redundancy entitlement, and £115,115 compensatory award exposure under the 2024 caps referenced earlier | Automated probation workflows, structured exit case files, versioned approvals |
| Absence and sick pay | Underpayment risk and inconsistent entitlements when the old waiting period remains in place | Day-one SSP rules, eligibility logic, absence-trigger automation |
| Leave handling | Manual errors on paternity and unpaid parental leave requests | Self-service leave types, approval routing, manager prompts |
The board-level argument is straightforward. Configuration reduces manual judgement, and manual judgement is where most HR errors happen. Training helps, but training decays. System logic stays in place.
This is especially true for organisations in the 50 to 4,000 employee range, where generic HRIS tools are too shallow and enterprise suites are too heavy. You need something that can absorb the change, not just record it afterwards.
Your 90-Day Implementation Checklist
Start with the data. Week one should be a full audit of contracts, employee records, absence categories, and retention rules. The owner here is HR Operations, with Payroll and IT checking that the source data matches the live employee population.
In weeks two to four, rewrite the policies and configure the leave and absence rules. Draft the new SSP policy, update paternity and unpaid parental leave workflows, and train the payroll team on the new calculation path. If the manager-facing experience is inconsistent, fix that before go-live.
Weeks five to eight are where flexible working, guaranteed-hours handling, and pay-gap reporting need testing. The owner here is HR Systems, with Legal checking the wording and Finance checking the reporting outputs. Run the workflow in a test tenant before it touches live cases.
By weeks nine to twelve, harden dismissal documentation, tribunal-readiness, and Right to Work flows. Reissue the contract template, test the Power Automate flow, and confirm every manager knows where the evidence trail sits. This is the point where your project manager should stop asking for more policy opinions and start asking for sign-off.
If your HR team is still trying to manage uk employment law updates through email chains and static documents, you're carrying risk you don't need. DynamicsHub helps UK employers turn those dates into working system rules inside Microsoft Dynamics 365 HR by Hubdrive, so payroll, leave, probation and compliance all move together. Visit DynamicsHub or phone 01522 508096 today to scope a UK-based implementation that holds up when the next deadline lands.
