How We Fixed a Broken Absence Culture (Without Making Half the Team Go Formal)

Absence management is one of those topics that every warehouse manager has to deal with eventually, but that very few operations handle well from the start. The problem is usually not that managers don't know absence is high. The problem is that there is no consistent process, so nothing happens, and the culture quietly develops around that gap.

That was the situation when I started in this role. There was no return-to-work interview process. Absence was not being tracked in any meaningful way. Different managers were handling it differently — some having conversations, some not. And the result, over time, was a culture where calling in sick for any reason, on any shift, carried no practical consequence and required no follow-up.

The absence rate was around 20%. That is not a difficult situation to improve in isolation. It is a difficult situation to improve fairly — because if 20% of your team is above the threshold for formal action, you cannot open formal proceedings against 20% of the team at once. You will not have the management capacity, you will not get the outcome you are looking for, and you will create an adversarial dynamic that makes everything worse.

This is what we did instead.

What I Walked Into

The picture was consistent when I started: reliable people covering for absent colleagues, management spending time chasing cover rather than managing operations, and an informal understanding across the floor that absence was effectively self-managed. Not in a dishonest way — most people were genuinely unwell when they called in. But there was no signal to the team that absence patterns were being watched or that there would be a conversation when someone returned. So the threshold for what constituted an acceptable reason to be absent had drifted significantly.

The people with good attendance records were the ones carrying the weight. They were being asked to flex shift patterns, pick up additional tasks, and cover roles they had not been asked to cover before — without any visible acknowledgement that their reliability was part of what was holding the floor together. That breeds resentment quietly, and left unchecked, it eventually affects the behaviour of people who previously had no absence issues.

The other challenge was the scale. At around 20% absence, applying the Bradford Factor — the standard scoring system that weights frequency of absence — would have flagged roughly half the team for formal action. That is not a viable starting point. Formal proceedings take management time, create tension, and require HR involvement that the operation simply did not have capacity to sustain across that number of people simultaneously. If you try to formalise half your workforce at once, you will lose most of those cases, damage relationships across the operation, and probably not improve your absence rate at all.

Getting the Numbers First

Before changing anything, I pulled whatever absence data existed — timesheets, sick day records, manager notes — and calculated the team average. That number became the dividing line: anyone above the team average was in the cohort for formal process. Anyone at or below was managed through return-to-work conversations only.

This approach had several advantages over a fixed Bradford Factor threshold. First, it was defensible — you are comparing each individual to the team, not to an external benchmark that has never been applied in this operation. Second, it was proportionate — in a team where 20% absence is the norm, a fixed threshold would still catch everyone, whereas the average threshold creates a manageable group. Third, it was dynamic — as the average improved over time, the threshold tightened naturally.

It also gave us the data to have honest conversations. When you can sit down with someone and show them their absence record alongside the team picture, the conversation changes. It moves from "you've been off a lot" — which people can dismiss — to "here's where you sit relative to your colleagues" — which is much harder to argue with.

What We Actually Introduced

The intervention had four components, introduced together so the process felt complete from the start.

Welfare Meetings: The Part That Gets Missed

The welfare meeting is the piece most absence management frameworks either skip or handle badly. It matters because not all absence is avoidance. Some of your team will have underlying health conditions — physical or mental — that are genuinely driving their absence record, and treating those cases the same as someone who simply finds it easy to call in sick will not produce the right outcome for either party.

A welfare meeting is not a disciplinary conversation dressed up with a different name. Its purpose is to understand what is driving the absence and to find practical adjustments that make regular attendance more achievable — lighter duties during a recovery period, a temporary shift change to accommodate a medical appointment schedule, adjusted responsibilities during a flare-up of a chronic condition.

In practice, a welfare meeting often produces a better outcome than formal process for cases where a health condition is the root cause. Someone with a chronic condition who has their duties adjusted in a way that reduces their symptom exposure will attend more consistently than someone who is put through a formal process and still faces the same barriers on every shift.

It also matters from an Equality Act perspective. Persistent health-related absence can relate to a disability as defined under the Act, and an employer who has made no reasonable adjustments before moving to formal action is in a weaker legal position than one who has documented a genuine attempt to support the individual. The welfare meeting creates that record.

How the Team Responded

The reaction was mixed in a predictable way. People with high absence records were suspicious — they could see something had changed and some pushed back, particularly in the early RTW conversations. The framing of the interview mattered here. It had to be clearly positioned as a consistent process that applied to everyone, not as a targeted intervention aimed at specific people. The moment a return-to-work interview felt like a personal accusation, it generated resistance. When it felt like an administrative step that everyone went through, people accepted it.

The people with strong attendance records were relieved. That is the word several of them used in the weeks that followed — relieved. Not because they wanted colleagues to be disciplined, but because they had been watching the imbalance for a long time and it had been frustrating. The introduction of a consistent process meant that someone returning after their fifth absence of the year had to at least acknowledge that, rather than walking back on to the floor as if nothing had happened.

The broader cultural shift came from visibility. Word moved around the floor relatively quickly that absences were being tracked and that a return-to-work conversation was now a certainty, not a maybe. That alone changed the calculation for people who might have previously called in on a difficult morning without a clear medical reason. It did not make everyone suddenly present — that was never the point — but it raised the floor meaningfully and it did so without a single confrontational interaction.

How the 8 Months Unfolded

When the Company Policy Arrived

About 18 months into the process — roughly 10 months after the absence rate had already stabilised below 3% — the company announced a standardised absence management policy that would apply across all sites. For most operations, a policy rollout like that is the starting point. For us, it was a formal consolidation of something that had already been the operational reality on the floor for well over a year.

That ordering mattered. The cultural shift had already happened before the policy made it official. Staff were not encountering a new policy as a change to their routine — they were encountering a formal document that described what had already become normal. That is a much easier implementation than the reverse: issuing a policy and then trying to build the process and culture around it afterwards.

The policy also gave the process institutional backing that helped sustain it through management changes. When a new manager joins a team that already has an embedded absence process, they inherit a working system. When a policy exists but no culture has been built around it, the process tends to decay the moment a manager leaves.

Three Things to Do This Week

1. Pull your last 6 months of absence data and calculate your team average

   Even a rough spreadsheet — names, number of absences, total days — is enough to start. The team average becomes your working threshold. Anyone above it is your starting cohort for the formal process. You do not need a sophisticated system to do this, just the data and a few minutes.

2. Write a one-page RTW interview template and use it for every return from today

   Five questions is enough: What was the reason for the absence? How are you feeling now? Is there anything that made coming in today difficult that we should be aware of? Is there any support you need? And an acknowledgement of the absence record to date. Keep it short. The point is consistency, not interrogation.

3. Identify 2–3 people in your above-average cohort and schedule a welfare conversation

   Not a disciplinary — a conversation. Particularly if their absences follow a pattern that suggests a health condition might be involved. Ask what is going on, whether there is anything you can adjust to make consistent attendance more achievable, and document what was discussed and agreed. That conversation changes the dynamic more quickly than almost anything else you can do.

Managing shift cover across an operation with variable attendance is significantly easier when your scheduling tool gives you real-time visibility of who is in and who is not. Connecteam and Deputy both handle this well for warehouse and logistics teams. See also: team performance management tools and how we planned peak labour with agency staff.