Predictive Scheduling Laws by State

The first time I heard the term predictive scheduling, I assumed it was software that forecasts staffing needs. It is not. It is a body of labor law, called Fair Workweek law in most of the cities that have it, and in the places where it applies, routine moves like trimming a slow shift become payments you owe by law.

These laws change what an employer is allowed to do when building and changing schedules. For most small businesses they do not yet apply, but the trend is expanding, the penalties are steep, and knowing where you stand is worth the few minutes it takes.

This guide covers what these laws require and which states and cities have them. Most content on this topic is written for large multi-location enterprises, so this guide keeps the small and growing business in view: the thresholds that decide coverage, the steps to take as you approach the size where they might apply, and an honest answer to the question every owner asks first, whether this applies to them at all.

Fair Workweek laws reward employers who post schedules early and document changes cleanly. I built FirstHR to hold that paperwork (employee records, the written scheduling policy, and signed acknowledgments), while the schedule stays in your scheduling tool. This article is general information, not legal advice, and because these laws change frequently, confirm current specifics with your state or city labor agency or counsel.

What Is Predictive Scheduling?

Predictive scheduling refers to labor laws, commonly known as Fair Workweek laws, that require covered employers to provide employees with advance notice of their work schedules and to compensate them when schedules change on short notice. The purpose is to give hourly workers, primarily in retail, hospitality, and food service, more stable and predictable schedules so they can plan their lives, arrange childcare, and rely on their expected income.

These laws emerged to address just-in-time scheduling, the practice of assigning or changing hourly workers' shifts with little or no notice based on real-time demand. They put some of the burden back on the employer by attaching notice requirements and costs to last-minute changes. San Francisco passed the first such law in 2014, and the approach has spread to a growing set of cities and one state since.

Keep the legal concept separate from scheduling software. Some workforce tools market forecasting or AI features under the label predictive scheduling, meaning the software predicts staffing needs. That is a different thing entirely from the Fair Workweek laws this guide covers, which are legal obligations, not product features. In a compliance context, predictive scheduling means the laws, and that is the subject here.

Just-in-Time Scheduling and Why It Drew Laws

Just-in-time scheduling is the practice of setting and changing hourly shifts at short notice against real-time demand: sales data, the weather, foot traffic, a slow Tuesday. It is also called on-demand scheduling, and across retail and food service it was simply how staffing worked before any of these laws existed.

The employer logic is sound. Payroll is the largest controllable cost in a service business, and matching labor to demand protects a thin margin. The cost lands on the employee, who cannot hold a second job, book childcare, or predict a paycheck. Fair Workweek laws do not ban the practice. They put a price on it.

The scale of that cost shows up in survey data. According to the Shift Project at the Harvard Kennedy School, 60 percent of service-sector workers get less than two weeks of notice, 57 percent see last-minute changes to when a shift starts or ends, and weekly hours swing 34 percent on average within a month.

The Core Requirements

Although the specifics vary by jurisdiction, predictive scheduling laws share a common core of requirements. Knowing these five requirements gives you the shape of nearly every one of these laws, so you know what to look for when you check your own jurisdiction.

Beyond the three central requirements shown above, most laws add two more. Employers typically must provide a good-faith estimate of expected hours to new hires at the time of hiring, so employees know roughly what to expect before they start. And many laws include an access-to-hours provision requiring employers to offer available additional shifts to existing part-time employees before hiring new staff, which changes how covered employers approach adding headcount.

Of those two, the good-faith estimate is the one that has to be handed over as a document, so the form below sets out what a new hire can expect: the range of weekly hours, the days and shift times, how extra shifts are offered, and where schedules get posted.

Two more features round out the typical law. Employees generally have the right to decline shifts that were not on the posted schedule, without penalty. And the laws include anti-retaliation protections, so an employer cannot punish an employee for asserting their rights, requesting predictability pay, or declining a non-compliant shift. Together, they turn scheduling from something an employer does unilaterally into a documented process.

Where Predictive Scheduling Laws Apply

The single most important fact about these laws is that they are geographic: they apply based on where your employees physically work, and coverage is a patchwork. There is no federal predictive scheduling law, so an employer's obligations depend entirely on the state, city, or county where the work happens. A business can be covered in one location, subject to different rules in another, and completely exempt in a third.

At the highest level, the map has three kinds of places. First, jurisdictions with active laws: Oregon statewide, plus a set of cities and counties, mostly concentrated in California, the Pacific Northwest, and a few major cities elsewhere. Second, preemption states, which have passed laws specifically banning cities from enacting local scheduling ordinances, so no local law can exist there. Third, everywhere else, where no predictive scheduling law currently applies but one could be introduced.

