Fair Workweek, Reporting-Time Pay & Schedule-Driven Premiums

Hotel labor demand is event-driven: a group adds sixty covers to Saturday's banquet, a citywide convention cancels, a storm empties the beach club. Predictive scheduling ("fair workweek") laws price exactly that volatility — and a hotel that doesn't know which of these laws reach it will either pay premiums it never owed or litigate premiums it never paid. Layered underneath are older schedule-driven rules — reporting-time pay, split-shift premiums, spread-of-hours — that quietly generate class claims of their own. This brief shows the premium math regime by regime, then prices the exposure on a stated banquet workforce.

The federal floor that isn't there#

Scheduling is structurally unlike every other issue on this site: the FLSA pays only for hours worked and says nothing about notice, cancellation, or rest between shifts. There is no federal predictive-scheduling statute and no federal reporting-time pay. The hierarchy collapses to two layers, and coverage is binary: a regime either reaches your hotel and supplies a complete premium schedule, or it does not and you owe nothing. The "highest floor wins" logic that governs minimum wage has no work to do — these are not floors stacked on a federal base but standalone codes, each with its own coverage test and dollar formulas. That is exactly why copying one jurisdiction's handbook into another is so costly (below).

Where fair-workweek laws actually reach hotels#

As of mid-2026, exactly five enacted predictive-scheduling regimes cover hotel operations — verified against each ordinance's covered-industry definitions:

Emeryville's ordinance is written around retail and fast food and does not reach hotels — neighboring Berkeley's does, two miles away. No state or city enacted a new hospitality-covering scheduling law in 2025–2026.

The premium math, regime by regime#

The five regimes share an architecture — good-faith estimate at hire, 14-day posted notice, predictability pay for employer changes, a clopening rest rule, access-to-hours, and recordkeeping — but the dollar formulas differ in ways that decide where the real exposure sits. Every figure below is the ordinance's own. Three structural variables drive the divergence: the rest-period threshold (9, 10, or 11 hours), the clopening multiplier (1.25× or 1.5×, or Philadelphia's flat fee), and Chicago's unique per-employee pay ceiling.

The change-inside-the-window premium is identical in all five — one hour at the regular rate — so high-frequency revision, not cancellation, is the dominant cost driver for a busy banquet department, as the worked examples below show.

Chicago's coverage cliff#

Chicago is the only one of the five with a per-employee pay ceiling, and it cuts a hard edge through a single banquet team. Coverage is tested employee by employee against $33.85/hour or $64,945.55/year from July 1, 2026, re-tested each July 1 — so an employee can move in or out of coverage from one summer to the next without any change in duties. A banquet captain paid just above the ceiling is outside the ordinance entirely: no predictability pay, no clopening premium, no good-faith estimate. The servers beside her at $20.00/hour are squarely inside it. The same canceled gala therefore generates premiums for the line servers and nothing for the captain who supervised them — and a one-dollar raise pushing a lead server past the ceiling silently removes that employee's protections (and the hotel's liability) on the next July 1 re-test. Re-scrub coverage rosters every July 1.

Where they don't — and what over-compliance costs#

The best-known scheduling laws do not cover hotels, and the dataset records why for each:

• New York City Fair Workweek — the most-cited scheduling law in the country — reaches fast-food chains (30+ locations nationally) and retailers (20+ city employees) only (N.Y.C. Admin. Code §20-1201 et seq.).
• San Francisco's Formula Retail Employee Rights ordinances reach formula retail chains (40+ establishments worldwide); a hotel is not a formula retail establishment (S.F. Police Code arts. 33F–33G).
• Seattle Secure Scheduling covers retail and food-service firms (500+ worldwide); hotels are reached instead by Seattle's separate 2019 Hotel Employee Protections package (SMC chs. 14.26–14.29 — workload caps, panic buttons, retention), which imposes no scheduling premiums.
• LA City Fair Work Week covers retail businesses (NAICS 44–45, 300+ employees); hotels sit in NAICS 721 and are regulated through the hotel-worker minimum wage and Hotel Worker Protection Ordinance instead, neither adding scheduling premiums (LAMC ch. XVIII art. 5).
• LA County (eff. July 1, 2025 — the newest ordinance in the country) is retail only, 300+ employees, unincorporated areas; it excludes hotels.
• Emeryville covers retail and fast-food firms only — a hotel is neither, though Berkeley's hotel-covering ordinance applies two miles away (Emeryville Muni. Code ch. 5-39).

