Predictive Scheduling and Fair Workweek Laws by State

A single missed shift change in New York City — adding two hours to a fast-food worker's shift the day before, after the 14-day-advance-notice window closed — owes a $10 to $75 premium under the city's Fair Workweek Law. Repeated across a 30-store chain over a quarter, NYC's Department of Consumer and Worker Protection has settled multiple cases totaling roughly $300,000 in 2020 alone, and the enforcement-action volume has grown each year since. The compliance posture isn't "what does federal law require" — the FLSA doesn't reach scheduling — but "which of the 11 state and city jurisdictions cover this employee, what's the advance-notice window, and what does the predictability-pay schedule say when the change happens."

The Fair Labor Standards Act and its regulations govern wages, hours, and recordkeeping — not scheduling. Every predictive scheduling rule in the United States is state-level or city-level law. Oregon is the only state with a statewide statute (SB 828, effective July 1, 2018). Ten cities have their own Fair Workweek ordinances: New York City (the largest market), San Francisco (the original 2014/2015 law), Seattle, Philadelphia, Chicago (uniquely covering healthcare and manufacturing), Los Angeles City (effective 2023), Los Angeles County (effective July 1, 2025 — the most recent expansion), Berkeley and Emeryville in California, and Evanston, IL (effective January 1, 2024). This guide covers the federal baseline (such as it is), each jurisdiction's advance-notice and predictability-pay framework, the clopening rule and the right to rest between shifts, the industry coverage variations, multi-jurisdiction compliance for remote and multi-location workforces, and the 2024–2026 expansions that put more retail and grocery operators under coverage every quarter.

Quick reference

• Federal floor: No FLSA scheduling rule. Every advance-notice / predictability-pay obligation comes from state or city statute.
• States with predictive scheduling laws: Oregon only (statewide). Every other rule is at the city level.
• Cities with Fair Workweek / predictive scheduling ordinances (10, as of 2026-05-25): New York City, San Francisco, Seattle, Philadelphia, Chicago, Los Angeles City, Los Angeles County (effective July 1, 2025), Berkeley, Emeryville, Evanston (IL).
• Standard mechanic: 14 days' advance written schedule + predictability-pay premium (typically 1 hour for minor changes, up to 4 hours for major changes within 24 hours) + right to decline shifts that begin within 9–11 hours of the previous shift's end (the "clopening" rule).
• Industry coverage: retail, food service, and hospitality are universally covered. Chicago alone reaches healthcare and manufacturing — and that expansion drives most of the cluster's enforcement-action volume outside NYC.
• The litigation pattern: the per-employee, per-violation premium amounts are small ($10–$75 typically), but the volume per workforce + per workweek scales into six- and seven-figure aggregate exposure when a multi-state retailer misses the advance-notice window across stores. NYC DCWP, SF OLSE, and Chicago OLS have all run multi-employer enforcement sweeps in the past 24 months.

The 5 Most Expensive Predictive Scheduling Mistakes

Before the per-jurisdiction rules, the failure patterns that drive enforcement actions and class-action settlements. Each is structurally repeatable across the cluster.

1. Posting the schedule less than 14 days before the start of the shift. The single most-litigated violation across every Fair Workweek jurisdiction except NYC retail (which uses 72 hours instead of 14 days). The 14-day floor applies in Oregon, SF, Seattle, Philadelphia, Chicago (since July 1, 2022 — raised from 10 days), LA City, LA County, Berkeley, Emeryville, and Evanston. A scheduling system that defaults to a weekly posting cadence has a structural 7-day gap — every published schedule violates the 14-day rule for the second week. The fix is operational: post schedules at least 14 days before the FIRST shift in the schedule, not 14 days before the schedule's posting date. Use a managed two-week rolling posting window and the violation goes away.

2. Missing the clopening rule by counting hours from clock-out instead of from end-of-scheduled-shift. Most Fair Workweek jurisdictions have a right-to-rest provision — employees may decline shifts that begin within 9 to 11 hours of the previous shift's end (Oregon 10h, Seattle 10h, Chicago 10h, LA City 10h, LA County 10h, Berkeley 11h, Emeryville 11h, Philadelphia 9h, Evanston 11h, NYC fast food 11h; San Francisco has no statutory clopening minimum). If the employee works past the scheduled end-of-shift (closing a register, finishing a customer, cleaning), the 9–11 hour rest window starts when the SHIFT ends, not when the employee finally clocks out. Scheduling a closing-to-opening "clopening" pair that's compliant on paper turns into a violation the moment closing runs long. Premium pay typically equals 1.5× the regular rate for the hours worked within the rest window if the employee consents to the clopening.

