Fair workweek laws: do they reach your restaurant, and what changes if they do

The short answer

There is no federal rule about posting a schedule ahead of time. Eleven cities and one state have written their own, and they nearly all say the same thing: give the team the schedule 14 days ahead, and pay a premium if you change it after that.

Whether any of it reaches you depends almost entirely on a size threshold, and most independent operators sit below it.

First, find out if you are covered

This is the only question that matters before you read further.

Where	Who it covers
Oregon, statewide	Retail, hospitality and food service, 500+ employees worldwide
Seattle	Retail and food service, 500+ employees worldwide
Chicago	100+ employees globally, or a restaurant chain with 30+ locations and 250+ employees
San Francisco	Formula retail, meaning chains of 40+ locations
Berkeley	Covered industries with 10+ employees in the city
New York City	Fast food and retail
Philadelphia, Los Angeles, Evanston, Emeryville, LA County	Thresholds vary, generally large employers

Two things surprise people.

Berkeley starts at 10 employees. If you run a single restaurant there with a full crew, you are covered. Nowhere else is the bar that low.

A franchise counts against the brand, not your store. Run one location of a national chain and you are likely inside the threshold, while the independent place across the street is not. It is the most common way a small operator discovers the law applies to them, usually late.

What it costs when you change a shift

Predictability pay is the mechanism. Change a posted shift inside the 14 day window and you owe money on top of the hours worked.

Chicago and Seattle generally use one hour at the regular rate per change. New York City fast food is more granular, with fixed amounts of $10, $15, $45 or $75 depending on how late the change lands and whether you added, cut or moved the shift.

None of these are large on their own. They add up because scheduling changes are not rare: one manager moving four shifts a week across a year is a real number, and every one of them has to be tracked and paid.

The clopening rules are the sharp edge

Closing at midnight and opening at 8am is normal in this industry and it is what these laws target hardest.

Chicago and Seattle both require 10 hours between shifts. In Chicago an employee who agrees to work anyway is owed 1.25 times their rate for that shift. In Seattle the hours falling inside the rest window are paid at time and a half. New York City fast food adds a $100 premium.

The trap is that a clopening rarely looks like one on the schedule. Two normal shifts on two different days, eight hours apart in practice. You find it by looking at the gap between the end of one shift and the start of the next, which is exactly the check nobody does by eye on a Friday afternoon.

If you are not covered, post two weeks ahead anyway

Here is the part worth reading even when none of the above applies to you.

The cost of a late schedule is not the fine. It is the person who took a second job because they could not plan around yours, and the Saturday you spent texting five people to cover a shift.

Turnover in food service runs high, and the reason people give for leaving is rarely the pay alone. It is not knowing what next week looks like. Publishing early is the cheapest retention lever available, and it costs nothing but deciding earlier.

There is also a practical argument. A schedule posted two weeks out gets read. A schedule posted Saturday for Monday gets missed, and the person who misses it is the one you have to replace.

Making it work in practice

Four things, in order of how much they help:

1. Build from last week rather than from scratch. Most weeks are 80 percent the same. Duplicating and adjusting takes minutes; starting empty takes an hour, which is why it gets postponed until Saturday.
2. Check the gap between shifts before you publish, not after someone complains. Anything under 10 hours is worth a second look whether or not a law says so.
3. Make sure the team actually received it. In a covered city, posted means given to the employee. A file on your laptop is not posted, and neither is a photo of a printout stuck to the break room wall that half the closing shift never sees.
4. Keep a record of what was published and when. If a dispute ever comes, the question is what the employee was told and on what date. A tool that keeps versions answers that in seconds; a spreadsheet overwritten twelve times cannot answer it at all.

We cover the mechanics in how to make a work schedule for a small business, and the delivery side in sending your team their schedule without an app.

Where to check

Rules change, thresholds get revised and new cities join. Before you rely on anything here, check the ordinance for your own city: they are published by the local labor standards office, and the thresholds are the first thing to look at.

Squadra Planning builds the week from the previous one, shares it as a link your team opens with no account, and keeps every published version. It is free up to 10 employees. It will not tell you whether your city has an ordinance, but it will make posting two weeks ahead take about the same effort as posting two days ahead.