The common thread: coverage follows the business, not the building. A leased Starbucks, a 40-location branded restaurant, or a 300-employee retailer operating inside the hotel can be independently covered as retail or fast food even where the hotel is not.

The over-compliance trap Policy teams that read "Seattle has predictive scheduling" and bake 14-day notice plus premium pay into the national handbook convert a non-obligation into a contractual one. Quantify it: a single banquet department revising the posted schedule twice weekly hands out roughly $26,000/year in voluntary one-hour premiums under the model below — at one property, in a city that imposes nothing; multiply across a non-covered portfolio and the gift runs to seven figures. Voluntary notice is good practice; voluntary premium entitlements in a handbook are a gift to the plaintiffs' bar. Write premiums as jurisdiction-specific addenda only.

Exposure anatomy#

Predictability pay accrues per change, per employee, per week — and the same ordinances that create the liability require the employer to keep the records that prove it. The statute supplies the remedy directly (one hour per change, the half-shift figure per cancellation, the rest premium per clopening), with no liquidated multiplier in the formula — so exposure scales by volume, not penalty tier, which makes it deceptively cheap per event and ruinous in aggregate.

Litigation risk — the records prove the case The expensive pattern: banquet management treats the BEO as the schedule and revises staffing daily by group chat. Every employer-initiated revision inside 14 days is potentially an hour per affected server; each cancellation inside 24 hours costs the half-shift figure — per person, per change. The trap is structural: the ordinances require the employer to retain schedule versions, change consents, and premium-payment records, so the plaintiff need not reconstruct the violations — the employer's own mandated records (and the group-chat thread) are the proof of frequency. Burden mechanics live in recordkeeping; the point here is narrower and worse: these ordinances manufacture the plaintiff's evidence by design.

California's reporting-time stack#

