Last updated: June 2026.
Not legal advice. Penalty structures, thresholds, and coverage vary by jurisdiction and change over time. Confirm your obligations in each location with qualified counsel.
TL;DR: Fair workweek laws penalize two types of employer-driven schedule changes: changing a shift on short notice (you owe roughly one extra hour at that worker's regular rate) and cutting a shift or sending someone home early (you owe roughly half their regular rate for every scheduled hour they did not work). As of Q2 2026, these laws apply in Oregon, Seattle, Chicago, Philadelphia, and Los Angeles County, among other jurisdictions. To avoid penalties, post schedules at least 14 days in advance, document every employee-initiated change in writing, and apply the rule at the moment you build the schedule, not afterward.
It is Tuesday afternoon and you are building next week's schedule. One store is slow midweek, so you trim a shift. A closer calls out, so you ask someone to come in on short notice. You send two people home early when the rush never shows. Normal moves. The kind you make every week to keep coverage tight and labor cost in line.
In a growing number of places, each of those moves now carries a price set by law. Not a fine you risk if you get caught. A payment you owe the moment you make the change. Most operators have never added it up.
In this post:
Fair workweek laws (also called predictive scheduling laws) require employers to post schedules in advance and pay a premium when they change them inside a protected window. As of Q2 2026, the laws in effect include Oregon's statewide Fair Workweek Act, plus city and county ordinances in Seattle, Chicago, Philadelphia, San Francisco, and Los Angeles County.
Los Angeles County's ordinance took effect July 1, 2025, covering retail employers with 300 or more global employees in unincorporated areas of the county. It is distinct from the separate City of Los Angeles ordinance, and the geographic boundary matters. Chicago's threshold for covered employees rose to $33.85 per hour (or $64,945.55 per year) effective July 1, 2026, and that figure adjusts upward each July via the Consumer Price Index. A growing number of states are weighing their own statewide versions. Oregon remains the only state with a predictive scheduling law on the books.
The common thread: employers in covered jurisdictions must post schedules at least 14 calendar days in advance. A change inside that window triggers predictability pay.
Related reading: Predictive Scheduling Laws in 2026. The broader jurisdiction map this post builds on.
Across Oregon, Seattle, Chicago, Philadelphia, and LA County, the penalty structure follows a consistent two-rule model.
Rule 1, short-notice change with no hour loss: You owe roughly one additional hour at that worker's regular rate. This applies whether you move the shift, add to it, or swap it, as long as the change happens inside the 14-day advance notice window.
Rule 2, cut or cancellation: You owe roughly half the worker's regular rate for every scheduled hour they did not work. Sending someone home when the rush never arrives is not a free adjustment.
To estimate your own exposure: take one normal week, count the short-notice changes, and assign one premium hour each. Count the early send-homes, and assign half-pay for the hours lost. Multiply by locations. Multiply by 52.
If a single store makes eight short-notice changes per week, that is eight premium hours from that store before you count a single early send-home. Across 25 locations over a year, the hours accumulate into real money that rarely shows up as its own line in a payroll report, because it was never being tracked.
The next section covers the edge cases where that count gets larger than operators expect.
Most operators understand the 14-day posting rule. The traps are the edge cases that look like normal scheduling decisions.
Trap 1: Sending someone home early is not free. Cutting the back half of a slow shift triggers half-rate pay for the hours the employee loses. The labor cost you appear to save comes back as a predictability premium.
Trap 2: "The employee asked for it" only protects you if you documented it. Employee-initiated changes are exempt from predictability pay in every jurisdiction reviewed. The burden is on the employer to document that the employee initiated the change. Chicago's June 2026 amendment put that documentation requirement explicitly in writing. Without a record, the exemption does not apply.
Trap 3: Clopening costs money even when the worker is willing. Scheduling a late close into an early open inside the minimum rest window (10 hours in most jurisdictions) requires written employee consent and still owes a clopening premium. The employee's willingness does not waive the premium. Consent is a precondition for scheduling it at all, not a substitute for the pay obligation.
Trap 4: Adding hours triggers pay too. In Oregon, Seattle, Chicago, and LA County, adding time to a shift or tacking on extra shifts on short notice owes the same one-hour premium as any other employer change inside the 14-day window.
Trap 5: "LA County" and "LA City" are not the same rulebook. The LA County ordinance, which took effect July 1, 2025, covers unincorporated areas of the county only. The City of Los Angeles has its own separate retail fair workweek rule. Employers operating across the broader metro area need to know exactly which ordinance governs each location. Assuming one set of rules covers all of "LA" means reading the wrong rulebook for half your locations.
These traps only show up after the fact if your scheduling tool does not flag them in real time. The section below explains what to look for in a system that catches these before they happen.
A scheduling system built for fair workweek compliance must apply each location's rules automatically, flag a violation as you build the schedule rather than after payroll runs, handle overlapping city, county, and state rules on the same shift, and let you set a rule's effective date once so a threshold change applies everywhere on the day it takes effect.
Compliance with fair workweek laws cannot be checked after the fact. The premium attaches the moment a schedule change is made, which means the rule must be applied during scheduling, not discovered in a payroll report three months later.
Before trusting any workforce management system with multi-jurisdiction predictive scheduling compliance, ask it four questions:
Ask those four questions in a demo and watch where each system goes quiet. Most answer the first one or two, then fall back to after-the-fact reporting for the rest. We built WorkAxle's rule engine to work at the point of scheduling. You codify your rules once, in a no-code builder: the hours caps, the minimum rest between shifts, the consecutive-day limits, the day-of-week restrictions, written the way you would write any other policy.
From there the engine checks every shift and change against those rules as the schedule is built. The moment a shift breaks a rule, it surfaces right there on the schedule, color-coded as a soft warning or a hard error, so the scheduler sees the conflict before the schedule is published, not in a payroll report three months later.
Each rule set carries its own effective date, so when a threshold moves you update the rule once and the system applies it on that day, with no vendor release cycle in between. Rules attach by location and employee group, so the right rule set follows the right site instead of someone reconfiguring it store by store.
For authoritative jurisdiction-level detail, the LA County DCBA fair workweek page and the Oregon BOLI predictive scheduling page are the primary official sources for each ordinance's current requirements.
If your operation spans more than one of these jurisdictions, the patchwork only widens from here. The question is whether your scheduling system keeps up with it automatically, or leaves you to find the bill later.
Fair workweek laws require covered employers to post employee schedules at least 14 calendar days in advance and to pay a premium when they change those schedules inside that window. The two core payment obligations are: one additional hour at the employee's regular rate for any employer-initiated change that does not reduce total hours, and half the regular rate for every scheduled hour the employee does not work due to an employer-initiated cancellation or reduction.
Predictability pay is the premium an employer owes when it changes a covered employee's schedule inside the advance notice window. For a short-notice change that does not cut hours, the calculation is roughly one extra hour at the employee's regular rate per change. For a shift cut, cancellation, or early send-home, the employer owes approximately half the employee's regular rate for each scheduled hour not worked. The method stays expressed in hours, because regular rates vary by employee and jurisdiction.
Employee-initiated changes are exempt from predictability pay in every major fair workweek jurisdiction, including Oregon, Chicago, Seattle, Philadelphia, and LA County. However, the employer bears the documentation burden. Chicago's June 2026 amendment requires that employee-initiated exemptions be documented in writing. Without a written record showing the employee requested the change, the exemption does not hold and the premium is owed.
A clopening is when an employee works a closing shift and an opening shift with less than the minimum rest period in between, typically 10 hours in most fair workweek jurisdictions. Written employee consent is required before a clopening can be scheduled at all. Consent is not a waiver of the premium: the employer still owes a clopening premium even after the employee agrees. In Chicago, that premium is 1.25 times the regular rate for the entire affected shift. In Oregon, Seattle, and LA County, it is 1.5 times the regular rate for each hour worked within the rest window.
No. Los Angeles County's Fair Workweek Ordinance, which took effect July 1, 2025, covers only unincorporated areas of the county and applies to retail employers with 300 or more global employees. The City of Los Angeles has a separate retail fair workweek ordinance that took effect April 1, 2023, and operates under its own rules, including a different clopening premium calculation. Employers operating across the greater LA metro area need to determine which ordinance governs each specific location. Assuming one rule covers all of "LA" is one of the most common compliance errors in multi-location retail.
Yes, in most major fair workweek jurisdictions. In Oregon, adding 30 or more minutes to a shift triggers one additional hour of pay at the employee's regular rate. Seattle owes the same one-hour premium when an employer directs an employee to add hours. LA County triggers the premium for any employer-initiated change exceeding 15 minutes of additional work. Chicago requires one hour of predictability pay for any schedule change within the 14-day advance notice window, including shift additions.
Compliance has to be enforced when the schedule is built, not audited afterward. WorkAxle is a workforce management platform with a no-code rule engine that checks each shift against your location-specific scheduling rules as you build it, flagging conflicts in real time. Because rules are effective-dated, a threshold change applies automatically on its effective date.
This article is for general information and is not legal advice. Penalty structures, thresholds, and coverage vary by jurisdiction and change over time. Confirm your obligations in each location with qualified counsel.
If your scheduling operation spans more than one fair workweek jurisdiction, bring your most complex scheduling scenario to a demo. We will show you how the rule engine applies each location's rules as the schedule is built, and where it flags a change before it becomes a penalty.
See your most complex scheduling scenario in our rule engine