Predictive scheduling laws: what employers actually owe

A server calls in sick on Friday. You move two people around, add an hour to a third, and text the team. Routine. In Oregon, that Friday afternoon just cost you an hour of pay per changed shift, and if one of those people closed the night before, possibly time and a half on top.

Predictive scheduling laws turn the schedule itself into a contract. Post it, and changing it has a price. This guide covers what Oregon and Seattle actually require, because those are the two we can cite line by line.

What are predictive scheduling laws?

They go by several names, predictive scheduling, secure scheduling, fair workweek. The mechanics are consistent: give the schedule far enough in advance, and pay a premium when you change it after posting.

The logic is worth understanding before the detail, because it explains every rule that follows. The theory is that an unpredictable schedule costs the worker real money, in childcare booked and lost, in a second job they cannot hold, in hours they counted on and did not get. The law does not forbid you to change a schedule. It makes you carry the cost of changing it, instead of pushing that cost onto the person.

Two consequences for an operator. First, these are not posting rules, they are payroll rules: the money lands in the same pay period. Second, the trigger is the moment you post, not the moment the shift starts.

Which employers are covered?

Coverage is narrow, and the thresholds are the first thing to check. Both regimes aim at large retail and food service, not at the independent restaurant.

Three details on the Oregon count that decide borderline cases. The 500 is worldwide, not in Oregon, and chains and integrated enterprises count together. The headcount is the average number of employees on each work day across 20 or more workweeks, in the current or the preceding calendar year, so a seasonal spike can pull you in. And three groups are excluded both from coverage and from the count: workers whose primary duties are unrelated to those operations, salaried employees exempt from minimum wage, and workers supplied by worker leasing companies.

How much notice must you give, and what does a late change cost?

Both regimes land on the same headline number: 14 days. In Oregon the schedule must be in writing and posted at least 14 calendar days before the first day on it, and it must include on-call shifts as well as work shifts.

Then the price list starts. This is where the two regimes diverge, and where most of the money is.

Note the asymmetry, because it drives behaviour. Adding work costs a flat hour. Taking work away costs a multiple of what the person lost. The law is built to make cancellations expensive and additions merely annoying.

Both regimes carve out events outside your control. Oregon exempts natural disasters and similar events, and any change the employee requested. Seattle drops the premium when operations cannot begin or continue because of a public official's recommendation, including a public health official.

What is the rule about clopening shifts?

Closing at midnight and opening at seven is the pattern these laws target most directly, and both put the threshold at 10 hours.

In Oregon you may not schedule someone during the first 10 hours following the end of the previous calendar day's work or on-call shift, unless the employee requests or consents to it. If they do work inside that window, those hours are paid at one and a half times the regular rate. Roadside assistance work is excluded.

Seattle reaches the same place from the other direction: pay time and a half for any hours worked between a closing and an opening shift separated by less than 10 hours.

The practical reading is the same in both. You can still run a clopening, with consent in Oregon. You simply pay for it, every time, and the cost lands on the person who approved the schedule.

What else do the laws require?

Four obligations that are easy to miss because they sit outside the schedule itself.

A good faith estimate at hire. Both require a written estimate of the median hours the person can expect. Oregon adds an explanation of the standby list and whether employees who are not on it may be expected to work on-call shifts. Seattle requires the estimate again annually, and whenever there is a significant change.

The right to decline, and to ask. In both, an employee may decline hours that were not on the posted schedule. Oregon lets employees ask in writing to be added to shifts, and those additions escape the notice rules. Employees may also ask not to be scheduled at certain times or locations, and you may require reasonable verification. Seattle requires an interactive process on schedule preference requests, and you must grant requests tied to major life events unless you have a bona fide business reason to refuse.

Access to hours, in Seattle only. Before hiring someone new, post the available hours for three days and offer them to qualified current employees. Oregon has no equivalent: its standby list is voluntary, not a right of first refusal.

Records. Seattle requires three years. Oregon requires the schedule posted conspicuously, in English and in the language the employer usually uses, plus a Predictive Scheduling poster. We could not confirm an Oregon retention period or the penalty amounts for either jurisdiction on the official pages, so we are not quoting figures we have not read.

One more thing worth saying plainly: these two are the regimes this guide verifies. Several other US cities have adopted their own ordinances, and the thresholds and premiums differ enough that you cannot assume Oregon rules travel. Check the one that covers your locations before you build a policy on this page.

How do you actually run this in a schedule?

The legal text is short. Operating it is not, for one reason: compliance is decided by two timestamps you probably do not record today, the moment the schedule was posted and the moment it changed.

Three habits cover most of the exposure.

• Freeze the schedule at a date, not at a feeling. If the 14 days start when you post, you need to know when you posted, to the day, and be able to show it.
• Log every change against the posted version, with who asked. An employee-requested change is free in Oregon. The same change initiated by you is not. Without a record, you will pay for both.
• Watch the gap between a closing shift and the next opening on the same person, before you publish, not after. Ten hours is the number to screen for.

That is exactly what staff scheduling is for: the posted version is kept, every later edit is attributed, and the gap between two shifts for the same person is visible while you are still building the week. Worked hours come from time tracking rather than from the roster, which matters when premium pay depends on hours actually not worked. And when someone swaps a shift themselves through the employee app, the request is on record as theirs.

If you want the neighbouring rules, our guides on shift swap policy and on breaks in an 8-hour shift cover the two questions that come up next, and the employee availability form is the document that makes the Oregon consent rule workable.

Want to see what your own week looks like against a 14-day posting rule? Book a free demo and we will build it from your real roster, not from a prepared example.

Sources

• Oregon Bureau of Labor and Industries, Predictive Scheduling. Legal basis ORS 653.412 to 653.490 and OAR 839-026.
• Seattle Office of Labor Standards, Secure Scheduling Ordinance, SMC 14.22 and rules SHRR Chapter 120.

Frequently asked questions

Does predictive scheduling apply to small businesses?

Generally no. Both regimes covered here set the bar at 500 employees worldwide, and Seattle adds a 40-location test for full service restaurants. An independent restaurant or a single store is outside them. Be careful with the Oregon count though: it is worldwide, chains and integrated enterprises count together, and it is an average across 20 or more workweeks, so a group that looks small locally can still be covered.

Can I still change a schedule after posting it?

Yes. Neither law forbids changes, it prices them. In Oregon, adding more than 30 minutes or moving a shift without losing hours costs one hour at the regular rate, while cutting or cancelling costs one and a half times the regular rate for each scheduled hour not worked. Changes the employee asked for, and events outside your control such as a natural disaster, do not trigger the premium.

What happens if an employee volunteers for the extra shift?

In Oregon a change the employee requested does not trigger predictability pay, and an employee may ask in writing to be added to shifts without the notice rules applying. The same logic covers the rest rule: someone may work inside the 10-hour window if they request or consent to it, though the hours are still paid at one and a half times. What matters in practice is that you can show the request came from them.

Do these rules cover on-call shifts?

Yes, and that is where employers are most often caught. Oregon requires on-call shifts to appear on the written schedule posted 14 days ahead, and owes one and a half times the regular rate for each scheduled hour not worked when an on-call shift is not used. Seattle owes half the hours not worked when someone is scheduled on-call and not called in. An on-call shift is not a free option.