Predictive Scheduling Laws: What Employers in Covered Industries Must Know

A manager changes the schedule on Thursday night for a shift that starts Saturday morning. Under a predictive scheduling law, that change — made less than the required advance notice period — could trigger a premium pay obligation for the affected employee. One last-minute schedule swap, multiplied across a workforce of 200 hourly employees, adds up fast.

Predictive scheduling laws (also called fair workweek laws) have been passed in a growing number of cities and states over the past decade. They were originally aimed at large retail and food service employers in major cities, but the model has spread. If you operate in a covered jurisdiction and haven’t audited your scheduling practices recently, there’s a good chance you have exposure you haven’t identified yet.

Which Jurisdictions Have Predictive Scheduling Laws

As of 2026, jurisdictions with active predictive scheduling requirements include: Oregon (statewide), New York City, Chicago, Seattle, San Francisco, Los Angeles, Philadelphia, Emeryville (CA), and several others. More are in various stages of proposed legislation.

Oregon’s law — the first statewide predictive scheduling law in the US — applies to retail, hospitality, and food service employers with 500 or more employees worldwide. New York City’s law targets fast food employers and retail employers with 20 or more locations globally. Seattle and San Francisco have similar size thresholds. The specifics vary by jurisdiction, which is why “predictive scheduling” isn’t a single standard you can implement once and apply everywhere.

Core Requirements: What These Laws Actually Require

Most predictive scheduling laws share a common core. Employers must post work schedules a set number of days in advance — typically 7 to 14 days, depending on the jurisdiction. If a schedule change is made after posting, the employer may owe the affected employee a premium payment, often called a “predictability pay” or “schedule change premium.” This payment is typically one to four hours of pay at the regular wage rate, regardless of whether the employee works additional or fewer hours as a result of the change.

Most laws also require a rest period between shifts — commonly 10 or 11 hours. If an employee is scheduled for a closing shift and then an opening shift the next morning with less than the required rest, the employer owes a premium. This “clopening” restriction is one of the most operationally challenging provisions, particularly for food service and hospitality employers running morning and evening shift cycles.

Some jurisdictions also require that employers offer additional hours to existing part-time employees before hiring new staff. This “right to hours” provision affects how you can staff up for busy periods — you can’t just hire seasonal workers if existing employees want more hours and are qualified to work them.

Employee-Initiated Changes: The Mutual Consent Exception

Every predictive scheduling law includes some form of mutual consent exception. If an employee requests a schedule change — swaps a shift with a coworker, asks to leave early, volunteers to come in on a day off — the premium pay obligation typically doesn’t apply. The law is designed to penalize employer-driven last-minute changes, not employee-initiated flexibility.

The documentation requirement for this exception is where employers get into trouble. “The employee asked for it” is easy to say and hard to prove if a claim is filed months later. Most laws require written documentation of employee-initiated changes, signed by the employee. A verbal conversation between a manager and an employee at the end of a shift doesn’t satisfy the documentation requirement in most jurisdictions. If your scheduling system doesn’t capture and retain this consent documentation automatically, you’re managing the compliance risk manually — and that’s a gap.

Recordkeeping Requirements

Predictive scheduling laws typically require employers to retain scheduling records for a defined period — commonly two to three years. Records that need to be retained include the posted schedules, the date and time each schedule was posted, any changes made after posting, the reason for changes, and any premium pay that was owed and paid. In jurisdictions with a right-to-hours provision, you may also need records of hours offered to existing employees before any new hire decisions.

For operators using paper schedules or basic spreadsheets, meeting these recordkeeping requirements means building a parallel documentation system. For operators using a scheduling platform that integrates with payroll, much of this documentation is already being captured as a byproduct of normal operations — you just need to confirm that the records are retained for the required period and accessible for a potential audit.

Penalties for Non-Compliance

Enforcement varies by jurisdiction. Some rely primarily on employee complaints to trigger investigations. Others have active agency enforcement with periodic audits. Penalties typically include back payment of any premium pay that should have been paid, civil penalties per violation, and in some cases attorney fees in private actions. Class-action exposure is real — a single scheduling practice applied to 500 hourly employees over two years creates a large pool of potential claimants.

The operational disruption of an enforcement investigation — records requests, manager interviews, payroll reconciliation — often costs more than the underlying liability. Early compliance is almost always cheaper than retroactive correction.

Integrating Scheduling Compliance into Daily Operations

Netchex’s scheduling tools are built to work alongside payroll, so advance schedule posting, change documentation, and premium pay calculations can be handled within a single system rather than tracked manually across disconnected tools. For operators in covered jurisdictions, that kind of integrated workflow turns a compliance burden into a normal part of daily scheduling. Talk to a Netchex consultant about predictive scheduling compliance in your specific cities.

Frequently Asked Questions

This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page