For a business operating in a single location, this is simple: you check whether your city and state have a law and whether you meet its threshold. For a multi-location business, it is genuinely complex, because the same company can face completely different scheduling obligations in different stores. That complexity is why larger multi-location employers invest heavily in compliance systems, and why a growing business should understand the map before it expands into a covered jurisdiction.

The Jurisdictions With Laws

Here is the practical breakdown of where these laws currently apply. Oregon stands alone as the only statewide law; everything else is a city or county ordinance. The table below summarizes the major jurisdictions and their headline requirements, but because these laws change and thresholds update, treat it as a starting point and verify the current details with the relevant agency before relying on them.

A few jurisdictions deserve special note. The Oregon law covers retail, hospitality, and food-service employers with 500 or more employees worldwide, requires 14 calendar days of written notice, and bars work in the 10 hours after a previous shift unless the employee agrees and is paid time and a half.

New York City splits its rules by industry, and the gap is wide. Retail employers owe 72 hours of notice and cannot schedule on-call shifts at all. Fast food follows the 14-day standard and owes a $100 premium whenever a worker consents to a clopening shift.

Chicago reaches well beyond retail and food service: seven industries, including healthcare and manufacturing, at employers with 100 or more employees globally. Coverage also turns on pay, reaching employees who earn $33.85 an hour or $64,945.55 a year or less, a ceiling the city raises every July 1.

Rest between shifts is where the numbers diverge. Seattle, Oregon, and Los Angeles all set the gap at 10 hours, Berkeley and New York City (for fast food) at 11, and Philadelphia at 9. An employee can decline work inside the gap, and where they agree to it the employer owes a premium: time and a half in Berkeley, Seattle, Oregon, and Los Angeles, a flat $40 in Philadelphia.

The thresholds are where small businesses find their answer. Among the laws that count employees globally, the lowest bar is 36, set by San Jose, whose narrower ordinance only requires offering extra hours to existing part-time staff before hiring.

For a full Fair Workweek law counted the same way, the bar is 56, set by Berkeley (which also needs 10 or more of those employees inside the city) and by Emeryville. It rises to 100 in Chicago, 250 with 30 locations in Philadelphia, 300 for retail in Los Angeles, and 500 in Oregon and Seattle.

Two city laws count only the employees inside the city, and both start lower. New York City covers a retailer with 20 or more employees across its stores in the city, and San Francisco covers a formula retail chain with at least 40 stores worldwide and 20 or more employees in the city. Many of the other counts run company-wide or worldwide rather than per location, which matters for franchises and chains.

What the Oregon Predictive Scheduling Law Requires

Beyond the notice and rest rules above, the state Bureau of Labor and Industries attaches three further obligations. Every new hire receives a written good-faith estimate of the median hours expected in an average month. Predictability pay runs at two different rates. And the voluntary standby list has conditions attached to the word voluntary.

The two rates work like this. Adding a shift, or moving one inside the notice window without cutting hours, costs an extra hour at the regular rate. Cutting hours or canceling a shift costs half the regular rate for each scheduled hour the employee no longer works.

The rest premium is separate and steeper: work scheduled inside the 10 hours following a previous shift is paid at one and a half times the regular rate. And the standby list, which lets an employer call in extra help without owing predictability pay, counts as voluntary only where the employee agreed in writing and was told how to come off it.

Understanding Predictability Pay

Predictability pay is the mechanism that gives these laws their teeth, and it is the part most likely to surprise an employer, because it turns ordinary scheduling decisions into direct costs. It is the premium you owe when you change a posted schedule inside the advance-notice window.

The typical structure follows two rules. For a short-notice change that does not cut hours, such as moving a shift or adding to it inside the notice window, you owe roughly one additional hour of pay at the employee's regular rate. For a cut or cancellation, where the employee loses scheduled hours, you owe roughly half their regular rate for each hour they no longer work.

Sending someone home early when the expected rush never materializes is therefore not a free adjustment in a covered jurisdiction. It carries a defined cost.

Exceptions to predictability pay exist, most importantly for employee-initiated changes, but they typically require written documentation to hold up. Some jurisdictions have tightened this, requiring that employee-initiated changes be documented in writing or the premium is owed anyway. Accurate scheduling and time records are the foundation here.

