Skip to main content

Bradford Factor

The Bradford Factor is a widely used formula that helps you identify patterns of short, frequent absences. It is based on the principle that many short absences are more disruptive to a business than fewer, longer ones - and in hospitality, where every shift matters, this is especially true.

Who can see Bradford scores​

Only owners and admins see Bradford scores. They see a person's score on their profile's Absences tab, in the Absences report and in the Bradford column of the Team list. Members and viewers see none of these: the profile, report and Team list show without the score. A score is never in the Employee costs report or in return-to-work guidance, for anyone.

The Absences report's CSV export leaves Bradford scores out unless you ask for them. Owners and admins see an Include Bradford scores tick box beside the export button on that report. The checkbox starts unticked when you open Reports. Clear it before exporting without Bradford scores. When selected, the CSV adds a Bradford scores by person section listing everyone at or above your threshold, in alphabetical order.

The formula​

The Bradford Factor score is calculated as:

B = S² x D

Where:

  • S = the number of spells of absence in the last 12 months. Absence records that touch or overlap count as one spell, so Monday to Wednesday logged as one record and Thursday logged as another is still one spell.
  • D = the total number of days absent across all spells, with each day counted once.

The key insight is that S is squared - so the number of separate occasions has a far greater impact on the score than the total duration.

Why frequency matters more than duration​

Consider two team members at your restaurant, both absent for a total of 10 days over the past year:

Worked example 1: one long absence​

Jamie - had one absence of 10 days (recovering from a broken wrist).

  • S = 1 (one instance)
  • D = 10 (ten days total)
  • B = 1² x 10 = 10

Worked example 2: many short absences​

Alex - had 10 separate absences of 1 day each (various Monday mornings).

  • S = 10 (ten instances)
  • D = 10 (ten days total)
  • B = 10² x 10 = 1,000

Both examples total 10 days of absence. The scores differ because they count a different number of separate spells.

Worked example 3: mid-range pattern​

Sam - a cafe supervisor who had 3 separate absences totalling 6 days (2 days, 1 day, and 3 days).

  • S = 3
  • D = 6
  • B = 3² x 6 = 54

At the default threshold of 200, 54 is below the threshold.

Worked example 4: escalating pattern​

Jordan - a bakery team member who had 5 separate single-day absences.

  • S = 5
  • D = 5
  • B = 5² x 5 = 125

At the default threshold of 200, 125 is below the threshold. Two more separate single-day absences would make the score 343 (7² × 7).

Threshold​

StaffBrik uses a default Bradford score threshold of 200. Owners and admins can change it in StaffBrik > Settings, under Absence & holiday > Bradford score threshold, to any whole number from 1 to 10,000,000. Members and viewers don't see the setting. Scores at or above your threshold are marked in amber; scores below it stay neutral.

When an employee's score reaches or exceeds your threshold:

  • Their score shows in amber with the words "at or above your threshold", on their profile, in the Absences report and in the Team list's Bradford column, for owners and admins. Below it, the score is neutral.
  • They are listed in the Absences report, which lists everyone at or above your threshold, in alphabetical order, for owners and admins.
  • Each owner and admin gets a notification, for example Jordan: absence history to look at, with a View absence history link. It doesn't give the score, and members and viewers don't get it.
  • An alert shows on the StaffBrik dashboard and on Home, for owners and admins only, for example High Bradford: Jordan with "At or above your Bradford warning threshold". It doesn't give the score. Everyone at or above the threshold gets one.

Every place that shows a score uses the same rolling 12-month score, judged against the threshold it was worked out with. After you change your threshold, the Absences report refreshes; until it does, it shows the list it was worked out with, under the threshold its heading names.

tip

The score is a prompt to talk, not a measure of anyone.

Which absences count?​

Not all absence categories count toward the Bradford Factor. This is deliberate and important for legal compliance.

CategoryCounts Toward Bradford Factor?
Standard sickYes
UnauthorisedYes
Disability relatedNo
Approved medicalNo
CompassionateNo
caution

Equality Act 2010 Compliance: Disability-related absences are excluded from the Bradford Factor calculation. Including them could amount to treating a disabled employee less favourably because of something arising from their disability. This is a legal requirement, not optional. StaffBrik handles this automatically - you do not need to manually adjust scores.

Approved medical absences (planned surgeries, hospital appointments) are also excluded. These are pre-arranged, cause minimal disruption, and penalising employees for them would discourage transparency.

Days they went home partway​

If someone starts a shift and goes home sick, and you log it with Went home partway through a shift (see Logging absences), that day counts as a full day for the Bradford Factor and for pattern alerts, the same as a day they were off. Losing someone halfway through a shift is just as disruptive to the rota. The category rules above still apply, so a Disability related absence never counts.

The Bradford score on a profile​

On a person's profile, the Absences tab shows owners and admins a Bradford score card:

  • the score, and "At or above your threshold of 200" or "Below your threshold of 200", with your own threshold. The card is amber at or above it and neutral below it;
  • the sum, for example 3² × 50 = 450, and "3 separate spells of absence, 50 days of absence recorded in total";
  • what the number means:
    • S² × D: the number of separate spells of absence, squared, multiplied by the total days recorded for those spells.
    • The score looks back 12 months from today, using the first day of each recorded absence. It counts the full length of each spell, including any future days already recorded.
    • Brikly leaves out absences logged as disability-related, approved medical or compassionate.
    • It's a prompt to talk, not a measure of anyone.

In the Absences report and the Team list's Bradford column, a score shows as a small badge. Hover over it, move to it with the keyboard, or tap it on a phone to see the same explanation; tap again to close it. It updates automatically as absences are logged or fall outside the 12 months.

Pattern detection alerts​

StaffBrik monitors absence patterns and raises alerts when:

  • An employee's Bradford Factor score crosses the threshold.

  • An employee has 3 or more absences in a rolling 8-week period.

  • There is a day-of-week pattern - e.g. repeated Monday or Friday absences.

  • An employee is off sick next to their holiday, judged against approved holiday.

These alerts appear on the StaffBrik dashboard and on Home, for owners and admins only, and help you have timely, supportive conversations with your team rather than letting issues build up.

  • Protected absences never count. Disability-related, approved medical and compassionate absences are never used for a pattern alert.
  • Reviewed alerts stay reviewed. Once a manager has reviewed a pattern, the nightly check leaves it reviewed.
  • Old patterns resolve themselves. When the absences behind a pattern leave the 12-month window, the pattern is resolved overnight, without a notification.
  • Leavers' alerts are resolved when they are archived.
  • The Pattern alerts card on the Absences page counts only patterns nobody has reviewed yet.
info

Pattern detection is designed to prompt supportive management conversations, not punitive action. An employee with repeated Monday absences may be struggling with childcare arrangements, experiencing burnout, or dealing with a health issue they haven't disclosed. The alert is a prompt to check in.

Rolling 12-month window​

The score looks back 12 months from today, using the first day of each recorded absence. It counts the full length of each spell, including any future days already recorded. Absences that started more than 12 months ago drop out of the calculation automatically. This means scores naturally decrease over time if the pattern improves - you do not need to manually reset anything.