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. Predictive scheduling is a body of labor law, also called Fair Workweek law, that changes what an employer is allowed to do when building and changing schedules, and in the places where it applies, it turns routine moves like trimming a slow shift into payments you owe by law. For most small businesses these laws 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 clears up what these laws actually require, which states and cities have them, and, crucially for a growing business, whether they apply to you and what to do as you approach the size where they might. Most content on this topic is written for large multi-location enterprises. This guide keeps the small and growing business in view: the thresholds that determine coverage, the practical steps to prepare, and an honest answer to the question every owner asks first, which is whether this even applies to them.

A quick disambiguation before we start, since the term is used two ways. Predictive scheduling in this guide means the Fair Workweek labor laws, not the AI-powered forecasting features some scheduling software markets under a similar name. Everything here is about legal requirements. I build the scheduling and record-keeping tools that support compliance into FirstHR, because these laws reward employers who post schedules early and document changes cleanly. 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. While flexible for the employer, that practice left workers unable to plan, arrange care, or count on their income. Predictive scheduling laws shift some of that burden back to the employer by attaching notice requirements and costs to last-minute changes. San Francisco passed the first such law in 2015, and the approach has spread to a growing set of cities and one state since.

It is important to separate the legal concept 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. When people search for predictive scheduling in a compliance context, they mean the laws, and that is the subject here.

The Core Requirements

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

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 fundamentally changes how covered employers approach adding headcount.

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, these requirements reshape scheduling from something an employer does unilaterally into a more structured, 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. Oregon's law applies to retail, hospitality, and food-service employers with 500 or more employees worldwide, requires 14 days of written notice, and mandates a 10-hour rest period between shifts. New York City splits its rules by industry, requiring 72 hours of notice for retail employers and applying the 14-day standard to fast food. Chicago has unusually broad industry coverage, reaching seven industries including healthcare and manufacturing that most other laws do not touch, and its wage-based coverage threshold adjusts upward each year.

The thresholds are where small businesses find their answer. They range widely, from around 10 employees in a city like Berkeley to 500 in Oregon and Seattle, and many count employees worldwide or company-wide rather than just at one location, which matters for franchises and chains. Because these details vary so much and change so often, the jurisdictions that matter are the ones where you actually operate, and the current figures should always be confirmed with that jurisdiction's labor agency. The broader work of building compliant schedules in the first place is covered in the guide to making a work schedule.

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, and it is owed automatically the moment you make the change, not only if an inspector finds it.

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. So sending someone home early when the expected rush never materializes is not a free adjustment in a covered jurisdiction; it carries a defined cost.

This is why predictability pay is as much an operational challenge as a legal one. The manager making a scheduling change at the store may not be thinking about a payroll obligation, so the two systems have to be connected for compliance to actually happen. There are usually exceptions, most importantly for employee-initiated changes, but those exceptions 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, as covered in the time and attendance guide.

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.

Roughly eleven states have enacted this kind of preemption, including Alabama, Arkansas, Florida, Georgia, Indiana, Iowa, Kansas, Michigan, Ohio, Tennessee, and Wisconsin. In these states, the question of predictive scheduling is effectively settled: there is no law and cities cannot create one. This is part of why the national picture is a two-speed map, with some regions expanding these protections city by city while others block them at the state level.

At the same time, a number of states have considered or introduced statewide predictive scheduling legislation, though state-level bills have generally faced stronger opposition than city ordinances and most have not passed. The landscape genuinely shifts from year to year as bills are introduced, amended, and defeated, and as new city ordinances take effect. That volatility is exactly why any compliance decision should rest on a current check of your specific jurisdiction rather than on a general sense of the trend. Presenting the debate evenhandedly, supporters argue these laws protect vulnerable hourly workers from income instability, while opponents, often from the hospitality and retail industries, argue they impose costly rigidity on businesses that depend on flexible staffing. Both concerns are real, and the balance struck differs by jurisdiction.

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 recent enforcement. In New York City, a settlement resolving Fair Workweek violations reached tens of millions of dollars, covering hundreds of thousands of violations across a large number of hourly workers, and stands as one of the largest worker-protection settlements in that city's history. An earlier settlement in the same city with another large employer also ran to tens of millions. These are single-company actions in a single city, which gives a sense of the aggregate exposure across all covered jurisdictions.

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. Enforcement agencies in the most active cities investigate complaints and can assess penalties that accumulate quickly when violations are repeated or affect many workers. The consistent lesson is that the businesses that get into trouble are usually the ones without records to show what they scheduled and when they changed it, which points directly to prevention.

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. Third, 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 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, which connects to sound staffing and scheduling generally.

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 also what makes scheduling work smoothly for any business. Approaching it that way turns compliance from a burden into a set of habits worth having regardless, and keeping those functions connected rather than scattered is part of the broader value covered in the HR automation guide. Documenting your scheduling policy in your employee handbook makes expectations clear for everyone.

Frequently Asked Questions