Absence: the formula, and what the figure hides when it looks normal
Echipa HR 365 · reviewed 2026-09-02 · 5 min read
The absence rate is the number of absence days divided by the number of planned working days, times 100. All the difficulty is in the numerator: what you count as absence decides whether the figure measures a problem or merely the existence of holidays.
What goes into the numerator and what does not
An absence indicator that includes annual leave measures nothing: leave is planned, paid and wanted. Equally, a training day or a business trip is not an absence, it is work somewhere else. What stays useful in the numerator is unplanned absence — the kind that breaks somebody’s schedule that morning.
| Type of day | Counts as absence? | Why |
|---|---|---|
| Planned annual leave | No | Planned months ahead, covered by a stand-in |
| A sick day called in that morning | Yes | Unplanned; somebody picks up the work the same day |
| Unauthorised absence | Yes | The most expensive case, tracked separately |
| Unpaid leave requested 3 weeks ahead | No, but reported separately | Planned, though it can signal something else |
| Lateness under an hour | Not in days — measured separately, in hours | Mixing units makes the figure incomparable |
| Training, travel, off-site work | No | Working time, in another place |
A department of 24 people, one month
The month has 21 working days. Nobody was away for the whole month. Unplanned absence: 19 sick days called in that morning and 3 unauthorised days.
- Planned working days
- 24 × 21 = 504
- Unplanned absence days
- 19 + 3 = 22
- Absence rate
- 22 ÷ 504 × 100 = 4.4%
- Of which unauthorised
- 3 ÷ 504 × 100 = 0.6%
- The figure to report
- 4.4%, of which 0.6% unauthorised
Nu intră în calcul:
- annual leave in the same month — planned, so a different indicator
- training days and business travel
- lateness, which is tracked in hours rather than days
Three cuts without which the figure says nothing
A 4.4% rate across the whole company is an average of very different zones. Three cuts turn it into information:
- By department and by shift. The night shift almost always has a higher rate, and if you do not separate it, it pulls the company average without anybody knowing where it came from.
- By concentration: how many people produce the absences. Twenty-two days can mean 22 people with one day each (normal) or 3 people with 7 days each (something else entirely). The same figure, two different problems.
- By day of the week. A concentration on Mondays and Fridays is a behavioural pattern; an even spread is usually genuine illness.
The second cut is the most useful and the most rarely done. The practical rule: if fewer than 20% of people produce more than half the absence days, you have an individual problem, not a team one — and team-level interventions will feel unfair to everyone else.
What you do with the figure, depending on what it shows
Three patterns and the response to each
- Absence concentrated on a few people — an individual conversation, with concrete data (the days, not the impression), not a general announcement to the team
- Absence spread evenly, rising — check the schedule and the workload first — it usually precedes or accompanies overload
- Absence concentrated on one shift or location — the problem is almost certainly the conditions there or the direct manager, not the people
What never works: a general announcement that “absence has risen and we have to do something”. It lands on exactly the people who are never away and leaves the intended audience unchanged, because the message is not addressed to them by name.
What it costs, so you can argue for an intervention
The cost of an unplanned absence day is not that day’s salary. It is the salary plus the cost of covering: overtime for whoever picks it up, or production not delivered if nobody does. In manufacturing and retail, where the post has to be covered, the second component is often larger than the first. Without that figure, any discussion about investing in reducing absence stays a matter of opinion.
How you communicate the figure without it feeling like surveillance
An absence indicator presented badly produces exactly the behaviour it was meant to correct: people come in ill and infect the team, or take a leave day instead of a sick day, which moves the problem into another report.
- Do not circulate a named list. The team figure is operational information; names go only into the individual conversation, with the person present.
- Do not tie the indicator to bonuses or to league tables between teams. It gets optimised immediately, and not by fewer illnesses.
- Present it alongside coverage: “we had 22 absence days and on 6 occasions we could not cover the shift” says something; the percentage alone does not.
- When you discuss it individually, start from the facts and the effect, not from a label: how many days, over what period, what happened to the work on those days.
The third recommendation is what changes the conversation with leadership. Absence does not cost through a percentage, it costs through uncovered shifts — and the two do not overlap at all in a well-sized team.
What rate is normal?
It depends so much on industry and season that a universal threshold is useless. Compare with yourself: the same month, last year, the same department. A rise of 1.5 points against the equivalent period means more than any comparison with a market average.
Do I track absence individually or only per team?
Both, but for different purposes. The team figure is for organisational decisions; the individual one is for the conversation with the person, and it stays between the manager, HR and them.
Absences recorded with a reason and a resolution, not just ticked
Every day away has its type, who picked up the work and how it was resolved — so the cuts above take one click rather than a reread of a register.
See the hours and absence module
You can create an account in a few minutes and use every module for 7 days, no card required.