Washington State Lunch Break Laws: Meals and Rests

Washington state lunch break laws require a meal period of at least 30 minutes that starts no sooner than two hours and no later than five hours into the shift, plus a paid 10-minute rest period for every four hours worked. Nobody can be required to work more than five consecutive hours without a meal, or more than three hours without a rest.

Those rules come from WAC 296-126-092, and they apply to almost every non-agricultural employee in the state regardless of company size. Washington meal and rest break rules exist because there are no federal lunch break laws underneath them, which is why the answer changes at every state line. Washington sits in the strict half of the country on breaks, closer to California than to Texas, but the mechanics are different enough that copying a California policy across the border gets you the wrong answer. Here is what the rules actually say, what a violation costs, and how to record breaks so you can prove compliance a year later.

What do Washington state break laws require by shift length?

The break laws Washington state enforces run meal and rest breaks on separate counters, the same as in California, but Washington ties the meal to a window rather than a single deadline. This table covers the common shift patterns.

Shift length	Meal periods	Rest periods
Under 5 hours	None required	One paid 10-minute rest
5 to 8 hours	One 30-minute meal, starting between hour 2 and hour 5	Two paid 10-minute rests
8 to 10 hours	One 30-minute meal	Two paid 10-minute rests
10 to 12 hours	One 30-minute meal, plus a second if the shift runs 3 or more hours past a normal workday	Three paid 10-minute rests
12 hours or more	Two 30-minute meals	Three or more paid 10-minute rests

The overtime meal rule is the one nobody remembers. Employees "working three or more hours longer than a normal work day shall be allowed at least one thirty-minute meal period prior to or during the overtime period." If your normal day is 8 hours and someone works 11, that second meal is owed, even if they already had lunch at hour 4.

The two-to-five hour window trips up more employers than the length

Most owners know about the 30 minutes. Fewer know the meal cannot start too early. A 7:00 a.m. opener who takes lunch at 8:30 has taken it at hour 1.5, and that meal does not satisfy the rule, because the regulation says the meal period must commence "no less than two hours nor more than five hours from the beginning of the shift."

The late side is the more common problem. Same 7:00 a.m. start means lunch has to begin by noon. Push it to 12:30 because the morning ran long and you have a violation, plus a separate one under the rule that "no employee shall be required to work more than five consecutive hours without a meal period."

Whether employees can waive lunch breaks has a two-part answer here. Meal periods can be waived in Washington when the employee and the employer both agree, and that part is not unique to the state, since California lunch break laws allow a meal waiver too under Labor Code 512(a) when the workday runs six hours or less. What matters in either state is that the waiver is the employee's choice rather than a scheduling decision made for them, and that they can revoke it. Get it in writing, because a verbal agreement is worth very little when a claim arrives two years later.

Rest breaks are different, and this is the line employers cross most often: an employee cannot waive a rest break. L and I states plainly that employees "cannot waive rest break requirements." A worker who would rather leave 10 minutes early than stop mid shift is not allowed to make that trade, and an employer who lets them is out of compliance even though everybody agreed.

When does a Washington meal break have to be paid?

A meal period is unpaid only when the employee is genuinely free of the job. WAC 296-126-092 says meal periods "shall be on the employer's time when the employee is required by the employer to remain on duty on the premises or at a prescribed work site." The trigger is being kept on duty. Requiring someone to stay on site is allowed without paying for the meal, but only if they are completely free from work duties for the whole break. As L and I puts it, employers do not have to pay for a meal break when the employee "is free from all duties for their entire break." Answering the phone, watching the counter, or covering the floor is duty, and that is what makes the meal paid.

That catches a lot of real setups. A lone retail clerk who has to stay in the store during lunch. A job-site crew told to stay on site because the gate gets locked. A front desk person eating at the desk. In each case the meal is paid time, and if the employee also worked, that time counts toward the 40-hour overtime threshold as well.

Interruptions do not restart the clock, they extend it. An employee who is pulled back into work owes nothing extra in minutes beyond reaching 30 total minutes of actual mealtime, excluding the interruptions. L and I is explicit on both halves of this: the employee is "still entitled to 30 total minutes of mealtime, excluding interruptions," and "the entire meal period must be paid regardless of the number of interruptions." So if someone punches out at 12:00 and gets pulled back at 12:12, you owe them the remaining 18 minutes of uninterrupted mealtime, and the whole period is paid. You do not owe a fresh unpaid 30. Rest periods are simpler: they are always "on the employer's time," so employees never punch out for one.

