Los Angeles's fair workweek law doesn't cover restaurants

Before anything else about predictive scheduling: find out whether the law applies to you. Most restaurants it gets written for are not covered by anything, and the roundups that list ten cities almost never say so.

The clearest example is Los Angeles. Both the City of Los Angeles Fair Work Week Ordinance and the newer Los Angeles County ordinance are retail-only. They cover NAICS 44–45 employers with 300 or more employees. Restaurants and fast food are expressly outside them. Every "fair workweek laws affecting restaurants" article I checked lists Los Angeles. An LA restaurateur reading those is preparing for obligations that do not exist.

The coverage gate is the whole story

Here is what it actually takes to be covered where restaurants are in scope:

Read the New York City row twice. The Fair Workweek Law's restaurant provisions apply to fast food, defined as limited-service. Full-service restaurants in New York City — essentially the entire independent dining scene — are outside it.

And Berkeley is the outlier that matters. No location threshold at all. Berkeley's own guidance works an example: an operator with three restaurants, one in Berkeley and two in Oakland, totaling exactly 100 employees, is covered. It is the only jurisdiction in the country whose predictive scheduling rules reach a genuinely independent multi-unit operator.

Two more that get miscategorized constantly:

San Jose is not a predictive scheduling law. Its Opportunity to Work Ordinance is access-to-hours only — offer extra hours to existing part-timers before hiring — but it applies to all industries at 36 employees, which makes it the lowest bar in the country for that one obligation.

Euless, Texas was repealed on 24 September 2024, killed by the state preemption statute that took effect in 2023. It still appears on live vendor lists in 2026.

Where these laws cannot arrive

This is the omission I found most consistently. Articles list the jurisdictions and never mention that a group of states has forbidden any more from appearing.

I can verify preemption statutes barring local scheduling ordinances in Georgia, Iowa, Tennessee, Arkansas, Michigan and Texas. Industry trackers put the total at eleven states, but I could not retrieve a primary source enumerating all eleven, so I'm giving you the six I confirmed rather than the number everyone repeats. Texas's is the only one with a documented kill — it eliminated Euless.

If you operate in one of those states, local predictive scheduling planning is wasted effort. That is worth knowing before you buy software to manage it.

If you are covered, here is what varies

The 14-day posting requirement is close to universal. Almost everything else is not, and the differences are the part that costs money.

Two jurisdictions pay clopenings in flat dollars rather than a multiplier, and San Francisco — the city that started all of this in 2015 — has no rest rule at all.

San Francisco differs on the other axis too: its predictability pay only triggers below seven days' notice, not fourteen. A schedule change ten days out costs nothing in San Francisco and costs an hour of pay in Chicago. If you run units in both, one rule does not fit.

The thing managers do that costs money

Sending someone home early on a slow night is a paid event.

Berkeley's own FAQ works the arithmetic: cut a server fifteen minutes short with under 24 hours' notice and you owe 0.25 hours of predictability pay — four hours or the hours actually reduced, whichever is less. Managers universally treat "it's dead, go home" as free. In a covered jurisdiction it is a wage.

Three more mechanics worth knowing:

Premiums stack. Berkeley confirms that asking someone to pick up a shift on under 24 hours' notice that also breaks the 11-hour rest window owes both the rest premium and an hour of predictability pay. One shift, two payments.

Consent is not a defense anymore in Chicago. Rules effective 1 June 2026 apply the right-to-rest premium regardless of whether the employee requested or consented to the shift. The old fix — get them to agree — no longer works there.

Predictability pay is wages, not a penalty. It's computed at the regular rate and owed on top of pay for hours worked. New York City requires it to appear separately on the wage statement.

The penalties are structured to compound

Chicago charges $300 to $500 per offense, and defines each affected employee as a separate offense and each day as a separate offense. One bad scheduling practice, forty employees, thirty days is not a fine — it is arithmetic.

For scale on enforcement: New York City announced a $38.9 million settlement with Starbucks in December 2025 covering more than 500,000 violations across 300-plus locations — $35.5 million in restitution to over 15,000 workers plus $3.4 million in penalties, working out to roughly $50 per worker per week for the period July 2021 through July 2024.

That is a chain with a compliance department. The exposure is not theoretical.

The records rule that flips the burden of proof

Philadelphia's retention period is two years — the shortest in the country — but the sting is in what happens if you don't have them. If an employer fails to maintain records or doesn't produce them within thirty days, the ordinance provides that "it shall be presumed that the employer has violated the Chapter, absent clear and convincing evidence otherwise."

You are guilty unless you can prove otherwise, and the proof is paperwork you no longer have. Chicago's rule runs three years or the duration of any pending claim, whichever is longer, which means a claim filed in year three extends the obligation indefinitely.

Philadelphia also presumes retaliation for any adverse action within ninety days of protected activity — and explicitly includes reducing hours or denying additional hours as adverse action. Cutting a complainer's shifts is presumptively unlawful.

Two carve-outs worth checking before you assume you're covered

Chicago excludes small franchisees. Its definition of "restaurant" excludes businesses limited to three or fewer locations in the city owned by one employer under a sole franchise. A franchisee of an 8,000-unit brand with three Chicago stores is outside the ordinance.

Chicago's wage cap moves every July. Employees above a set hourly and salary threshold aren't covered — and the threshold rises annually, most recently to $33.85 an hour effective 1 July 2026. Someone outside coverage last year can be inside it this year with no change in their pay. Check the current figure rather than the one in an article.

Universal exceptions across most ordinances: threats to persons or property, utility failures, acts of God, war or civil unrest, mutually agreed shift trades, employee-requested changes documented in writing, and documented just-cause discipline. Note the "in writing." A verbal "can I leave early?" isn't documented, so it isn't an exception.

The other lever moved in the opposite direction

While these laws were tightening what you can do after a schedule is posted, federal law loosened what you can do inside a shift.

The 80/20 rule was vacated on 23 August 2024, and the Department of Labor formally removed it from the regulations effective 17 December 2024. The pre-2021 dual jobs rule is back: the tip credit is unavailable when an employee works a genuinely separate non-tipped occupation, but the 20%-and-30-minute tracking regime is gone federally.

Note "federally." New York, Connecticut and Maryland maintain their own state-level thresholds. And nothing about the vacatur touches the scheduling rules — if anything the two combine awkwardly: you have more freedom to assign tipped side work and less freedom to move the shift once it's posted. I went through the tip-credit mechanics themselves in the tip pooling post.

What to actually do

If you're a single-unit independent anywhere except Berkeley, the honest answer is: nothing. These laws don't reach you. Spend the attention on the scheduling practices that reduce turnover on their own merits, which I covered in the scheduling post.

If you're growing, the thresholds are the thing to watch — 30 locations and 250 employees recur across Chicago and Philadelphia, and crossing either one changes your obligations without anyone notifying you. That is the same pattern I found with PCI paperwork: growth silently moves you into a heavier regime.

If you're already covered, three concrete items. Make sure your posted schedule gets amended and retransmitted in writing within 24 hours of any change, because Chicago and Philadelphia both require it. Make sure predictability pay shows as a separate line on the wage statement. And keep the schedule records for the longer of the local requirement and any open claim, because in at least one city the absence of records is itself the finding.

Disclosure: I work at Katalyst, and scheduling and time tracking are things we sell. Which is exactly why the first section of this post is the one I'd want you to act on: for most independent restaurants the correct amount of predictive-scheduling compliance software is none, because the law doesn't apply. Check your threshold before anyone sells you a solution to it.