A line manager opens the shared absence spreadsheet on Monday morning and sees that a reliable colleague has now been away for thirty-one days. Cover is breaking, two deadlines are drifting, and the rest of the team is carrying work they can't absorb indefinitely. The manager's immediate problem isn't how to label the absence. It's how to keep the operation moving while treating the employee fairly.
That's the point at which long term sick stops being background administration and becomes an operating problem. Small businesses feel the impact quickly because one person's absence can affect customer service, delivery dates, payroll, supervision, and morale at the same time. This guide gives you a practical route through the decisions that follow, including the four-week threshold, correct pay, fit-note records, welfare contact, phased return planning, reasonable adjustments, and controls that reduce repeat risk.
Table of Contents
- The Moment Long Term Sick Stops Being Background Noise
- What Long Term Sick Means in UK Workplaces
- Why Long Term Sick Is a Structural Problem for Small Teams
- Pay, Fit Notes, and Annual Leave During Long Term Sick
- Phased Return, Adjustments, and Risk Assessments That Hold Up
- Risk Mitigation for Small Businesses Managing Long Term Sick
- Using a Leave Management Tool to Support the Whole Process
- A Practical Checklist for the Rest of This Week
The Moment Long Term Sick Stops Being Background Noise
A team can absorb a short absence with a shift swap or a small change to a deadline. After several weeks, those fixes stop working. Customer commitments, payroll, supervision, and ordinary workload still need owners, while the absent employee needs fair, consistent contact. For a small business, long term sick is an operating issue that requires decisions, not a label on an attendance record.
UK guidance commonly treats sickness lasting four weeks or more as long-term sickness. The NICE guidance on workplace health and long-term sickness absence uses that definition, and government guidance reflects the same practical threshold. Four weeks does not predict the cause, duration, or outcome. It marks the point at which informal handling should give way to a managed case.
The manager's next decision is whether the business has reliable evidence and a workable cover plan. Record:
- The absence timeline: the first day, current position, and every material change.
- The contact history: welfare discussions, the employee's preferred contact method, and agreed actions.
- The evidence: fit notes and occupational health information, stored securely and separately from team messages.
- The operational plan: temporary cover, exposed deadlines, and duties that cannot be reassigned easily.
- The return route: possible adjustments and a phased return, without imposing a recovery deadline.
A leave-management tool such as LeaveWizard can keep these actions connected. It gives managers one working record for absence dates, documents, contact, and cover decisions, so policy does not sit apart from day-to-day operations.
Manager's rule: Once an absence affects capacity, treat it as a live operational case, not a line in a spreadsheet.
Handle the remaining team with equal discipline. Share only what colleagues need to manage workload, priorities, cover, and communication. Do not disclose medical details or encourage speculation. Health information is confidential, but unallocated work still needs a clear owner. Review the cover plan regularly and record decisions as the case develops.
What Long Term Sick Means in UK Workplaces
Start with the duration. An employee who is off sick for more than four weeks may be classed as long-term sick, according to GOV.UK guidance on taking sick leave. That threshold does not predict the cause, risk, or likely outcome. It tells the manager to replace routine attendance administration with structured case management.
Short-term absence is generally a brief episode followed by a straightforward return. Intermittent absence follows a different pattern. The employee returns between episodes, but repeated absences may create a separate attendance-management concern. Long term sick usually means one continuous period away from work, although NICE also recognises recurring long-term sickness involving more than one episode lasting over four weeks.
The label does not determine the legal treatment. An absence linked to a disability may be long term sick, but disability is a legal concept based on the circumstances and the effect of an impairment, not the length of the absence. An industrial injury may also cause long-term sickness. Authorised unpaid leave remains a different category, even when the employee is not working. Record each category separately, then assess where they overlap.
| Dimension | Short-Term Absence | Long Term Sick |
|---|---|---|
| Typical pattern | A brief episode with a straightforward return | A continuous or recurring absence requiring active case management |
| Manager focus | Notification, cover, basic welfare, and return recording | Evidence, contact, occupational health, adjustments, capability, and operational planning |
| Documentation | Initial notification and any required medical evidence | A continuous evidence chain, contact notes, reviews, fit notes, and agreed plans |
| Return approach | Often a normal return with a brief check-in | May require a phased return, changed duties, risk assessment, or workplace adjustments |
| Main risk | Repeated short episodes may affect reliability | Lost capacity, unclear prognosis, failed return, discrimination risk, or capability concerns |
The four-week threshold changes the manager's questions. Ask what contact the employee can manage, whether the fit note contains useful work-related information, whether occupational health input would clarify options, and which temporary arrangements protect the business without placing an unsafe burden on colleagues.
Keep one working record for those decisions. LeaveWizard can connect absence dates, documents, contact notes, and cover arrangements, giving a small business a clearer link between policy, evidence, and daily capacity.
Good management sits between two poor responses. Treating the absence as entirely private leaves the business without a plan. Treating it as an attendance failure invites pressure, poor decisions, and possible discrimination risk. The manager's job is to protect the employee's confidentiality while making the operational choices the team still needs.
Why Long Term Sick Is a Structural Problem for Small Teams
A small team can absorb a day or two of absence. Months away are different. One extended absence removes capacity, specialist knowledge, and decision-making time, so the manager must solve a cover problem while supporting the employee properly.
The Office for National Statistics sickness absence data recorded 148.8 million working days lost because of sickness or injury in the UK in 2025, averaging 4.4 days lost per worker. The overall sickness absence rate was 2.0% in both 2024 and 2025, yet that figure conceals greater exposure among employees with long-term health conditions.
In 2025, workers with long-term health conditions had a sickness absence rate of 4.0%, compared with 1.0% for workers without those conditions, according to the same ONS release. Long-term health conditions accounted for 92.4 million lost days, more than 62% of all sickness-related absence that year. For a small employer, long term sick is an operating issue, not a category reserved for large organisations with specialist HR teams.
The infographic uses 2023 data, while the surrounding figures use later ONS data. It provides historical context rather than a direct comparison with the 2025 figures.
Why small firms feel the loss faster
A team of fifteen has little spare capacity. One person away for months removes roughly seven percent of headcount, before considering whether that employee holds a skill nobody else can reproduce quickly. Colleagues cover urgent work, improvement projects slip, and decisions take longer because the team has less resilience.
The HSE's work-related ill health and injury data for 2024/25, presented in the linked ONS dataset, records 1.9 million workers in Great Britain suffering from work-related ill health and 40.1 million working days lost to work-related illness and workplace injury. 35.7 million of those days were attributed to illness, rather than injury. The leading categories were stress, depression or anxiety at 52% of cases, and musculoskeletal disorders at 27%.
Each category creates a different management decision. An attendance warning will not resolve an unsustainable workload. Someone with a musculoskeletal condition may need the job's physical demands reviewed before any return is safe or workable. A manager needs clear visibility of absence dates, role dependencies, work allocation, contact, and agreed controls. LeaveWizard can connect those records with cover arrangements, linking policy and evidence to the capacity the business still has available.
One case creates two risks at once. The absent employee may miss appropriate support, while colleagues carrying the work move towards exhaustion. Manage only the individual file and the operating problem remains unsolved.
Pay, Fit Notes, and Annual Leave During Long Term Sick
A long-term absence becomes expensive when payroll dates, medical evidence, and holiday records drift apart. Set one clear process, then make the manager, employee, and payroll team work from the same dates and decisions.
Start with Statutory Sick Pay eligibility and the rules that apply to the absence period. From 6 April 2026, SSP is payable from the first full day of sickness absence, replacing the previous three waiting days, and eligible employees can receive it regardless of earnings under the GOV.UK SSP rules. SSP still has a statutory limit of 28 weeks. Payroll should identify the likely end of entitlement early and explain what happens next, rather than raising the issue in the final pay run.
A fit note may be needed after seven days of sickness for benefits or SSP purposes, as explained in the fit-note guidance for employers and line managers. Treat its wording as evidence for a work conversation, not as a fixed forecast. “Not fit for work” does not necessarily mean the employee cannot work throughout the entire period. “May be fit for work with adjustments” should prompt a review of duties, hours, equipment, and working patterns.
| Day / Week | What changes | Manager action | Evidence to keep |
|---|---|---|---|
| First seven days | The employee may self-certify the initial sickness period | Confirm notification and agree a suitable contact route | Absence start date and notification record |
| After seven days | A fit note may be needed for SSP or benefit purposes | Check the note's dates and work-related recommendations | Fit note or approved record of its contents |
| At four weeks | The absence may be classed as long term sick | Move to structured case management and consider occupational health input | Case review, welfare notes, and current evidence |
| Before week 28 | SSP entitlement may be approaching its statutory limit | Ask payroll to confirm the exact position and explain next steps clearly | Payroll calculation and employee communication |
| During the absence | Annual leave continues to accrue during sickness | Reconcile holiday records and handle any holiday request correctly | Holiday balance, requests, approvals, and carry-over decision |
Use a Statutory Sick Pay calculation guide as a sense check alongside payroll's own calculation. LeaveWizard should hold the absence dates, review points, and supporting records. It should not replace payroll's decision, but it can stop date arithmetic and case evidence being scattered across inboxes and spreadsheets.
Annual leave is a common source of hidden liability. An employee continues to accrue annual leave during sickness, and holiday can be carried over where the applicable rules allow it. The employee may also request paid holiday while off sick. Approving that request does not automatically end the sickness absence. Record the holiday separately, then reconcile the holiday balance, absence record, payroll treatment, and any carry-over decision.
Phased Return, Adjustments, and Risk Assessments That Hold Up
A return to work becomes an operating decision before the employee comes back. The manager must coordinate contact, evidence, cover, adjustments, and reviews so the arrangement works in the job, not only on paper.
Build contact around support, not surveillance
Agree a contact rhythm that suits the employee and the absence. Weekly welfare calls during the first month, followed by fortnightly contact, can give a small business a reliable review point without turning every conversation into pressure for a return date. Record the date, attendees, relevant information shared, work-related concerns, agreed actions, and next review date.
Keep questions practical. Is the employee receiving suitable support? Would occupational health clarify what work they can safely do? Are workplace factors contributing to the absence? What contact method is manageable? Avoid requesting unnecessary diagnosis details, and do not promise an adjustment before checking whether it works for the role.
A single case record also protects continuity when a manager is covering another role. LeaveWizard can keep review dates, contact notes, and supporting records together, so the next decision is based on evidence rather than scattered emails.
Write the return plan before the return
A phased return needs named actions, owners, starting duties, hours, restrictions, and a review date. A gradual build-up over four weeks may be more workable than a full restart, but four weeks is not a template. The plan must reflect the employee's condition, role, and clinical or occupational health advice.
Replace vague wording such as “lighter duties” with specific controls. These might include altered hours, restricted lifting, screen breaks, a changed shift pattern, less customer-facing work, or temporary home working where the role permits it. State who will supervise the arrangement and how the manager will change it if the employee's capacity or business demands shift.
Use phased return guidance for UK workplaces to structure the discussion. An occupational health opinion is particularly useful where a fit note is broad, a previous return has failed, or the business cannot judge whether a proposed adjustment is safe. The employer, employee, and relevant professional advice must still shape the final decision.
Make the risk assessment specific
Under the Management of Health and Safety at Work Regulations 1999, assess the work when a known disability or health condition changes the employee's capability. The assessment should record:
- The effect of the condition: Which limitations or risks affect the work?
- The affected tasks: Which duties, locations, equipment, or shifts create difficulty?
- The controls: What adjustments, supervision, equipment, or restrictions will apply?
- The owner: Which manager will implement and monitor them?
- The review date: When will you test whether the arrangement still works?
A generic office assessment is not enough. “Standard controls apply” does not demonstrate that anyone considered the actual job, the employee's restrictions, or the effect on colleagues and customers.
Handle disability disclosure with equal care. The Equality Act 2010 requires reasonable adjustments where the employer knows, or ought reasonably to know, about a disability. Record relevant conversations, but keep sensitive medical details separate from the operational adjustment record. That separation gives managers usable instructions without spreading private health information.
Risk Mitigation for Small Businesses Managing Long Term Sick
Long term sick becomes an operating risk when one absence changes who serves customers, approves work, or holds key knowledge. In a small firm, cover decisions cannot wait for a perfect medical prognosis. The manager needs a live view of the absence, the work left uncovered, and the next decision date.
Set controls before a case becomes urgent:
- One absence record: Store absence dates, contact notes, fit-note periods, review dates, and payroll flags in one searchable location.
- A deputy for critical roles: Name someone who can make decisions, access essential information, and keep customers moving.
- An escalation path: Set out when the line manager involves the owner, HR adviser, payroll, occupational health, or legal counsel.
- A standing OH relationship: Choose a provider before a complex case arrives, rather than while deadlines are already slipping.
Each control should trigger a management decision. Early welfare contact can identify a communication problem before trust breaks down. An occupational health referral can clarify functional capability before managers build plans around an unclear prognosis. A written return plan can set expectations for duties, hours, and review points before the employee comes back.
Record the decision, its owner, and the date it will be reviewed. That record links policy to daily cover: it shows what support was offered, which adjustments were considered, and why the business changed duties, arranged cover, or sought further advice. Keep sensitive medical information restricted, while giving managers the practical instructions they need.
Managers can worry that early contact feels like pressure. It is supportive when the contact is agreed, proportionate, and documented. Keep welfare management separate from premature disciplinary action. If the case later moves towards capability or dismissal, the Acas Code of Practice on disciplinary and grievance procedures remains relevant to fair process.
LeaveWizard can help close the administrative gap by keeping absence information, review reminders, and case decisions together. The point is not to replace judgement. It is to give the manager a reliable timeline for payroll checks, cover planning, welfare contact, and escalation.
A short explainer can help managers place these controls in ordinary operations rather than leaving them in an HR file.
Using a Leave Management Tool to Support the Whole Process
A spreadsheet may handle straightforward holiday requests. It becomes unreliable when one employee has ongoing sickness absence, several fit notes, SSP milestones, welfare reviews, accrued holiday, and a possible phased return. Dates get miscalculated, attachments remain in personal inboxes, and payroll may need answers from a manager who is unavailable.
The operating question is simple: can someone see what happened, what is due next, and who owns it?
| Operational checkpoint | Spreadsheet plus email | Dedicated leave-management tool |
|---|---|---|
| First notification | A manager enters a date manually and forwards an email | The absence is recorded as a defined event |
| Document storage | Fit notes sit across inboxes and shared folders | Evidence can be connected to the employee record |
| Welfare cadence | Follow-up dates depend on personal reminders | Review dates can be scheduled and monitored |
| Return-to-work steps | Phased hours and duties may sit in a document | The plan and review points can be tracked together |
| Reporting | Managers reconcile several files | Absence patterns and case timelines can be reported from one record |
LeaveWizard records sickness absence, attaches fit-note information to the employee record, sets reminders around SSP cut-off points, schedules phased-return reviews, and keeps an auditable timeline for capability discussions. Its employee leave-management software gives small employers one place to manage absence records instead of relying on one manager's memory.
That improves control, but it does not transfer responsibility to the software. A tool cannot decide whether an adjustment is reasonable, diagnose a condition, or replace occupational health advice. The manager still has to assess the evidence, agree practical actions, and review whether the arrangement works for the employee and the team.
The useful benefit is the administrative link between policy, evidence, payroll dates, and daily cover. A recorded review date can prompt contact. A visible absence timeline can help payroll check the right information. A shared case record can show why duties changed or cover was arranged.
Keep a spreadsheet if it provides timely, accurate, searchable records. Choose a dedicated tool when missed reminders, duplicated information, or unclear ownership starts creating risk. The trigger is not company size. It is whether the current process can give a reliable answer when someone asks what happened, what happens next, and who owns the next action.
A Practical Checklist for the Rest of This Week
Treat this as an operating handover, not another policy exercise. By the end of the week, every live case should have an owner, a next action, and a cover plan.
- Review current cases against four weeks: Separate absences needing long-term management from short-term or intermittent cases.
- Confirm SSP positions: Ask payroll to check each relevant case against the 28-week SSP limit and rules applying from 6 April 2026.
- Book welfare contact: Agree the channel with each employee, add dates to the calendar, and record outcomes.
- Check fit-note continuity: Identify gaps, expired notes, unclear recommendations, or missing records after the seven-day point.
- Set a return review: Add a provisional date even without a confirmed return, so the case remains active.
- Create one searchable record: Bring together absence dates, contact notes, evidence, holiday information, cover, and decisions.
- Assign operational cover: Name deputies for work that depends on the absent employee.
A manager should be able to answer three questions quickly: what happened, what happens next, and who owns it. LeaveWizard carries dates, records, reminders, and return-to-work actions into one absence-management workflow, reducing the risk that work disappears between spreadsheets and emails.
LeaveWizard helps small businesses record sickness absence, organise fit-note and review information, monitor leave and SSP dates, and keep return actions visible. Visit LeaveWizard to see how it supports a clearer absence-management process.
