Can You Change an Employee's Schedule Without Notice? What You Owe, by City

Can you change an employee's schedule without notice?

In most of the United States, yes. No federal law requires you to give notice before you change an employee's schedule, and most states do not either. The exception is a growing set of cities and a few states where advance-notice laws apply to larger employers in retail, food service, hospitality and a handful of other industries. In those places, a late change is legal but it costs you money, and in some cases you need the employee's written consent first.

So the question to answer before you move anyone's shift is not "am I allowed?" It is "which rule applies to this employee, and what does this specific change cost?" That depends on where the person works, how big your company is, how far ahead the schedule was posted, and what kind of change you are making.

This post covers the default rule, the places where it flips, the numbers on each late change, the exceptions, and how to change schedules without turning every change into a retention problem. If you want the broader map of which jurisdictions have these laws, our guide to predictive scheduling laws covers that. This one is about the moment a manager has to move a shift and wants to know what happens next.

What does federal law say about schedule changes?

Federal law mostly stays out of it. The Department of Labor describes the Fair Labor Standards Act as setting minimum wage, overtime pay, recordkeeping and youth employment standards. Advance notice of a schedule is not on that list. The same page notes there is no limit on the number of hours employees 16 or older may work in a week, which is why an employer can add hours to a shift without breaking federal law.

That does not mean a schedule change is free. Two federal rules still reach it.

The first is overtime. Covered nonexempt employees must be paid one and one-half times their regular rate for hours worked over 40 in a workweek, and that rule applies no matter how short the notice was. A shift you add on Thursday can push someone past 40 and turn a flat-rate shift into a time-and-a-half one. Our overtime policy guide and the post on how to calculate overtime walk through the math.

The second is discrimination law. An employer can generally require punctuality and ask for approval of schedule changes in advance, but the EEOC's guidance says an employer may have to accommodate an employee who needs a schedule change because of a religious conflict, unless it would pose an undue hardship. After the Supreme Court's decision in Groff v. DeJoy, the EEOC says undue hardship is shown when a burden is substantial in the overall context of an employer's business, and the old "more than a de minimis cost" test no longer applies. For a manager, the practical point is that a refusal to swap a shift for a religious reason deserves a second look before you say no.

Outside those two rules, the default is at-will scheduling. An employer decides when work is needed and employees who cannot meet the schedule may face consequences. The rest of this post is about where local law overrides that default.

Where do advance-notice laws override the default?

A set of states and cities have passed what are called fair workweek or predictive scheduling laws. They differ in the details, but they share a shape: a covered employer must post a schedule in advance, and if the employer changes it late, the employer pays a premium or gets written consent, or both.

The main thing that varies is who is covered. These laws are written for large employers in specific industries, not every business with a schedule. Here is how the main ones compare. The pay figures are explained in the sections that follow.

Two things in that table catch managers out. The first is that the size thresholds are high in Oregon and Seattle. A 40-person restaurant group with one location is not covered by either, even though it sits in the same city. The second is that New York City is not one rule. Fast food and retail have different notice periods, and on-call shifts are prohibited for retail.

Check the current wage and size tests with your city before you rely on any row. Chicago's pay threshold is one to watch, and our Chicago Fair Workweek guide tracks the current number.

What does a late change cost in New York City?

New York City publishes the most specific price list, so it is the clearest place to see how this works. For fast food employers, the Department of Consumer and Worker Protection sets a premium for each late change, and the amount depends on how much notice you gave and what you did to the shift. As of the city's fast food FAQ updated in September 2023, the premiums are:

Those are per change, per worker, so a manager who rewrites a Saturday for six people has six premiums to pay. The city also treats a clopening, two shifts over two days with less than 11 hours between them, as its own category. A scheduled or agreed clopening that gets worked carries a $100 premium.

Two more features matter for managers. Workers have a right to say no to additional hours without negative consequences, and accepting extra hours takes written consent that is tied to a specific shift and, for planned changes, given before the schedule is posted. The consent does not waive a premium that is owed.

Retail is stricter in a different way. Employers with 20 or more employees must give schedules at least 72 hours before the first shift on them, and on-call shifts are prohibited, as is cancelling a shift on less than 72 hours' notice. Under the city's retail FAQ, requiring more than 15 minutes of extra time on shorter notice needs the employee's advance written consent, recorded with the date and time and tied to the specific change. General or ongoing consent does not count.

