PunchAutomatic Lunch Deductions: The Quiet Wage Claim Hiding in Your Timesheets
Automatic Lunch Deductions: The Quiet Wage Claim Hiding in Your Timesheets
The short answer: Subtracting 30 minutes from every shift for lunch is not illegal by itself. It is only legal on the days the break actually happened and the employee was completely relieved of duty. Every other day, the deduction is unpaid work time, and unpaid work time near the 40-hour line is unpaid overtime. The fix is not a better policy or a better memory. It is to stop subtracting the break and start recording it. In Punch, lunch is its own punch, with a start and an end, on the same timestamped record as the shift.
What an Auto-Deduction Actually Is
An automatic deduction is a payroll rule, not a time record. It says: if a shift runs more than six hours, remove 30 minutes.
That rule is a guess about what happened. It is a good guess in an office. It is a much worse guess on a roof, in a crawlspace, in a truck between calls, or behind a counter during a rush. The rule fires whether or not anyone ate.
The gap between the guess and the day is where wage claims live. Auto-deduction shows up year after year in wage and hour class actions, concentrated in healthcare, manufacturing, food service, and field work, for one reason: the practice creates a systematic, repeating shortfall that is easy to plead on behalf of an entire crew at once.
What Federal Law Requires
Two regulations do most of the work here.
Meal periods. Under 29 CFR 785.19, a bona fide meal period is not hours worked. Ordinarily 30 minutes or more qualifies. The condition is strict: the employee must be completely relieved from duty for the purpose of eating a regular meal. The regulation says plainly that an employee is not relieved if required to perform any duties, whether active or inactive, while eating. DOL Fact Sheet #22 gives the textbook example. A worker who eats at a desk and keeps answering the phone is working, and that time must be paid.
Short breaks. Under 29 CFR 785.18, rest periods of short duration, roughly 5 to 20 minutes, must be counted as hours worked. That has a direct consequence for auto-deduction. If your crew realistically takes two 15-minute pauses and never a full 30, the deducted half hour was never a meal period in the first place. It was paid rest time you removed from the check.
Recordkeeping. 29 CFR 516.2 puts the burden of an accurate record on the employer, including hours worked each workday and total hours each workweek. This is not a shared obligation. It is yours.
What the DOL Settled in 2026, and What It Did Not
In opinion letter FLSA2026-7, issued May 28, 2026, the Wage and Hour Division addressed a secured facility where leaving for lunch meant a long walk to the parking lot and a pass through security gates, leaving 10 to 15 usable minutes off site. The Department concluded that an employee's voluntary choice to travel off site during an otherwise bona fide meal period does not convert the meal period into paid time, even when the trip is inconvenient.
Read what that letter does and does not do for you. It protects the unpaid status of a real break. It says nothing that rescues a deduction taken on a day the break never happened. The whole letter rests on the meal period being bona fide in the first place, which means completely relieved of duty. That premise is exactly the thing an auto-deduction never verifies.
Why the Deduction Fails on Real Job Sites
Nobody sets out to shave hours. The deduction fails for ordinary reasons.
A tech eats in the van between calls while dispatch reroutes them. A framer sits down for eight minutes because the delivery arrived early. A crew works straight through to beat the weather and get home. A shop hand keeps an eye on the phone while the sandwich sits there. Every one of those days is a full day of work with 30 minutes removed.
The usual patch is a form. Tell the crew to report a missed break so payroll can add it back. That patch is weak twice over. Courts have questioned putting the burden of recording hours on the employee, because the statute puts it on the employer. And in practice the form does not get filled out. Someone who just worked nine hours without sitting down is not chasing paperwork over half an hour.
The Math When It Fails
Take one worker at $28.00 an hour who genuinely misses lunch three days a week. That is 1.5 unpaid hours a week. If those hours sit past 40, they carry a premium, so the week is short by about $63.00.
Now scale it the way a lawyer will. Six crew members, two years back, is roughly $19,600 in straight back wages before anything else is added. The FLSA reaches back two years, or three for a willful violation. Back pay is commonly doubled as liquidated damages. The employee also recovers attorney's fees and costs.
Then there is the part that makes the deduction genuinely dangerous. Under Anderson v. Mt. Clemens Pottery Co., when an employer's records are inaccurate or inadequate, an employee only has to show the amount of uncompensated work as a matter of just and reasonable inference. The burden shifts to you to rebut it with accurate records. An auto-deduction produces the one thing you cannot rebut with, which is a timesheet that shows a break the same way on every shift, including the shifts where it never happened.
Some States Raise the Stakes Further
Federal law does not require you to provide a meal break at all. Many states do, and a few attach their own money to a missed one.
California is the sharpest example. When a compliant meal period is not provided, the employee is owed one additional hour of pay at their regular rate. In Naranjo v. Spectrum Security Services, decided May 23, 2022, the California Supreme Court held those premiums are wages, which means they must appear on the wage statement under Labor Code section 226 and must be paid at separation or expose the employer to waiting time penalties under section 203. A 2024 follow-on decision softened the wage statement penalty where an employer had a good faith belief it was complying, but the premium itself, and the section 203 exposure, remain.
If you operate in more than one state, an auto-deduction applies a single guess to several different rule sets at once. Our meal and rest break guide covers the state layer in more detail.
The Fix: Record the Break, Do Not Subtract It
Punch is built on the position that a timesheet should be a record of what happened, not an estimate corrected later.
Lunch is a separate action. An employee punches in, starts lunch, ends lunch, and punches out. Four timestamps, to the minute, nothing rounded. A day where the crew worked straight through simply has no lunch on it, so there is nothing to add back and nothing to argue about. A day with a real 34-minute break shows 34 minutes. That is the record 29 CFR 516.2 asks you to keep, and it is the record that answers a Mt. Clemens inference instead of feeding it.
Lunch is never gated by location. People eat wherever they are, so punch-out and lunch have no geofence on them. Punch confirms location at punch-in only, on iOS, when you turn it on. That check is a boundary on a map, never facial recognition and never a photo at the punch. Proving a crew was on site should not require a camera in anyone's face. Trust beats surveillance.
Punches work offline. A basement, a canyon, or a rural lot still records a real punch that syncs when service returns, so a dead zone never turns into a missing half hour.
From there the week carries itself. Punch totals hours against your fixed workweek and applies overtime automatically using more than 50 built-in country and state presets, so the minutes you stopped losing at lunch are priced correctly when they cross the line. Split shifts stay clean segments on one day. Managers approve or reject a week or a whole pay period in bulk, and every decision is recorded against the shift. Approved hours export to Excel or a QuickBooks CSV, or push straight into QuickBooks Online. For crews without company phones, a shared iPad becomes a punch station with a PIN.
Why Punch Beats the Per-Seat Alternatives
Every non-exempt person you employ is exposed to this problem, which means the cost of fixing it scales with headcount on a per-seat platform. ClockShark, Connecteam, Buddy Punch, QuickBooks Time, and Homebase all bill by the user, and the approval, overtime, and export tooling that carries a clean break record tends to sit a tier up or behind an add-on.
Punch charges one flat price per organization. Every plan includes every feature, from geofenced punch-in to kiosk mode to bulk approvals to QuickBooks Online export. Owners are always free. Hire four seasonal hands in March and your software bill does not move.
The Bottom Line
An automatic lunch deduction is a bet that the break happened. You are the one holding the recordkeeping obligation, so you are the one who loses that bet, at two or three years deep and doubled.
Stop betting. Record the break as its own punch and the exposure disappears, because the timesheet stops disagreeing with the day.
Start with Punch and let lunch record itself.
This article is general information, not legal advice. Wage and hour rules differ by state and change over time. Confirm your obligations with the DOL guidance in force and with a qualified employment attorney before setting policy.