Chicago Updated Its Fair Workweek Rules. Where Should a Warehouse Track Predictability Pay?

If you run a Chicago warehouse, fulfillment center or 3PL and your schedules move with volume, the honest answer is that predictability pay belongs wherever your schedule changes are actually recorded — and for most covered operations that is the workforce-management (WFM) or timekeeping system you already run, not a side spreadsheet. The arithmetic is simple. The hard part is catching every employer-initiated change the moment it happens and classifying it correctly. That is a data-capture problem, and it is where a person, not a formula, carries the judgment.

Chicago amended its Fair Workweek rules effective June 1, 2026, and the changes make the recordkeeping heavier, not lighter. The ordinance has applied since 2020, but the 2026 rules add detail to what counts as an exempt voluntary change, require a new written agreement for each applicable schedule change instead of a blanket standing consent, and expand the records you keep and the good-faith estimate you give. If you are covered, predictability pay is a recurring cost that has to be computed per worker, shown separately on the wage statement and paid on time.

First question: are you even covered?

Start here, because the ordinance only reaches specific employers. A covered employer is primarily engaged in a covered industry — which includes warehouse services and manufacturing — with more than 100 employees globally (250 for not-for-profits) and at least 50 covered employees. A covered employee is one who does most of their work in Chicago and earns at or below the wage ceiling: $32.50 an hour for 2026, indexed each year (a salary cap, originally $50,000 when the ordinance took effect, is indexed too). Warehouse and light-manufacturing crews paid hourly almost always sit under that ceiling, which is why a warehouse or 3PL is covered on the same terms as a restaurant or retailer.

See how a warehouse operation can organize scheduling exceptions and handoffs.

What actually triggers predictability pay

Once a schedule is posted at least 14 calendar days ahead, most employer-initiated changes to it owe the worker extra pay. The amounts come from the ordinance: one hour of predictability pay at the regular rate when the employer adds hours or changes a shift, and at least 50 percent of the regular rate for previously scheduled hours a worker loses when a shift is cut or canceled on less than 24 hours' notice — including being sent home early. A separate right-to-rest premium of at least 1.25 times the regular rate applies when a worker consents in writing to a shift starting fewer than 10 hours after the previous one ended. For these amounts the "regular rate" excludes overtime, holiday and other premium pay.

The exemptions are where operators get into trouble. Predictability pay is not owed when a change is genuinely voluntary and employee-initiated — but under the 2026 rules a standing "the worker agreed to pick up extra shifts" policy is not enough; you need a written record for each change. Filing an employer-driven change as voluntary is exactly the error an audit looks for.

The real problem: capturing and classifying every change

A volume-driven warehouse can change dozens of shifts in a week — a late trailer, a demand spike, a call-off. Each change is a small decision: was it employer-initiated (pay owed) or voluntary (documented, no pay)? Did the worker get 24 hours' notice? The dollar figures are trivial to compute; the expensive mistakes are missed changes and wrong classifications. So the tooling question is not "what calculates predictability pay" but "what reliably records every change, with its reason and timestamp, so the calculation has clean inputs."

Three ways to run it

There is no single right tool. Each of these can work; the difference is where your change data actually lives and how much volume you handle.

A worked month, with the numbers shown

The following figures are an illustrative example with assumed numbers, not a Clairvance client result. Say a covered picker crew earns an assumed $22.00 an hour. In one week the operation, on its own initiative and with less than the required notice:

• adds a shift for 6 workers (one hour of predictability pay each): 6 × 1 × $22.00 = $132.00;
• cancels an 8-hour shift for 4 workers on under 24 hours' notice (50 percent of the lost hours): 4 × (0.5 × 8 × $22.00) = 4 × $88.00 = $352.00;
• sends 3 workers home 3 hours early (50 percent of the lost hours): 3 × (0.5 × 3 × $22.00) = 3 × $33.00 = $99.00.

That is $583.00 in predictability pay for one week, on top of the hours actually worked, each line shown separately on the worker's wage statement and paid by the next payday. The number itself is small; the risk is that three of those thirteen changes never got recorded, or that one got mislabeled voluntary. If a pattern like this recurs most weeks, the records — not the math — are what an audit will test.

What a person still owns

This comparison is an editorial decision method, not a compliance certification or legal advice. Automation can capture a change, stamp the time, do the arithmetic and push the result to payroll. It should not be the thing that decides whether a change was voluntary. Keep three judgments with a named person: classifying each change as employer-initiated or genuinely voluntary; confirming the written per-change consent exists before treating a change as exempt; and signing off on the weekly predictability-pay total before it reaches payroll. Those are the points where a wrong call becomes a wage claim.