In an office, absence is visible: the empty chair, the quiet corner. In a hybrid team, a sick day can hide inside a working-from-home day for weeks, leave balances live in a spreadsheet only one person trusts, and nobody can say who is actually available on Thursday. Absence management is not a bigger problem in hybrid teams, but it is a far less visible one.
The short version
- Record every absence type in one system, next to attendance and leave, not in a separate spreadsheet.
- Separate planned absence from unplanned. Unplanned is where cost and disruption concentrate.
- Use simple measures such as the absence rate and the Bradford Factor, and pair them with human judgement.
- Approve leave with team coverage in view, or anchor days quietly fall apart.
Start with one record
Most absence problems are records problems. Holiday in a spreadsheet, sickness in an inbox, appointments in a calendar nobody checks, and no link to who was expected on site. Each record is roughly right; together they cannot answer the basic questions. Who is off today. Who has leave left. Is this the third Monday in a row.
Put every absence type in one system with clear categories, and give people self-service to request leave and see their own balance. When requesting is easy and visible, the informal I-will-just-message-my-manager route, where records go to die, dries up on its own. Accrual rules belong in the same place, so leave accrual stops being a year-end argument.
Separate planned from unplanned
Booked holiday is a cost of doing business and a sign of a healthy team. Unplanned absence is where disruption lives. Reporting that mixes the two hides the signal, so split them everywhere you count.
For unplanned absence, two measures cover most needs: the absence rate, the share of scheduled days lost, and the Bradford Factor, which weights frequent short spells more heavily than one long one. Both are conversation starters, not verdicts. A raw score applied automatically punishes people with health conditions and can breach equality law; the score plus a human review is the standard for a reason.
The hybrid blind spot
The hardest hybrid case is the vague day: not in the office, not on leave, not obviously working. Sometimes it is flexibility doing its job. Sometimes it is unrecorded sickness, and occasionally a pattern of absenteeism that would have been noticed in week two in an office. The answer is not surveillance. It is clarity: if someone is unwell, it is recorded as sickness, wherever they are working. People record honestly when a sick day is not treated as a failure and the system takes less than a minute.
Approve with coverage in view
Approving leave without seeing the team calendar is how anchor days collapse. The approver needs one screen showing who else is off, who is expected in, and what that does to cover. That is also the argument for keeping absence next to workplace booking rather than in a separate HR silo: the Thursday question, who is in, who is off, and is there space, only has an answer when both halves live together.
- One system for every absence type, with self-service requests and visible balances.
- Planned and unplanned absence split in every report.
- Absence rate and Bradford Factor tracked, reviewed by a person, never auto-triggered.
- Leave approvals shown against team coverage and office anchor days.