Last updated: 10 November 2026
A Bradford Factor calculator applies the formula S² × D to produce a single score representing how disruptive an employee's absence pattern has been over a rolling 52-week period, where S is the number of separate absence spells and D is total days lost. Most UK employers set trigger points between 200 and 500 before a formal conversation starts.
Key Takeaways
- Pulse Operations notes that the Bradford Factor formula is S² × D, where S is the number of separate absence spells in 52 weeks and D is total days absent in that period.
- Ten one-day absences score 1,000 points (10 × 10 × 10), compared with just 10 points for one continuous ten-day absence (1 × 1 × 10), per the PolicyPros Attendance Management Policy guide (2024).
- UK employees took an average of 9.4 sickness absence days in 2025, the highest level since the CIPD began tracking in 2010, according to CIPD / Personnel Today (2025).
- Pulse Operations advises that the Equality Act 2010 requires employers to disregard or discount disability-related absence before applying a Bradford Factor trigger point, or risk a discrimination claim.
- Mental ill health is cited in 41% of CIPD respondents' top three causes of long-term absence, per the CIPD Health and Wellbeing at Work 2025 report (2025).
What is the Bradford Factor and what does it measure?
The Bradford Factor is an absence-scoring formula that measures the disruption caused by short, frequent, unplanned absences rather than the total number of days lost. It originated from research associated with the University of Bradford School of Management and was adopted widely across UK industry, including a notable historic application at HM Prison Service.
The underlying logic is operational, not medical: an employer covering a rota — a security contract, a hospital ward, a warehouse shift — finds that frequent unplanned gaps are harder to cover than one long, predictable absence. A single two-week absence can be planned around with holiday cover. Ten scattered single-day absences each arrive without warning and each require a last-minute scramble.
That's precisely the pressure Pulse Operations sees from security and facilities operators managing 24/7 rotas: unplanned short absences are the ones that actually break a shift pattern, because there's no lead time to find cover. The Bradford Factor was built to flag that pattern, not to measure ill health itself — a distinction employers frequently lose sight of once the number becomes a disciplinary trigger.
How is the Bradford Factor score calculated?
The Bradford Factor score is calculated using the formula S² × D, where S is the number of separate absence episodes (spells) an employee has had in the preceding 52 weeks, and D is the total number of calendar days lost to absence across all those spells in the same period. Squaring the spell count is what makes the formula weight frequency so heavily.
Worked example, using the figure from the PolicyPros Attendance Management Policy guide (2024): an employee with ten separate one-day absences in a year scores 1,000 (10 × 10 × 10). An employee absent for one continuous ten-day spell scores just 10 (1 × 1 × 10) — a hundredfold difference for the identical total of ten days lost.

