Predictive Scheduling
Definition, rules and examples

Unpredictable schedules make it hard for hourly employees to plan child care, school, second jobs, and transportation. Predictive scheduling laws aim to give workers more stability while still letting businesses adjust to demand. For employers, compliance depends on good scheduling habits: publishing schedules early, tracking changes, and knowing when a change triggers extra pay.

How predictive scheduling works

Although each law is different, most share common elements:

• Advance notice: schedules posted a set number of days ahead.
• Good-faith estimate: a written estimate of expected hours given at hire.
• Predictability pay: extra pay for employer-initiated changes after the schedule is posted.
• Rest between shifts: a premium for "clopening" shifts with too little time between them.
• Right to decline: employees can turn down hours added after the schedule is posted.

Examples of state and city laws

Oregon

According to Oregon's Bureau of Labor and Industries (BOLI) predictive scheduling page:

• Coverage: retail, hospitality, and food service employers with 500 or more employees worldwide. Exempt salaried workers and some others are not covered.
• Notice: a written schedule at least 14 calendar days before the first day it covers, posted where employees can see it, including all work and on-call shifts.
• Good-faith estimate: new employees receive a written estimate including median expected monthly hours, an explanation of the voluntary standby list, and whether on-call shifts may be expected.
• Rest between shifts: employees generally cannot be scheduled within 10 hours after the end of a shift unless they request or agree to it; hours worked in that window are paid at 1.5 times the regular rate.
• Predictability pay for employer changes without 14 days' notice: one extra hour at the regular rate when the employer adds more than 30 minutes to a shift, changes a shift's timing without loss of hours, or adds a shift; and half the regular rate for each scheduled hour not worked when the employer cuts hours, changes timing with lost hours, cancels a shift, or does not call in an on-call employee. Exceptions include changes requested by the employee and events outside the employer's control.

Seattle

According to the City of Seattle's Secure Scheduling Ordinance page:

• Coverage: hourly employees at retail and food service establishments with 500 or more employees worldwide; full-service restaurants must also have 40 or more full-service locations worldwide.
• Notice: schedules posted at least 14 days in advance; employees can decline hours not on the originally posted schedule.
• Rest between shifts: time-and-a-half for hours worked between closing and opening shifts that are less than 10 hours apart.
• Premium pay: one hour of pay for hours added or for date or time changes; half the hours not worked when an employee is sent home early or scheduled for an on-call shift and not called in, unless an exception applies.

Other cities and states have their own versions. Our predictive scheduling laws guide covers the topic in more depth, and you should confirm details with each jurisdiction's official agency.

Worked example: Oregon predictability pay

A covered Oregon retailer posts a schedule 14 days in advance. Then, with less than 14 days' notice and no exception applying:

In this example, late changes cost $93.00 in predictability pay on top of wages for hours actually worked. Planning schedules more accurately in advance reduces these costs.

Best practices

• Find out whether you are covered in each state and city where you operate, based on industry, employee count, and location count.
• Publish schedules early, at or before the required notice period.
• Forecast demand carefully using sales history, events, and seasonality.
• Log every schedule change with the date, who requested it, and why, so you can show whether an exception applies.
• Use employee-initiated swaps where allowed, with manager approval and documentation.
• Watch rest between shifts when building closing and opening rotations.
• Train managers on what triggers premium pay.

Common mistakes

• Posting schedules late during busy seasons.
• Sending employees home early without recording predictability pay.
• Scheduling "clopening" shifts without consent or premium pay where required.
• Not documenting employee-requested changes, making exceptions hard to prove.
• Assuming one city's rules apply in another.

Getting ready if a law applies to you

If your business may be covered by a predictive scheduling law, start with a short readiness review. Confirm your employee and location counts against each law's thresholds. Review how far ahead you currently publish schedules and how often they change after posting. Identify the managers who build schedules and make sure they know the notice period and the premium rules. Finally, decide where you will record the reason for each change, since exceptions such as employee-requested swaps usually depend on documentation. With these pieces in place, compliance becomes part of the normal scheduling routine rather than a separate task.

How EZTime helps

EZTime helps you build and publish schedules ahead of time with AI shift scheduling and reusable shift templates. Shift swaps with manager approval give employees flexibility while keeping a record of who requested each change, and PTO and absence management shows approved time off before the schedule goes out. Actual hours are captured with a GPS mobile time clock with geofencing, NFC tags, a tablet kiosk, or biometric clocks, with timecard corrections tracked in an audit trail. Payroll-ready Excel and PDF exports work with any payroll software; EZTime does not run payroll. Plans start at $2 per employee per month with a 14-day trial. See scheduling software and pricing.

This is general information, not legal advice.