3. Treating predictability pay as employer-discretionary instead of statutory premium owed. Every Fair Workweek jurisdiction defines the predictability-pay schedule precisely — typically 1 hour at the regular rate for changes within 14 days but more than 24 hours before the shift; 4 hours (or shift length, whichever is shorter) for changes within 24 hours. Employers that compensate "as a courtesy" with a flat dollar amount, or that treat predictability pay as negotiable with the affected employee, owe the statutory premium for every change in the look-back period. Worked example: a 5-store retailer averaging 3 schedule changes per week per store across 50 affected employees, with a $20/hour average wage, owes 1 hour × 3 changes × 50 employees × 52 weeks × 5 stores × $20 = $780,000 per year in predictability pay if it skipped the obligation entirely. That's the upper bound; the lower bound (changes with full 14-day notice that don't trigger the premium) is zero. Most employers are somewhere in between, with multi-quarter back-pay exposure when an audit lands.

4. Missing the good-faith-estimate-at-hire requirement. Oregon, Seattle, Philadelphia, Chicago, NYC, LA City, Berkeley, and Evanston all require employers to provide a written good-faith estimate of expected hours / shifts at the time of hire (and on annual update in some jurisdictions). The estimate isn't a contract — actual hours can vary — but failure to provide it is a discrete per-employee violation independent of any actual scheduling problem. Penalty schedules vary: Philadelphia imposes administrative fines; LA City imposes $50 per day per employee for unlawful withholding of predictability pay (a related but separate penalty); NYC DCWP can assess civil penalties per violation. The aggregate exposure on missed good-faith estimates alone, for a multi-state retailer with hundreds of new hires per year, is consistently six-figure when surfaced in an enforcement sweep.

5. Applying HQ-state scheduling defaults to remote or multi-jurisdiction employees. A Texas-headquartered retailer with stores in NYC, LA City, and Chicago that runs a national scheduling system on a 7-day-advance-notice template violates all three jurisdictions' rules. The 14-day-advance-notice + clopening + predictability-pay framework applies per employee work location, not per employer HQ. A multi-state operator's compliance design has three workable shapes: (a) per-jurisdiction policy modules in the scheduling system; (b) "strictest-everywhere" — adopt the 14-day + 11-hour-clopening + Chicago-industry-coverage framework across the entire workforce, even where state law doesn't require it; or (c) audit by work-location quarterly and apply per-jurisdiction adjustments. Shape (b) eliminates per-jurisdiction policy complexity at the cost of slightly higher labor expense (more predictability pay than legally required in lower-coverage states). For multi-state retailers, the strict-everywhere posture is consistently the lowest-total-cost compliance design.

   Salaried non-exempt employees deserve their own consideration in this analysis. Fair Workweek frameworks generally cover hourly employees, but some jurisdictions extend coverage to salaried non-exempt workers — particularly in Chicago (Chapter 6-110 covers all non-exempt employees in the 7 covered industries) and NYC fast food (just-cause termination and clopening apply to all fast food employees regardless of pay structure). See our salaried non-exempt employees guide for the §778.113 fixed-workweek vs §778.114 fluctuating-workweek frameworks; predictability pay flows into the regular rate computation under either method.

Federal baseline: FLSA doesn't reach scheduling

The Fair Labor Standards Act (29 USC §§201 et seq.) and its implementing regulations (29 CFR Parts 516, 778, 785) govern minimum wage, overtime, regular-rate computation, and recordkeeping. They do not govern advance scheduling notice, predictability pay for last-minute changes, or rest periods between shifts. The Department of Labor's Wage and Hour Division has been explicit on this:

"The FLSA does not require payment for time not worked, such as vacations, sick leave or federal or other holidays. ... [Other] benefits are generally a matter of agreement between an employer and an employee (or the employee's representative)."

DOL WHD Compliance Assistance — Pay

