What Is Fair Workweek and Predictive Scheduling? A Plain Answer for Independent Operators

Fair workweek (also called predictive scheduling) is a set of city and state laws that require covered employers to post the schedule a fixed number of days in advance — usually 7 or 14 — pay workers a premium called "predictability pay" if they change it late, and give staff a minimum rest gap between shifts. Most of these laws only apply to large employers (often 250+ employees globally and 30+ locations), so the average single-site independent retailer or venue is almost certainly not in scope today. But the habits the laws target — last-minute shift changes, no posted schedule, no paper trail — cost you staff whether a law applies or not.

Here's the ground-level version, written for an operator who heard the term from an employee or a city council notice and just wants to know: does this apply to me, and what would it mean for next week's schedule?

The scenario most operators are in

You're closing up. A staff member mentions "the predictive scheduling law" and asks if the Friday change you made counts. You nod, then go home and Google it. An hour later you have 40 tabs open and no clearer answer than when you started.

That's the position this page is written for. Not a legal brief. Just what the laws are aiming at, who's covered, and what to actually do.

What fair workweek laws actually require

Every fair workweek law in the US is different in the details, but they share a common core. Four things show up almost everywhere:

Advance notice of the schedule. Post it 7 to 14 days ahead, depending on the city. Some require written or electronic posting with a timestamp.
Predictability pay. If you change a posted shift inside the notice window — cut hours, add hours, move a shift — you owe the employee a premium on top of their normal wages. The amount varies (often one extra hour of pay for adds, half the lost shift for cuts).
Right to rest. Workers can decline shifts that start fewer than 9 to 11 hours after their last one ended ("clopening" rules). If they accept, you owe a premium.
Good-faith estimate at hire. Give new hires a written estimate of the hours and days they should expect.

The specifics — the notice window, the dollar amount, the exceptions for weather or emergencies — vary sharply by city and industry. Don't memorize them generically. If you operate in a covered city, read the city-specific rule.

Who is actually covered

Most fair workweek laws are aimed at big employers, not corner stores. Common thresholds:

Headcount: 250+ or 500+ employees globally (not just at your location).
Locations: 30+ locations worldwide for retail; some chicago-style laws use lower bars.
Industry: Retail, fast food, hospitality, and warehouse are the usual targets. White-collar and salaried roles are usually exempt.
Jurisdiction: Only specific cities and states — currently NYC (retail and fast food), Philadelphia, Chicago, Seattle, San Francisco, Los Angeles, Oregon (state-wide). New ones get added every year.

If you run one store with twelve staff, you're almost certainly out of scope today. The reason to still know the threshold: franchise systems count the franchisor's employees, growing chains can cross the line without realizing, and acquisitions can pull you in overnight. Know where the line sits before you bump into it.

The habits these laws are targeting

Strip away the legal language and the laws are trying to stop one specific behavior: posting a rough schedule, then changing it freely right up to the day the shift starts. That forces workers to keep a whole week open, can't take a second job, can't plan childcare, and can't predict their paycheck.

Every small operator recognizes this pattern, because we've all done it. A callout comes in. You blow up the group chat. Someone picks it up. Hours shift. Nothing is written down. Nobody knows what they're actually working until the day of.

Even if no law applies to you, this is the single biggest reason staff quit retail and venue jobs. The fix isn't compliance — it's a posted schedule, published once, with changes that go through a real channel and leave a record. That's a retention move first and a compliance move second.

The record-keeping basics that matter either way

Whether a fair workweek law covers you or not, three things make your scheduling defensible and your team calmer:

A timestamped published schedule. When was the schedule released? In writing. Verbal "I told them Tuesday" doesn't count anywhere.
A change log. Every shift change — who requested it, when, who approved it, when it was communicated. This is what you'd hand a labor inspector. It's also what stops the "I never agreed to that" argument with staff.
Clock-in records that match the posted shift. If someone was scheduled 10–6 and clocked 10:14–6:32, that's a record. If there's no posted shift to compare against, you have nothing.

Schedaddle handles this by default — a published schedule is timestamped, changes are logged, and the geofenced time clock ties clock-ins back to the roster — but the principle is the same whatever tool you use. Get the schedule out of group chats and into something with a record.

Predictability pay is not overtime

Operators conflate these constantly. They're separate.

Overtime is a federal/state rule about hours worked past 40 in a week (or 8 in a day in some states). You pay 1.5x the regular rate.
Predictability pay is a premium for changing a posted shift late. It's usually a flat amount (one hour's pay, or half the missed shift) and it's owed whether or not the employee crosses 40 hours.

They stack. If a last-minute change pushes someone into overtime AND happens inside the predictability window, you owe both. One does not replace the other. If you're in a covered city and you've been treating predictability pay as "basically overtime," you're underpaying.

What this page is — and isn't

This is education, not legal advice or a compliance product. Schedaddle does not auto-block non-compliant schedules, does not calculate predictability pay for you, and does not guarantee compliance with any specific city's law. What we do have is an in-app labor-law reference covering 16 markets that flags when you're scheduling against a known rule — and dedicated city pages that go rule by rule.

If you actually operate in a covered jurisdiction, the city-specific page is the next step, not this one.

Where to go if you need the city-by-city detail

If you operate in NYC, Philadelphia, Chicago, Seattle, San Francisco, Los Angeles, or anywhere in Oregon — or you're considering opening there — start with the city-by-city breakdown at fair workweek. Each page covers the notice window, the predictability pay amounts, the exceptions, and the records you'd need to produce.

If you're not in a covered city, you can probably close this tab. But before you do, one honest question:

When did your team last find out about a shift change the same day it happened?

That's the real diagnostic, whether or not a law technically applies to you. If the answer is "this week," the law isn't your problem — your schedule is. Worth fixing either way.