Absenteeism

Absence and absenteeism are not the same thing. An employee who applies for leave, has it approved and takes it has been absent, and nothing has gone wrong. The work was covered because someone knew in advance.

Absenteeism is the residue: absence the organisation did not plan for. That covers the employee who does not turn up and does not say why, the one who calls in on the morning of a shift often enough that the roster stops being reliable, and the one who is nominally on approved leave but applied for it after the fact every time.

Defining it by reason instead of by planning is where most policies go wrong. Illness is a legitimate reason and unplanned illness still leaves a desk empty. The point of measuring absenteeism is not to decide who deserves sympathy. It is to find out where the work is not getting covered and why.

The common measure is the absence rate: days lost as a proportion of days scheduled, over a period.

Two of these are worth running together. A team with a low absence rate and a high frequency rate has a different problem from a team with the reverse, and only one of them shows up if you look at days lost alone.

Weighted scores deserve a caution. They were designed to make repeated short absence visible, and they do that well. Used as an automatic trigger for disciplinary action they penalise chronic conditions and disability, which is both unfair and legally exposed. A weighted score is a reason to have a conversation, not a substitute for having one.

Absenteeism is almost never distributed evenly. An organisation reporting a modest overall rate frequently has two or three teams carrying most of it, and the aggregate figure conceals that completely.

The cuts that tend to be informative are by team, by manager, by shift, by tenure band and by location. Concentration in any of them points somewhere specific.

• Concentrated in one manager's team, with other teams in the same function normal, the variable is the manager rather than the work.
• Concentrated on night or early shifts, the roster is doing something the people on it cannot sustain.
• Concentrated in the first three months of tenure, the problem is usually selection or onboarding, not attendance.
• Concentrated at one location, look at commute, facilities, local management and whether that site has a supervisor vacancy.

This is why absence data is worth holding against the rest of the employee record rather than in an attendance system that only knows about days. The cut that explains the number is rarely the one the attendance report offers.

Persistent absenteeism in a team resolves to a small number of causes, and disengagement is the most common of them. Someone who has decided to leave often stops turning up reliably some weeks before they say so, which makes a rising team absence rate a leading indicator of attrition rather than a separate problem.

Health is the next, and it splits in two. Acute illness is unpredictable and short. Chronic conditions and caring responsibilities produce a steady, patterned absence that a policy built for the flu handles badly. The second group is usually better served by an adjustment to the work than by an attendance conversation.

Then there is the roster itself. Where absence spikes on particular shifts, or in the week after a run of overtime, the schedule is generating the absence and no amount of attendance management will fix it.

Finally there is the leave policy. Where employees cannot get planned leave approved, some of them take it unplanned instead. An organisation with a strict approval culture and a high unplanned absence rate is usually looking at the same days twice.

The interventions that work start from the cause rather than the day count.

• Run a return-to-work conversation after every absence, briefly and consistently. It is the single most effective measure, and it works because it makes absence noticed rather than because it is punitive.
• Give managers their own team's data. Most managers do not know their absence rate and are surprised by it, and the surprise is what produces action.
• Separate the chronic from the acute early, and move the chronic cases to an adjustment conversation instead of an attendance one.
• Check whether planned leave is actually obtainable in the teams with the worst unplanned absence.
• Look at the roster before looking at the people, wherever the pattern is concentrated on particular shifts.

Attendance incentives are popular and are worth thinking about carefully. Paying for attendance reliably produces attendance, including from people who are ill and should be at home, and it penalises the employee with a chronic condition who cannot win it. The behaviour it buys is often not the behaviour intended.

Absence data touches more of the record than it first appears to.

• Payroll, because unpaid absence reduces gross pay and can affect contributions and accrual.
• Leave balances, because unplanned absence is frequently recorded against casual or annual leave and consumes an entitlement the employee will want later.
• Performance, where absence is often held against an appraisal without ever having been raised as an issue at the time.
• Attrition, because the same teams tend to appear in both.

The last one is the reason to treat this as a management measure rather than an administrative one. Absence is one of the few signals that moves before people resign, and it is available to anyone willing to read it by team rather than in total.