A schedule has to satisfy two sets of rules. One is written by legislators and varies by state and sometimes by city; the other is written by nobody and is enforced by people quitting. Both are cheaper to respect than to fix afterwards.
⚖️ The rules that live inside the schedule
These are the ones that touch scheduling directly. What follows is what to look up, not legal advice — rules differ by jurisdiction and they change:
- Breaks and meal periods. Many states set when a break is owed and whether it is paid. The scheduling tool can prompt for them; whether they actually happen is a floor-management question.
- Minors. Hour limits, late-night restrictions and school-day rules are strict and are enforced. If you employ anyone under 18, put their limits into the system so a schedule cannot break them by accident.
- Advance notice. A number of cities have predictive or fair-workweek scheduling rules: publish a set number of days ahead, pay a premium for late changes, and offer extra hours to existing staff before hiring. If you are in one of those cities this is not optional, and the penalties are per shift.
- Rest between shifts. Closing then opening the next morning — a "clopening" — is restricted or compensated in some places, and is a bad idea everywhere.
- Records. Keeping schedules, punches and changes for the required period is the boring habit that decides a wage dispute. Your tool does this automatically if nobody deletes anything.
Overtime is the obvious neighbour to all of this, and it is a cost question rather than a scheduling one. What it costs, how to forecast it and how to avoid paying for it are the next course in the catalog.
⚖️ Fairness, which is a scheduling problem
The good shifts and the bad shifts are not distributed by accident, and staff can tell you exactly how they are distributed. Some workable rules:
| The question | A rule that survives contact |
| Who gets the busy, high-tip shifts? | Say it plainly: seniority, performance, or rotation. Any of the three is fine. Unstated is not |
| Who works holidays? | A rotation published in advance, so it is a turn and not a punishment |
| Who closes? | Rotate it, or pay for it. Do not let it settle on whoever complains least |
| Who gets extra hours? | Offer openly to everyone qualified. In some cities this is also a legal requirement |
| Whose request gets approved when two clash? | First in, or an alternating rule. Decide before it happens, not while both are waiting |
Then audit yourself once a quarter. Pull the last twelve weeks and count who worked which shift types. If the pattern is not what you believed, you have just found the reason someone has been quietly unhappy.
⏰ Honest hours
- People clock themselves in and out. Not a manager doing it for them, and not one employee clocking in another. If punching is from personal phones, use whatever location check the tool offers.
- Edits leave a trail. A punch correction is normal — someone forgot. A pattern of corrections by the same manager is worth a look, and the tool will show it.
- Nobody works off the clock. Not the ten minutes of setup before punching in, not the cleanup after punching out. This is where wage claims come from, and it is usually a well-meaning habit rather than anyone's bad intent.
- Approve hours before payroll, weekly. It is fifteen minutes and it is the last moment errors are cheap.
- Scheduled hours and paid hours are different numbers. The gap between them is the subject of the next topic.
🗣️ Cutting hours, which everyone handles badly
January arrives, sales drop, hours have to come down. Doing it silently through the schedule is the most common way restaurants lose good people, because from the other side it is indistinguishable from being pushed out.
Say it before it appears: what is happening, roughly how long, how you are deciding who is affected, and what would change it. People accept a bad month explained to them and start job-hunting over a bad month delivered by notification.