How Multi-Unit Restaurants Get Hit by
Predictive Scheduling Laws

What Predictive Scheduling Laws Actually Require

Predictive scheduling legislation, sometimes called "fair workweek" laws, imposes requirements on employers in covered jurisdictions before they can change a posted schedule. The specifics vary by jurisdiction, but the core obligations are consistent:

• Advance notice: Schedules must be posted a defined number of days before the workweek begins. Oregon requires 7 days; Chicago, New York City, and Seattle require 14 days.
• Premium pay for changes: Schedule changes made after the notice period trigger premium pay obligations, typically an hour of "predictability pay" for each shift change, regardless of whether the employee's total hours change.
• Rest between shifts: Most laws require a minimum of 8 to 11 hours between shifts. Scheduling a closing shift followed by an opening shift without that rest period triggers an additional premium, called "clopening" pay.
• Good-faith estimate: Some jurisdictions require that employers provide employees with a written estimate of expected hours at hire and on request.

Where Multi-Unit Operators Consistently Fall Short

The challenge isn't understanding the rules, most payroll and HR teams know them. The challenge is that enforcement requires your scheduling data and your payroll system to be synchronized in real time, and for your payroll system to actually calculate and pay the premium when it applies.

In practice, here's where the breakdown happens:

• Schedule changes made verbally or via text. A manager tells an employee to come in two hours earlier. No system sees it. No premium is triggered. The employee shows up; payroll has no record of a change.
• POS schedule not updated. The scheduling tool has the corrected schedule; the POS still has the original. The employee clocks in against the original; the discrepancy is invisible until a dispute surfaces.
• Premiums not calculated at payroll run. Even when schedule changes are documented, the payroll system has to know to calculate predictability pay for that employee, for that period. Without automation, this is a manual step, and it gets missed.
• No audit trail when a claim is filed. The employee files a claim. The employer can't produce the original posted schedule, the change record, or any documentation that premium pay was or wasn't owed. The claim settles.

What a Compliant Automated Workflow Looks Like

The fix is a data loop that runs without human intervention:

1. The master schedule is posted in your scheduling system. MAD Software ingests it and pushes it to the POS for clock-in validation.
2. Any change made in the scheduling system after the notice deadline is captured with a timestamp.
3. The validation engine flags the change and calculates the premium pay obligation per the applicable jurisdiction's rules.
4. The premium lands in the correct earning code in your payroll file, automatically, every period, with the applicable hours and rate.
5. Every schedule version, every change, and every payroll calculation is logged with an immutable audit trail.

If a claim is filed, the audit log produces the answer. If an auditor asks, the data is there. If a new location opens in a covered jurisdiction, the rules are already in the engine.