Back to Blog
·StaffMagic Team

Predictive Scheduling Laws: What Hospitality Employers Need to Know

ComplianceScheduling

A growing number of cities and states are passing “predictive scheduling” or “fair workweek” laws that require employers to give workers advance notice of their schedules. If you operate in Seattle, San Francisco, New York City, Chicago, Philadelphia, Oregon, or a handful of other jurisdictions, these laws may already apply to you.

Here’s what hospitality employers need to understand about predictive scheduling requirements.

The Core Requirements

While specific rules vary by jurisdiction, most predictive scheduling laws share common elements:

Advance notice: Employers must post schedules a certain number of days before they take effect—typically 7 to 14 days. Schedules posted with less notice may trigger penalties.

Predictability pay: If you change an employee’s schedule after posting it, you may owe them additional compensation. This includes adding hours, subtracting hours, or changing the timing of shifts. The penalty is often 1-4 additional hours of pay per change.

Right to rest: Employees may have the right to decline shifts that don’t provide adequate rest between them. “Clopening” (closing late, opening early) often triggers extra pay or must be voluntarily accepted.

Good faith estimate: At hire, employers must provide a written estimate of expected hours and schedule. This isn’t a guarantee, but it sets expectations and can be used as evidence if actual hours consistently differ.

Right to input: Employees may have the right to request schedule changes and have those requests considered in good faith.

Who’s Covered?

Predictive scheduling laws don’t apply to all employers. Typical thresholds include:

  • Industry: Usually food service, retail, and hospitality
  • Employer size: Often 500+ employees globally (some laws set lower thresholds locally)
  • Employee type: Typically hourly employees, not salaried managers

Check your specific jurisdiction—thresholds vary significantly. A restaurant chain with 600 employees nationwide may be covered in Seattle but not in Chicago, depending on how many employees are in each location.

What Triggers Predictability Pay?

Understanding what triggers extra pay helps you avoid unintentional violations:

Adding hours after posting: Asking someone to come in early or stay late after the schedule is posted usually triggers predictability pay, unless the employee requests the additional time.

Subtracting hours: Sending someone home early or canceling a shift also triggers pay in most jurisdictions. You may owe them a portion of the hours they lost.

Changing shift times: Moving a shift from 9 AM to 11 AM is a change that triggers pay, even if total hours stay the same.

Exceptions exist: Most laws allow penalty-free changes if the employee requests the change, if the employee accepts the change in writing, in cases of natural disaster or emergency, or if the business unexpectedly closes (power outage, water main break).

The Cost of Non-Compliance

Predictability pay adds up. Consider a restaurant in a jurisdiction requiring 14-day notice with 2-hour predictability pay for each change:

  • Manager cancels one server’s shift due to slow projection: 2 hours pay
  • Another server is asked to stay an extra hour: 2 hours pay
  • A cook’s shift is moved from 3 PM to 5 PM: 2 hours pay

Three routine schedule adjustments just cost you 6 extra hours of pay. Multiply that across a busy week with a staff of 50, and non-compliance becomes very expensive.

Beyond predictability pay, some jurisdictions impose fines for violations and allow employees to sue for damages.

How to Stay Compliant

Compliance isn’t about eliminating schedule changes—that’s impossible in hospitality. It’s about building systems and habits that minimize changes and document everything properly.

Plan ahead: The more accurate your demand forecasting, the fewer post-posting changes you’ll need. Use reservation data, historical patterns, and event calendars to get schedules right the first time.

Post early: If your jurisdiction requires 14 days notice, aim for 16 or 17. The buffer gives you time to catch errors before the clock starts.

Document everything: When changes happen, document the reason, whether the employee agreed, and what compensation was provided. Scheduling software can automate this tracking.

Train managers: Every manager needs to understand what triggers predictability pay. A well-meaning “can you stay an extra hour?” might cost the company real money.

Build flexibility into the base schedule: Instead of scheduling to exact demand, slightly over-schedule and plan for where you’ll reduce if it’s slow. Offering (not requiring) people to go home early is often cheaper than mandatory cuts.

The Role of Scheduling Software

Managing predictive scheduling compliance manually is theoretically possible but practically difficult. Modern scheduling platforms help by:

  • Automatically tracking when schedules are posted and all subsequent changes
  • Calculating predictability pay owed when changes occur
  • Flagging clopening violations before they happen
  • Documenting employee consent for voluntary changes
  • Generating compliance reports for audits

The right software doesn’t just reduce compliance risk—it also provides visibility into how much schedule changes are actually costing you, which often motivates better planning.

Looking Ahead

Predictive scheduling laws are spreading. If you’re not covered today, you may be tomorrow. States and cities are introducing new proposals regularly, and federal interest has grown.

Even if you’re not legally required to provide predictable schedules, there’s a business case for doing so. As we’ve covered elsewhere, schedule predictability improves retention, reduces callouts, and increases employee satisfaction.

Whether you’re complying with law or just following best practice, the same disciplines apply: plan ahead, forecast accurately, communicate early, and document changes. These habits protect you legally and make your operation run better.