A district manager swaps a barista's Saturday closing shift for a Tuesday morning opening shift three days before the schedule takes effect. In most of the country, that's just Tuesday. In eleven U.S. jurisdictions, it's a payroll liability that has to hit the books before the next paycheck runs — and if it doesn't, the fine can run into the millions. Starbucks found that out the hard way in New York City, where it settled predictive scheduling violations for $38.9 million. Chipotle paid $20 million for scheduling practices that affected roughly 13,000 NYC workers. These aren't abstract compliance risks; they're recurring payroll line items that a growing number of retail, food service, and hospitality employers now have to plan for the same way they plan for overtime.
What "Predictive Scheduling" Actually Means
Predictive scheduling laws — also called fair workweek laws — require covered employers to give hourly employees their work schedules a set number of days in advance, and to pay a premium ("predictability pay") when they change that schedule after it's posted. The logic is straightforward: unpredictable, last-minute shift changes make it nearly impossible for hourly workers to arrange childcare, hold a second job, or budget a paycheck. The laws convert that instability into a cost the employer has to absorb, which is meant to push employers toward more stable scheduling in the first place.
As of mid-2026, eleven jurisdictions enforce some version of this framework: Oregon (the only statewide law), San Francisco, Emeryville, Berkeley, and Los Angeles City and County in California, Seattle, Chicago, Evanston, Philadelphia, and New York City. Coverage thresholds vary a lot — Oregon and Seattle only apply to employers with 500 or more employees, while Berkeley's ordinance kicks in at just 10. If you operate retail, food service, or hospitality locations across several of these cities, you're very likely running several different rulebooks at once, not one.
The Core Requirements Employers Have to Track
Every one of these ordinances is built around a handful of recurring obligations, even though the exact numbers shift from city to city.
A good-faith estimate at hire. Before or shortly after a new hourly employee starts, most laws require a written estimate of their expected weekly hours over a typical 90-day period, whether on-call shifts are part of the job, and the general days and times they can expect to work. This becomes the baseline the rest of the law measures against.
Advance notice of the schedule. Nearly every jurisdiction requires the posted schedule to go out 14 calendar days before the workweek starts. New York City's retail ordinance is the outlier at 72 hours. Miss the deadline and any change you make afterward — even a minor one — can trigger predictability pay.
Predictability pay for changes. This is where the real payroll exposure lives. Typical rates run one hour of pay at the employee's regular rate for adding time or changing a shift, and half the regular rate for cutting hours or canceling a shift outright. Several cities — Berkeley, Emeryville, and Evanston among them — escalate to up to four hours of pay for cancellations inside 24 hours. Philadelphia and New York City's fast-food ordinance add a specific "clopening" premium (an employee closing one night and opening again too soon after) of $40 to $100 on top of the standard change pay.
Right to rest between shifts. Minimum rest periods between the end of one shift and the start of the next range from 9 hours (Philadelphia) to 11 hours (New York City, Berkeley, Emeryville, Evanston). If an employee agrees to work a shift that falls inside that window anyway, most ordinances require time-and-a-half for those hours.
Right to decline, and a voluntary standby list. Employees generally can't be penalized for turning down additional or last-minute hours. Employers can maintain a voluntary standby list for people willing to pick up unplanned shifts, but the list has to be opt-in, employees have to be told in writing how to join and leave it, and — critically — hours accepted off the standby list don't generate predictability pay the way an involuntary schedule change does. A standby list, run correctly, is one of the few tools that gives multi-location employers real flexibility inside these laws.
Recordkeeping. Most ordinances require employers to retain original posted schedules, every subsequent change with a timestamp, employee consent records for standby-list or short-rest shifts, and the predictability pay calculations tied to each change — typically for three years. Regulators in these cities lean on payroll and scheduling records first when a complaint comes in, so gaps in that record are what turn a disputed shift change into a documented violation.
What It Costs to Get Wrong
Penalties compound fast because they're assessed per employee, per violation, not per incident. San Francisco and Los Angeles City both allow penalties up to $500 per employee per violation. New York City escalates on repeat offenses — $500 for a first violation, $750 for a second, $1,000 for anything after that within a two-year window. Berkeley and Emeryville combine a flat $1,000-per-employee penalty with an additional $500 per violation. Run one uncorrected scheduling practice across a 40-person location for a full quarter and the math turns into a five- or six-figure exposure before a regulator even has to argue intent.
The Preemption Map Cuts the Other Way
Eleven states have gone the opposite direction and passed laws that bar their cities and counties from enacting predictive scheduling ordinances at all: Alabama, Arkansas, Florida, Georgia, Indiana, Iowa, Kansas, Michigan, Ohio, Tennessee, and Wisconsin. If every one of your locations sits inside a preemption state, none of this applies to you yet. But the map isn't static — nine more states (Connecticut, Hawaii, Illinois, Massachusetts, Minnesota, New Jersey, North Carolina, Rhode Island, and West Virginia) currently have fair workweek legislation under active consideration, and the jurisdiction count has grown every year since San Francisco passed the first ordinance in 2015. Berkeley, Evanston, and Los Angeles County all added coverage within the last two years alone. A footprint that's compliant-by-default today is a reasonable bet to need a compliance program within a few years.
A Practical Compliance Approach for Multi-Location Employers
Start by mapping every location against the current jurisdiction list, not against what you remember from the last time you checked — the list keeps growing, and a new store opening in a covered city resets your obligations for that location on day one. From there, three things matter most in practice: posting schedules on a fixed 14-day (or 72-hour, where applicable) cadence rather than whenever a manager gets to it, building predictability pay into your scheduling software or POS labor module so a change automatically flags the premium owed instead of relying on a manager to remember, and treating the standby list as the primary release valve for legitimate last-minute needs — call-outs, weather, sudden rushes — since hours filled through it don't trigger the change penalty the way an imposed reschedule does.
The recordkeeping requirement is really an accounting requirement wearing an HR label. Three years of posted schedules, every change, every consent form, and every predictability-pay calculation is a lot of documentation to reconstruct after the fact, but trivial to maintain if your payroll categories separate predictability pay from regular wages and overtime from the start. Coding it as a distinct line item — rather than folding it into "miscellaneous payroll adjustments" — does two things: it makes your labor cost per location honest (a store racking up frequent predictability pay is telling you something about how it's being scheduled), and it hands your bookkeeper or accountant a clean audit trail if a regulator or a former employee ever asks for one.
Keep the Paper Trail as Clean as the Schedule
Fair workweek compliance ultimately comes down to two things: scheduling discipline and record integrity, and the second one is a bookkeeping problem as much as an HR one. Beancount.io's plain-text accounting makes it straightforward to break out predictability pay, clopening premiums, and standby-list hours as their own tracked categories — version-controlled, auditable, and exportable the moment a labor department or your own finance team wants to see the numbers behind a location's scheduling practices. Get started for free and keep the compliance paper trail as organized as the rest of your books.