1. Rules
The numbers behind the preset (edit any of them)
Presets are a starting point, not a legal reading. Cities amend these rules and apply them by employer size and industry. Check each number against your city's official guidance.
2. Posted schedule
3. Changes after posting
Paste a schedule and a posting time, then click Check.
Result
| Employee | Shift starts | Issue | Notice (h) | Premium | Detail |
|---|
How it works
Late posting: a shift that starts less than the required number of days after the posting time is flagged. No dollar figure is added because the remedy differs by city.
Changes: adding hours or moving a shift without losing hours is measured against the add/move window, and cancelling or cutting a shift against the cut/cancel window. Notice is the time from when the worker was told to the earlier of the old and new start. The premium is the flat dollars plus the hours of pay, or the share of pay for the hours lost, from the boxes above.
Rest: after all changes are applied, any two shifts for the same person closer together than the minimum rest are flagged, and the hours that fall inside the rest window are priced at the multiplier. The worker's written consent is required to schedule it at all.
Not modelled: employer-size and industry coverage, emergency exceptions, daylight-saving shifts, and any city rule other than the numbers you can see. Worker-requested changes can be marked requested to exclude them.
Related tools: the shift roster builder to build the schedule in the first place, and the overtime pay calculator for the hours that spill past 40.
Checked: the test suite recomputes hand-worked Seattle and Chicago cases, including the exact boundary at 14 days and 24 hours.
Common questions
What is a fair workweek or predictive scheduling law?
A city or state rule that makes larger retail, restaurant and hospitality employers post work schedules in advance, usually 14 days, and pay the worker extra when the employer then adds hours, moves a shift or cancels one at short notice. Seattle, Chicago, New York City, Philadelphia, San Francisco, Los Angeles and Oregon each have their own version with different thresholds and different premiums.
How do I check a schedule for predictive scheduling violations?
Paste the posted schedule and the date it was posted, paste each later change with the time the worker was told, pick the city preset or type your own numbers, and the page lists every shift that was posted too late, every change made inside the notice window with the premium pay it triggers, and every closing-then-opening pair that breaks the rest rule.
How is predictability pay calculated?
It depends on the city. Under the Seattle and Chicago presets a change that adds hours or moves a shift inside 14 days costs one hour of pay at the worker's regular rate, and a cancellation or cut inside the window costs half the pay for the hours not worked. The page applies the numbers in the boxes, which you can overwrite to match the current text of your own ordinance.
Are these city numbers current and complete?
No promise. The presets are a starting point written from the public ordinance summaries, ordinances are amended, thresholds depend on employer size and industry, and there are exceptions such as worker-requested swaps and emergencies. Check the figures against your city's official page or your attorney before you rely on them, and edit any box that is out of date.
Does it handle worker-requested changes and emergencies?
Mark a change line with a final field of requested and the page counts no premium for it and reminds you to keep the written request. Emergency and other statutory exceptions are not modelled; leave those lines out and keep your own record.
Is my staff schedule uploaded anywhere?
No. Everything is calculated in your browser, nothing is sent to a server, and there are no accounts. Names stay on your device.