What is the Bradford Factor?
The Bradford Factor attempts to turn employee absence into a number.
The formula gives greater weight to frequent, short-term absences than to fewer, longer ones. It is usually expressed as B = S² × D, where S is the number of separate absence episodes and D is the total number of days absent over a defined period.
The mathematics produces striking differences. An employee who is absent once for ten consecutive days scores 10. Someone who takes ten separate one-day absences scores 1,000.
That difference is the entire point.
The assumption behind the formula is that repeated, unpredictable absences are generally more disruptive to an organisation than a single continuous absence. Each episode can require work to be redistributed, shifts rearranged, meetings changed, or colleagues asked to compensate.
The Bradford Factor, therefore, does not simply count how much someone is absent. It heavily penalises how frequently absence occurs.
Where did the idea come from?
The origins of the Bradford Factor are less certain than its name suggests.
It is widely associated with Bradford University’s School of Management in the UK and is generally traced to thinking about absenteeism and workforce disruption that gained currency in the latter decades of the 20th century. Yet a definitive original study establishing the formula and its authorship is surprisingly difficult to identify.
What is clearer is why the idea spread.
Absence management had an obvious measurement problem. Ten days away from work could mean one prolonged illness or ten unexpected Monday mornings. The operational consequences could be very different, even though conventional absence statistics recorded exactly the same number of lost days.
The Bradford Factor offered employers something irresistible: a simple number that appeared to capture that difference.
As HR systems became more sophisticated, the calculation became easy to automate. Organisations could establish thresholds at which a score triggered an informal conversation, an absence review, or formal action.
Simplicity helped turn the formula into policy.
It also created many of its problems.
Why is it relevant for HR?
The Bradford Factor addresses a genuine organisational concern.
Repeated unplanned absences can disrupt operations, increase workloads for colleagues, complicate scheduling, and create resentment when teams repeatedly compensate for the same person’s absence. Managers need some way of identifying patterns rather than relying on memory or subjective impressions.
Used carefully, the Bradford Factor can provide that signal.
It can also reveal patterns beyond individual employees. If absence frequency rises across a particular team, location, or manager, HR may be looking at something larger than attendance: excessive workloads, poor management, unsafe conditions, low morale, or another organisational problem.
This is where the number is potentially most useful. Not as an answer, but as an invitation to ask a better question.
The uncomfortable reality
The Bradford Factor measures absence with mathematical precision while remaining completely indifferent to its cause.
An employee experiencing repeated illness can produce exactly the same score as someone casually taking days off. Caring responsibilities, disability-related absence, workplace injury, recurring treatment, poor mental wellbeing, and disengagement can all look remarkably similar once converted into S² × D.
The formula cannot distinguish vulnerability from unreliability.
That becomes dangerous when organisations treat thresholds as verdicts rather than indicators. Mechanically applying absence thresholds without considering disability, protected leave, or reasonable adjustments can also create legal exposure.
There is a behavioural consequence too. Employees who know that every additional episode dramatically increases their score may decide that coming to work ill is safer than staying home. A system designed to control absenteeism can therefore encourage presenteeism.
There is an even more fundamental problem. The Bradford Factor assumes frequency is a proxy for disruption. Modern work makes that assumption less reliable.
Several short absences by an employee with considerable autonomy may cause little operational difficulty. One strategically timed absence in a tightly staffed frontline operation could cause considerably more. Yet the formula may judge the first employee much more harshly.
The Bradford Factor measures a pattern. It does not measure its consequences.
What should HR do with it?
The distinction between a trigger and a verdict is crucial.
A high Bradford score can tell HR that an absence pattern deserves attention. It cannot explain why the pattern exists or determine what should happen next.
That requires conversation and context.
Managers need to understand whether an employee requires support, whether adjustments are appropriate, whether working conditions are contributing to the pattern, and whether there is actually an attendance problem at all.
Transparency matters too. Employees should understand how absence is recorded, whether the Bradford Factor is being used, what thresholds mean, and what happens when one is reached. A measurement system employees discover only when it is used against them is unlikely to inspire trust.
Most importantly, Bradford scores should never travel alone. Performance, role requirements, operational impact, individual circumstances, and direct conversation provide information the formula simply cannot.
Numbers can identify patterns. People still have to interpret them.
The takeaway
The Bradford Factor survives because it solves one problem remarkably well: it turns a messy pattern of absence into a number that managers can understand.
Its weakness is the temptation to believe that the number understands the employee.
It does not.
For HR, the distinction matters. Absence data can reveal where attention is needed, but it cannot determine what fairness requires.
The Bradford Factor can tell an organisation how often somebody was missing.
It cannot tell it why.