24-Hour Shift Schedule

Round-the-clock cover needs a rota that respects rest breaks and fatigue limits. The common patterns, the staffing maths and UK compliance points.

In this article, we'll break down what a 24-hour shift schedule is, explore the industries that commonly use them, and discuss their significance.

What is a 24-hour shift schedule?

A 24-hour schedule is a way to organise people so your operation is covered around the clock without gaps.

What it actually means

A true 24/7 rota has continuous cover across nights, weekends and public holidays. Teams rotate through set patterns so that every hour is staffed while individual employees still get rest days. The rota design (e.g., 12-hour or 8-hour shifts) is a choice, not a legal requirement.

What it is not

It’s not a single “best” template or a legal mandate. There’s no U.S. federal limit on daily hours; overtime is due after 40 hours in a workweek for non-exempt staff, regardless of how those hours are spread. In the UK, the Working Time Regulations add specific rules for night workers; typically an average of 8 hours in any 24-hour period, averaged over 17 weeks, plus health assessments.

Compliance basics at a glance

Topic

United States

United Kingdom

Daily hour limit

None set by FLSA

No fixed daily cap; night work limited to 8 hours on average/24h

Overtime trigger

>40 hours/week for non-exempt workers

Weekly average 48-hour limit unless opted-out; overtime rates are contractual

Night work

Paid as contract/CBAs specify

Health assessment + record-keeping duties for night workers

Key risk area

Long blocks causing fatigue

Night work averaging and health surveillance

💡Takeaway: Treat “24-hour” as a coverage outcome, not a fixed template. Pick a pattern that balances fatigue risks, service levels and labour cost, then validate it against your jurisdiction’s rules.

Below are proven patterns managers use to keep 24/7 cover while giving staff predictable time off. For more options and how to choose between them, see our guide to shift patterns.

  • Panama / 2-2-3 (12-hour): Often called “2-2-3”, this rota uses four teams on two 12-hour shifts to cover all hours. Teams work 2 days on, 2 off, 3 on, then mirror the pattern; over four weeks most staff get along weekend every other week. Great for simple staffing maths; rotation between days and nights can be tiring.

  • DuPont (12-hour rotating): A four-team cycle combining 4 on / 3 off, 3 on / 3 off, 3 on / 4 off, with a built-in 7-day break in many variants. It delivers strong coverage with regular recovery, but transitions between day and night blocks need careful management.

  • Pitman (2-3-2, 12-hour): Also known as the Every Other Weekend Off schedule. Employees work 2 on / 2 off / 3 on, then 2 off / 2 on / 3 off the next week. It’s popular in emergency services because it spreads weekends more fairly; like Panama, night rotation requires good fatigue controls.

  • 4-on / 4-off (12-hour or 10-hour): Four consecutive shifts followed by four days off. Easy to understand and swap, with predictable blocks of recovery. Watch forfatigue during the fourth shift, especially on nights; plan breaks and handovers well.

📊Quick comparison:

Pattern

Teams

Typical shift length

Cycle length

Weekends off

Notes

Panama / 2-2-3

4

12h

4 weeks

Every other week (long)

Simple coverage; rotates day/night

DuPont

4

12h

4 weeks

Varies; includes 7-day break

Good recovery; complex rotation

Pitman (2-3-2)

4

12h

2 weeks

Every other week

Even weekend spread; rotate nights

4-on / 4-off

4 (often)

12h (or 10h)

8 days

Every 8 days

Very predictable; watch last-shift fatigue

 

✅ Good practice tips (apply to any pattern):

  • Prefer forward rotation (days → evenings → nights).

  • Limit consecutive night shifts and ensure 48–72 hours recovery after night blocks.

  • Schedule meal and rest breaks clearly and enforce them.

  • Add a standard handover checklist at shift change.

👉 Takeaway: Choose the pattern that fits demand and wellbeing, then test it for staffing levels, compliance and fatigue before you roll it out.

Common pitfalls to avoid

  • Confusing assigned staff with coverage. Two names on a rota do not equal 2-person cover once leave and sickness hit; use the headroom factor. 

  • Ignoring fatigue when chasing efficiency. Under-staffing and long blocks drive fatigue risk; UK HSE and US OSHA advise examining workload, breaks and night work when setting staffing levels.

  • Copying another organisation’s headroom. Start with a reference percentage, then tune it using your own leave, sickness and training patterns from the last 12–24 months. 

Simple checklist to size a 24/7 team

  1. List fixed posts and minimum safe cover per hour.

  2. Calculate weekly cover hours (posts × 168).

  3. Choose the rota type and average hours/FTE (e.g., 40 or 42).

  4. Compute base FTEs (cover hours ÷ hours/FTE).

  5. Add headroom from real absence data.

  6. Sanity-check for fatigue (consecutive nights, recovery time, breaks).