Two employees can lose the same number of working days and receive wildly different scores purely because of how that time was distributed. This is the formula's defining feature and its most common source of confusion: HR teams explaining a high score to a confused employee often find the maths itself is the first thing that needs unpacking.
A second worked example
| Employee | Spells (S) | Days lost (D) | Calculation | Score |
|---|---|---|---|---|
| A | 1 | 12 | 1² × 12 | 12 |
| B | 4 | 8 | 4² × 8 | 128 |
| C | 6 | 6 | 6² × 6 | 216 |
| D | 10 | 10 | 10² × 10 | 1,000 |
Employee A, out for nearly two weeks with one illness, scores lower than Employee C, who had six separate one-day absences totalling six days. This is exactly why the Bradford Factor is described as a frequency metric, not a severity metric — and why it must never be read as a proxy for how ill someone has been.
What counts as a separate instance versus a continuous absence?
A separate instance of absence is any period of sickness that follows a gap of at least one full working day from the employee's previous absence; a continuous absence is one unbroken run of absent days, regardless of length, and counts as a single spell (S = 1) no matter how many days it covers.
This distinction drives the entire calculation, so getting it wrong distorts every score that follows. Practical edge cases that trip up calculators and payroll teams include:
- Friday-then-Monday absences — if an employee is off sick on a Friday and returns fit on Monday, that's one continuous spell if the weekend sits inside it under most policies, but employers must define this explicitly in their attendance policy.
- Same illness, repeated within days — a relapse after returning to work for one day typically counts as a new, separate spell under the standard formula, even though it's clinically the same condition.
- Part-day absences — a half-day for a medical appointment is usually tracked separately from sickness absence and excluded from the Bradford calculation entirely.
- Pre-booked annual leave, maternity leave, paternity leave, jury service and approved unpaid leave are universally excluded from Bradford Factor calculations; the formula is designed to capture unplanned sickness absence only.
Because these rules are policy-defined rather than legally fixed, two employers calculating the same raw absence record can legitimately produce different scores. Any attendance policy using the Bradford Factor needs a written definition of what constitutes a new spell, agreed with HR and ideally reviewed by an employment solicitor before rollout.
What Bradford Factor score is considered high, and what thresholds do UK employers use?
A high Bradford Factor score is typically anything employers flag as a trigger point for formal action, and most UK organisations set that threshold somewhere between 200 and 500 points over a rolling 52-week period, though thresholds vary significantly by sector and workforce.
Commonly cited banding used across UK HR practice looks like this:
| Score range | Typical interpretation | Common employer response |
|---|---|---|
| 0–50 | Low disruption | No action |
| 51–150 | Monitor | Informal return-to-work conversation |
| 151–300 | Trigger point | Formal review meeting, occupational health referral considered |
| 300–500 | High | Formal warning stage under absence policy |
| 500+ | Very high | Final warning or capability process considered |
These bands are illustrative, not statutory — there's no legally mandated Bradford Factor threshold in the UK, and Acas guidance on trigger points is explicit that triggers should prompt a conversation and investigation, not an automatic sanction. Pulse Operations also warns against applying triggers mechanically without considering the underlying cause of absence, which matters hugely given that the Equality Act 2010 requires disability-related absence to be treated differently (covered below).
Context matters when setting a threshold. A security contractor running a 24/7 rota with rotating shift patterns will see naturally higher spell counts across a workforce than a 9-to-5 office team, simply because shift workers report sickness against more individual scheduled shifts per month. Employers should calibrate thresholds against their own historical absence data rather than importing a generic number from a different sector.
How do I use an online Bradford Factor calculator?
An online Bradford Factor calculator is a digital tool — typically a web form or spreadsheet — that applies the S² × D formula automatically once a user inputs an employee's absence spell count and total days lost, removing the need for manual arithmetic.
To use one, you typically need:
- The employee's start date for the rolling 52-week period (usually "today minus 52 weeks" or the policy year start).
- A log of every absence spell within that window, each with a start and end date.
- The total number of calendar days covered by each spell.
- A count of distinct spells (S), derived automatically from the dates entered.
- Exclusions already removed — annual leave, maternity/paternity leave, approved compassionate leave and any disability-related absence your policy discounts.
Most calculators then output S, D and the final score instantly, alongside a flag if the score crosses a pre-set trigger point. The quality of the output depends entirely on the quality of the absence log behind it — a calculator fed incomplete or inconsistently recorded dates will produce a misleading score, however accurate its arithmetic.
This is the practical weak point for most manually-run attendance systems: the formula itself is simple, but maintaining an accurate, up-to-date, 52-week rolling log of spells across dozens or hundreds of shift workers is where errors creep in, particularly when absence is recorded by different managers across different sites using different conventions.
Are there free, reliable Bradford Factor calculator tools for UK businesses?
Free Bradford Factor calculators and Excel templates are widely available from UK HR and employment law websites, and they're generally reliable for calculating the formula correctly, though their reliability depends on manual data entry staying accurate and current.
A basic Excel-based approach typically uses a spreadsheet with columns for employee name, each absence start/end date, and formulas that count distinct spells (COUNTIF logic) and sum total days, before multiplying spell-count-squared by days. This works adequately for small teams with low absence volumes and a single manager tracking data.
Where free tools and spreadsheets typically break down:
- Pulse Operations notes there's no automatic rolling window — most spreadsheets need manual updating to keep the 52-week period current, so old spells that should have dropped off continue inflating scores.
- No link to actual shift records — absence is recorded separately from the rota, so a manager has to cross-reference who was actually scheduled to work before confirming a spell is genuine unplanned absence rather than, say, a swapped shift.
- No audit trail — when an employee disputes a score, there's often no verifiable record of exactly when each absence was logged, by whom, or against what shift pattern.
- Manual exclusion errors — forgetting to strip out a period of approved compassionate leave or a pregnancy-related absence from the raw data is a frequent, legally risky mistake.
For single-site office employers with modest absence rates, a well-maintained spreadsheet can be entirely adequate. For multi-site shift-based operators — security contractors, FM providers, mobile patrol teams — the practical bottleneck shifts from "can we calculate the formula" to "can we trust the underlying attendance data it's built on," which is a rostering and time-and-attendance problem as much as an HR one.
What are the legal risks of using the Bradford Factor in the UK?
The Bradford Factor carries real discrimination risk under the Equality Act 2010 because it's a mechanical formula applied to absence data that frequently includes disability-related sickness, and treating disabled employees the same as non-disabled employees when their absence stems from a protected condition can amount to unlawful discrimination arising from disability.
The legal exposure runs in three main directions:
Discrimination arising from disability. Section 15 of the Equality Act 2010 makes it unlawful to treat someone unfavourably because of something connected to their disability — including absence caused by that disability — unless the employer can objectively justify it. A Bradford Factor trigger that disciplines a disabled employee for disability-related sickness absence, without adjustment, is a well-established tribunal risk.
Failure to make reasonable adjustments. Employers have a duty to adjust how absence policies apply to disabled employees, which commonly means discounting disability-related absence from the Bradford calculation, extending trigger points, or disapplying the standard policy entirely for a known condition.
Indirect discrimination via pregnancy and maternity. Pregnancy-related sickness must be recorded and excluded separately from ordinary sickness absence under UK employment law; folding it into a standard Bradford score and acting on the resulting figure is a recognised route to an unfair dismissal or discrimination claim.
Acas guidance on absence trigger points is unambiguous that triggers "should not be applied automatically" and that managers must look at the reasons behind the figures before deciding on next steps. A Bradford Factor score is evidence to investigate, not a verdict to act on — and tribunals have consistently taken a dim view of employers who treated it as the latter.
How should employers handle disability, pregnancy and mental health absence within the formula?
Employers should exclude or separately discount disability-related absence, pregnancy-related sickness, and clearly document mental-health-related absence before applying any Bradford Factor trigger, because folding these categories into a standard score risks both discrimination claims and a genuinely unfair outcome for the employee.
Practical steps that reduce legal exposure:
- Flag disability status early. Where an employee has disclosed a disability or a condition likely to meet the Equality Act 2010 definition, agree in writing which absences are disability-related and strip those episodes out of the Bradford calculation before the score is generated.
- Record pregnancy-related absence on a separate code. Payroll and rostering systems should capture pregnancy-related sickness distinctly from general sickness, so it never contributes to a standard trigger-point score.
- Treat mental health absence with particular care. Mental ill health is cited in 41% of respondents' top three causes of long-term absence, per the CIPD Health and Wellbeing at Work 2025 report (2025) — a pattern of short absences linked to a disclosed mental health condition may itself be disability-related and require the same discounting as a physical condition.
- Get occupational health involved before, not after, a disciplinary stage. A referral can establish whether a condition meets the Equality Act threshold and what adjustments are reasonable, well before a trigger point forces a decision.
Rachel Suff, Senior Policy and Practice Adviser at the CIPD, has said: "It's really important for individuals, organisations and society that employers take a proactive approach to support people managing health conditions while working." A rigid, unadjusted Bradford Factor policy runs directly against that principle, and is increasingly recognised in UK employment tribunals as both bad practice and legal risk.
What should happen once a high Bradford Factor score is identified?
A high Bradford Factor score should trigger a structured conversation, not an automatic disciplinary step — the first action is always a return-to-work interview or review meeting to understand the cause of the pattern before any formal process begins.
A defensible sequence looks like this:
- Return-to-work interview after every absence, regardless of score, to record the reason and flag any disability or pregnancy connection early.
- Review the score against context — check for excluded categories that haven't been stripped out, confirm the spells are genuinely separate, and look at whether the pattern clusters around specific shifts or rota changes.
- Informal conversation once a lower trigger point is reached, focused on support options rather than warnings.
- Occupational health referral where a health condition is suspected, before any formal stage.
- Formal review meeting under the written absence policy if the pattern continues, with the employee given the right to be accompanied.
- Disciplinary or capability process only as a last resort, and only where disability-related and pregnancy-related absence has been properly excluded and reasonable adjustments considered.
With 148.8 million working days lost to sickness or injury across the UK in 2025, per the Office for National Statistics (2025), and workers with a long-term health condition accounting for more than 62% of those days — 92.4 million of the 148.8 million, per ONS data analysis via Clifton Ingram (2025) — a sizeable share of any high Bradford Factor score across a UK workforce will trace back to an underlying condition that needs careful, lawful handling rather than a template warning letter.
Who is responsible for monitoring Bradford Factor scores in a UK organisation?
Responsibility for Bradford Factor monitoring sits jointly with HR, who own the policy and legal compliance, and line managers, who hold the day-to-day knowledge of individual circumstances needed to interpret a score correctly before any action is taken.
| Responsibility | Typical owner | Why |
|---|---|---|
| Setting trigger points and policy wording | HR / Head of People | Needs legal input and sector benchmarking |
| Logging absence accurately against the rota | Line manager / rostering system | Manager knows which shifts were actually scheduled |
| Running return-to-work interviews | Line manager | First point of contact, builds trust |
| Checking disability/pregnancy exclusions | HR, with manager input | Legal risk sits with the organisation, not the individual manager |
| Approving formal/disciplinary escalation | HR, with senior sign-off | Consistency across the organisation, reduces claim risk |
In shift-based operations — security, FM, mobile patrol, multi-site estates — this split is harder to run cleanly than in a single-office business, because absence against a rota needs cross-referencing with who was actually due in, on which shift pattern, at which site. Mo Hassan, Founder of Pulse, makes a related point about why records built from memory rather than the shift's actual data tend to fall apart under scrutiny:
A handover written from memory at 6am is fiction with good intentions. Build it from the shift's actual record — the patrols, the incidents, the check calls — and a quiet night stays one honest line while an eventful one reads like a proper log. — Mo Hassan, Founder, Pulse
Put the checkpoints, site notes and prior issues in the platform before the first shift, and a brand-new officer arrives knowing the building's history." The same logic applies to absence data — when attendance isn't tied cleanly to the actual rota a manager built, the Bradford Factor score it produces is only as trustworthy as the manual cross-checking behind it.
How does the Bradford Factor compare to other absence management approaches?
The Bradford Factor compares to simpler absence metrics — like a straight days-lost count or a percentage absence rate — by weighting frequency over duration, which makes it useful for spotting disruptive patterns but poor at measuring overall absence volume or genuine ill health severity.
| Method | What it measures | Strength | Weakness |
|---|---|---|---|
| Bradford Factor (S² × D) | Frequency-weighted disruption | Flags patterns of short, unplanned absence | Penalises frequent short absences far more than long genuine illness |
| Total days lost | Volume of absence | Simple, easy to benchmark | Ignores disruption caused by frequency |
| Absence rate (% of working hours/days) | Overall workforce absence level | Good for sector benchmarking | Doesn't flag individual patterns |
| Trigger-based return-to-work only | Qualitative review after every absence | Captures context and cause every time | No quantitative early-warning signal |
The Office for National Statistics measured a UK sickness absence rate of 2.0% of working hours in 2025, unchanged from 2024, equating to 4.4 days lost per worker — a national benchmark figure, but one that tells an employer nothing about whether their own absence is concentrated in a few disruptive patterns or spread evenly. That's the gap the Bradford Factor is designed to fill, and why most UK attendance policies use it alongside, not instead of, a simple days-lost or percentage-rate measure.
Sector context matters too: public sector employees had a sickness absence rate of 2.9% compared with 1.7% in the private sector in 2025, and managers, directors and senior officials had the lowest absence rate at 1.0%, compared with 3.3% for operatives, according to the Office for National Statistics (2025). Operative-heavy shift-based sectors — security, FM, logistics — should expect naturally higher Bradford scores on average than desk-based teams, and should set thresholds accordingly rather than copying a benchmark from a different type of workforce.
What are common mistakes when calculating or interpreting the Bradford Factor?
The most common mistake is applying the Bradford Factor mechanically as a disciplinary trigger without investigating the cause of the underlying pattern first, which creates both legal risk and poor management outcomes.
Other frequent errors:
- Failing to exclude disability-related or pregnancy-related absence before generating the score, creating direct Equality Act 2010 exposure.
- Miscounting spells — treating a Friday-to-Monday absence inconsistently, or splitting a relapse incorrectly, skews the squared element of the formula disproportionately.
- Using a stale 52-week window — forgetting to drop old spells that should have rolled off, inflating current scores against outdated history.
- Setting one threshold for an entire organisation regardless of role or shift pattern, penalising operative and shift-based staff who naturally show different absence patterns than office-based managers — reflecting the operative-versus-manager gap the ONS data shows.
- Treating the score as proof of poor performance rather than a prompt for a conversation, contrary to Acas guidance on how trigger points should be used.
- Not cross-referencing absence against the actual rota, so swapped shifts, cancelled shifts or rostering errors get logged as genuine sickness spells.
Your Bradford Factor calculator checklist
- Confirm your written absence policy defines what counts as a separate spell versus a continuous absence
- Exclude annual leave, maternity/paternity leave, jury service and approved unpaid leave from every calculation
- Flag and discount disability-related absence before generating any score
- Record pregnancy-related sickness on a separate code, never folded into the general Bradford figure
- Set trigger points calibrated to role type — operative/shift-based staff versus office-based managers
- Run a return-to-work interview after every absence, regardless of the resulting score
- Cross-check every absence entry against the actual rota before logging it as a genuine spell
- Get HR sign-off before any formal or disciplinary action, and consider an occupational health referral first
FAQ
What is the Bradford Factor formula?
The Bradford Factor formula is S² × D, where S is the number of separate absence spells an employee has had in the preceding 52 weeks and D is the total number of days lost across those spells. Squaring the spell count means frequent short absences score far higher than one long continuous absence covering the same total days.
How do you calculate a Bradford Factor score?
You calculate a Bradford Factor score by counting distinct absence spells over a rolling 52-week period, summing the total days lost, then applying S² × D. For example, four spells totalling eight days gives 4² × 8 = 128 points.
What is a good or acceptable Bradford Factor score?
A good Bradford Factor score is typically anything below the lowest trigger point an employer sets, commonly below 50 points in a rolling year. Most UK organisations treat scores between 200 and 500 as a formal trigger point, though there's no legally fixed threshold.
Is the Bradford Factor legal in the UK?
The Bradford Factor itself is legal to use in the UK, but applying it mechanically without excluding disability-related or pregnancy-related absence risks breaching the Equality Act 2010. Acas guidance states trigger points should prompt investigation and conversation, not automatic disciplinary action.
Does the Bradford Factor include annual leave or planned absence?
No, the Bradford Factor excludes annual leave, maternity and paternity leave, jury service and other approved planned absence. It's designed to measure unplanned sickness absence only.
Can the Bradford Factor be used to dismiss an employee?
A Bradford Factor score alone should never be the sole basis for dismissal; it can support a fair capability or conduct process only where the employer has investigated the cause, excluded disability-related and pregnancy-related absence, and followed a proper disciplinary procedure with the right of appeal.
Does Acas recommend using the Bradford Factor?
Acas does not specifically endorse the Bradford Factor formula, but its guidance on absence trigger points applies directly: triggers should prompt review and conversation rather than automatic action, and managers must consider the underlying reasons for absence before deciding on next steps. See Acas's trigger points guidance.
Scoring absence fairly on shift-based rotas with Pulse Operations
Bradford Factor calculations are only as reliable as the attendance data feeding them, and that data problem is sharpest for exactly the operators Pulse Operations works with: security contractors, FM providers and mobile patrol teams running rotating shift patterns across multiple sites. An absence logged against the wrong shift, or a swapped shift mistaken for a genuine spell, distorts the whole formula before HR ever sees the score.
Pulse Operations's rostering and time-and-attendance service builds rosters against contracted hours and captures time & attendance directly from the officer app, so absence data is tied to the actual shift pattern an employee was scheduled against — not a manager's separate spreadsheet reconstructed after the fact. That's the same discipline Pulse Operations brought to its own founding operation, Priority First — a sister company with the same majority owner as Aether Agency Ltd, which runs Pulse — where mobilising three sites in a single July fortnight depended on site and shift data being accurate from day one rather than living in someone's head.
If your attendance records are scattered across spreadsheets and WhatsApp messages and you're not confident a Bradford Factor score built from them would survive a tribunal challenge, it's worth talking to Pulse Operations about how rostering and payroll-ready exports can clean that up before you set your next trigger point. Full details, including published per-operative pricing, sit at pulse-operations.co.uk/rostering.
Related Reading
- 4 on 4 off shift pattern explained (UK, 2026)
- Agency Workers Regulations Security: 2026 Compliance Guide
- 4 on 4 off average weekly hours: the 2026 rules
Add pulse-operations.co.uk as a preferred source on Google
Back to all insights