The implication: every predictive scheduling rule in the United States is state-level or city-level law. There is no federal floor that constrains an employer's scheduling discretion (separate from the existing federal wage and overtime requirements). State and city statutes fill the gap entirely.

The federal-baseline implication for multi-state operators: there is no preemption argument available to defend non-compliance with state or city Fair Workweek rules. FLSA's silence on scheduling means the supremacy clause doesn't reach the question. Each jurisdiction's law applies to employees who work in that jurisdiction, regardless of where the employer is headquartered.

How predictability pay interacts with the federal regular rate

Predictability pay is non-discretionary compensation paid pursuant to a statutory requirement. Under 29 CFR §778.208, non-discretionary compensation must be included in the regular rate of pay for overtime calculations under FLSA §7. The practical effect: a covered employee who works overtime in a workweek that also includes predictability-pay premiums has their overtime regular rate recomputed to include those premiums — increasing the half-time owed on every overtime hour that week. See our overtime rules by state guide for the regular-rate framework, and our how to calculate retro pay guide for the §778.209 apportionment math when the predictability-pay component is computed late and surfaces as a retro adjustment.

Oregon — the only statewide statute

Oregon Senate Bill 828, effective July 1, 2018, made Oregon the only state with a comprehensive statewide predictive scheduling law. The statute is codified at ORS 653.412 to 653.485; the regulations and enforcement framework live with the Oregon Bureau of Labor and Industries (BOLI).

Coverage — ORS 653.412 + 653.428

ORS 653.412 defines the covered employer:

"(8) 'Large employer' means an employer that employs 500 or more employees worldwide."

The 500-employee floor combined with the industry list (retail trade, hotels, motels, food services) means most Oregon retail and hospitality chains are covered; small independent businesses generally are not. The 500-employee count is global, not Oregon-specific — a national chain with 200 employees in Oregon but 5,000 globally is covered; a regional chain with 400 employees all in Oregon is not. ORS 653.428 defines the covered industries:

"'Employer' means a person that employs 500 or more employees worldwide and provides services relating to retail trade, hotels and motels, or food services as those terms are described in the most recent edition of the North American Industry Classification System ..."

Advance notice — ORS 653.436

Effective July 1, 2018, employers had to give a written work schedule at least 7 calendar days before the first shift on the schedule. Effective July 1, 2020, that window expanded to 14 calendar days. The written schedule must include all on-call shifts; "voluntary" on-call shifts that are not in the written schedule are not enforceable.

Predictability pay — ORS 653.450

Once the schedule is posted, employer-initiated changes that adjust the date / start time / end time of a shift, add more than 30 minutes of work, or add a new shift trigger predictability pay:

• One additional hour at the regular rate of pay for each instance where the employer adds more than 30 minutes to a shift, changes the start or end time without loss of hours, or schedules an additional on-call or standard shift.
• One-half the employee's regular rate for each scheduled hour that the employee does not work when the employer subtracts hours or cancels a shift, OR for each shift the employee was on call but not called in.

Right to rest — ORS 653.442

ORS 653.442 gives employees the right to decline clopening shifts:

"An employee may decline any work shifts not included in the employee's written work schedule. ... An employer may not schedule or require an employee to work during ... the first 10 hours following the end of the previous calendar day's work shift or on-call shift."

If the employee consents in writing to a clopening shift, the employer must pay 1.5× the regular rate for the hours worked within the 10-hour rest period — the highest clopening premium in the statewide-applicable category.

Right to additional hours — ORS 653.428

Before hiring new employees, covered employers must offer available hours to existing employees. The offer must be in writing, and the employee has at least 7 days to respond.

Things Oregon employers consistently miss

• The "500 employees worldwide" threshold is global, not Oregon-specific. A national retail chain with 200 employees in Oregon but 5,000 globally is covered; a regional chain with 400 employees all in Oregon is not.
• On-call shifts must be in the written schedule. Employers that maintain a separate "on-call list" outside the posted schedule treat those shifts as voluntary — but the statute requires them to be scheduled in writing 14 days in advance. Surprise on-call assignments owe predictability pay.
• The 10-hour rest window starts at the end of the SCHEDULED shift, not at clock-out. A closing employee who finishes at 11:30 PM scheduled end-of-shift but doesn't clock out until 12:15 AM starts the rest window at 11:30 PM — not 12:15 AM. Opening shift the next day can begin at 9:30 AM without triggering the clopening rule; an 8:00 AM opening would.