Enforcement is active. In March 2026 the Mayor's Office announced settlements and filings against fast food and retail employers, including more than $1.5 million in restitution to over 760 workers from one franchisee, for failing to provide schedules in advance, failing to get consent for changes and failing to pay required premiums. The cheapest mistake in this area is a pattern of small ones, because every affected worker and every week counts.

What do Oregon, Seattle and Chicago require?

The three other big regimes use a simpler two-tier price: one hour of pay for most late changes, and half pay for hours you take away.

Oregon's Bureau of Labor and Industries describes the rule for covered retail, hospitality and food service employers. The written schedule must be given at least 14 calendar days before the first day on it and must include all work shifts and on-call shifts. Without that notice, the employer owes one hour at the regular rate, plus wages earned, if it adds more than 30 minutes to a shift, moves a shift without losing hours, or adds a shift or on-call shift. It owes one-half times the regular rate for each scheduled hour not worked if it cuts a shift, moves it so hours are lost, cancels it, or does not call in an on-call employee.

Oregon also builds in the other side of the arrangement. Workers may decline shifts that are not on the posted schedule, and they may ask for extra shifts in writing at any time after posting, which does not trigger change pay. Employers may keep a voluntary standby list, though workers must request or agree to it in writing. One caution: the BOLI page says nothing about penalties, and the state legislature's own statute page for this chapter notes that some sections were amended or repealed in the 2026 session. Check the current statute before you rely on any specific section number.

Seattle's rules look similar. Its Office of Labor Standards says hourly employees at retail and food service establishments of employers with 500 or more employees worldwide are covered, with full-service restaurants also needing 40 or more locations worldwide. Schedules must be posted at least 14 days ahead. Employees may decline hours that were not on the original schedule, and the city lists a one hour premium when hours are added or a shift's date or time changes, and half the hours not worked when someone is sent home early.

Chicago's ordinance is worth reading in the code itself rather than a summary. Under municipal code section 6-110-050, the notice requirement moved from 10 days to 14 days for schedules beginning July 1, 2022. The employer owes one hour of predictability pay for each shift where it adds hours, changes a shift's date or time with no loss of hours, or cancels or subtracts hours with more than 24 hours' notice. For hours cancelled or cut with less than 24 hours' notice, the employer owes no less than 50 percent of the employee's regular rate for the hours not worked. The city's own web page for the program still shows the original 10 day figure, which is a good reason to check the code.

What if you only owe reporting time pay?

Some states do not have a notice law but do have a rule for the other end of the problem: the employee shows up and the work is not there. California is the best known. The Division of Labor Standards Enforcement says an employee who reports for a scheduled workday and is not put to work, or is given less than half the usual day's work, is owed pay for half the usual or scheduled day, in no event less than two hours nor more than four hours at the regular rate. Exceptions include operations that cannot start because of threats to employees or property, utility failures and causes outside the employer's control.

This is a different mechanism from a predictive scheduling law, and it applies whether or not your company is large. If you cut an employee's shift on the day, our guide to reporting time pay explains how to calculate it and which states have it.

What does this look like on a real schedule?

Here is a worked example with illustrative numbers, not real payroll. Suppose a restaurant in Oregon with more than 500 employees worldwide posts the week 14 days out. An employee is scheduled for a six-hour shift on Friday at $18 an hour. On Wednesday, the manager cuts the shift to four hours because bookings dropped.

The change happened with less than 14 days' notice, and two scheduled hours were not worked. Under the Oregon rule, the employer owes one-half times the regular rate for each of those hours: two hours at $9, or $18. The employee is paid for the four hours worked ($72) plus the $18, for $90 total.

Now change the facts. The manager instead adds two hours to a Thursday shift for an employee who has already worked 38 hours that week. Oregon's rule means one hour of pay at the regular rate for a change that adds more than 30 minutes. Separately, federal overtime kicks in for the hours over 40. So the cost of that single decision is the hour of change pay, plus the extra two hours worked, with a premium on the hours past 40.

In New York City fast food, the same cut on Wednesday for a Friday shift is a reduction with less than seven days' notice, so the premium is $45 for that one worker. If the manager waits until the morning of the shift, the premium for reducing hours with less than 24 hours' notice is $75. The longer you wait, the more the same decision costs.

