Statutory Notice Period a UK Employer's Guide for 2026
- Jul 4
- 11 min read
An employee hands in their resignation on a busy Monday morning. Later that week, you're considering letting someone else go because the role no longer fits the business. The contracts are in a folder somewhere, payroll needs an answer, and you need to know one thing quickly. How much notice are you required to give or receive?
Many UK SMEs frequently get caught out. Owners often assume the contract answers everything. It doesn't. The law sets a floor, and if your process is loose, a simple exit can turn into a dispute about final pay, end dates, or whether the termination was handled properly at all.
I see this most often when a business is moving fast and treating notice as an admin task instead of a compliance task. That's risky. A notice period affects payroll, handover, access to systems, holiday calculations, and sometimes whether a dismissal decision stands up to scrutiny.
It also sits alongside wider people risk. If your HR and safety processes already overlap in day-to-day operations, it helps to treat exits the same way, with a joined-up approach to compliance, communication, and workforce planning. This is the same principle behind joining up health and safety and HR in the workplace.
Table of Contents
The Foundation What Is the Statutory Notice Period - The legal minimum every employer needs to know - A quick reference table - Why this baseline matters in practice
Calculating Notice Periods in Practice - A simple method that works - Worked examples for common situations
Handling Special Cases Redundancy Dismissal and Sickness - Redundancy is not the same as dismissal - Gross misconduct changes the position completely - Sickness and other absence during notice
An HR Checklist for Managing the Notice Period - The operational steps that prevent disputes - When PILON or garden leave may help
Sample Notice Letters for UK Employers - Employer letter confirming termination with notice - Employer letter acknowledging resignation
The Foundation What Is the Statutory Notice Period
The legal minimum every employer needs to know
The statutory notice period is the legal minimum notice required by law. It isn't optional, and it can't be reduced by contract.
For employer-to-employee termination, the rules are set out in the Employment Rights Act 1996. As summarised by Croner's guide to statutory notice periods, the minimum employer notice is:
Less than one month of service: no statutory notice required
Between one month and two years: one week's notice
Two years of service: two weeks' notice
More than two years: one additional week for each further year of service
Twelve years or more: capped at 12 weeks
That cap matters. Even for a long-serving employee, the statutory entitlement from the employer does not rise above 12 weeks under the Act, unless the contract gives more.
Practical rule: Treat statutory notice as the floor, not the full answer. The contract may improve on it, but it can't lawfully undercut it.
In day-to-day HR work, the mistake isn't usually misunderstanding the idea. It's failing to calculate service correctly, or assuming a short contractual clause overrides the legal minimum. It doesn't.
A quick reference table
Employee's Length of Service | Minimum Statutory Notice Required |
|---|---|
Less than one month | No notice |
One month to less than two years | One week |
Two years | Two weeks |
More than two years | One week for each complete year of service |
Twelve years or more | 12 weeks |
This table is the quickest way to sense-check an employer-led exit.
Why this baseline matters in practice
For SMEs, this isn't just a legal technicality. It drives real decisions. If you're ending employment, the notice period affects when salary stops, when benefits end, when a replacement starts, and how you manage customer or site handover.
It also affects how you communicate the exit. A manager who says “today is your last day” before HR checks statutory entitlement can create a problem in minutes. Even if you later tidy it up with pay in lieu, you've started on the back foot.
The cleanest exits happen when the business checks service length first, contract second, and communication third.
That order matters. Get it the wrong way round and you spend the rest of the process correcting avoidable errors.
Statutory vs Contractual Notice Which One Applies
A common SME mistake starts with a manager reaching for the contract, seeing “one week's notice,” and assuming that settles it. It does not. The contract is only part of the answer.
In most ordinary terminations, the employee gets whichever notice period is longer: the statutory minimum or the contractual notice clause. ADP's explanation of UK notice periods reflects that basic rule. A contract can give more generous notice. It cannot lawfully cut below the statutory minimum where that minimum applies.
The practical risk is not usually the legal principle. It is applying the wrong rule to the wrong type of exit.
For redundancy or a standard dismissal, employers should usually compare the contract with the statutory minimum and use the longer period. For gross misconduct, the position can be different. If you have grounds for summary dismissal and your process supports that decision, employment can end without notice. That distinction matters. I often see employers assume “dismissal” always means statutory notice must be paid. It does not. A fair redundancy process and a gross misconduct dismissal are both dismissals, but they do not carry the same notice outcome.
Resignations are simpler. An employee with at least one month's service must usually give at least one week's notice, unless the contract requires more. If the contract says one month on resignation, that is the period to use.
The other point employers miss is timing. Notice usually starts the day after it is given, not on the same day. If notice is handed over on Monday, day one is Tuesday. That small error can affect final pay, holiday calculations, benefits cut-off dates, and the date you tell a replacement to start.
Use this sequence before any end-date is confirmed:
Check what kind of exit you are dealing with. Redundancy, ordinary dismissal, resignation, and gross misconduct do not all lead to the same notice result.
Read the notice clause and any PILON or summary dismissal wording.
Compare the contractual notice with the statutory minimum where notice is required.
Count the notice from the following day.
Confirm the final working day, or termination date if payment in lieu applies, in writing.
Often, costly errors occur. A business treats a misconduct dismissal like a redundancy and overpays notice, or treats a redundancy like gross misconduct and underpays it. The legal rule is not difficult. Choosing the right rule for the reason employment is ending is what protects the business.
Calculating Notice Periods in Practice
A simple method that works
Notice calculations get easier when you stop treating them as a legal puzzle and use the same sequence every time.
Use this method:
Identify who is giving notice. Employer and employee notice don't follow the same rules.
Check continuous service. The employee's length of service drives the statutory position.
Read the contract carefully. Look for notice clauses, probation clauses, PILON clauses, and any wording about summary dismissal.
Compare the two positions. Apply the longer notice if it's an ordinary termination or resignation.
Confirm the final date in writing. Don't leave the end date open to interpretation.
This works well in SMEs because it gives managers a repeatable process instead of relying on memory.
Worked examples for common situations
Take an employer-led termination first. An employee has worked for 18 months. Their contract says either side can give one week's notice. In that case, the contractual and statutory positions match, so one week applies. If you give notice on Monday, the notice starts on Tuesday.
Now take a longer-serving employee. They have worked for five years and the contract says one month's notice. The statutory position for employer notice is longer at that stage, so the statutory entitlement would be the one to follow. This is exactly the type of case where businesses go wrong if they look only at the contract.
If the numbers don't match, stop assuming the contract controls the exit. Compare both positions before any letter goes out.
For resignation, the pattern is different. Suppose an employee has worked for three years and the contract is silent on resignation notice. The statutory minimum is one week if they've been employed for more than one month. If the contract instead requires one month, then the contract governs because it is longer.
A few practical checks help:
Watch incomplete years of service: don't round up unless your contract expressly improves on the statutory position.
Use the notice date, not the meeting date alone: if notice is confirmed in writing later, make sure everyone agrees on when notice was given.
Keep payroll involved early: final salary, holiday pay, and benefits depend on the correct end date.
The businesses that handle exits well usually don't have more complex systems. They just use the same checking routine every time.
Handling Special Cases Redundancy Dismissal and Sickness
A common SME mistake starts like this. A manager decides to remove a role, calls it a dismissal, then issues the wrong notice or withholds notice pay because the employee has also raised conduct concerns. That shortcut creates risk fast.
Redundancy, ordinary dismissal, and summary dismissal for gross misconduct do not follow the same notice logic. If you treat them as interchangeable, you can get the termination date wrong, underpay notice, and create an avoidable dispute.
Redundancy is not the same as dismissal
In redundancy, the job is disappearing or the business need has changed. That matters because the employee is usually entitled to notice in the normal way. You should not lift a conduct dismissal approach and drop it into a redundancy process.
The practical distinction is simple. Redundancy generally means notice must be given, or paid in lieu if the contract allows and you choose to use that route. Dismissal for gross misconduct can remove the right to notice entirely, but only if the misconduct is serious enough and the process is sound.
Situation | Notice position | Main employer risk |
|---|---|---|
Genuine redundancy | Statutory or contractual notice applies, whichever is longer | Underpaying notice or using the wrong process |
Ordinary dismissal, such as capability or conduct short of gross misconduct | Statutory or contractual notice applies, whichever is longer | Focusing on the reason for dismissal and forgetting the notice entitlement |
Gross misconduct summary dismissal | No notice only if summary dismissal is justified | Calling conduct “gross misconduct” without enough evidence or a fair procedure |
That comparison is where employers often go wrong. The reason for termination drives the notice outcome.
For employers reviewing wider termination exposure, this unfair dismissal compensation calculator guide is useful context alongside your notice checks.
Gross misconduct changes the position completely
Summary dismissal is the exception, not the default. If gross misconduct is established, employment can end without statutory notice and without notice pay.
The problem is not the label. It is whether the facts support it.
I see this in practice with theft allegations, data misuse, serious insubordination, and violence. Some cases plainly justify summary dismissal. Others sit in a grey area where the employer is frustrated, the investigation is rushed, and the evidence would not hold up well if challenged. In those cases, refusing notice pay can be more expensive than paying it.
A safer approach is to ask three questions before confirming zero notice:
Was the conduct serious enough to destroy trust and confidence?
Did you investigate properly and give the employee a fair chance to respond?
Can you explain, with documents, why summary dismissal was reasonable?
If the answer is shaky on any of those points, stop and reconsider the notice position before the letter goes out.
Sickness and other absence during notice
Sickness absence does not cancel the need to handle notice correctly. An employee can be off sick and still be in a notice period. The issue is usually not whether notice exists. The issue is how notice pay, sick pay, holiday, and the final termination date interact.
Keep the categories separate. A redundancy process should stay a redundancy process even if the employee is absent. A capability dismissal for ill health needs its own fair process. Absence should never be used as a shortcut to treat a case as misconduct.
Watch for higher-risk cases:
long-term sickness where medical evidence is incomplete
disability-related absence
maternity or other family leave
overlapping issues, such as sickness during a live redundancy consultation
Those are the cases where small errors become tribunal points. Slow the process down, confirm the contractual wording, and document why you chose that termination route and notice position.
An HR Checklist for Managing the Notice Period
A notice period goes wrong operationally long before it goes wrong legally. The letter might be fine, but the handover is vague, the laptop isn't returned, the final payslip is wrong, and the line manager says something that contradicts HR.
Use a checklist. It prevents small errors from turning into larger disputes.
The operational steps that prevent disputes
Verify the notice position: confirm service length, contract wording, and the final date before any formal communication goes out.
Put the outcome in writing: state the date notice was given, when it starts, and the employee's final day of employment.
Plan the handover early: identify client work, open projects, passwords, licences, site information, and any knowledge that exists only in that employee's head.
Coordinate final pay carefully: include salary due, accrued but untaken holiday where applicable, deductions, and any agreed payments.
Control system access: decide what stays live during notice and what should be limited, especially for finance, client data, and sensitive records.
Arrange return of property: laptops, phones, keys, passes, tools, uniforms, and documents should all be listed and tracked.
A good checklist also protects the remaining team. It shows that the exit is organised and professional rather than improvised.
When PILON or garden leave may help
Sometimes working notice isn't the best option. If the relationship has broken down, or the employee has access to sensitive information, you may consider Payment in Lieu of Notice (PILON) or garden leave, if the contract supports it.
PILON can help where you need a clean break. Garden leave can help where you want the employee bound by duties during the notice period but kept away from active work and client contact.
Before you use either, check the contract and think through the practical consequences:
For PILON: make sure the payment is calculated properly and confirmed clearly.
For garden leave: define expectations on availability, confidentiality, and contact with clients or colleagues.
For both options: align HR, payroll, IT, and line management before informing the employee.
This short video gives a useful prompt for managers reviewing notice period handling and wider people processes.
Notice periods can also affect wellbeing, both for the departing employee and the team left behind. If a difficult exit is creating stress, this practical guide to supporting mental health at work is worth keeping in your wider HR toolkit.
Sample Notice Letters for UK Employers
Clear letters reduce arguments. They don't need legal theatre. They need accurate dates, plain wording, and a record of what has been decided.
Employer letter confirming termination with notice
Dear [Employee Name],I am writing to confirm that your employment with [Company Name] will terminate with notice.Your notice period is [insert notice period], and your employment will end on [insert final date].During your notice period, [set out whether the employee will work their notice / be placed on garden leave / receive payment in lieu if contractually permitted].We will confirm arrangements for final pay, accrued holiday, return of company property, and any handover requirements separately.Yours sincerely,[Name][Job Title]
Employer letter acknowledging resignation
Dear [Employee Name],Thank you for your letter/email confirming your resignation. I acknowledge receipt of your notice on [insert date notice was received].In line with your [contractual/statutory] notice period, your final day of employment will be [insert final date].We'll confirm handover arrangements, final pay, outstanding holiday, and return of company property with you shortly.Yours sincerely,[Name][Job Title]
Keep these letters simple. The detail belongs in the supporting offboarding plan, not in a long and confusing notice letter.
Conclusion Protecting Your Business with Compliance
Most notice period problems aren't caused by complicated law. They're caused by rushed decisions, weak documentation, and treating redundancy, resignation, and dismissal as if they all work the same way.
The safest approach is consistent. Check the contract. Check the statutory minimum. Apply the longer notice where required. Calculate dates carefully. Put everything in writing. And when redundancy or gross misconduct is involved, slow down and make sure you're using the right legal route.
That distinction matters. Redundancy notice and summary dismissal are not the same, and mixing them up can create avoidable risk.
If you're unsure, get advice before the letter goes out, not after the dispute starts.
If your business needs practical support with compliance, training, and people risk management, KODOBI helps UK employers build safer, more organised workplaces with clear, workable systems.
Comments