New York City — the largest jurisdiction (Admin Code §§ 20-1201 et seq.)

NYC's Fair Workweek Law (NYC Administrative Code, Title 20, Subchapter 22) is the most-litigated predictive scheduling framework in the United States. Effective November 26, 2017, with subsequent expansions through 2021, the law operates with two distinct frameworks — one for fast food, one for retail — and adds a unique just-cause termination layer for fast food workers that no other Fair Workweek jurisdiction has.

Coverage — fast food and retail tracked separately

• Fast food employees: any employee at a fast food establishment that is part of a chain with 30 or more locations nationally. "Fast food establishment" is defined by the law (counter service, limited preparation, primarily food and beverage). The 30-location threshold is national, not NYC-specific.
• Retail employees: retail establishments with 20 or more employees in NYC (employed by the same employer regardless of the employer's total location count).

Advance notice — fast food (14 days) and retail (72 hours)

Fast food employers must provide a 14-day advance written schedule. The DCWP's official Fair Workweek FAQ for fast food employers states the rule directly:

"Fast food employers must give workers their work schedules at least 14 days in advance. The work schedule must include all regular shifts, on-call shifts, and the start and end times of each shift."

DCWP Fair Workweek FAQs (Fast Food)

Retail employers must provide a 72-hour advance schedule. The retail framework's 72-hour rule operates differently from the predictability-pay model used everywhere else in the cluster: retail employers may NOT cancel, shorten, or postpone a scheduled shift, OR require an employee to work outside posted hours, with less than 72 hours' notice — period. The rule is a prohibition, not a compensation requirement. Premium pay applies to the narrow set of voluntary post-notice agreements; structurally, the rule eliminates last-minute changes rather than pricing them.

Predictability pay (fast food) — Admin Code §20-1222

For fast food employees, schedule changes after the 14-day advance posting trigger premium pay:

The premium-pay schedule is per-change, per-employee. A 3-store fast food chain that runs the entire schedule on a 7-day-in-advance basis owes the $15 / $45 / $75 premium on every shift change for every covered employee — quickly scaling into five- and six-figure aggregate exposure per quarter.

Clopening — Admin Code §20-1231

Fast food employees may not be required to work back-to-back shifts separated by fewer than 11 hours. The "clopening" prohibition is one of the strictest in the cluster (Oregon and the standard model use 9–10 hours). If the employee consents in writing, the employer pays a $100 clopening premium per shift.

Just-cause termination — Admin Code §20-1271 (fast food only)

NYC's Fair Workweek Law uniquely imposes a just-cause termination requirement for fast food employees, effective July 4, 2021. Employer must have a legitimate business reason to terminate; progressive discipline applies; the employee can challenge a termination through DCWP arbitration. Other predictive scheduling jurisdictions do not have this layer — NYC stands alone.

Right to additional hours — Admin Code §20-1241

Before hiring new fast food employees, the employer must offer available shifts to existing fast food employees at the same location for at least 3 days. Retail employers have analogous obligations under §20-1251.

Enforcement — NYC DCWP

The NYC Department of Consumer and Worker Protection (DCWP) has been the most active Fair Workweek enforcement agency in the country. The June 2020 DCWP announcement covered settlements totaling nearly $300,000 across multiple fast food employers for advance-notice and predictability-pay violations.

State-and-city-by-state framework table

The table covers all 11 jurisdictions (1 statewide + 10 city-level) with the advance-notice window, predictability-pay schedule, clopening rule, and headcount threshold. The table is the cross-jurisdiction reference for a multi-state operator's compliance design.

How to read the predictability-pay column

The "1 hr / 0.5 hr" notation means: 1 hour of additional pay at the regular rate for additions or shift-time changes that don't reduce hours; 0.5× the regular rate for hours the employee was scheduled but doesn't work (cancellations or reductions). "1 hr / 4 hr" means: 1 hour for changes with 24-hour to 14-day notice; 4 hours (or shift length, whichever is less) for changes within 24 hours. NYC fast food uses a fixed-dollar schedule ($10 / $15 / $45 / $75) instead of regular-rate multiples — the only jurisdiction that does.

Industry-specific frameworks

The standard coverage list across the cluster is retail + food service + hospitality. Chicago expands to healthcare and manufacturing. NYC's framework separates fast food from retail. The industry-coverage variations matter because a single employer operating multiple businesses may have different obligations per business line.

Retail — the universal-coverage industry

Every Fair Workweek jurisdiction covers retail. The definition varies: SF uses the "Formula Retail" framework (chain-store-coverage based on 40+ locations worldwide); LA City and LA County use NAICS codes 44-45 (which include grocery, general merchandise, department stores); Oregon and Seattle use a broader "retail trade" definition that incorporates Bureau of Labor Statistics retail-industry codes. The 2025 expansion to LA County via NAICS 44–45 explicitly captured grocery and general merchandise that prior city-level frameworks (Berkeley, Emeryville, SF) had excluded — that's the structural reason why LA County is the largest single-jurisdiction expansion of the past 24 months.

Food service — fast food vs full-service split

NYC's framework treats fast food as a separate category with its own thresholds, advance-notice window (14 days), and predictability-pay schedule ($10–$75 per change). Other jurisdictions use a broader "food services" definition that includes fast food, full-service restaurants, and limited-service restaurants — Seattle requires 500+ employees AND 40+ full-service locations worldwide; Philadelphia uses 250+ employees AND 30+ locations; Chicago has separate thresholds for restaurants (250+ employees AND 30+ locations).

Hospitality — hotels and motels

Oregon, NYC, Philadelphia, Chicago, and Berkeley all cover hotels and motels. Seattle does not. The coverage threshold is typically the same as the retail or food-service threshold for the jurisdiction — there's no separate hospitality framework.

Chicago's healthcare and manufacturing expansion

Chicago is uniquely among the cluster the only jurisdiction that reaches healthcare and manufacturing. Hospitals, residential care facilities, manufacturing plants, and warehousing operations in Chicago with 100+ global employees are covered by Chapter 6-110. The expansion came from Chicago's 2019 Fair Workweek Ordinance design choice — every other jurisdiction's coverage list mirrors the original SF/NYC retail-hospitality-food framework.

Industries explicitly NOT covered

Across all 11 jurisdictions, the following industries are generally outside Fair Workweek scope:

• Professional services (law firms, consulting, finance, technology).
• Construction (per-project scheduling structurally differs; covered by separate federal frameworks like Davis-Bacon for federal contracts).
• Trucking and CMV operations (FMCSA hours-of-service rules govern).
• Public-sector employees (federal employees, state/municipal workers — covered by CBA-driven scheduling).
• Independent contractors (not employees under FLSA-equivalent definitions; classification challenges trigger separate liability under our overtime rules by state guide).

Multi-state and multi-jurisdiction compliance

Fair Workweek law follows the employee's work location, not the employer's HQ. Same pattern as overtime, breaks, and off-the-clock — see our final paycheck laws by state guide for the same work-location principle applied to wage timing.

Concrete scenarios:

• Texas-headquartered retailer with stores in NYC, LA City, and Chicago. Three different advance-notice frameworks apply per store. NYC retail (72 hours), LA City retail (14 days), Chicago restaurants/retail (14 days with healthcare/manufacturing extension if relevant). The Texas HQ's 7-day default doesn't reach those stores.
• California-based retailer with stores in SF, Berkeley, Emeryville, LA City, and LA County (unincorporated areas). Five distinct frameworks all apply. SF and Berkeley have different headcount thresholds; LA City and LA County have different coverage definitions (LA County reaches grocery via NAICS, LA City does not).
• Remote employee in a covered city working for a non-covered employer. An employer below the headcount threshold in NYC is not covered; an employer above the threshold in NYC is covered for every employee who works in NYC, regardless of where the employer is headquartered. Coverage attaches to the employer's qualifying status, not the employee's individual situation.

The strict-everywhere defense: adopt the 14-day-advance-notice + 11-hour-clopening + predictability-pay-as-statutory framework across the entire workforce. A multi-state operator that runs the strictest applicable rule across all locations eliminates per-jurisdiction policy complexity, simplifies training for store managers, and minimizes the audit-driven exposure when a state or city expands its coverage (as LA County did in July 2025). Marginal labor cost: the predictability-pay premium paid in locations where the law doesn't require it. Avoided cost: the per-jurisdiction enforcement-action exposure that scales with workforce headcount.

Recordkeeping — what every jurisdiction requires

Every Fair Workweek jurisdiction requires the employer to maintain records of:

• The posted work schedule (with date posted documented).
• Every schedule change after posting (with date of change and reason).
• The good-faith estimate provided at hire (and the employee's signed acknowledgment).
• Employee consent to clopening shifts (where applicable).
• Predictability-pay payments made (with the underlying change documented).

Retention windows vary by jurisdiction — typically 3 years in line with 29 CFR §516.5 federal payroll-records retention. LA County requires 3 years specifically; Seattle requires 3 years; NYC requires 3 years; Chicago requires 3 years. California's underlying recordkeeping retention extends to 4 years for the Unfair Competition Law lookback window, which affects Berkeley, Emeryville, SF, LA City, and LA County simultaneously.

When records are inadequate, the same Anderson v. Mt. Clemens Pottery Co., 328 U.S. 680 (1946), burden-shifting rule that applies to FLSA back-wage claims applies to Fair Workweek enforcement: the employee establishes the schedule changes and missed predictability pay as "a matter of just and reasonable inference," and the employer carries the evidentiary burden of disproving the estimate. See our recordkeeping requirements by state guide for the §516 retention framework and the state extensions.

The defensive posture: capture the posted schedule + every change + the timestamp of every change as a byproduct of running the scheduling system. Modern scheduling software generates this record natively; the question is whether the retention setting matches the 3-year statutory floor. Scheduling systems that authenticate the actual clock-in are doubly load-bearing — the schedule-vs-actual-time delta documents whether the employee worked outside the posted schedule, and accurate clock-in identification prevents the buddy-punching exposure that creates derivative wage-statement violations independent of Fair Workweek. See our buddy punching guide for the clock-in fraud detection patterns and the asymmetric §226 exposure that attaches even to OVERPAID hours.

Where predictive scheduling connects to the rest of the wage-and-hour stack

Predictive scheduling isn't a standalone topic. The underlying compensable-time, regular-rate, and recordkeeping mechanics live in adjacent areas of wage-and-hour law that this article cross-links to throughout. Five connection points matter:

Meal-and-rest breaks — the underlying premium-pay framework

In California cities (SF, Berkeley, Emeryville, LA City, LA County), missed-meal-period premium pay under Labor Code §226.7 stacks on top of Fair Workweek predictability pay. A schedule change that also causes a missed meal period creates two separate premium-pay obligations. See our meal and rest break laws by state guide for the §226.7 mechanic and the Naranjo cascade.

Off-the-clock work — pre-shift and post-shift compensable time

Fair Workweek frameworks define the "scheduled shift" boundaries — but compensable time under FLSA reaches every minute the employee is "suffered or permitted to work" plus the 29 CFR Part 785 integral-and-indispensable activities. Pre-shift system logins, dispatch, and post-shift closing tasks can start the continuous workday before the scheduled shift begins. See our off-the-clock work by state guide for the federal "knew or should have known" standard and California's broader "subject to control" test.

Overtime regular rate — predictability pay flows into the OT computation

Predictability pay is non-discretionary compensation under 29 CFR §778.208. For employees who work overtime in a workweek that includes predictability-pay premiums, the regular rate gets recomputed to include those premiums. See our overtime rules by state guide for the regular-rate framework, and our how to calculate retro pay guide for the §778.209(b) apportionment math when predictability-pay corrections are made retroactively. Note that under the no tax on overtime framework, the half-time portion of overtime calculated on a regular rate that includes predictability pay still qualifies for the OBBB §225 deduction when correctly identified on the W-2 — the predictability-pay component itself is not separately deductible, but the FLSA-required overtime premium computed on top of it is.

Final paycheck — unpaid predictability pay at separation

When an employee separates with unpaid predictability-pay premiums from the look-back period, those premiums are "wages" subject to the state final-pay timing rules. California §203's waiting-time penalty cascade attaches; Massachusetts §150's strict-liability treble damages attach (Boston is not a Fair Workweek jurisdiction, but Massachusetts employers with employees who work in covered jurisdictions have the dual exposure). See our final paycheck laws by state guide for the state-by-state timing rules and the Reuter v. City of Methuen strict-liability framework.

Recordkeeping — the 3-year retention framework

Fair Workweek's 3-year retention requirement aligns with 29 CFR §516.5 federal payroll-records retention. State extensions (NY and Hawaii at 6 years) and California's 4-year Unfair Competition Law lookback extend coverage further. See our recordkeeping requirements by state guide for the per-state retention windows and the Mt. Clemens burden-shifting rule that turns recordkeeping failures into damages multipliers.

Recent changes (2024–2026)

Four expansions between 2024 and 2026 have meaningfully reshaped the Fair Workweek landscape — LA County's July 2025 effective date, Berkeley's January 2024 effective date, Evanston's January 2024 effective date (after a deferred September 2023 start), and Chicago's July 2022 expansion from 10-day to 14-day advance notice.

2025

• Los Angeles County Fair Workweek Ordinance (effective July 1, 2025). The most recent and largest single-jurisdiction expansion. Covers retail businesses under NAICS codes 44–45 (grocery, general merchandise, department stores) with 300+ employees worldwide operating in unincorporated LA County. 14-day advance notice; 1 hour for additions / 0.5× for cancellations; 10-hour rest between shifts with consented-shift 1.5× premium pay. LA County DCBA Fair Workweek page. The expansion explicitly captures grocery (not covered by LA City's prior 2023 ordinance, which applies only to retail under a narrower definition).

2024

• Berkeley, CA Fair Workweek Ordinance (effective January 12, 2024). Berkeley Municipal Code Chapter 13.102 mirrors Emeryville's framework: 14-day advance notice; 1 hour for changes with 24-hour to 14-day notice, 4 hours for changes within 24 hours; 11-hour clopening rule. Coverage threshold: 10+ employees in Berkeley AND 56+ globally (franchise networks: 100+ globally). Industries: building services, healthcare, hotel, manufacturing, retail, warehouse services — mirrors Chicago's broader scope.
• Evanston, IL Fair Workweek Ordinance (effective January 1, 2024). Originally scheduled for September 1, 2023; effective date delayed by a city-granted grace period to allow employer compliance preparation. Evanston Municipal Code Chapter 3-34. 100+ employees globally; 14-day advance notice; 1 hour for changes 24-hour to 14-day notice, 4 hours for less than 24 hours; 11-hour clopening.

2022

• Chicago Fair Workweek Ordinance amendment — 14-day advance notice (effective July 1, 2022). The initial 2020 ordinance required 10 days' advance notice; the 2022 amendment raised it to 14 days, matching Oregon's 2020 amendment and bringing Chicago into alignment with the cluster's modern standard.

If you discover you've been doing this wrong

Fair Workweek audits routinely uncover accumulated exposure: missed 14-day-advance-posting windows, unpaid predictability pay across multiple workweeks, missed good-faith estimates at hire, clopening pairs scheduled without consent or premium pay. The unwinding playbook:

1. Identify which jurisdictions cover which employees. For each location and each employee, determine which Fair Workweek framework applies based on the employee's work location and the employer's headcount / industry profile. A single multi-state retailer can have 4–6 different rules running simultaneously across stores.

2. Audit the schedule-posting cadence. Pull the posted schedules and the actual shift records for the full statute-of-limitations look-back window (typically 3 years per the recordkeeping framework; California's UCL extends to 4 years). For each workweek, compare the post date against the start date of the first shift — if less than 14 days (or the applicable jurisdiction's advance-notice window), every shift in that schedule is potentially subject to predictability pay for any subsequent change.

3. Compute the predictability-pay exposure. For each schedule change in the look-back window, apply the jurisdiction's specific schedule (1 hour for minor changes, 4 hours for major within 24 hours, NYC's fixed-dollar fast food schedule, etc.). Sum across changes, employees, and weeks. The aggregate is the back-pay exposure floor.

4. Pay back voluntarily with documentation. Voluntary payment before any complaint or enforcement action is the cleanest defensive posture. Document the audit methodology, the look-back window, the payment schedule, and the corrective process improvement. The voluntary-payment posture supports the good-faith defense to escalating penalties in most jurisdictions, and short-circuits the per-day penalty accrual in jurisdictions like LA City ($50/day per employee for unlawful predictability-pay withholding).

5. Fix the scheduling system. Most Fair Workweek violations trace to one of three root causes: (a) a scheduling tool that defaults to a 7- or 10-day posting cadence and doesn't enforce the 14-day floor; (b) a schedule-change workflow that doesn't capture the timestamp + reason for each change (creating the predictability-pay audit gap); or (c) a multi-state policy that applies the HQ-jurisdiction's rules to every store. Fixing the system removes the recurrence; the back-pay payment closes the historical window.

6. Bring in employment counsel before exposure crosses ~$50,000 per workforce or any individual employee crosses ~$10,000 in unpaid premiums. The strict-liability frameworks in NYC (which assesses civil penalties on top of restitution) and the per-day penalty schedules in LA City and LA County mean the exposure ceiling rises quickly when the violation pattern is systematic.

The through-line

Predictive scheduling exposure clusters around three structural failure modes: scheduling systems that default to a 7- or 10-day posting cadence and structurally violate the 14-day advance-notice rule; schedule-change workflows that don't capture the timestamp and trigger the predictability-pay obligation; and HQ-state-default policies that apply Texas (or Florida, or another non-covered-state) scheduling rules to employees who work in NYC, SF, Chicago, or any other covered jurisdiction. Under the per-employee, per-change, per-workweek accrual model that every Fair Workweek statute uses, small per-shift premiums ($10 to $75 in NYC, 1 hour at regular rate in Oregon and Chicago, up to 4 hours in California cities) compound across workforces and lookback windows into seven-figure aggregate exposure when a multi-state retailer or chain restaurant gets audited.

The highest-leverage fix is to standardize to the strictest applicable rule any covered jurisdiction requires. A 14-day advance-posting policy + 11-hour clopening rule + predictability-pay-as-statutory framework + good-faith-estimate-at-hire documentation, applied across the entire multi-state workforce, eliminates per-jurisdiction policy complexity and removes the structural violation patterns at the source. The marginal labor cost — predictability pay in locations where the law doesn't require it — is small compared to the avoided cost of the per-jurisdiction enforcement-action exposure that scales with workforce headcount.

Sources

Federal context

• FLSA — 29 USC §§ 201 et seq. (no federal scheduling rule; FLSA governs wages, hours, and recordkeeping only)
• 29 CFR Part 516 — Recordkeeping (federal payroll-records retention; state predictive scheduling laws layer on top)
• 29 CFR §778.208 — Inclusion of bonuses in the regular rate (predictability pay flows into OT computation)
• DOL WHD Handy Reference Guide — FLSA (no federal scheduling-rule confirmation)

Statewide (Oregon)

• ORS 653.412 — Definitions
• Oregon BOLI — Predictive Scheduling

New York City

• NYC Admin Code §§ 20-1201 et seq. — Fair Workweek Law
• NYC DCWP Fair Workweek FAQs (Fast Food)
• NYC DCWP Fair Workweek FAQs (Retail)
• NYC DCWP — Fast Food Settlements ($300K, multiple employers, 2020)

California cities

• San Francisco Police Code Articles 33F + 33G — Formula Retail Employee Rights
• SF Office of Labor Standards Enforcement — Formula Retail
• Los Angeles City Fair Work Week Ordinance (LAMC Chapter 9.5)
• Los Angeles County Fair Workweek Ordinance (LA County Code Chapter 8.105)
• Berkeley Municipal Code Chapter 13.102 — Fair Workweek Employment Standards
• Berkeley Workforce Standards and Enforcement
• Emeryville Municipal Code Chapter 5-39 — Fair Workweek Employment Standards
• Emeryville Fair Workweek Ordinance — City page

Other cities

• Seattle Municipal Code Chapter 14.22 — Secure Scheduling
• Philadelphia Code Chapter 9-4600 — Fair Workweek Employment Standards
• Philadelphia Department of Labor — Fair Workweek
• Chicago Municipal Code Chapter 6-110 — Fair Workweek Ordinance
• Chicago Office of Labor Standards — Fair Workweek
• Evanston Municipal Code Chapter 3-34 — Fair Work Week Ordinance
• City of Evanston — Fair Workweek page

Federal cases (cross-cluster)

• Anderson v. Mt. Clemens Pottery Co., 328 U.S. 680 (1946) — burden-shifting when employer records are inadequate (applies to Fair Workweek recordkeeping)