Setting Fair and Legal Break Policies
How to set a restaurant break policy that's fair to staff and compliant with state law — meal breaks, rest breaks, and how to document them correctly.
A fair and legal restaurant break policy starts with knowing your state's specific meal and rest break rules — they vary far more than most owners expect — then writing a policy that's realistic for a working shift, documented consistently, and applied the same way to every employee regardless of how busy the shift is.
Break requirements vary significantly by state, and some states have no meal or rest break requirement at all. Confirm your specific state's rules before finalizing a policy — this article explains the general landscape, not legal advice for your location.
Two different kinds of breaks
- Meal breaks are typically longer (30 minutes or more) and unpaid, because the employee is expected to be fully relieved of duty — not eating standing up at the pass while watching tickets.
- Rest breaks are typically shorter (10-15 minutes), paid, and don't require the employee to be fully off duty in the same way.
Some states require both, tied to shift length; others require neither and leave it to employer policy. This is the single biggest reason a policy copied from a friend's restaurant in another state can be a compliance problem.
| Shift length | Common requirement pattern (varies by state) |
|---|---|
| Under 5 hours | Often no meal break required |
| 5-8 hours | One unpaid meal break commonly required |
| Over 8 hours | Additional break or second meal period in some states |
| Every 4 hours worked | Rest break sometimes required regardless of shift length |
The compliance trap specific to restaurants
Because restaurants run on tickets and tables, it's common for an employee to be interrupted during an unpaid meal break — asked a quick question, or pulled back to help for two minutes. If a break is legally required to be duty-free and it's regularly interrupted, that break may not legally count as a break at all, which can create wage liability even though nobody intended it.
How to actually protect a meal break
- Have a clear signal (a specific chit, a note on the schedule board) that shows who's on break.
- Cross-train enough staff that one person stepping away for 30 minutes doesn't create a crisis — see Cross-Training Staff to Improve Flexibility.
- If someone is pulled back during a legally required unpaid break, pay them for the interruption and restart the break, or document it as a paid break for that instance.
Takeaway: The break policy on paper matters less than whether breaks actually happen uninterrupted in practice — an on-paper policy that's routinely violated during real shifts is often worse than having no formal policy at all, because it creates a paper trail of the violation.
Document it consistently
Log break start and end times for every shift, not just when something goes wrong. A simple log protects you if a break-related wage claim ever comes up, and it surfaces patterns — like one shift that never manages to get proper breaks in — before they become a habit.
Put it in the handbook and the schedule
Your break policy should be written plainly into your employee handbook and reflected in how you build the schedule — schedule enough coverage that breaks are actually possible during a rush, not just on paper.
Use the worksheet below to log break times by shift and flag any that were interrupted or skipped, so you catch a pattern before it becomes a liability.
Enforcement lives in the time clock. If your POS time clock prompts a break punch and flags shifts that ran past the break threshold without one, the manager sees the miss the same day instead of at a wage claim. Cobblestone POS includes time clock and scheduling with the POS, which makes the break record a byproduct of clocking in rather than a separate task.
Bottom line
Know your specific state's meal and rest break rules, staff enough that breaks are realistic during a real shift, and document what actually happens — not just what the policy says should happen.
Break Policy & Log Template