Rest periods, the three-hour rule, and intermittent breaks

Washington rest period law requires a rest of not less than 10 minutes on the employer's time for each four hours of working time, scheduled "as near as possible to the midpoint of the work period." On top of that, no employee can be required to work more than three consecutive hours without a rest. Both conditions have to hold, which is why a scheduled 10-minute break at hour 3.5 fails even though the four-hour math worked out.

Washington does allow an alternative for jobs where the work naturally comes in waves. If the nature of the work permits employees to take intermittent rest periods equivalent to 10 minutes for each four hours worked, scheduled breaks are not required. Think of a slow-shift front desk or a delivery route with real gaps. That flexibility is easy to abuse, so document why the role qualifies rather than assuming it does.

Rest breaks cannot be combined with a meal period to make a longer lunch, and employees cannot bank them to leave early. Both patterns are common and both create liability.

What does a missed break cost in Washington?

Washington does not use California's one-hour premium. The remedy is narrower: the employee is owed pay for the break time they should have had, plus interest, and the state Department of Labor and Industries can order back wages after a worker files a complaint. Willful violations can add civil penalties.

Narrower does not mean cheap, because missed rest breaks compound quietly across a whole crew. Take a business paying the 2026 Washington state minimum wage of $17.13 per hour, up from $16.66 in 2025, with employees regularly missing one 10-minute rest per day. That is 41.7 unpaid hours a year for one person, about $714.

The bigger risk is that a rest break complaint rarely arrives alone. An L&I investigation into breaks tends to pull in overtime calculations, minimum wage compliance, and record keeping in the same visit, which is why the rate you pay matters twice over. Our Washington minimum wage guide tracks the annual January adjustment, and the Washington overtime rules page covers the weekly 40-hour math.

What happens to unpaid break time when someone leaves

Missed break pay doesn't disappear at separation, it moves into the last check. Washington final paycheck rules come from RCW 49.48.010, which says that when an employee stops working, "whether by discharge or by voluntary withdrawal," the wages due "shall be paid to him or her at the end of the established pay period." There is no same-day rush the way California handles it, and there is also no room to leave anything out.

That is where sloppy break coding turns expensive. If rest periods were logged as unpaid, or a meal got deducted on a day the employee never left the counter, the final check is short, and a short final check is a wage complaint that arrives with its own paper trail. Reconcile break coding before the last check goes out, not after L and I calls.

Minors, and where Washington layers on more

Teen employees get more protection, not less. Federal child labor rules apply here in full: 29 CFR 570.35 caps 14 and 15 year olds at 3 hours on a school day and 18 hours in a school week, 8 hours on a non-school day and 40 in a non-school week, within a window of 7 a.m. to 7 p.m. that extends to 9 p.m. from June 1 through Labor Day. Washington adds its own hour limits and paperwork requirements on top, and where the two systems differ, the stricter rule wins.

Break timing for minors is tighter too. Practically, if you employ high schoolers in a restaurant or grocery store, build the schedule around the teen limits first and fill in adult coverage after. Retrofitting a compliant schedule at 4 p.m. on a Friday never goes well.

Six scheduling habits that break the rules without anyone noticing

Every one of these comes from the regulation above, and every one of them looks completely normal on a schedule.

• Lunch at 9:30 for a 9:00 start. Too early. The meal has to begin at least two hours into the shift, so it does not count.
• The 5.5-hour shift with no meal. Anything past five consecutive hours of work requires a meal period, even on a short shift.
• One rest break on an 8-hour day. Two are owed, and the three-consecutive-hours rule means the first has to land early.
• Combining both rests into a 20-minute coffee break. Rests cannot be stacked, and they cannot be bolted onto lunch to make a longer meal.
• Letting people skip rests to leave 20 minutes early. Employees like it, and it is still a violation plus an unpaid-time problem.
• Treating an 11-hour day like an 8-hour day. Three or more hours past a normal workday triggers a second 30-minute meal.

None of these are exotic. They are what happens when a schedule gets built around coverage and the break rules get applied afterward, by memory, during a rush.

