Employee Statement of Sickness: What UK Employers Need to Know
Employee statement of sickness is a phrase that often causes confusion for employers, particularly smaller businesses without dedicated HR support. It usually comes into play during the early stages of absence, yet mistakes made here can lead to problems later, especially around sick pay, record keeping, and trust.
I regularly speak to employers who are unsure when they can rely on an employee statement of sickness, how long it applies for, and what they are entitled to ask for next. The rules are not complicated, but they are precise, and misunderstanding them can create unnecessary disputes.
This article explains how an employee statement of sickness works in practice, how it fits into wider absence management, and what UK employers should be doing to protect themselves while remaining fair.
What an Employee Statement of Sickness Is
An employee statement of sickness is a self-certification provided by an employee when they are off sick for a short period. It allows the employee to confirm that they were unfit for work without needing a medical certificate.
In most cases, an employee statement of sickness covers absences of up to seven calendar days. This includes weekends and non-working days. During this period, employers should not insist on a fit note from a GP.
The statement can be provided using the HMRC self-certification form or through an employer’s own sickness absence procedure. What matters is that the information is recorded accurately and consistently.
Problems often arise where employers demand medical evidence too early or refuse to accept self-certification. Tribunals tend to view that approach unfavourably, particularly where trust has not previously been an issue.
Employee Statement of Sickness and Statutory Sick Pay
Employee statement of sickness is closely linked to Statutory Sick Pay. For SSP purposes, self-certification is sufficient evidence for the first seven days of absence.
Employers are entitled to withhold SSP if eligibility conditions are not met, but not simply because a fit note has not been provided during the self-certification period. This is a common area of misunderstanding.
I have advised employers who refused SSP because the employee did not attend a GP appointment during the first week. In those cases, the employer’s position was difficult to defend.
Clear internal policies help here. Employees should know how and when to submit an employee statement of sickness, and managers should understand what evidence is acceptable at each stage.
Managing Absence Beyond Self-Certification
Once an absence extends beyond seven days, employers are entitled to request a fit note. At that stage, the statement of sickness no longer applies on its own.
However, employers should be careful not to treat this as a sudden shift in tone. Good absence management builds on earlier communication rather than replacing it.
Fit notes may suggest that an employee is not fit for work or may be fit with adjustments. Employers should read these carefully and consider whether temporary changes could support a return.
Where absence continues, keeping accurate records from the statement of sickness stage onwards becomes important. These records often form part of later capability or long-term sickness decisions.
Trust, Consistency, and Common Pitfalls
Employee statement of sickness relies heavily on trust. Most employees use self-certification appropriately, but employers sometimes worry about misuse.
Where patterns emerge, such as frequent short absences, employers are entitled to investigate. However, treating all self-certification with suspicion usually backfires.
Common mistakes I see include:
- Demanding GP evidence during the self-certification period
- Applying different standards to different employees
- Failing to keep proper absence records
Consistency matters. If one employee’s statement is accepted but another’s is challenged without clear reason, allegations of unfair treatment may follow.
Employee Statement of Sickness and Longer-Term Issues
While employee statement of sickness is designed for short absences, it often forms the starting point of longer-term sickness management.
Repeated self-certified absences may indicate an underlying health issue or workplace problem. Employers should approach this sensitively, using return-to-work meetings to explore what support may be needed.
Handled well, these conversations can prevent escalation. Handled badly, they can damage relationships and increase the risk of grievance or claim.
In situations where absence becomes prolonged, the early records created through employee statements of sickness can become important evidence of how the employer responded.
Legal Risks and Practical Safeguards
Employee statement of sickness itself rarely leads directly to claims. The risk lies in how employers respond to it.
Refusing sick pay, disciplining employees prematurely, or ignoring patterns altogether can all create legal exposure. The safest approach is one that is measured, documented, and consistent.
Many employers sense-check their approach against external guidance such as ACAS. This can be helpful for general understanding, but it does not replace advice tailored to your business.
Where absence issues overlap with capability, disability, or dismissal risk, it is sensible to look at the wider picture and seek proper free initial employment law advice before taking action.
From my experience, employers who handle employee statements of sickness calmly and consistently are far less likely to face disputes later. The early stages of absence management often set the tone for everything that follows.
Employee statement of sickness should be seen as a routine administrative tool, not a battleground. When combined with clear policies and sensible communication, it supports both the business and the employee.
If your organisation is experiencing repeated short-term absence or uncertainty around sickness procedures, reviewing your approach now can prevent problems later.
For further guidance from Employers Law, you may find these pages helpful: