Minnesota Meal and Rest Break Rules for Employers

What changed for Minnesota employers on January 1, 2026?

Three things changed on January 1, 2026. Rest breaks gained a hard 15-minute minimum, the meal-break trigger dropped from eight consecutive hours to six with a firm 30-minute minimum, and both breaks now carry a private liquidated-damages remedy that did not exist under the prior law. The old statute promised only vague “adequate time,” and it carried no liquidated-damages remedy.

The rest-break rule in Minn. Stat. § 177.253 now requires a break of “at least 15 minutes or enough time to utilize the nearest convenient restroom, whichever is longer, within each four consecutive hours of work.” The meal-break rule in Minn. Stat. § 177.254 now covers “each employee who is working for six or more consecutive hours” and sets a floor of “at least 30 minutes.” The change that matters most to your budget is the remedy: an employer that skips a required break is liable for the break time that should have been allowed, at the employee’s regular rate of pay, plus an equal amount as liquidated damages. These amendments passed in the 2025 legislative session and sit alongside the broader run of 2025 Minnesota employment law changes and newer duties such as pay transparency rules.

How often must I provide rest breaks, and how long must they be?

You must allow a paid rest break of at least 15 minutes, or enough time to reach the nearest convenient restroom if that takes longer, within each four consecutive hours of work. The statute reads that an employer must allow a rest break of “at least 15 minutes or enough time to utilize the nearest convenient restroom, whichever is longer, within each four consecutive hours of work” (Minn. Stat. § 177.253, subd. 1).

Two details trip employers up. First, the break must fall inside each four-hour window, not get pushed to the end of a long shift. An employee scheduled for eight hours needs a chance to break within the first four hours and again within the second four. Second, the safest approach is to schedule a short rest break roughly every two hours rather than trying to time the exact four-hour edge, because a break that lands a few minutes late is a violation just the same.

When does an employee earn a 30-minute meal break?

An employee who works six or more consecutive hours must be allowed a meal break of at least 30 minutes. The statute covers “each employee who is working for six or more consecutive hours” and requires “a meal break of at least 30 minutes” (Minn. Stat. § 177.254, subd. 1). The prior law used an eight-hour trigger, so a common six-and-a-half-hour retail or clinic shift that needed no meal break in 2025 needs one in 2026.

The trigger is consecutive hours, not total hours for the day or week. It ties directly to how Minnesota counts hours worked for a given stretch of a shift. One 30-minute meal break satisfies the statute for the shift; Minnesota guidance treats a single meal break as the requirement even on a 12-hour shift, though nothing stops you from offering a second, and on long shifts a second break is usually the better practice for both morale and error rates.

How does break pay work under Minnesota and federal law?

The 15-minute rest break is paid; the 30-minute meal break can be unpaid, but only when the employee is completely relieved of duty. That split comes from two sources working together. Minnesota law says that, apart from the violation remedy, “nothing in this section requires the employer to pay the employee during the meal break” (Minn. Stat. § 177.254, subd. 2). The federal Fair Labor Standards Act (“FLSA”) supplies the rest of the rule.

Under 29 C.F.R. § 785.18, short rest periods “running from 5 minutes to about 20 minutes” are common and “must be counted as hours worked.” A 15-minute rest break sits squarely inside that band, so it is paid, and the Minnesota Department of Labor and Industry (“DLI”) applies the same 20-minute line. A bona fide meal period is different: under 29 C.F.R. § 785.19, it “is not worktime” only when “the employee must be completely relieved from duty.” So a genuine 30-minute lunch can be unpaid, but a lunch the employee works through becomes paid time that also counts toward overtime pay in Minnesota. The practical rule: pay the short breaks, and treat the meal break as unpaid only if the employee truly steps away.

Does federal law require these breaks?

No. Federal law does not require employers to provide meal or rest breaks at all. The FLSA sets no break mandate; it only tells you how to treat break time you choose to give. The federal regulations on rest and meal periods presuppose that the breaks are voluntary and speak only to whether the time is paid. Minnesota is the source of the requirement itself.

This matters for two kinds of employers. If you have long assumed that “federal law does not require breaks,” that assumption is now wrong for your Minnesota workforce, because the state statute supplies the mandate the FLSA lacks. And if you run a multistate operation on a single national handbook, a federally compliant “we provide breaks as operations allow” policy will not meet the Minnesota floor. The two systems stack cleanly once you see the division of labor: Minnesota law creates the break, and federal law sets the pay treatment. Comply with both, and start from the Minnesota rule because it is the stricter of the two on whether a break must happen.

Which of my employees are covered, and who is exempt?

The break rules reach every “employee” as defined by the Minnesota Fair Labor Standards Act (“MFLSA”), which is most of your hourly workforce. The definition in Minn. Stat. § 177.23, subd. 7, says “‘Employee’ means any individual employed by an employer but does not include” a list of categories. The ones a typical business will hit are:

• Anyone “employed in a bona fide executive, administrative, or professional capacity, or a salesperson who conducts no more than 20 percent of sales on the premises of the employer.”
• Certain agricultural workers.

Employees covered by a collective bargaining agreement are not exempt from these rules; instead, §§ 177.253 and 177.254 let a collective bargaining agreement establish different rest or meal break terms.

One trap deserves a flag. Being exempt from overtime under the federal FLSA does not make an employee exempt from the Minnesota break rules. The MFLSA has its own definitions, and an employee your payroll system codes as “exempt” for federal purposes may still be a covered “employee” who is owed breaks here. When in doubt, treat the worker as covered; the cost of an unnecessary break is trivial next to the cost of a missed one.

How do these rules play out for field crews, remote workers, and production lines?

For hard-to-relieve workforces, the rest break is rarely the problem; the meal break is, because it quietly turns into paid time. The recurring pattern I see is the working lunch: a machine operator who eats at the line, a field crew that cannot leave a job site, or a remote worker who never actually clocks out. In each case the employee is not “completely relieved from duty” under 29 C.F.R. § 785.19, so the 30-minute meal break the employer treated as unpaid is legally paid time, and skipping it altogether triggers the Minn. Stat. § 177.254 remedy.

The statute requires the employer to “allow” the break, which for these teams means building relief into the schedule rather than hoping it happens. On a production line, that is coverage or rotation so the line does not stop when one person breaks. For field crews, it is a planned window and a clear instruction that the meal break is genuine downtime. For remote and hybrid staff, it is a written expectation that they take an unpaid, duty-free meal break on a six-hour day and a timekeeping system that records it. The goal is to make the break real, not to paper over a lunch that everyone knows was worked.

What is my liability if supervisors let breaks slip?

An employer that fails to allow a required break owes the employee the break time at the regular rate plus an equal amount as liquidated damages, and faces two enforcement channels on top of that. The statute is direct: the employer “is liable to the employee for the meal break time that should have been allowed at the employee’s regular rate of pay, plus an additional equal amount as liquidated damages” (Minn. Stat. § 177.254, subd. 4), and the rest-break section says the same thing (Minn. Stat. § 177.253, subd. 3).

The dollar value of one break is small. What makes the exposure real is where it goes next. An employee “may bring a civil action seeking redress for a violation or violations of sections 177.21 to 177.44 . . . directly to district court” (Minn. Stat. § 177.27, subd. 8), and if the employee wins, the court “shall order” the employer to pay “reasonable costs, disbursements, witness fees, and attorney fees” (subd. 10). That mandatory fee-shifting is the part that surprises business owners: a claim worth a few hundred dollars in missed breaks can carry tens of thousands in the employee’s legal fees. Separately, DLI can enforce the same rules by compliance order, and an employer “found to have repeatedly or willfully violated” the law faces “an additional civil penalty of up to $10,000 for each violation for each employee” (subd. 7). Because the harm often repeats across a whole shift or crew, the per-employee, per-violation structure is what turns a scheduling habit into a payroll-wide claim. Solid timekeeping is your best defense, the same discipline that the Minnesota Wage Theft Act recordkeeping duties already demand.

How should I write my break policy and set up timekeeping?

Write your policy to the statutory floor, not above it, and build timekeeping that records the opportunity to take breaks. The statute requires you to “allow” breaks, not to force them, so your job is to provide and document a real chance to break, not to police whether every employee uses it. The single most useful thing I tell employers is to stop conflating “allow” with “guarantee”: you are not liable merely because an employee declined a break you genuinely offered and never discouraged, but you are liable if your schedule never gave them the chance.

Two drafting cautions follow. First, do not promise more than the statute requires. Under Minnesota’s unilateral-contract doctrine, a handbook can create commitments a court will enforce, so a policy that guarantees “two paid 20-minute breaks and a paid lunch” can bind you to that richer promise even though the statute asks for less. Keep the language at the legal minimum unless you intend to offer more, a point covered in our note on employee handbook risks. Second, capture breaks in your timekeeping the way you capture hours, so you can prove a break was available; the same care that goes into PTO policies that comply with Minnesota wage law belongs here. Align the break policy with your other Minnesota obligations, including earned sick and safe time, so your handbook reads as one coherent set of rules rather than a stack of separate memos.

The value of any single break is small, but the fee-shifting and per-employee penalties make a pattern of missed breaks expensive, and the fix is not complicated. Match your written policy to the statutory floor, build scheduling that gives every covered employee a genuine chance to break, and keep timekeeping that shows you did. If you would like a second set of eyes on your break policy or your exposure on a specific shift pattern, email [email protected] with a short description and any relevant documents. For a related obligation that trips up the same employers, see our guidance on final pay rules for departing employees and the rest of our employment law practice.