What is the Bradford Factor?

The Bradford Factor is a simple, widely used metric that highlights the operational cost of short, frequent unplanned absences. For site‑first operations managers who run mixed workforces (employees, contractors, temps), it’s useful because it prioritises disruption — not just total lost hours.

If your payroll and site logs live in spreadsheets, photos or scattered clocks, Bradford scores will be unreliable and won’t help you spot the real risks. Capture it™ Time & Attendance solves that by creating one auditable source for who was on site, when, and why — so Bradford calculations are accurate and defensible.

The Bradford Factor — quick definition and why it matters

• Purpose: measure disruption caused by frequent short absences rather than total absence time.
• Why ops care: repeated short absences cause more rostering friction, tool and vehicle reassignments, and safety risk at sites than a single long absence. Bradford helps you see that risk and act before it becomes a payroll or safety problem.

The formula (simple)

Bradford score = S × S × D

• S = number of separate absence incidents in a chosen period (usually 52 weeks)
• D = total days absent in that same period

Example:

• Worker A: 1 absence of 5 days → S=1, D=5 → score = 1 × 1 × 5 = 5
• Worker B: 5 absences of 1 day → S=5, D=5 → score = 25 × 5 = 125

The higher the score, the greater the disruption caused.

How to use Bradford scores sensibly

1. Choose a sensible period — 26 or 52 weeks are common. Keep finance and HR aligned.
2. Use thresholds for action, not punishment. Typical bands: Low (<50), Moderate (50–199), High (200–499), Severe (500+). Localise thresholds to your business and union agreements.
3. Look at the context: seasonal peaks, site pressures, role type. Contractors and short‑term staff can skew results.
4. Combine Bradford with safety and headcount signals — an elevated score on a critical site is higher risk than the same score at a low‑activity depot.
5. Make the Bradford one input in a fair absence management process — support, rostering changes or formal review where patterns repeat.

Common pitfalls that make Bradford scores misleading

• Fragmented data sources (paper logs, photos, multiple clocks) produce under‑ or over‑counting of incidents.
• Misclassified absence reasons: sickness vs authorised leave vs time off to attend training.
• Contractor and visitor records kept separate from employee records. Bradford needs a single person-level history.
• No audit trail for approvals or overrides — difficult to defend in grievance or tribunal.

If you rely on a patchwork of spreadsheets and gate photos, the Bradford score can give false positives that damage trust and create unnecessary HR workload.

How Capture it™ fixes the common problems

Capture it™ is built for site‑first operations teams who need clean, auditable attendance data across mixed workforces.

• Single source of truth: centralised clock-ins (biometrics, proximity, mobile geolocation, PC clocking) and contractor/visitor records feed one dataset — accurate S and D values.
• Clear incident classification: record absence reasons and link them to site and role metadata so Bradford counts are meaningful.
• Roll‑call and headcount: instant site checks let you see the operational impact of absences in real time.
• Payroll‑ready exports: export validated Bradford inputs and reconciliation reports for payroll and people teams. No manual reconciliation.
• Audit trail: timestamped approvals and change history make Bradford decisions defensible with full evidence for audits or disputes.
• Low‑disruption pilot: test Bradford reporting on 1–3 sites first to validate thresholds and workflows before wider rollout.

Practical steps to implement Bradford scoring this month

1. Centralise inputs: stop new paper sign‑ins and consolidate clocking options (mobile + site clocks) for a 30‑day period.
2. Clean historic data: run a 3‑month reconciliation to normalise absence reasons and remove duplicates.
3. Choose your period and thresholds with payroll/HR (26 vs 52 weeks). Document them.
4. Run Bradford scores weekly and flag people in Moderate+ bands for a trigger review (coaching, rostering, welfare check).
5. Link Bradford flags to site risk: map high scores to sites with high contractor churn or critical activities and adjust cover plans.
6. Keep an auditable log of every review decision for payroll and compliance.

If you’re using Capture it™, these steps are fast: the platform gives you roll‑call, incident filters and export formats ready for payroll teams.

Quick checklist — readiness for Bradford scoring

• All clocking sources feed a central system (no paper logs).
• Absence reasons are standardised in your records.
• Contractors and visitors are recorded against person IDs.
• Payroll export includes per‑person absence incidents and total days.
• A weekly report flags scores above your chosen threshold.
• Review process and documentation in place for flagged cases.

Summary

Bradford scores are useful — but only when the underlying attendance data is reliable. Capture it™ turns fragmented site records into audit‑ready data so your Bradford calculations reflect real disruption, not paperwork noise.

Contact us for more information