It Counts How Often. It Never Asks Why.

The Bradford Factor turns your people's absence into a number. Here's what that number can't see, and why it might be punishing exactly the wrong people.

Right. Let me tell you about a formula that's quietly running in the background of a huge number of workplaces, deciding who gets pulled into a room for a chat about their attendance. It's called the Bradford Factor, and once you understand what it actually does, you might never look at your absence data the same way again.

The maths is simple. It takes the number of separate times someone's been off, squares it, and multiplies by the total days. Square the frequency. That's the whole trick. And it means frequency gets punished far harder than length.

Here's what that does in practice. Someone off for one solid fortnight with a serious illness scores low. Someone who's had ten scattered odd days, a migraine here, a sick child there, a morning they just couldn't get out of bed, scores through the roof. Same number of days lost. Very different verdict. On paper, the second person looks like your problem.

Now sit with who that second person usually is.

It's the single parent whose childcare falls through. It's the person managing a condition that flares without warning. It's the one caring for an elderly relative. It's the employee who's so quietly overloaded that their body keeps writing them the sick note their manager won't. The Bradford Factor can't tell any of them apart from someone who simply can't be bothered. It measures the absence with real precision, and it's completely, blissfully blind to the reason.

That's the whole problem in one line. It counts how often. It never asks why.

And it gets worse, because people aren't daft. Once your team works out that every separate day off sends their score rocketing, they do the logical thing. They come in ill. They sit at their desks running on empty, because being present and useless feels safer than being absent and flagged. A formula built to cut absence ends up manufacturing presenteeism, and presenteeism is the far more expensive problem. The IPPR puts it at 44 productive days lost per employee, every single year, to people who turned up but were in no fit state to work. That's the cost that never shows up in your absence figures, because technically nobody was absent. You've not solved anything. You've just moved the problem somewhere you can't see it.

Look, I understand the appeal. Leaders need a way to spot patterns, and a messy pile of absence records doesn't give you that. A single number feels like clarity. And used properly, a high score can be genuinely useful. But only as a smoke alarm, never as a verdict. The number can tell you something's worth a look. It cannot tell you what, and it certainly cannot tell you who deserves a conversation and who deserves support.

Here's where Pressure Literacy comes at it differently. If three people on the same team are all setting that alarm off, the answer isn't three attendance reviews. It's a question. What's going on in that team that's making people ill or absent this often? Because frequent short absence is very often the most honest signal you'll ever get that the pressure in a system has outrun the people in it. It isn't unreliability. It's the load, leaking out the only way it can.

So by all means, keep the number if it helps you spot the pattern. But the moment you treat that score as a character reference, you've stopped leading people and started auditing them. And the ones who'll pay for it are usually the ones already carrying the most.

The leaders I back are the ones brave enough to look at a high score and ask the harder question. Not "why can't this person be more reliable," but "what are we doing that's costing them this much." That question is where the actual work starts. Everything before it is just arithmetic.

A formula can tell you how often somebody was missing. Reading why they were is the entire job. And no amount of squaring will ever do it for you.

That reading is exactly what Pressure Literacy is built for. It's the skill of seeing the pressure your numbers can't, before it turns into absence, resignations or a score in a spreadsheet. If you'd like to know what your organisation's real pressure picture looks like, get in touch, and we'll talk about where to start.