Bradford Factor Explained: A Fair Way to Track Staff Absence
- Trefnus
- 5 days ago
- 8 min read
Published: 15 June 2026 | Last reviewed: 15 June 2026
Tracking staff absence fairly is one of the trickiest parts of managing a small or medium-sized business.
Get it wrong, and you risk either letting genuine problems go unaddressed or treating someone unfairly because of circumstances beyond their control.
The Bradford Factor is one of the most widely used tools for spotting absence patterns that may need attention. It is not a legal requirement, but many UK employers use it as part of a wider sickness absence policy.
It highlights frequent short-term absences, which tend to disrupt teams more than a single longer absence.
This article explains what the Bradford Factor is, how it is calculated, where it works well, where it falls short, and how to use it as one part of a transparent approach to managing staff absence.
What Is the Bradford Factor?
The Bradford Factor is a scoring formula developed to highlight the impact of frequent, short, unplanned absences on a team.
The idea behind it is straightforward: an employee who takes ten separate single days off causes more disruption to planning and cover arrangements than someone who takes one block of ten consecutive days off, even though the total number of days lost is the same.
The Bradford Factor score reflects this by weighting the number of separate absence episodes much more heavily than the number of days absent.
The Bradford Factor Formula
The Bradford Factor score is calculated using the following formula: B = S² × D
Where:
S = the number of separate absence episodes (instances) in a given period, usually a rolling 12 months
D = the total number of days absent across those episodes in the same period
Because S is squared, repeated short absences increase the score very quickly, even if the total number of days lost is small.
Worked Examples
The table below shows how different absence patterns produce very different Bradford Factor scores, even when the total number of days absent is the same.
Absence pattern | Episodes (S) | Total days (D) | Bradford score (S² × D) |
One block of 10 consecutive days | 1 | 10 | 10 |
5 separate single days | 5 | 5 | 125 |
10 separate single days | 10 | 10 | 1,000 |
3 episodes: one 2-day, two 1-day (4 days total) | 3 | 4 | 36 |
This is the central insight behind the Bradford Factor. A single ten-day absence, perhaps due to a planned operation or a serious illness, scores far lower than ten separate one-day absences, even though both involve the same number of days off work.
Why Employers Use the Bradford Factor
For SMEs, even a small number of frequent short absences can have a disproportionate effect. Cover has to be arranged at short notice, colleagues pick up extra workload, and planning becomes difficult.
Common reasons employers use the Bradford Factor include:
Identifying patterns of frequent short-term absence that may otherwise go unnoticed
Providing an objective, consistent starting point for absence review meetings
Triggering a conversation at a defined threshold, rather than relying on managers' individual judgement
Applying the same scoring method to everyone, which supports predictability and policy transparency
It is worth being clear from the outset: the Bradford Factor should not be used as a standalone disciplinary trigger. A high score indicates that a pattern exists and may warrant a conversation, but it does not by itself establish a cause, and it should never substitute for a fair, individual review of the circumstances.
Setting Fair Bradford Factor Thresholds
The Bradford Factor score itself does not tell you what to do. It is simply a number. Fairness comes from how an employer designs and applies the policy around it.
Most organisations set trigger points, such as score thresholds that prompt an informal chat, a formal review meeting, or a referral to occupational health. There is no single correct threshold, and what works for one organisation may not suit another.
To keep the process fair, consider the following points when setting thresholds:
Set thresholds before they are needed, and apply them consistently across the whole team
Communicate the policy clearly to all staff, including how scores are calculated and what happens at each trigger point
Decide on the review period used for the calculation, and apply it consistently (see below)
Treat the score as a prompt for a conversation, not as an automatic disciplinary outcome
Example Trigger Levels
Many organisations use tiered triggers, for example an informal review at a lower score and a formal review at a higher one. Figures vary significantly by sector, team size, and an organisation's typical absence baseline, so these should be treated as illustrative rather than recommended:
Informal review: scores in the region of 50 to 100
Formal review: scores above roughly 200
These ranges are commonly cited starting points, not fixed standards. The right thresholds for any organisation should be set by looking at its own historical absence data, then adjusted over time as needed.
Rolling Period vs Fixed Annual Period
The Bradford Factor calculation depends on the time period over which episodes and days are counted. Two approaches are common:
Rolling 12 months: the most common approach. Absences older than 12 months automatically drop out of the calculation, so the score reflects recent patterns rather than penalising someone indefinitely for absences from years ago
Fixed annual period: the calculation resets at a set point each year, for example aligned with the payroll or holiday year. This is less responsive to recent changes, since an absence early in the period can sit in the calculation for almost a full year
Whichever approach is used, it should be set out clearly in the absence policy and applied consistently across the organisation.
A note on tracking absence data Bradford Factor calculations rely on accurate records of absence dates and episode counts. Some organisations manage this in a spreadsheet, while others use dedicated absence management software that calculates scores automatically and flags trigger points as they are reached. Trefnus Staff is one example of a tool built for this purpose, alongside team rotas and holiday tracking. Explore Trefnus at: |
Where the Bradford Factor Falls Short
The Bradford Factor has well-documented limitations, and a fair absence policy needs to account for these rather than applying the score mechanically.
It Does Not Distinguish Between Causes of Absence
A high Bradford Factor score can result from genuinely unrelated short illnesses, such as a cold one month and a stomach bug another. It can also result from absences linked to a disability, pregnancy-related illness, or a long-term health condition managed through multiple short episodes.
Treating all high scores the same way risks unfair outcomes, and depending on the circumstances and any adjustments already in place, may raise discrimination concerns under the Equality Act 2010. Any absence policy should include a step to review the reasons behind a score before deciding on next steps.
It Can Discourage Reporting Genuine Illness
If staff feel that any short absence will count heavily against them, some may come to work while unwell, which can affect both their own recovery and the health of colleagues. A fair policy makes clear that the score is a trigger for a supportive conversation, not an automatic penalty.
It Treats All Episodes the Same Regardless of Length
Because the formula only counts the number of episodes (not their individual length up to the total), a one-day absence and a two-day absence both count as a single episode. This is generally accepted as part of how the tool works, but it is worth understanding when interpreting scores.
Best Practice for Fair Absence Tracking
Whether or not an organisation uses the Bradford Factor, the following practices help support a transparent, consistent approach to managing staff absence:
Have a clear, written absence policy that all staff can access, including how absence is recorded and reviewed
Apply the same process and thresholds to everyone in a similar role, to avoid claims of inconsistent treatment
Record the reason for each absence where appropriate, with sensitivity around health information
Hold return-to-work conversations after absences, focused on support rather than blame
Keep accurate, accessible records of absence dates, durations, and any related notes or occupational health input
Review absence data regularly, looking for patterns across teams as well as individuals, which may point to wider issues such as workload or working conditions
Good record-keeping is the foundation of fairness. Without accurate data on absence dates and durations, it is difficult to apply any policy, Bradford Factor or otherwise, consistently.
Frequently Asked Questions
Is the Bradford Factor a legal requirement in the UK?
No. The Bradford Factor is not required by UK law. It is a voluntary management tool that many employers choose to use as part of their absence management policy. Employers are free to use it, adapt it, or use a different approach entirely, provided their overall absence policy is applied fairly and consistently.
What is a typical Bradford Factor trigger point?
There is no single standard trigger point, as it depends on the organisation, sector, and typical absence patterns within the team. Many employers set multiple trigger levels, for example one score that prompts an informal review and a higher score that prompts a formal meeting. Employers should set thresholds based on their own absence data and review them periodically, rather than copying figures from another organisation.
Can a high Bradford Factor score lead to dismissal?
A high score on its own should not lead directly to dismissal. It is a starting point for a conversation about the reasons behind the absences and any support that may help. Disciplinary action, if it follows, should be based on a fair process that considers the underlying causes, any reasonable adjustments needed, and the employer's own absence policy, not on the score in isolation.
Does the Bradford Factor apply to disability-related absence?
Absences related to a disability need particular care. Including disability-related absences in a Bradford Factor score without adjustment could lead to unfair treatment and potential discrimination claims under the Equality Act 2010. Many employers choose to record and review disability-related absence separately, or to disregard it when calculating trigger points, while still recording it for support purposes.
How long should absence data be kept for Bradford Factor calculations?
Most employers use a rolling 12-month period, meaning absences older than 12 months drop out of the calculation automatically. This keeps the score reflective of recent patterns rather than penalising someone indefinitely for absences from several years ago. Whatever period is chosen, it should be applied consistently and set out in the absence policy.
What is the easiest way to track Bradford Factor scores for a small team?
For small teams, a simple spreadsheet can work initially, but it becomes time-consuming and prone to errors as headcount grows or absence patterns become more complex. Dedicated absence management software can calculate scores automatically, flag trigger points, and maintain accurate records, which saves time and supports consistency across the team.
Conclusion
The Bradford Factor is a useful starting point for spotting patterns of frequent short-term absence that might otherwise go unnoticed. Its strength lies in highlighting disruption caused by repeated episodes, but the score itself is only one part of a fair absence management process.
Good practice comes from how the score is used: clearly communicated thresholds applied the same way to everyone, a genuine conversation about the reasons behind any pattern, and proper consideration of health conditions and disability. The Bradford Factor should never be the sole basis for a disciplinary decision.
Combined with accurate record-keeping and a written policy that staff understand, it can support, rather than replace, good management judgement. If managing absence records and calculations manually is becoming a burden, software designed for this purpose, such as Trefnus Staff, can take care of the calculations automatically, leaving more time for the conversations that actually matter.
Further Reading and Official Guidance
Disclaimer: The information in this article is intended for general guidance only and does not constitute professional legal, financial, or regulatory advice. Always consult a qualified professional for advice specific to your circumstances.
