Every dispatcher on the night shift shows up fifteen minutes early. Not because they want to — because the collective bargaining agreement requires it. Roll call: pass the radio codes, confirm who's covering which sector, sign off on the equipment check. Fifteen minutes, five nights a week, fifty-two weeks a year. The employer had quietly stopped paying for it years ago, treating it as a courtesy buffer that helped everyone land closer to a standard 2,080-hour work year. Nobody complained — until a union official asked the Department of Labor directly whether that math actually held up.
It didn't. In January 2026, the U.S. Department of Labor's Wage and Hour Division answered that question in Opinion Letter FLSA2026-3, and the answer has implications for a lot more workplaces than 911 call centers.
The question: does mandatory roll call count as "hours worked"?
The union representing a group of emergency dispatchers asked the DOL three related questions about a mandatory 15-minute pre-shift roll call written into their CBA:
- Is roll call time properly classified as "hours worked" under the Fair Labor Standards Act?
- Can that time be used to fill pay periods that would otherwise fall short of 80 hours?
- Can the roll call time be excluded from overtime calculations, given that its whole purpose was to nudge employees toward a standard annual hour count rather than to accomplish operational work?
The employer's theory — that time added purely for scheduling-symmetry reasons doesn't "count" the same way as time spent actually working — is a familiar one. Plenty of employers treat huddles, briefings, and equipment checks as informal, off-the-clock housekeeping. The DOL's answer draws a hard line against that assumption.
The DOL's answer: mandatory + designated compensable = it counts
The Department's analysis turned on a simple fact: the CBA itself designated the roll call as both mandatory and compensable. Once an employer and a union agree, in writing, that an activity is required and paid, the DOL isn't going to entertain a side argument that it's really just administrative housekeeping that shouldn't count toward overtime. The roll call time is compensable work time, full stop, and it must be included when calculating any overtime owed under the FLSA.
That closes off the first and second questions pretty cleanly — you can't use "extra" mandatory time to quietly pad a pay period toward a threshold without it also counting toward overtime exposure. But the third question is where the opinion letter gets genuinely useful for employers, because the DOL didn't just say "you owe overtime." It pointed toward a structural way to avoid that outcome entirely — if the employer sets things up correctly in advance.
The overlooked lever: FLSA Section 7(b) partial overtime exemptions
Most employers know about the standard rule: overtime kicks in after 40 hours in a workweek. Employers in law enforcement and fire services often know about the Section 7(k) exemption, which lets those specific professions use an extended "work period" (up to 28 days) instead of a strict weekly threshold.
Section 7(b) is the lesser-known cousin of 7(k), and it's not limited to police and fire. It's available to any employer whose employees are covered by a bona fide collective bargaining agreement that meets specific statutory conditions. There are two flavors:
Section 7(b)(1): If the CBA is certified as bona fide by the National Labor Relations Board, the employer can pay overtime only for hours worked over 12 in a day or over 56 in a week — not the standard 40-hour weekly threshold. The tradeoff: the CBA must guarantee that no employee works more than 1,040 hours in any 26-consecutive-week period.
Section 7(b)(2): This version relies on a guaranteed compensation arrangement rather than NLRB certification. The CBA must (a) specify a fixed rate of pay for all hours worked or guaranteed, (b) guarantee the employee between 1,840 and 2,080 hours of work over a specified 52-week period, (c) cap actual hours worked at 2,240 during that same period, and (d) require overtime pay for any hours worked beyond the guaranteed amount that also exceed 40 in a given workweek, plus any hours beyond 2,080 total.
Here's the part that matters for the dispatch-center scenario: the DOL specifically noted that a relatively small addition of work time — like a 15-minute roll call — doesn't automatically blow past the thresholds that keep a 7(b)(1) or 7(b)(2) arrangement valid. If the CBA already includes the required statutory language and the employer stays within the hour caps, adding the roll call time doesn't trigger new overtime liability under the FLSA, even though the same 15 minutes absolutely would be counted as overtime-eligible hours worked under the standard 40-hour rule.
In other words: the DOL didn't give the employer a way to avoid paying for roll call. It confirmed the employer has to pay for it as regular hours worked — but a properly structured 7(b) agreement can mean that pay doesn't have to come at an overtime premium.
Running the numbers: what changes under a 7(b) arrangement
Numbers make this concrete. Say a dispatcher works five 8-hour shifts a week, plus the mandatory 15-minute roll call before each one — 40 hours and 15 minutes per week, every week.
Under the standard 40-hour rule, that extra hour and 15 minutes a week (5 × 15 minutes) pushes the employee over the weekly threshold every single pay period. At time-and-a-half, that's a small but permanent overtime line that never goes away — and it compounds across every dispatcher on every shift, every week of the year. For a 20-person dispatch center, that's roughly 25 extra overtime-hours-equivalent paid out every week, indefinitely, for time that was never meant to be "extra" work in the first place.
Under a properly structured 7(b)(2) arrangement, the employer instead guarantees the employee a fixed number of hours (say, 2,000) over a 52-week period at a specified rate, and overtime only applies to hours worked beyond that guarantee that are also over 40 in a given week, or beyond 2,080 for the year. Because the roll call time is small relative to the annual guarantee, it can be absorbed into the guaranteed-hours bucket rather than triggering a weekly overtime premium — as long as the CBA's guarantee, rate, and hour-cap language meet the statutory requirements DOL laid out in 29 CFR 778.602 and 29 CFR 516.20.
The dollar difference isn't dramatic on any single paycheck. But multiplied across a dispatch center's full roster, every week, for years, it's the difference between a payroll line that quietly overpays overtime premiums the employer never intended to owe, and one that pays every compensable minute at straight time until the actual statutory thresholds are crossed.
Common questions this opinion letter raises
Does this apply if we don't have a union? No — Section 7(b)(1) and 7(b)(2) both require a genuine collective bargaining agreement with specific statutory language. A non-union employer can't adopt a 7(b) arrangement by policy memo; it needs an actual CBA, negotiated with a recognized union, that meets the hour-guarantee and rate requirements.
Does this mean roll call is always paid? Only if it's mandatory. The DOL's compensability finding turned specifically on the fact that this CBA labeled the roll call as both required and paid. Purely voluntary pre-shift activities — employees who show up early by choice, with no requirement to do so — sit on different legal footing, though that distinction gets litigated often and shouldn't be assumed without documentation.
What if our CBA is silent on whether roll call is paid? That's the riskiest position of all. Silence tends to get resolved against the employer once a wage claim or grievance is filed, because ambiguity in a CBA is often read in the employee's favor. Getting explicit, unambiguous language into the agreement — one way or the other — protects both sides from a costly dispute later.
Is this specific to emergency dispatch? No. The 15-minute roll call happens to be a dispatch-center fact pattern, but the reasoning applies to any mandatory pre- or post-shift activity under a CBA: security screenings at a manufacturing plant, equipment inspections at a trucking terminal, briefings at a warehouse. If it's required and the agreement calls it compensable, it counts toward hours worked — and if you want a 7(b) exemption to apply to a schedule that includes it, that exemption has to be built into the CBA correctly from the start.
What this means if you're not running a dispatch center
Section 7(b) exemptions apply narrowly — they require a real collective bargaining agreement with specific statutory language, not an informal handshake with a group of employees. But the underlying lesson generalizes to almost any employer with mandatory pre-shift or post-shift activities:
- "It's just five minutes" is not a legal defense. Mandatory prep time — equipment checks, security screenings, briefings, sign-in procedures — is compensable if it's required, regardless of how brief or how administrative it feels. This has tripped up warehouses, call centers, and retail chains in wage-and-hour litigation for years; FLSA2026-3 is a fresh reminder that the DOL isn't softening that position.
- Verbal or implied "time-banking" arrangements don't hold up. The employer in this case assumed that extra time worked earlier in the year could informally offset shorter weeks later, without any of it counting toward overtime. That kind of unwritten averaging scheme is exactly what the FLSA's overtime rules are designed to prevent — you can't average hours across weeks to avoid paying overtime unless a specific statutory exemption applies.
- A written exemption has to be built correctly, in advance. If you have unionized employees working extended or irregular schedules, a 7(b) arrangement can be a legitimate way to manage overtime costs — but only if the CBA contains the required guarantees before the fact. You can't retroactively claim an exemption you never actually structured.
- Track compensable time precisely, not approximately. Once an activity is mandatory, it needs to show up in your time records and your payroll calculations — not get absorbed into a vague "starts at 8, roughly" convention.
Keeping payroll costs visible before they become a liability
Wage-and-hour exposure like this often stays invisible until an employee or union raises it — because unpaid mandatory minutes rarely show up as a distinct line in a general ledger. They get buried inside a payroll total that looks correct on the surface. A bookkeeping system that separates payroll into clear categories — regular wages, overtime premium, and any accrued-but-unpaid time — makes it much easier to spot a gap like the one in FLSA2026-3 before it becomes a six-figure back-pay claim.
Keep Your Payroll Records Transparent and Auditable
If your business runs shift work, mandatory pre-shift activities, or a collective bargaining agreement with complex overtime rules, the accuracy of your payroll ledger matters as much as the accuracy of your paycheck. Beancount.io offers plain-text accounting that gives you complete transparency and a full audit trail over every payroll entry — no black boxes, no vendor lock-in. Get started for free and see why developers and finance-minded business owners are switching to plain-text accounting.