Back to playbooks

Scheduling Fairness and Stability

Use when: workers are dealing with unstable schedules, last-minute changes, or unpredictable hours.
Goal: make schedules predictable enough that people can plan life, childcare, transportation, and income.

Why this matters

Unstable scheduling creates a hidden monthly squeeze:

• income volatility
• higher childcare and transportation costs
• burnout and turnover
• lower service quality from constant churn

Core guardrails

1. Posting window: schedules posted at least 14 days in advance.
2. Change premium: late changes trigger extra pay.
3. Minimum shift length: no ultra-short shifts unless worker-requested.
4. Rest window: minimum time between closing and opening shifts.
5. Hours floor: part-time workers get a minimum weekly-hours expectation band.
6. Worker preference capture: availability and constraints are collected and respected.

Quick targets

• scheduling policy or handbook language
• actual schedule logs for the last 8-12 weeks
• no-show and callout rates
• turnover and vacancy data by team
• overtime and agency coverage costs

Core questions

• How far in advance are schedules actually posted?
• How often are shifts changed after posting?
• Who absorbs the cost of late changes?
• Which teams have the worst volatility?
• Is instability caused by forecasting, staffing, or policy design?

One-ask examples

• “Post schedules 14 days ahead by default.”
• “Add predictability pay for changes inside 72 hours.”
• “Set an 8-hour minimum rest window between shifts.”
• “Track and publish schedule-change rates monthly.”

Scoreboard

• % schedules posted on time
• schedule-change rate after posting
• late-change premium paid
• turnover rate in affected teams
• worker-reported schedule predictability

Use with

• Workplace Issue Map

Definition of done

Leave with:

1. one schedule-stability rule change
2. one owner
3. one metric cadence
4. one follow-up date

Back to playbooks