What Is Predictability Pay? A Plain-Language Guide for Retail and Venue Operators

It's Saturday, 9:47pm. You realize Sunday's open is overstaffed, so you text Maria: "Hey, come in at 12 instead of 10." She says fine. If your store is in Chicago, you just owed her extra money — even though she worked the shift. That extra money is called predictability pay, and most operators don't learn it exists until an audit or a lawyer's letter.

What predictability pay actually is

Predictability pay is a mandatory extra payment — usually one hour of wages, sometimes more — that an employer owes an employee when a posted schedule changes inside a protected advance-notice window. It is not a fine. It is not a penalty paid to the city. It is wages, paid to the employee, on top of the hours they actually work (or would have worked).

The idea behind the laws is straightforward: hourly workers can't plan childcare, a second job, or transit around a schedule that keeps moving. So covered jurisdictions require employers to post schedules 7 to 14 days in advance, and to pay a premium when they change them late. The notice window varies by city. The trigger — a manager-initiated change inside that window — is the same everywhere.

The two moments it triggers

There are two everyday moves that cost you money under these ordinances.

1. A schedule change inside the notice window. You posted the roster last Sunday. On Saturday night you shorten Maria's Sunday shift from 10am–4pm to 12pm–4pm. Even though she showed up and worked, you owe her a predictability pay premium (in Chicago, one hour of pay at her regular rate) for changing a posted shift with less than the required notice.

2. An on-call or "just-in-time" shift that gets cancelled. You told Devon on Monday to be "on call" for Friday night. Friday afternoon you text: "Don't bother coming in." In most covered cities, that cancellation itself triggers predictability pay — often half the wages he would have earned. On-call shifts that never activate are the single most expensive habit in retail scheduling.

Who it actually applies to

Predictability pay is not federal. It exists in specific cities and one state, and the rules differ in every one of them. As of now, the jurisdictions with active fair workweek / predictable scheduling laws that trigger predictability pay include:

• Oregon (statewide, for large retail, hospitality, and food service employers)
• New York City (retail and fast food, separate rules)
• Chicago
• Philadelphia
• San Francisco
• Seattle
• Los Angeles (retail)

Most also have employer-size thresholds — a 12-person boutique in Chicago may or may not be covered depending on whether it's part of a larger chain. If your business is in Cleveland, Boise, Nashville, or almost any suburb or rural market, you are almost certainly not covered today. Don't manufacture compliance anxiety you don't need. But if you are in one of those cities, the exposure is real, and the specific numbers matter. Your city's actual rules — hours of premium, notice window, employer size thresholds — live on our fair workweek hub, broken out jurisdiction by jurisdiction.

The habit that creates the most exposure

Here is the pattern we see over and over from operators who get burned:

They know the notice window. So they publish a skeleton roster on Sunday to "meet the 14 days." Then, all week, they quietly edit it. Trim an hour off Tuesday. Move Wednesday's open by 90 minutes. Swap Thursday's closer. By the time the week actually happens, half the shifts have been changed inside the window — and every single one of those manager-initiated edits owes predictability pay.

A published roster is not a safe roster if you keep changing it. The law doesn't care that you technically posted something 14 days out. It cares whether the shift the employee is working now matches the shift you posted then. Silent edits are the highest-dollar mistake in covered jurisdictions, and they show up cleanly in an audit because scheduling software logs the change history.

What a compliant roster habit looks like

The workflow that keeps you out of trouble is boring, and that's the point.

1. Forecast before you publish. Look at last year's sales for the same week, known events, weather. Staff to real expected demand — not the demand you wish you had.
2. Publish once, on the same day every week. Then treat the published roster as a commitment, not a draft.
3. Route changes through the employee, not the manager. Staff-initiated shift swaps are generally exempt from predictability pay in every covered jurisdiction. Manager-initiated cuts are not. If Maria wants to swap with Devon and they both agree, that's their trade — no premium owed.
4. Log every change with a reason code. When an audit comes, "employee requested" vs. "business need" is the difference between owing nothing and owing thousands.
5. Use on-call shifts sparingly, or not at all. In covered cities, the cancellation cost usually erases whatever flexibility you thought you were buying.

This is the workflow Schedaddle is built around — a published roster with a full change log, staff-initiated swap requests that don't route through you, and a geofenced time clock that ties actual clock-ins back to the posted shift, so what happened and what was scheduled are the same record.

One honest question

If you're in a covered city, pull up your last two weeks of schedule edits. Count the manager-initiated changes made inside your notice window. At one hour of premium pay per change, what did last month actually cost you — and would you have known if no one had asked?