Picture a warehouse employee at a distribution center ringed by fencing and a single guarded entrance. She gets a 30-minute unpaid lunch. If she wants to eat in her car or grab food from a truck parked outside the gate, she has to walk to the checkpoint, badge out, walk to the lot, eat, walk back, and badge in again. By the time she's back at her station, she's had maybe 20 minutes to actually eat — the other 10 vanished into walking and waiting at security.
Is that "lost" time compensable? In May 2026, the U.S. Department of Labor's Wage and Hour Division answered that question directly in Opinion Letter FLSA2026-7, and the answer will surprise some employers who've been quietly adding buffer minutes to their break schedules out of caution. It also puts a fine point on how easily a well-intentioned meal-break policy can drift into a wage-and-hour liability if you're not careful about the details the DOL says do matter.
What FLSA2026-7 Actually Says
The opinion letter addressed a specific fact pattern: an employer operating inside a large, secured facility gives employees a 30-minute unpaid meal period. Employees are free to stay on-site or leave, but leaving means walking to the parking area and passing through a security checkpoint in both directions — time that eats into the 30 minutes.
The employer asked WHD a straightforward question: does the travel time through the checkpoint count as "hours worked" that must be paid, either by extending the break or paying for the shortfall?
The DOL's answer was no. Time an employee voluntarily spends traveling off the premises during a meal period — including navigating a security checkpoint — does not turn into compensable work time, and the employer isn't required to extend the meal period to make up for it. The letter leans on the decades-old federal standard for a "bona fide" meal period under 29 CFR § 785.19: the break is unpaid so long as the employee is completely relieved of duty for the purpose of eating a regular meal. Critically, the regulation has always said an employer doesn't have to let employees leave the premises at all for a break to qualify as unpaid — so choosing to leave, and losing minutes to that choice, doesn't change the analysis.
Put simply: the clock that matters isn't "how many minutes did the employee actually get to chew," it's "was the employee free from work duties for the full period." Self-inflicted time loss from a personal choice to leave the building doesn't convert a bona fide break into work time.
Why the Distinction Matters More Than It Sounds
This might look like a narrow, security-checkpoint-specific ruling, but it reinforces the core test that governs every meal-break dispute the DOL and courts actually see: the "predominant benefit" test.
The question is never "did the employee get every minute of relaxation possible." It's "who primarily benefited from how that time was spent, and was the employee free of job duties." Under the FLSA and the DOL's longstanding guidance (also reaffirmed in the same 2026 batch of opinion letters), a meal period fails the bona fide test when:
- The employee is required to stay at a workstation, desk, or machine while eating
- The employee must monitor equipment, answer calls, or respond to customers during the "break"
- The employee is interrupted mid-meal to perform job duties, even briefly
- The break is regularly cut short by employer-directed tasks
None of those apply to voluntarily walking through a security checkpoint. The employee chose to leave, chose to accept the walk time, and remained free of any job duty the entire time. That's the line FLSA2026-7 draws — and it's good news for any employer whose facility has a badge-in/badge-out perimeter, a guarded gate, a multi-building campus, or a remote parking structure.
What This Doesn't Change
The opinion letter is narrow, and reading too much into it is where employers get into trouble. A few things it does not say:
It doesn't touch state law. California, Washington, Oregon, Colorado, and several other states impose their own, often stricter, meal- and rest-break rules — including timely-break requirements, premium pay for missed or late breaks, and duty-free standards that go beyond the federal floor. California's meal-break premium (an extra hour of pay for a missed, late, short, or interrupted break) exists entirely independent of federal law, and this opinion letter doesn't preempt it. If you operate in a state with its own break statute, that state's rule controls regardless of what WHD says about the federal minimum.
It doesn't excuse interrupted breaks. If security screening itself becomes a duty — say, an employee is pulled aside to answer a work radio call while in the checkpoint line, or is asked to hold a facility key or equipment during the walk — that reintroduces a duty into the "break," and the bona fide meal period analysis flips.
It doesn't apply if the meal period habitually shrinks below a reasonable duration. WHD guidance and case law generally treat 30 minutes as a reasonable floor for an unpaid meal period; if checkpoint delays are so severe that employees are functionally getting only 10–15 minutes to eat on a regular basis, that's a fact pattern the letter didn't bless, and a smart employer should not assume it's covered.
The Compliance Move for Small and Mid-Size Employers
If your business operates out of a secured facility, a multi-tenant building with badge access, or any site where getting to a parking lot or break area takes real walking time, FLSA2026-7 gives you cover — but only if your policy and your practice line up with the letter's fact pattern. A few concrete steps:
- Write the policy down. Document that the meal period is unpaid, that employees are completely relieved of duty during it, and that they may choose to remain on-site or leave — travel time is their own choice and their own time.
- Audit for duty creep. Walk your own checkpoint process. Are employees ever asked to carry a radio, badge visitors through, or answer a supervisor's text during that walk? If so, that's compensable time and needs to be tracked and paid.
- Check your state. Run your policy against your state's meal-break statute before relying on the federal standard alone. A federal opinion letter is not a shield against a state law claim.
- Track actual break length, not just scheduled length. If your timekeeping system shows employees consistently clocking back in 25+ minutes after clocking out for a 30-minute break, that's a paper trail proving the break is bona fide — and it protects you if a wage claim ever surfaces.
- Don't assume it covers rest breaks. Short paid rest breaks (typically 5–20 minutes) are governed by different rules than unpaid meal periods; FLSA2026-7 is specific to the meal-period analysis.
Running the Numbers: Why "A Few Minutes" Adds Up Fast
It's worth actually doing the math on why the DOL's answer matters financially, not just legally. Say a distribution center employs 150 hourly workers, and a plaintiff's attorney argues that checkpoint delays effectively shorten every lunch by 10 minutes, five days a week.
- 10 minutes × 5 days = 50 minutes/week per employee
- 50 minutes × 52 weeks = ~43 hours/year per employee
- 43 hours × 150 employees ≈ 6,500 hours/year in disputed time
- At a blended $22/hour wage (plus potential overtime premiums and liquidated damages under the FLSA, which can double the exposure), that's a six-figure claim before a single deposition is taken
That's the exposure FLSA2026-7 forecloses — provided the facts match the letter: employees chose to leave, were free of duties the entire time, and the meal period itself was a genuine, uninterrupted 30 minutes. Change any one of those facts (mandatory on-site policy, a supervisor pinging someone mid-walk, a checkpoint so slow that lunches are routinely cut to 15 minutes) and the same math works against the employer instead of for them.
The Bigger Pattern: Read the Fine Print of Every Opinion Letter
FLSA2026-7 is one of several wage-and-hour opinion letters WHD has issued this year, and the common thread across most of them is that the DOL is drawing sharper, narrower lines around what does and doesn't count as compensable time — rulings that reward employers who document their policies carefully and go against employers who treat "close enough" break practices as good enough. Wage-and-hour class actions built on missed or shortened meal periods remain one of the most litigated areas of employment law precisely because the dollar exposure compounds fast: shave a few minutes off enough lunch breaks across enough employees over enough pay periods, and a "minor" scheduling quirk becomes a six- or seven-figure back-pay claim.
The safest posture isn't hoping a favorable opinion letter will bail you out after the fact — it's building break policies, timekeeping practices, and documentation that would hold up under scrutiny before a complaint ever lands on your desk.
Keep Your Payroll Records as Clean as Your Break Policy
Compliance rulings like FLSA2026-7 are only as useful as the records that back them up. If a wage-and-hour claim ever surfaces, the employer who can show a clear, timestamped history of scheduled versus actual break times — tied cleanly to payroll — is in a far stronger position than one relying on memory. Beancount.io brings that same discipline to your broader financial records: plain-text, version-controlled accounting that gives you a complete, auditable history of every transaction, with no black box and no vendor lock-in. Get started for free and see why developers and finance-savvy business owners are switching to plain-text accounting.