Case studies & real-world examples

Here are recent, practical examples showing how different sectors run 24/7 cover while protecting people and compliance.

  • Healthcare (NHS): self-rostering to cut fatigue and improve fairness

    • What happened: Several NHS Trusts piloted self-rostering/team-based rostering, letting ward teams express preferences and swap within safe rules. UCLH rolled self-rostering from four wards to nursing staff Trust-wide after a successful pilot for 152 staff. Reported benefits included better fairness, fewer clashes, and improved wellbeing without losing cover.

    • Why it matters: In 24/7 settings, small gains in predictability reduce fatigue and sickness. UK employers must also offer health assessments for night workers, which self-rostering supports by aligning patterns with personal risk.

  • Retail & hospitality (US): complying with predictive scheduling

    • What happened: Under NYC Fair Workweek, retail employers must give 72 hours’ advance notice of schedules; fast food has even stricter rules and predictability pay. Companies that standardised templates, locked notice windows, and documented changes reduced penalties and churn.

    • Why it matters: If you operate across cities/states, you’ll need auditable workflows and an electronic paper trail for schedule notice and changes.

  • Data signal: the UK night-time economy is growing even as retail shrinks

    • What happened: The Big Shift 2025 analysed 20.8 million shifts / 165 million hours for 189k UK workers. It found retail contraction alongside growth in the night-time economy, changing when and where managers need staff.

    • Why it matters: Demand is shifting later in the day. Build rotas from real demand curves (sales, footfall, tickets, orders) rather than tradition.

👉 Takeaway: The best results come from pairing the right rota with process controls (notice windows, swaps, health assessments) and data (demand patterns, absence, overtime). Copy the tactic that matches your risk and run a short, measured pilot before scaling.

How Shiftbase supports 24/7 scheduling

Running true round-the-clock cover is easier when planning, hours and leave live in one place. With employee scheduling, you can build rota templates for Panama/2-2-3, DuPont, Pitman or 4-on/4-off, set minimum staffing per shift, publish to the mobile app, and handle swaps without breaking coverage. Managers can track worked hours in real time using time tracking to control overtime and ensure handovers are logged. And with absence management, holiday requests, sickness and training are captured automatically, so you always see the true headcount against required posts.

Why it helps: You get predictable schedules, fewer last-minute gaps, and a clear audit trail for breaks, notice windows and changes: ideal for UK WTR night-work duties and US Fair Workweek-style rules.

Ready to stabilise your 24/7 rota? Start your free 14-day trial and build your first round-the-clock schedule in minutes.

Frequently asked questions

Yes: legality depends on compliance, not shift length. In the US, federal law (FLSA) does not cap daily hours, but non-exempt employees must receive overtime pay for hours over 40 in a workweek. States and cities may add break and notice rules.

In the UK, there's no fixed daily cap, but night workers must average no more than 8 hours in any 24-hour period (usually averaged over 17 weeks) and are entitled to health assessments.

A "clopening" is working a closing shift followed by an early opening shift. It reduces recovery sleep and raises fatigue risk. Some US local laws restrict short turnarounds; NYC Fair Workweek bans certain last-minute changes and requires 72-hour advance notice for retail schedules. Even where not regulated, avoid tight turnarounds or add premium pay and transport support.

First compute coverage hours (posts × 168), then divide by the average weekly hours per FTE, and finally add a headroom/relief factor for leave, sickness and training. Example: 2-person cover → 336 hours/week.

If your rota averages 42 hours/FTE and you add ~20–25% headroom, you'll need roughly 10 FTE. (Use your own absence data to set headroom.) Good practice: stress-test fatigue before finalising.

Employees have a day-one right to request flexible working (since 6 April 2024). You must follow the updated Acas Code of Practice, consult before refusing, and decide within the shorter statutory timeframe. In 24/7 settings, consider options such as fixed nights, partial remote tasks, or team-based/self-rostering within safety guardrails.

Break rules are jurisdiction-specific. The FLSA doesn't mandate meal or rest breaks, but many US states do (e.g., meal by the fifth hour; extra meals after longer shifts).

In the UK, workers get at least 20 minutes when working more than 6 hours, with additional protections for night work and young workers. Build breaks into templates and audit uptake.

Equal rotation isn't always safe. Evidence-based practice is to rotate forward (days → evenings → nights), cap consecutive nights, and provide 48–72 hours of recovery after night blocks. Monitor overtime, incidents and sickness to validate your pattern.

See all terms