In our experience, many late changes are not really decisions at all. Teams that manage schedules by hand often find a problem only after the week is posted, like a shift that accidentally puts someone into overtime, or a day that ends up over or understaffed. A late fix is where the premium, the overtime or both come from, and a hasty one can leave you short or overstaffed on top of it. The cheapest change is the one you catch before you publish.

The point is not that you should never change a schedule. It is that the cost grows as notice shrinks, and a manager who can see the cost before publishing will often choose differently.

Which changes do not trigger pay?

Every one of these laws has exceptions. The common ones are:

• Events outside the employer's control. Oregon's list includes floods, earthquakes, wildfires, snowstorms, extreme temperatures, and human-caused hazards like fires, explosions and war. Chicago's code lists threats to people or property, utility failures, acts of nature, civil unrest and pandemics.
• Changes the employee asks for. Oregon says a shift added at the worker's written request does not trigger change pay. Chicago exempts a change the employee requests and that is confirmed in writing.
• Mutual agreements and swaps. Under Chicago's code, a mutually agreed shift trade or coverage arrangement between covered employees is exempt, and so is a change mutually agreed to by the employee and employer and confirmed in writing.
• Self-scheduling. Chicago's code exempts covered employees who self-schedule. If your team picks its own shifts, that is worth knowing, and our post on self-scheduling in clinical teams looks at how it works in practice.
• Just-cause discipline. Chicago allows schedule changes for discipline for just cause, if the employer documents the incident in writing.

Notice what these have in common: several of them depend on a written record. A verbal "sure, I can cover Saturday" is not the same as a confirmed request, and New York City is explicit that consent must be documented and tied to the specific change. If you rely on an exception, keep the paper.

Can an employee refuse a schedule change?

Where these laws apply, often yes, at least for added hours. New York City fast food workers have a right to say no to additional hours without negative consequences, Oregon workers may decline shifts not in the written schedule, and Chicago employees may decline previously unscheduled hours.

Where no such law applies, the answer is the at-will default. An employee can say no, but the employer can generally treat a refusal as a performance issue. That default is subject to the discrimination rules above, any union contract or written employment agreement, and your own policies, so check them before you discipline anyone over a refused change.

How do you change schedules without losing people?

The legal question is only half the problem. The other half is that a late change is one of the fastest ways to lose an hourly employee, whether or not a law requires a premium. People plan child care, second jobs and school around a posted schedule. A change that lands the night before breaks something for them even if you pay for it.

A few practices keep changes from becoming a retention problem:

1. Post further out than the law requires. If the rule says 14 days, aim for 21. The notice requirement is a floor on how much planning time you owe, not a target.
2. Ask before you assign. Offer a change to volunteers first, in writing. A shift someone chose is cheaper than a shift someone was handed, and in several places it is also exempt from change pay.
3. Make the cost visible. Managers who know a change adds a premium make fewer of them, so put the cost in front of whoever makes the change, not on a payroll report two weeks later. In Shift Amp, a published week can't be edited in place. Changes go into a revision, and before it goes out the manager sees every added, removed and changed shift, the change in scheduled hours and exactly who will be notified, and still decides whether to publish. It doesn't price predictability pay, so keep your city's premium table beside it.
4. Keep a change log. Who requested the change, who agreed, when, and for which shift. If a complaint arrives, the record is the defense. New York City employees have two years to file.
5. Look at the rest gap before you publish. Oregon and Seattle require 10 hours between shifts unless the worker agrees, with time-and-a-half for hours in that window, and New York City fast food puts a $100 premium on a worked clopening. Our guide to minimum rest between shifts covers the state and city rules.

What should you do on Monday?

Start with coverage. Work out whether any of your employees fall under a city or state rule: where they work, your total headcount worldwide, and your industry. If you are under every threshold, you are in the at-will default for notice, though overtime and discrimination rules still apply.

If you are covered, pull last month's schedule and count the changes made after posting. Price each one using the table for your jurisdiction. That number tells you whether you have a compliance problem, a staffing problem or both.

Then fix the process, not the individual change. Decide your posting lead time, who can approve a change inside the notice window, and where consent gets recorded. A rule that lives in one manager's head fails the first time that manager is on vacation.

This article is general information, not legal advice. These laws change, and the figures here come from the official pages linked above as of October 2026, so confirm the current rule with your city or state labor agency before you act on it.