California has no predictive-scheduling statute (Berkeley's city ordinance is the only California fair-workweek law, and it reaches only Berkeley). But the conduct those laws price — cutting a shift on a soft night — is priced in California by an older rule: reporting-time pay. An employee who reports but is put to work for less than half the scheduled shift is owed half of it — minimum 2, maximum 4 hours — at the regular rate (IWC Wage Order 5 §5). For an 8-hour banquet shift cut on arrival, that is the 4-hour maximum.

Ward v. Tilly's (2019) closes the obvious workaround: an on-call check-in is a report. A housekeeper or banquet server required to phone in two hours before a possible shift "reports" by phone, and being told not to come triggers reporting-time pay though she never entered the building. That kills the call-in alternative in California — a hotel cannot dodge the premium by swapping an on-site call for a mandatory phone-in. The exceptions (threats, utility failures, acts of God) do not include slow occupancy.

Decision framework — three schedule architectures#

A covered hotel chooses how to absorb event-driven volatility. Three architectures, priced:

• (1) Post 14+ days out and absorb premiums for true emergencies. The schedule locks on cadence; genuine same-week changes pay one hour each, cancellations the half-shift figure. Cost is predictable (≈$26,000/season for a 25-person department revising twice weekly, per the model above). Best where event mix is stable — changes are occasional and the premium beats the rigidity of the alternatives.
• (2) Staff to a conservative floor plus a voluntary pickup board. Schedule a lean baseline, then fill peaks from a documented, employee-initiated pickup board. Employee-initiated swaps and pickups carry no predictability pay in any regime — the premium attaches only to employer-initiated changes (verify each ordinance's exception text first). The cost is the discipline to keep the board genuinely voluntary: a manager who "asks" a specific employee to pick up has arguably initiated the change. Best where event mix is volatile and the workforce can self-fill peaks — the single highest-value compliance tool a covered hotel has.
• (3) Oregon standby list. Oregon's statute blesses a formal voluntary standby list: opt-in employees can be offered extra hours without triggering predictability pay, and remain free to decline. It immunizes only the upward change — not employer-initiated cancellations or clopenings — and is an Oregon device with no equivalent in the other four regimes. Best in Oregon as a complement to (2), not a substitute.

Recommendation, by event-mix volatility: stable banquet calendars (corporate group houses, contract-driven occupancy) should run (1) — a manageable line item, and locked schedules reduce turnover. High-volatility properties (citywide convention hotels, weather-driven resorts) should run (2), backstopped by (3) in Oregon. In all cases route BEO-driven staffing through the change workflow, not a group chat, so genuinely employee-initiated changes are documented as such — the documentation is what converts the pickup board from theory into a defense.

How this compounds — interaction map#

Scheduling premiums transmit into three other issues through specific mechanisms, not mere adjacency.

Regular-rate coding (29 CFR 778.220). The transmission has two opposite legs, and miscoding either is the exposure. The unworked portion of show-up and schedule-change premiums — predictability pay for a canceled shift, reporting-time pay for time not worked — is not payment for hours worked, so it stays out of the FLSA regular rate (DOL's 2019 rule says so). But the extra pay for worked clopening hours — the 0.25× or 0.5× premium on hours actually on the clock — is compensation for work performed and must feed the overtime calculation. So idle-time premiums need a non-regular-rate earnings code and the clopening uplift a different code that feeds the regular rate; collapse the two and you either inflate overtime you don't owe or understate overtime you do. Full treatment in overtime and the regular rate.

Off-the-clock discovery. The group-chat staffing churn that triggers predictability pay is the same record that proves off-the-clock work — a manager texting "come in early, we'll fix the punch later" is discoverable evidence of both a schedule-change premium and unpaid pre-shift time. The two claims travel together because they live in the same thread.

Minors share the rule engine. Minor-hour restrictions — daily and weekly caps, prohibited late-night hours — run on the same scheduling system that drives fair-workweek compliance; an engine that ignores predictive-scheduling rules tends to ignore minor-hour limits too, so one rule engine should enforce both (see minors). And the predictability premiums are wages in California once owed, so the derivative wage-statement and waiting-time machinery can attach — that stack is developed in PAGA and class actions and applied here, not re-taught.

Reporting-time pay: the older premium layer#

Long before "fair workweek," several states priced the wasted trip to work. Unlike the fair-workweek laws, these rules reach every hotel in the state with no size threshold — and they price exactly the soft-night cut that fair-workweek laws reach elsewhere.

New York: hospitality call-in pay#

Under the Hospitality Industry Wage Order, an employee who reports to work must be paid at least three hours for one shift (or the full scheduled shift if shorter) — hours worked at the regular rate, the unworked balance at the basic minimum wage with no tip credit (12 NYCRR 146-1.5). A banquet server told at the door that the function shrank still costs three hours; the unworked portion is excluded from the regular rate, mirroring the federal treatment above.

The rest of the map#

Massachusetts pays three hours at minimum wage when an employee scheduled for 3+ hours reports and is sent home (454 CMR 27.04(1)). New Jersey guarantees one hour at the regular rate (N.J.A.C. 12:56-5.5); Connecticut's restaurant and hotel-restaurant wage order guarantees two hours' minimum daily earnings (Conn. Agencies Regs. §31-62-E1); D.C. pays four hours — worked hours at the regular rate, unworked at minimum wage (7 DCMR §907); Rhode Island three hours at the regular rate (R.I. Gen. Laws §28-12-3.2); New Hampshire two hours at the regular rate (RSA 275:43-a). Details by state in the 50-state center.

California's split-shift premium#

A split shift — a schedule interrupted by unpaid time beyond a bona fide meal period — costs one additional hour at the minimum wage per day (IWC Wage Order 5 §4(C)); the catch that saves employers is that wages paid above the minimum for that day offset the premium. The banquet lunch/dinner split is the canonical hotel example.

New York's spread of hours#

New York prices long days rather than split ones: whenever the spread of hours — the interval from the first minute of the workday to the last, including meal breaks and split-shift gaps — exceeds 10 hours, the employee is owed one extra hour at the basic minimum wage ($17.00 downstate, $16.00 upstate for 2026) on top of all wages, regardless of how much the employee earns (12 NYCRR 146-1.6).

The front desk is the classic trap: an agent covering 7:00 a.m. to 7:30 p.m. — even with a long off-duty afternoon break — has a 12.5-hour spread and is owed an extra $17.00 in New York City. Housekeepers returning for evening turndown and banquet staff working a breakfast plus a gala dinner hit the threshold constantly; payroll systems that see only paid hours never catch it. The wage order requires spread-of-hours records, so the claim is easy to prove — and cheap to settle only when caught early.

Compliance checklist#

• Coverage matrix per property: the five hotel-covering fair-workweek laws, employer-size thresholds re-tested annually (Chicago recalibrated June 1, 2026).
• Chicago coverage roster re-scrubbed every July 1: flag any employee paid near $33.85/hour or $64,945.55/year, where a raise moves them out of coverage and a freeze moves them in.
• No fair-workweek premium promised in any national handbook; jurisdiction-specific addenda only (the over-compliance trap is ≈$26,000/season per department).
• Schedules published on a fixed 14-day cadence at covered properties; every post-publication change coded as employee-initiated, excepted, or premium-bearing, with the premium type (change / cancellation / clopening) tagged for payroll coding.
• Shift-swap and pickup-board procedures documented and kept genuinely employee-initiated; Oregon standby list papered per statute (immunizes only added hours, not cancellations or clopenings).
• Banquet staffing routed through the schedule-change workflow, not group chat — the same thread is discoverable for off-the-clock claims.
• Clopening conflicts flagged at schedule build — night audit handing off to morning shifts trips the 9-to-11-hour rest rules, at a cost varying up to 2.7× by jurisdiction.
• Reporting-time and call-in premiums automated in every mandating state (California, New York, Massachusetts, New Jersey, Connecticut, New Hampshire, Rhode Island, D.C.); California call-in reviewed against Ward v. Tilly's and computed at the local hotel-worker minimum where one applies.
• Split-shift and spread-of-hours engines tested against banquet splits and 10+ hour spreads; premiums shown as wage-statement line items.
• Earnings codes split so unworked predictability/reporting premiums stay out of the regular rate while worked clopening uplift feeds overtime.

Key authorities#

• ORS 653.412–653.485 (Oregon Employer Work Scheduling Law); ORS 653.455 (predictability pay); ORS 653.442 (rest between shifts / standby list).
• Chicago Mun. Code §6-110-050, §6-110-060 (Fair Workweek Ordinance) and BACP rules effective June 1, 2026; Evanston City Code §3-34 (eff. Jan. 1, 2024).
• Philadelphia Code §9-4604, §9-4605 (Fair Workweek Employment Standards Ordinance).
• Berkeley Mun. Code §13.102.060, §13.102.070 (Fair Workweek).
• N.Y.C. Admin. Code §20-1201 et seq.; S.F. Police Code arts. 33F–33G; Seattle Mun. Code ch. 14.22; LAMC ch. XVIII art. 5 (§185.00 et seq.); Emeryville Muni. Code ch. 5-39 (non-coverage of hotels).
• IWC Wage Order 5-2001 §§4(C), 5; Ward v. Tilly's, Inc., 31 Cal.App.5th 1167 (2019).
• LAMC §186.00 et seq. (Citywide Hotel Worker Minimum Wage Ordinance, as amended by Ord. 188944).
• 12 NYCRR 146-1.5 (call-in pay), 146-1.6 (spread of hours).
• 454 CMR 27.04(1) (Mass.); N.J.A.C. 12:56-5.5; Conn. Agencies Regs. §31-62-E1; 7 DCMR §907; R.I. Gen. Laws §28-12-3.2; N.H. RSA 275:43-a.
• 29 CFR §778.220 and DOL's 2019 regular-rate final rule (premium excludability).