Absence management: measuring it without policing people

Absence management covers how a company records time away from work, notices when a pattern is forming, and handles the cases that need handling. It gets a bad name because it is often introduced as surveillance, but the underlying purpose is dull and reasonable: knowing who is in, planning around who is not, and treating two people in the same situation the same way.

Small companies usually run this on memory until roughly the point where two people are off in the same week and something is missed. That is the moment the informal system fails, and it fails in a way that lands on customers.

What absence management actually involves

• Planned time off: holiday requested, approved and visible to everyone who needs to plan around it.
• Unplanned absence: sickness, emergencies, dependants — recorded on the day, not reconstructed at month end.
• A notification rule: who to tell, by when, and how. Vague expectations here cause most of the friction.
• A return-to-work conversation, short and routine, after any period of sickness.
• Patterns: repeated short absences, or absences clustered around weekends and specific days.
• Cover: who does the work while someone is away, decided in advance for the roles where it matters.
• Records kept accurately, because they carry legal weight if anything ever becomes formal.

The return-to-work conversation does more than any policy document. Five minutes, routine for everyone, asking whether the person is fit to be back and whether anything at work contributed. It catches problems early, and because it happens every time, it is not a signal that someone is under suspicion.

Patterns, and the trap in measuring them

Frequent short absences generally disrupt work more than one long one, which is why some organisations use a scoring method such as the Bradford factor that weights frequency more heavily than duration. Used as a prompt to have a conversation, that is defensible. Used as an automatic trigger for disciplinary action, it is not, and it produces two predictable outcomes: people come to work while genuinely ill, and people with a disability or a chronic condition are disadvantaged by a formula that does not distinguish their situation from anyone else's.

Any threshold should therefore start a conversation rather than a process, and any absence connected to a disability, pregnancy or an ongoing medical condition is a legally distinct case in most jurisdictions. Those rules govern; a scoring method does not override them, and getting this wrong is expensive in a way no efficiency gain compensates for.

Setting it up

1. Write down the notification rule — who, by when, by what method — and make it the same for everybody.
2. Record every absence on the day it happens, with the type recorded consistently.
3. Make planned time off visible to the team so cover is arranged before rather than after.
4. Hold a short return-to-work conversation after every sickness absence, without exception.
5. Set a review threshold that prompts a conversation, and say plainly it is not automatic discipline.
6. Treat absence linked to a disability or an ongoing condition separately, following local rules and advice.
7. Look at the aggregate once a quarter: absence concentrated in one team is usually about the work, not the people.

What the numbers are actually telling you

A rising absence rate in one team is a symptom worth investigating before it is a problem to manage. Understaffing, an unreasonable workload, a difficult manager and a genuinely unpleasant task all show up as absence, and none of them are fixed by tightening the policy. Presenteeism — people at their desks while ill or unable to concentrate — costs more than absence and appears in no report at all, so a low absence figure is not automatically good news.

Where to keep it

The visibility part is calendar work: Ettex Calendar shows who is away and when on a shared team calendar, so planning around an absence does not require asking anyone. That solves the coordination problem, which for most small teams is the one that actually bites.

Be clear about what it is not. There is no leave-booking workflow, no entitlement or accrual calculation, no approval routing, no carry-over rules and no absence reporting — it shows the dates, it does not administer the policy. The records themselves, and anything sensitive about why someone was away, belong somewhere with deliberate access control rather than on a calendar the whole team can read.

Record on the day, make planned time off visible, hold the return-to-work conversation every time, and let thresholds start conversations rather than processes.