Overtime math is the wrinkle that catches payroll teams. According to Department of Labor Fact Sheet 56B, predictability pay and right-to-rest premiums may be left out of the Fair Labor Standards Act (FLSA) regular rate, the rate overtime pay is based on, when they are not prearranged and not reasonably schedulable in advance, while on-call pay must always be included. Pay for hours actually worked always counts.

Preemption States and Pending Laws

The predictive scheduling map has a second layer that is easy to miss: many states have moved in the opposite direction, passing laws that ban cities from enacting local scheduling ordinances at all. These preemption states mean that even a large city within them cannot pass a Fair Workweek law, so employers there face no such requirement regardless of city politics.

Two statutes show how this works. Iowa Code 364.3(12)(a) bars a city from adopting or enforcing any ordinance on terms or conditions of employment that exceed state or federal law, and it names scheduling practices outright.

Tennessee goes further still. Tennessee Code 7-51-1802 bars a local government from imposing any requirement on an employer covering hours worked or the scheduling an employer must provide, and then adds that the general assembly preempts and occupies the entire field of regulating the terms and conditions of employment, which in plain terms leaves that whole area to the state.

The Tennessee statute still lets a local government set hours and scheduling for its own employees. In a preemption state the question is settled for private employers: there is no law, and no city can create one.

The result is a two-speed map: some regions extend these protections city by city while others block them at the state level. Several states have also seen statewide predictive scheduling bills introduced, though those have met stronger opposition than city ordinances and most have not passed.

The argument on both sides is real. Supporters say these laws protect hourly workers from income that swings week to week. Opponents, mostly in hospitality and retail, say they impose cost and rigidity on businesses that live on flexible staffing.

The balance struck differs by jurisdiction, and the map shifts from year to year as bills are introduced, amended, and defeated and as new city ordinances take effect. That volatility is why a compliance decision should rest on a current check of your own jurisdiction rather than on a general sense of the trend.

Enforcement and Penalties

Enforcement of these laws has escalated significantly, and the penalties are large enough that covered employers cannot treat compliance as optional. Because predictability pay is assessed per violation, per employee, the arithmetic compounds fast: a modest per-incident amount, multiplied across many employees and many weeks, becomes a serious sum.

The scale is visible in New York City. Per the Department of Consumer and Worker Protection (DCWP, December 2025), a Fair Workweek settlement with a major coffee chain reached $38.9 million for more than 15,000 workers at over 300 locations, the largest worker protection settlement in the city's history. It displaced a 2022 settlement with a national restaurant chain worth up to $20 million.

Beyond headline settlements, covered employers can face civil penalties assessed per violation, back-pay obligations to affected employees, mandatory compliance measures, and in some places private lawsuits. Agencies in the most active cities investigate complaints, and the businesses that get into trouble are usually the ones without records to show what they scheduled and when they changed it. Clean records are the cheapest protection you have.

Does This Apply to My Business?

This is the question most owners actually have, and for most small businesses the honest answer is: probably not yet, but check, and watch the threshold. The reason is that nearly every predictive scheduling law applies only above a size threshold and only to specific industries, which leaves most small businesses outside their scope.

To answer it for yourself, work through three questions. First, do you operate in a jurisdiction that has a law, meaning Oregon or one of the covered cities and counties, and not a preemption state? If not, you are not covered. Second, are you in a covered industry, typically retail, hospitality, or food service? If not, you are usually exempt even in a covered city.

The third question is size. Do you meet the employee-count threshold for that jurisdiction, remembering that some count employees company-wide or worldwide rather than at one location? Only if all three answers are yes are you likely covered.

For a growing business, the threshold question is the one to watch. A business that is comfortably under the employee count today can cross into coverage as it grows, especially where the threshold is low or counts employees company-wide across multiple locations.

The smart move is to know your jurisdiction's threshold in advance, so that crossing it is a planned transition rather than a surprise violation. Even before you are covered, adopting the core practices, posting schedules early and documenting changes, costs little and prepares you.

How to Prepare and Comply

Whether you are covered now or preparing for the possibility, the practical steps are largely the same, and most of them are good scheduling practice regardless of the law. Here is a sequence that works for a small or growing business.

The through-line is that compliant scheduling and good scheduling are almost the same thing. Posting early, documenting changes, connecting scheduling to payroll, and keeping records are what these laws require, and they are also what makes scheduling run smoothly for any business. Documenting your scheduling policy in your employee handbook makes expectations clear for everyone.

If you do one thing this week, look up whether your city or state has a law and where its threshold sits, then start posting schedules a little earlier than you do now.

Frequently Asked Questions