← The library

Absence management (contested) Contested practice

Bradford Factor

The Bradford Factor scores absence as S² × D — spells of absence squared, times total days — so frequent short absences score far higher than one long one.

It gives absence management an objective-looking trigger number, and that is exactly its danger: the formula cannot tell a sick child from a sick culture, or a disability from a discipline problem.

Problem
Absence management (contested)
Altitude
Function
Effort to run
Light
Evidence base
Emerging

Theory & origin

Named after the University of Bradford’s School of Management, the factor encodes an operational truth: five separate Mondays disrupt a team far more than one five-day flu, so spells are squared while duration counts linearly. HR systems adopted it because it turns messy absence patterns into a single sortable number with policy trigger bands. The controversy is structural, not cosmetic: the formula is blind to cause. Chronic illness, disability-related absence and caring responsibilities all produce high-frequency patterns, which is how mechanical Bradford triggers walk employers into disability-discrimination claims and employees into hiding illness — presenteeism that costs more than the absence did.

Explore the model

How a consultant runs it

  1. 01 Use the score as a conversation trigger, never an automatic sanction — the formula flags patterns, humans establish causes.
  2. 02 Exclude protected and declared absences (disability-related, pregnancy, caring leave) from the calculation before any band is applied.
  3. 03 Set trigger bands with employee representatives and publish them; a secret formula breeds exactly the distrust it measures.
  4. 04 Read high scores as diagnostics first: clusters under one manager or one shift pattern are a management finding, not twelve individual ones.
  5. 05 Track presenteeism alongside — if scores fall while sick colleagues visibly work through illness, the policy is succeeding at the wrong thing.

When to use

  1. 01 Surfacing absence patterns a manager’s memory misses across a large workforce
  2. 02 Shift and frontline operations where short-notice absence has real coverage costs
  3. 03 As one input into a supportive attendance conversation — with cause established before consequence

When not to use

  1. 01 As an automatic disciplinary trigger — mechanical application is the direct route to discrimination claims
  2. 02 On populations with declared disabilities or caring duties without exclusions; the formula punishes the pattern their situation produces
  3. 03 Where the real problem is a sick culture — high scores clustered under one manager are not twelve attendance problems

Worked example

A 900-person contact centre runs Bradford bands mechanically and opens capability cases on everyone over 500. The consultant’s audit finds one case is migraine-driven — a likely disability accommodation failure, quietly settled — and that 60% of high scores sit in two teams with the same shift pattern and the same team leader. The formula was punishing individuals for a rota problem. Rebuilt policy: protected absences excluded, scores trigger supportive conversations not sanctions, and the rota is redesigned. Absence falls 22% the next year — most of it from the two teams whose real problem was never the employees.

Common pitfalls

  1. 01 Automatic sanctions off the raw score — the pattern behind most Bradford-related tribunal losses
  2. 02 Counting disability, pregnancy or caring absences because nobody built the exclusions
  3. 03 Driving presenteeism: employees working sick to protect the score, infecting the team and costing more
  4. 04 Reading individual scores where the real signal is managerial or structural clustering

Sample deliverable

One real engagement, end to end — watch the numbers travel from raw input, onto the chart, into the artifact.

Absence pattern scan — Jakarta contact centre

Input — raw data

  • Case A — 8 spells × 10dscore 640
  • Case B — 4 spells × 6dscore 96
  • Case C — 2 spells × 8dscore 32
  • Case D — 1 spell × 20dscore 20
↓

Process — mapped

Spells and days convert to S² × D; scores are read against bands, then against causes

↓
OutputDeliverable

Absence pattern scan — Jakarta contact centre

  • Case Amigraine · accommodation, not discipline
  • Cluster60% of high scores, one rota
  • Fixexclusions + rota redesign, −22% absence

Sources

Next in the library 9-Box Grid (Performance × Potential) →