Start with the distinction
One calendar may show both. One process should not treat them as the same.
Annual leave
Planned time offA holiday workflow should make entitlement, request status, the authorised approver, operational cover, and the decision clear. Managers should apply the organisation’s policy consistently and explain a refusal or alternative where the policy requires it.
Sickness absence
Health and workSickness is normally notified rather than submitted for discretionary approval. The process should cover reporting, relevant evidence, pay administration, supportive contact, return to work, and any adjustment or occupational-health route that applies.
Where the records meet
Workforce planning may need to show that a person is unavailable. It rarely needs to expose a diagnosis. Keep scheduling information separate from detailed health information, and give each only to people who need it for a defined purpose.
Five design failures
Where otherwise reasonable processes become unreliable.
Conflating holiday and sickness
A single generic “absence” route can obscure whether the organisation is making a holiday decision or supporting someone who is unfit for work.
Informal routes create conflicting records
Requests and notifications spread across messages, email, and conversations leave employees unsure what was recorded and managers unsure which record is authoritative.
Collecting or sharing too much
Detailed health information is more sensitive than a simple availability record. Broad access or unnecessary detail increases privacy risk without improving cover.
Applying trigger points mechanically
Review points can prompt a conversation, but they should not replace judgement. Disability-related and pregnancy-related absence may require different treatment, and reasonable adjustments must be considered where the duty applies.
Missing the support and return route
Contact that is absent, intrusive, or focused only on a return date can undermine a supportive process. The right contact, frequency, adjustments, and return plan depend on the individual circumstances.
Operational safeguards
Use absence information to ask better questions, not to infer intent.
A pattern can justify a fair review of workload, process, support, or workplace risk. On its own, it does not establish motivation, capability, misconduct, or future behaviour.
Purpose and proportionality
Decide why each field is needed before collecting it. Use simple availability data for scheduling where possible, and retain health detail only where there is a lawful and necessary employment purpose.
Confidentiality and access
Restrict detailed sickness and injury information to relevant authorised people. Reports for wider operational use should avoid identifying individuals or revealing medical circumstances.
Context and reasonable adjustments
Review absence in context. Consider whether disability, pregnancy, treatment, a workplace risk, or an agreed adjustment affects how a review point should be applied. Record agreed adjustments and revisit them when circumstances change.
Supportive return to work
Agree appropriate contact and a sustainable return plan with the worker. Where relevant, consider occupational-health input, a phased return, workplace adjustments, and a review of risk assessments.
Practical diagnostic
Can your process answer these questions without reconstruction?
1. Distinction
Can employees tell whether they are requesting annual leave or notifying sickness absence, including where the two overlap?
2. Ownership
Is the correct approver, notification recipient, fallback owner, and escalation route clear?
3. Authoritative record
Does one reliable record show entitlement, status, decisions, and operational availability?
4. Privacy
Are scheduling data and detailed health information separated, access-controlled, and retained for defined purposes?
5. Fair review
Do review points prompt human consideration of context rather than an automatic adverse outcome?
6. Adjustments
Can the organisation record and review reasonable adjustments without exposing unnecessary medical detail?
7. Return and support
Is there a named route for appropriate contact, return-to-work planning, occupational health, and follow-up?
8. Assurance
Can leaders examine de-identified trends and process quality without publishing individual absence comparisons?
If an answer depends on searching private messages or asking one person to remember, improve the process before drawing conclusions from the data.
Sources and boundaries
Apply the guidance to the person, policy, and jurisdiction.
This article provides general operational guidance, not legal or medical advice. Employers should check current law, contracts, collective arrangements, internal policy, and specialist advice for the circumstances. A system should support an authorised human process; it should not diagnose health conditions or make automatic employment decisions.
- Acas: Asking for and taking holiday
- Acas: Recording sickness absence and avoiding discrimination
- Acas: Disability-related absence and reasonable adjustments
- HSE: Supporting sickness absence and return to work
- ICO: Handling sickness and injury records
Review the operating record, not just the form.
See the high-level Veritas approach to connected records, permissions, and accountable human decisions.