9-Day Fortnight

A 9-day fortnight spreads full-time hours over nine days instead of ten. How to calculate it, who it suits and what has to go into the contract.

Written by: Rinaily Bonifacio

In this article we explore the concept of a 9-day fortnight to uncover benefits, how to calculate it, and the implementation process for organisations.

What is the 9-day fortnight working pattern?

A 9-day fortnight is a compressed hours pattern: staff work the same fortnightly total in nine days instead of ten, typically taking every second Friday off.

Comparison – Compressed 9-day fortnight vs 9/80 vs four-day week:

Aspect	Compressed 9-day fortnight	9/80 schedule (US term)	Four-day week (reduced hours)
Definition	Same total hours compressed into 9 days each fortnight; one earned/rostered day off (EDO/RDO).	80 hours worked over 9 days across two weeks; every other Friday off.	Fewer hours (often ~32/week) for the same pay; not compressed.
Typical pattern	4 × longer days + 1 standard day in Week A; 4 × longer days in Week B; off day every second week.	Week A: 4 × 9h + 8h Friday (often split 4+4 across two workweeks); Week B: 4 × 9h, Friday off.	4 working days/week with reduced hours overall; no “make-up” time.
Pay assumption	Same pay as 40-hour week (hours unchanged).	Same pay as 40-hour week (hours unchanged).	Same pay while reducing hours (where adopted).
Overtime exposure (headline)	UK: manage to Working Time Regulations average; longer days can increase fatigue risk; local rules apply via contracts/agreements.	Weekly FLSA OT triggers >40 hours per workweek; must define a fixed workweek so the mid-Friday split prevents 44-hour weeks. State overlays (e.g., California daily OT) still apply.	OT depends on local law; hours are cut, so OT risk typically falls, but coverage planning matters.
When it shines	You want predictable coverage with one extra rest day per fortnight, minimal payroll change.	You need a US-friendly variant with clear payroll rules and an every-other-week long weekend.	You’re pursuing well-being/retention and can redesign workloads to fit fewer hours.
Common pitfalls	Holiday clashes with the off day; uneven Friday coverage.	Mis-set workweek boundary → unintended OT; ignoring daily OT states (CA).	Cutting hours without process redesign; service levels dip.

Is it legal? Quick compliance snapshot

Here’s the shortest path to “can we do this?”, with the 2026 rules and where managers slip up.

🇬🇧 United Kingdom (employees’ right to request)

Since 6 April 2024, flexible working became a day-one right. Employees can make two requests per year, employers must consult before refusing, and give a decision within two months. Align your 9-day fortnight policy and workflow with this process.
GOV.UK guidance confirms compressed hours as a valid arrangement under flexible working. Keep records of requests and reasons if refusing.

🇺🇸 United States (FLSA baseline)

The FLSA is workweek-based: overtime is due for hours >40 in a fixed, recurring 168-hour workweek. A 9/80 schedule is allowed if your workweek boundary is set so the first Friday’s hours and the off-Friday fall in different weeks.
Daily overtime is not a federal rule, but state laws can add it.

State spotlight: California (common pitfall)

Daily overtime after 8 hours/day (double time after 12). To run compressed 9- or 10-hour shifts without daily OT, you generally need a votedAlternative Workweek under Labour Code §511. Plan this before announcing a 9-day fortnight.

Business case in 2026: what results can you expect?

Compressed hours can lift engagement and retention when you protect service coverage and manage overtime.

✅ Quick checklist (decision-maker view)

Confirm legal route (UK requests / US workweek / CA AWW if needed).
Choose A/B rotation and minimum Friday coverage level.
Model overtime and holiday collisions before the pilot.
Track impact: absence, overtime cost, service SLAs, retention.

Designing your pattern (coverage, fairness, payroll)

The aim is simple: guarantee service coverage, treat people fairly, and avoid overtime surprises.

Coverage: keep phones ringing and shifts filled

Split teams into A/B Fridays so one half is always in. Set minimum staffing for customer support, field service, or production lines.
Plan fatigue, not just headcount. Longer days increase fatigue risk; build in proper breaks and avoid stacking long shifts after nights. The HSE advises assessing patterns, workload and commute when designing shifts.

Fairness: who gets the “off Friday” and when

Rotate off-days quarterly to share “prime Fridays”.
Write clear swap rules (notice, approval, impact on overtime).
In the UK, align your process with the statutory flexible working framework (day-one right, two requests/year, consult before refusing, decision in two months).

Payroll: set boundaries before you pilot

US workweek definition: Fix a recurring 168-hour workweek (it can start any day/hour). For 9/80, split the first Friday into two 4-hour blocks across two different workweeks to avoid a 44-hour week.
UK Working Time: Keep average weekly hours within limits and record decisions under the flexible-working process (see Acas Code).

Who should avoid a 9-day fortnight?

This model isn’t universal. Here’s when compressed hours can do more harm than good.

Safety-critical or high-fatigue environments: If longer shifts raise safety risk (e.g., driving, heavy machinery, healthcare nights), prioritise shorter shifts or extra rest. The HSE links poorly designed long shifts to higher fatigue risk.
US teams in daily-OT states without AWW: Where daily overtime applies (e.g., California), compressed 9–10h days can become expensive unless you adopt an Alternative Workweek properly.
Thin Friday staffing or strict SLAs: If one fewer day of availability harms customer response or revenue, consider staggered off-days or a standard 5/40 with flexible start/finish instead. (Use data from your call volumes and ticket SLAs to decide.)

How Shiftbase supports a 9-day fortnight

Plan the rota, fast. Build and publish A/B Friday teams, use shift templates, and copy patterns forward so every second Friday is pre-planned. Add public holidays so rate cards and staffing are handled automatically.
Track hours with guardrails. Clock-in via web, app, or terminal; apply automatic overtime/surcharges and see live labour costs against your plan: helpful when compressing hours. Managers can review and approve hours on a fixed cadence.
Apply clear absence rules. Configure absence policies per contract, choose how public holidays affect balances, and register national holidays so time off on an “off Friday” is treated consistently.

👉Try Shiftbase free for 14 days to publish your first A/B rota and track costs in real time:

free trial.

Frequently asked questions

Use the statutory flexible working route: it's a day-one right, employees can make two requests/year, you must consult and decide within two months. Document agreed changes.

Yes, if you define a fixed 168-hour workweek and structure the first Friday so 4 hours fall in Week A and 4 in Week B. Otherwise, you may trigger >40 hours in a week.

Absence %, overtime cost, service SLAs, error/incident rates, retention/intent to stay. Benchmark compressed-hours adoption using CIPD DataHub charts by industry/occupation.

Rinaily BonifacioSenior Content Marketer

Rinaily writes for Shiftbase about HR, scheduling and building teams people actually want to work in. She turns the messy reality of workforce planning into practical advice you can put to work today.