Chicago’s Fair Workweek rules apply only when both your business and your workers meet the coverage tests. I start there - not with the event type. If your staff are covered, post schedules 14 days ahead and review late changes before payroll.
Here’s the checklist I use:
My rule: <u>a client’s booking change is also a scheduling and payroll decision</u>. Quickstaff can help organize the details, but software does not replace a compliance review.
Chicago Fair Workweek: Event Staffing Compliance
Once coverage is confirmed, move from eligibility to scheduling. Use event staff scheduling software or a written process for each event: turn every booking into a posted schedule and record any later changes. Keep the good-faith estimate separate from the posted schedule. The estimate projects work for the first 90 days before hiring; the posted schedule lists specific assignments.
The first deadline is the 14-day schedule notice.
Provide the written schedule at least 14 calendar days before its first day. Include work dates, start and end times, locations, and any on-call assignments. Post it where workers can access it, send it through the usual channel, or both. Employees may request electronic delivery. Keep the original schedule and every revision.
Covered workers may decline previously unscheduled hours offered within 14 days of the schedule’s start. This includes early setup, extended service, or added breakdown time.
For each added hour or revised call time, send a written offer with the date, hours, location, role, and response deadline. Record whether the worker accepted, declined, or did not respond, and keep that response with the schedule record. Never suggest that declining added hours will mean fewer future assignments, removal from a waitlist, or other retaliation. Send every accepted change to payroll for predictability-pay review.
Before hiring new workers or using temporary staff for available work, check whether qualified current covered employees must get the opportunity first. Use objective qualification standards, explain the assignment and how to accept it, allow a reasonable response period, and retain the offer and response records.
Chicago guidance also addresses temporary or seasonal workers with at least two weeks of service. Tracking availability helps, but it does not replace a documented offer and response window.
Check consecutive event shifts for a 10-hour rest period. A covered employee may decline a shift that starts less than 10 hours after the previous day’s shift ends. If the employee accepts and works that shift, Chicago guidance calls for pay at 125% of base pay for the affected shift.
Use one written process to review schedule requests. Apply the same standards each time, document the decision, and prohibit retaliation.
When a booking changes, turn the revised schedule into payroll records before the next payday. Before running payroll, collect the original and revised schedules, change timestamps, affected hours, worker rate, reason for the change, and worker response. Predictability Pay is generally due no later than the next payday for the pay period when the change occurred. Show it separately on the wage statement or other employee documentation.
Predictability Pay generally provides one additional hour of pay at the regular rate for a qualifying change within the 14-day window. If scheduled hours are reduced or canceled with less than 24 hours’ notice - including when a worker is sent home - the employee generally receives 50% of regular pay for the lost hours. Check each rule separately; don't automatically stack the payments. Predictability Pay is additional compensation, not overtime.
Use the change log to determine whether Predictability Pay, lost-hours pay, or both apply.
| Change type | Notice timing | Pay owed |
|---|---|---|
| Added hours | Within the 14-day window | Generally one additional hour of Predictability Pay; check exceptions. |
| Shift date or start/end time moved | Within the 14-day window | Generally one additional hour of Predictability Pay. |
| Shift shortened or canceled | Within 14 days, but more than 24 hours before the shift | Generally one additional hour of Predictability Pay. |
| Shift shortened, canceled, or worker sent home | Less than 24 hours’ notice | Generally at least 50% of regular pay for the hours lost. |
Review location changes case by case. Don't assume they're exempt; check the ordinance text and records.
Consent must cover the specific change. Separate employer-directed changes from worker-requested changes, qualifying voluntary shift exchanges, leave-related changes, and other recognized exceptions. For consent-based exceptions, keep written or electronic evidence showing the shift, change, date, and worker response. A casual text does not prove a consent-based exception.
Check the applicable rules and guidance against the ordinance in effect on the change date. Changes of 15 minutes or less generally don't require Predictability Pay. A client cancellation isn't a blanket exception: document the recognized exception or calculate the required compensation.
Hypothetical: A covered event worker earning $20.00 per hour loses a 6-hour shift with less than 24 hours’ notice. If the rule applies and no exception exists, the lost-hours payment is 6 × $20.00 × 50% = $60.00. That $60.00 compensates for the scheduled hours the worker lost; it is not pay for hours worked. Review Predictability Pay separately rather than automatically adding another $20.00.
Record regular wages, overtime, Predictability Pay, and lost-hours pay separately. Keep the calculation in the event’s payroll file.
Use the same review process every time a client changes a booking.
Before editing a worker’s schedule, review every client-requested booking change through one documented process.
| Client change | Scheduling action and records |
|---|---|
| Cancellation | Keep the original schedule, log the cancellation timestamp, and review the 24-hour pay rule. |
| Guest-count reduction | Treat the cut as employer-driven, not voluntary. Document the revised staffing plan and worker communications. |
| Delayed start | Send the revised start time and keep the original schedule version. |
| Venue change | Confirm the new location, reporting instructions, and any time change. Log the worker’s acknowledgment. |
| Added service hours | Offer hours to qualified current workers first. Document the offers and responses. |
| Replacement assignments | Check availability without displacing scheduled workers. Keep the reason for the replacement and the final assignment. |
After logging the change, update scheduling, payroll, and recordkeeping. Notify affected workers and send the change for pay review.
Quickstaff can help track booking changes, staff availability, and event messages. For compliance, keep separate records of schedule versions, consent, and payroll.
Keep client requests, original and revised schedules, worker offers and responses, pay calculations, and proof of payment for at least three years. Keep them longer if a claim, audit, or hold applies.
Post required Chicago notices at each covered site. Provide labor-law information with the first paycheck and again annually.
Train managers on anti-retaliation rules, and preserve records when a worker reports a concern.
Use this checklist to close each event file before payroll is finalized.
Quickstaff can help with scheduling, but a named reviewer must confirm compliance with current Chicago guidance and legal counsel.
Yes, temporary event workers generally have labor protections if they’re employees rather than independent contractors. Under federal law, nonexempt temporary employees have the same minimum wage, overtime pay, and workplace safety protections as permanent staff.
In Illinois, covered roles typically include banquet servers, bartenders, setup crews, ushers, and concessions staff. The actual working relationship determines classification - not just a label calling someone a contractor.
Chicago’s predictive scheduling laws require advance notice of work schedules. Booking an event or changing schedules with less than 14 days’ notice may trigger premium pay or specific notice requirements.
Quickstaff keeps clear, time-stamped records of communications and confirmations in one place. It also helps you manage staff availability, waitlists, and event rosters. These records support compliance with local regulations and help you avoid penalties for noncompliance.
Responsibility depends on the agreement between the staffing agency and the third-party client. They may share joint-employer duties, so contracts must clearly assign responsibility for scheduling, wages, and recordkeeping.
When Chicago’s predictive scheduling rules require premium pay for last-minute changes, determine who controls scheduling and pay. That helps establish which party is legally responsible for correcting violations or paying the required compensation.