Setting up your time clock for Washington compliance

Washington break compliance is mostly a timing problem, and timing problems get solved by software that watches the clock better than a busy shift lead can. The setup that works:

1. Track meal start time against shift start, not against the clock on the wall. The rule is a window measured from when the shift began.
2. Alert at hour 4.5. A manager nudge half an hour before the deadline prevents nearly every late-meal violation.
3. Make meals a real punch out and back in. Auto-deduction cannot tell you whether the meal started in the window.
4. Keep rest breaks paid and on the clock, with a minute cap. A rest coded at 10 minutes that runs 25 should show as an exception, not vanish into the shift.
5. Store waivers with the employee record. A verbal waiver is legal and worthless in a dispute.
6. Keep an audit log of punch edits. Who changed a meal punch, when, and why.

Kloqk's free time clock handles the pieces that matter here: paid and unpaid break types with minute caps, exact meal punches instead of assumed ones, and an audit log showing every edit and its author. That log is the documentation defense. When an L&I investigator asks whether a specific employee got a rest break on a Tuesday in March, you answer with a record instead of a recollection. If you are still comparing options, our overview of time clock software for small business lays out what else to check.

Washington break laws compared with other states

Multi-state employers need per-location rules, not one national policy. The differences are large enough to matter in both directions.

State	Meal period	Paid rest breaks	Remedy for a violation
Washington	30 minutes, starting between hour 2 and hour 5	10 minutes per 4 hours, none over 3 consecutive hours	Pay for the missed break time, plus possible penalties
California	30 minutes before the end of hour 5	10 minutes per 4 hours worked	One hour of premium pay per category, per workday
Oregon	30 minutes for shifts over 6 hours	10 minutes per 4-hour segment	Back pay and state penalties
Texas	None required	None required	No state remedy
Federal (FLSA)	None required	Not required, but breaks under 20 minutes must be paid	Back wages plus possible liquidated damages

The distance between the strict states and the permissive ones is wider than the table shows. California work break laws attach a premium hour of pay to every workday a meal is missed, late, or short, so the lunch break laws California enforces punish timing in a way Washington's remedy does not, and the labor laws California uses to police the records go further still, since rounding meal punches is banned there. There are no lunch and break laws in Texas for adult workers, and no Florida lunch break laws either, so in both places a break is a scheduling choice rather than a legal one. California break laws remain the outlier in cost.

Pay rules move independently of break rules. State overtime laws mostly track the federal 40-hour week, with California's daily 8-hour trigger as the big exception, so it's worth reading overtime pay laws by state and minimum wage by state together before you write one handbook for several locations. The labor laws in the state of Texas set no break requirement and no state overtime rule at all, and Florida state labor laws are close to the same, though the Florida minimum wage sits above the federal rate on a state schedule.

One more Washington quirk worth planning for. Because rest breaks are paid and meal breaks usually are not, the difference between a 10-minute rest and a 30-minute meal is not just time, it is payroll. Coding them interchangeably in a spreadsheet is how small businesses end up underpaying without meaning to, and it is why break types belong in the time clock rather than in a manager's head. Full state detail lives in our Washington meal and rest break guide, and the time card calculator will check a specific week for you.

Questions Washington owners and employees ask most

Washington state lunch break laws for employees come down to two numbers, 30 and 10, plus one window, hours two through five. For owners the numbers are the easy part. Proving they happened is the work.

Does my state require lunch breaks?

Washington does, and so do California and Oregon. Texas and Florida do not, for adults, and no federal rule stands behind any of it. The answer follows the work location, not the company's home office, so an employee working remotely from another state gets that state's rule on their shift. Build the policy per location and you never have to remember which is which.

Are 15 minute breaks required by law?

Washington requires 10 minutes, not 15. Plenty of employers schedule 15 anyway because it's easier to say and easier to remember, and more is always allowed. What isn't allowed is trading one 15-minute break for the two 10s an eight-hour shift earns. Federal law never requires a rest break at all, it only requires that a break under 20 minutes be paid, which is why a 15-minute break can't be deducted from a paycheck in any state.

Start here: export last month's time cards, calculate the gap between shift start and meal start for every shift over five hours, and count how many fell outside the two-to-five hour window. That count is your current exposure, and it usually points at one or two shifts rather than the whole schedule.