Yes. Manufacturing and warehouse services are two of the seven industries Chicago's Fair Workweek Ordinance names[1]. As of July 1, 2026, coverage turns on two tests: employer size (100 or more employees globally, at least 50 of them covered) and a per-employee wage line ($33.85 per hour or $64,945.55 per year)[1][2]. Covered plants and distribution centers owe 14 days of advance schedule notice, predictability pay when a posted schedule changes late, and a right-to-rest premium of 1.25 times the regular rate. Exposure is not identical across the two industries: the ordinance carries fifteen exceptions to predictability pay, and one of them is written for manufacturing employers only[3]. Warehouse services have no counterpart. To size your exposure, run both tests on your Chicago hourly roster this week.
This article is for general information and is not legal advice. Confirm obligations with qualified counsel.
You run a plant or a distribution center in Chicago, and you have always read "fair workweek" as a retail and restaurant problem. It is the story the coverage tells: predictive scheduling laws land on the mall and the drive-through, so a manufacturer or a logistics operator files it under "not us."
The ordinance itself does not draw that line. It names seven covered industries, and two of them are yours. Whether it reaches your workers is not decided by how "retail-like" the job feels. It is decided by your industry, your headcount, and a wage line that moved up again in 2026.
In this post:
- Does the ordinance cover manufacturing and warehouse workers?
- Who counts as a covered employer and a covered employee?
- What a covered plant or warehouse must operationalize
- Why it lands hard on manufacturing and warehouse
- The fifteen exceptions, and where a plant and a DC part ways
- When the line goes down at 2 p.m.
- What to do next
Does Chicago's Fair Workweek Ordinance cover manufacturing and warehouse workers?
Yes. Chicago's Fair Workweek Ordinance applies to large employers in seven named industries, and manufacturing and warehouse services are two of them. The other five are building services, healthcare, hotels, restaurants, and retail. Coverage follows the industry, not how closely the work resembles a store or a kitchen.
That list comes from the City's own Fair Workweek notice, the posting a covered employer is required to display[1], and from how the Office of Labor Standards describes coverage on its Fair Workweek page[4]. The question a plant or DC leader is really asking is not whether those two words appear in the ordinance. They do. It is whether their own workforce clears the two further tests that turn a named industry into an actual obligation.
New to how these laws work across the country? Start with the national picture, then come back here for the Chicago manufacturing and warehouse specifics.See Fair Workweek Laws 2026: Schedule Changes That Trigger Penalty Pay
Coverage key
| Coverage key | The line |
|---|---|
| Industry | Manufacturing or warehouse services (2 of the 7 named industries: also building services, healthcare, hotels, restaurants, retail)[1] |
| Employer size | 100+ employees globally (250 for not-for-profits; 250 across 30 locations for restaurants), at least 50 of them covered employees[1][3] |
| Employee wage | Worker earns at or below $33.85 per hour or $64,945.55 per year (adjusts upward each July)[1][2] |
Who counts as a "covered employer" and a "covered employee"?
Coverage in Chicago works like a lock with two keys: an employer test and a per-employee wage test. Both must turn before an individual worker is covered. A manufacturer or 3PL usually clears the employer bar easily, so the wage line is where the real surprises live.
You are a covered employer if you have 100 or more employees globally (250 for not-for-profits, or 250 across 30 locations for restaurants), at least 50 of whom are covered employees, and you are primarily engaged in one of the seven industries[1][3]. A regional manufacturer or a multi-site distribution operator meets the size threshold without much thought, though it is worth knowing that the City measures it as a 12-month average of global employees, counts covered employees the same way, and rounds down to a whole number[5]. A genuinely borderline operation should run the average rather than assume the answer.
The employee test is where operators get surprised. A covered employee performs the majority of their work in Chicago, measured by the total hours they worked inside and outside the city over the previous 90 days, and earns at or below an annually adjusted wage line[5]. As of July 1, 2026, that line is $33.85 per hour or $64,945.55 per year[2][1].
The line climbs every summer. Through June 30, 2026 it sat at $32.60 per hour or $62,561.90[3], so the pool of covered workers widens a little each July as the threshold adjusts upward. The practical read for a plant or DC: your salaried shift supervisor above the line is not covered, but your hourly line worker and your hourly pick-pack associate below it are. Coverage is decided worker by worker, not stamped on the company as a whole.
One warning before you sort that roster. Chicago is currently publishing three different wage thresholds across three live documents, and we have used the newest. The City's Fair Workweek page states $33.85 per hour and $64,945.55 per year[4]. The FAQ that same page links, Version 3.2 from December 2025, still states $32.60 and $62,561.90[3]. An older FAQ from July 2024 is also still hosted and states $31.85 and $61,149.35[6]. The Fair Workweek notice effective July 1, 2026 and the City's one-pager on the July 2026 changes both carry $33.85 and $64,945.55[1][2], and they are the most recent, so that is the pair we have followed. If someone hands you a lower figure out of a City PDF, check the date on the document before you rebuild your roster around it.
What must a covered plant or warehouse operationalize?
A covered employer owes three things: 14 days of advance schedule notice, predictability pay when a posted schedule changes late, and a right-to-rest premium when two shifts land too close together. A worker separately has a right to decline hours you did not previously schedule, which is a right rather than a premium. The 2026 rules tightened the documentation behind all of it.
Fourteen days of advance notice. You must post each covered employee's work schedule at least 14 days before the first day of that schedule[5][1]. The posted schedule has to be time-stamped with the date and time of posting, and it has to name every covered employee who works at the location, including the ones not scheduled that week[5]. That two-week horizon is the baseline the rest of the ordinance is built around.
Predictability pay for late changes. Change a posted schedule after that deadline and you owe the affected worker one hour of predictability pay per impacted shift, whether you added hours or moved a shift's date or time without cutting hours[1][5]. Cutting hours is where the number moves, and what moves it is proximity to the shift, not the 14-day deadline. Cut hours more than 24 hours before the shift starts and you owe the same single hour. Cut them inside the last 24 hours and the worker is owed at least 50 percent of the pay for the hours they lose[1][3]. Either way the charge attaches to the shift rather than the pay period, so it accrues change by change, and a change of 15 minutes or less does not trigger it at all[5].
The right to decline is not the offer process. These are two separate things and it is worth keeping them apart, because only one of them costs money. A covered employee may decline unscheduled hours added within 14 days of the start of the schedule those hours fall in[3]. That is a right, not a premium. Nothing is owed when a worker exercises it, so there is nothing to budget for.
Distributing additional hours is a different rule with its own process. Before you hire from outside, the hours go in writing to qualified covered employees at that location, then to covered employees at your other locations if you normally schedule across sites, then to temporary or seasonal employees who have worked for you two or more weeks in the previous 12 months[5]. The written offer has to carry the location, the start and end time, whether the shift is temporary or recurring, the qualifications and any training you will provide, and how and by when to accept[5]. Then the part worth writing on the wall: no predictability pay is owed for any shift accepted through that process[5]. For a plant re-staffing a stopped line, that is the most useful lever in the ordinance.
The right to rest. A worker is owed 1.25 times their regular rate for any shift that begins less than 10 hours after the end of the previous day's shift[1][5]. The test is the gap between one calendar day's shift and the next, and a shift begins on the day it starts, so two shifts on the same day less than 10 hours apart do not trigger it[5]. If the worker takes a double shift that starts inside that window, the 1.25 times rate is owed on the entire double shift, not only the second half. On a split shift, it is owed on the portions that begin inside the window[5]. Consent does not change any of it. The premium is owed whether or not the worker asked for the short turnaround[5].
Those obligations got more exacting on June 1, 2026. The updated rules expanded the good-faith-hours estimate employers give at hire, required time-stamped advance schedules, made on-call shifts something you list in advance rather than spring on the day, and added documentation and record-keeping duties around predictability pay and voluntary changes[7][8][9]. Predictability pay and right-to-rest pay now have to be paid by the next payday for the pay period the change fell in, or in which the two shifts were worked, and itemized separately on the wage stub[5]. After an employer-initiated change, the affected worker has to receive an amended schedule within 24 hours[3]. The direction of travel is toward more proof, earlier.
The record-keeping side of that shift is its own project: the audit trail has to be captured as the work happens, not reconstructed later when a complaint or an inspection forces the question.
| Obligation | Requirement |
|---|---|
| Advance notice | Post each covered employee's schedule at least 14 days before the first day of that schedule, time-stamped[5] |
| Predictability pay, hours added or shift moved | One hour of pay per impacted shift, for a change of more than 15 minutes made after the 14-day deadline[1][5] |
| Predictability pay, hours cut | One hour if the cut lands more than 24 hours before the shift; at least 50% of the pay for the lost hours if it lands inside 24 hours[1][3] |
| Right to rest | 1.25 times the regular rate for a shift beginning less than 10 hours after the end of the previous day's shift, owed even with the worker's consent[1][5] |
Why does this land hard on manufacturing and warehouse specifically?
Because the events the ordinance attaches a cost to are not a plant's exceptions. They are its operating model. Flexing coverage to demand hour by hour is how the floor and the dock get through a shift, and every unplanned flex is now a scheduling event you either price or document as one you do not have to pay for.
A line goes down and you re-staff the back half of a shift. A trucking delay pushes a receiving window and you pull two associates in early. Someone calls off and you fill the gap from the on-call list. In retail, a late change is a slow-Tuesday trim of one shift. In manufacturing and warehousing, that kind of change is the daily rhythm, which is why the same rule that barely touches a store can reshape a plant's labor cost.
"The operator's challenge is not intent. It is visibility: knowing, at the moment you move someone, whether that move just triggered a premium, and how much."Chicago Fair Workweek, manufacturing and warehouse
None of this makes the law unreasonable, and the ordinance asks for something achievable. The gap is operational, not ethical, which means it is the kind of gap a workforce management platform can actually close.
The fifteen exceptions, and where a plant and a DC part ways
Predictability pay is not owed for every late change. The ordinance lists fifteen exceptions in Section 6-110-050(d) of the Municipal Code[10], and the June 2026 rules make the entire predictability-pay obligation conditional on them: pay is owed for each employer-imposed change after the notice deadline "if not covered by an exception listed in Section 6-110-050(d)"[5]. The City itemizes all fifteen in its FAQ[3]. Several are ordinary operating events: a mutually agreed shift trade between workers, a change the worker requested, a subtraction of hours for a written and documented disciplinary reason, self-scheduling. Others are utility failures, acts of nature, and declared disasters.
One is written for manufacturers and nobody else. Exception 10, in the City's own rendering, reads: "Events outside the manufacturing Employer's control resulting in changes in the need for Covered Employees."[3]
A stopped line, a raw-material delay, an upstream supplier failure: those look to us like candidates for that exception. That reading is ours, not the City's. The Office of Labor Standards has not published guidance applying exception 10 to any specific event, and we could not read the statutory wording directly, because the code host the City links to returned an HTTP 403 to every request we made. The words quoted above are the City's summary of the exception in its FAQ, not the text of the ordinance[3][10]. Before that reading drives a real payroll decision, have counsel read the section itself.
Two limits matter as much as the exception does.
The exceptions do not reach the right to rest. The rules say so directly: the Section 6-110-050(d) exceptions do not apply to the right to rest[5], and the City's FAQ repeats it[3]. An event outside your control may take the predictability-pay charge off the table. It does not touch the 1.25 times premium.
The voluntary-change exceptions now require writing. A change the worker requested, a mutually agreed trade, the use of paid leave or PTO: all still exceptions, but the request has to be in writing to qualify, and where consent is required it has to be given for each individual change, time and date stamped, with general or ongoing consent explicitly insufficient[5]. A handshake swap on the floor is not an exception anymore. It is a predictability-pay charge with no paperwork behind it.
Then the divergence this post has to be honest about: there is no warehouse-services counterpart to exception 10. Nothing in the fifteen is written for a distribution center or a 3PL the way item 10 is written for a plant, and none of them covers a demand swing or a carrier failure at a warehouse[3]. Two operations on the same street, both covered, both flexing coverage the same way at 2 p.m., do not carry the same predictability-pay exposure. The DC absorbs it. The plant has an argument. If you run both in the city, they have to be modeled separately.
When the line goes down at 2 p.m.
Picture that re-staff. It is mid-shift, the line is stopped, and the scheduler is dragging three people onto the back half of the day to keep the floor running. The change is nine days inside the notice window, and one of those three is starting less than 10 hours after their previous day's shift ended.
What the operation just took on depends on facts the scheduler is not thinking about. The predictability-pay charge on those three adds is genuinely arguable: if the breakdown was an event outside the plant's control, exception 10 is in play, and any of the three who accepted the hours through the written offer process carries no predictability pay at all[3][5]. The right-to-rest premium is not arguable. It is 1.25 times the regular rate, it applies to the whole of that shift and to the whole of a double shift if that is what the worker ends up covering, no exception reaches it, and it is owed even if the worker asked for the hours[5]. There is also an amended schedule due to each of the three within 24 hours[3].
If the same 2 p.m. call happens in a distribution center down the road, the arguable part disappears. Exception 10 is not available there, so the predictability-pay charge stands unless those hours went through the offer process or the workers requested them in writing.
The scheduler has no idea about any of it, because the system they are working in was never told the Chicago rules exist.
I built WorkAxle so that the rule shows up at the moment of the change, not in the post-payroll reconciliation. And what has to be codified here is not one number. It is a two-tier test that turns on the 24-hour mark, an exception list that applies to one premium and not the other, a rest test measured from the end of the previous day's shift, and a written-offer path that switches the charge off. You configure that once, in a no-code rule builder, as a rule pack that belongs to your Chicago site. When a scheduler makes a move that would trip one of those rules, the engine surfaces it right there in real time, names the rule, and shows the cost the change would incur. The scheduler still makes the call, because keeping the line running may be worth the premium, and now they weigh it with the number in front of them instead of discovering it on the next check run.
That per-site design is what lets one deployment hold a whole footprint. Each location carries its own rule set, so your Chicago DC runs Chicago's rules while a plant in a state with no such law does not inherit rules it never had. WorkAxle is an enterprise workforce management platform built for the most complex, multi-union, multi-jurisdiction operations, where your own team configures the labor rules generic tools can't handle. It already automates multiple collective bargaining agreements and layered, site-specific rules in a single deployment, which is the same machinery a multi-jurisdiction fair-workweek footprint needs.
Want to see it on your own rules? Watch how the rule engine surfaces a predictability-pay cost at scheduling time.WorkAxle compliance rule engine
What should you do next?
Run the two-key test on your Chicago workforce this week. Confirm whether your operation clears the employer-size bar, then sort your Chicago hourly roster against the $64,945.55 line to see who is actually covered. That single exercise tells you the size of your exposure before a single premium is ever owed.
Then run the second pass, the one most operators skip. Separate your plants from your distribution centers and list the unplanned changes each site actually makes in a week. For every change on the list, ask two questions. Could it fall inside one of the fifteen exceptions, and could you document that it did? Could those hours have gone through the written offer of additional hours instead? That is where the exposure is actually managed, and the answers are different on a plant floor than they are on a dock.
Because that exposure accrues one unplanned shift change at a time, the fix is not a quarterly audit that catches problems after they hit payroll. It is seeing the predictability-pay and rest cost at the instant the change is made, while a scheduler can still weigh it against the reason for the change. That is the difference between managing the rule and paying for it.