When a wage-and-hour problem surfaces, the instinct is to look for a bad actor. In the data, that is almost never what you find. You find a fixed lunch schedule, an automatic deduction, a rounding rule — defensible-looking settings that drift a few minutes off the rules and then run, unexamined, for years. Here are the five patterns worth checking first.
1. Lunches that drift into the sixth hour
California requires the first meal period to begin before the end of the fifth hour of work on shifts longer than five hours. A fixed “everyone goes to lunch at 1:00” rule looks orderly, but for anyone who clocked in at 7:30, a 1:00 lunch starts in the sixth hour — non-compliant, every shift, automatically. In the data this shows up as a tight cluster of meal-start times that sit just past the five-hour mark for early-clock-in employees.
2. Missing second meals on long shifts
A second 30-minute meal is required on shifts longer than ten hours and must begin before the end of the tenth hour. Operations that rarely schedule long days forget the rule exists — so when a shift does run long (coverage, inventory, a no-show), the second meal simply never happens. Look for shifts over ten hours with only one recorded meal punch.
3. Automatic meal deductions that don’t match punches
Some systems subtract a fixed 30 minutes from every shift instead of recording an actual meal punch. The trouble is that the deduction asserts a meal happened on paper whether or not it did — and if the employee worked through or took a short lunch, the record now disagrees with reality. Automatic deductions are a common source of exposure precisely because they hide whether a compliant meal occurred. In the data, watch for identical 30-minute gaps with no corresponding clock-out/clock-in.
4. Short meals counted as “close enough”
A meal period that runs under 30 minutes is non-compliant — a 22-minute lunch is not a meal period that started on time but ran short, it is a missed meal period for premium purposes. These hide easily because the shift still “has a lunch” on it. Measuring the actual punch-to-punch duration, not just the presence of a break, is what surfaces them. See the break law guide for the timing rules in full.
5. Premiums paid at the base rate instead of the regular rate
This one is not a missed break at all — it is a mispaid one. When a premium is owed and paid, it must be paid at the regular rate of compensation, which includes nondiscretionary bonuses and similar pay, not just the base hourly rate. Payroll systems frequently default to the base rate, quietly underpaying every premium. We wrote up the mechanics in Ferra v. Loews, explained.
One caution on rest breaks: most employers don’t punch rest breaks, so the data usually can’t prove whether they happened. The defensible move is to treat shifts with no usable rest-break record as a record gap to investigate — not to inflate every gap into a violation. Conflating the two is how an audit loses credibility.
Why patterns beat spot-checks
Each of these is individually minor. The reason they matter is volume and repetition: the same setting, applied to a whole workforce over a multi-year look-back, is what turns a rounding decision into real exposure. It also means they are findable — a pattern that repeats is exactly what a systematic pass over the timecard data is good at surfacing, where a manual spot-check of a few shifts would miss it.
That is the job a break audit does: run the California rules against every shift in the export, separate detected issues from record gaps, and trace each finding back to the source row. If you are pulling the export yourself, the provider export guides cover which report to download for Homebase, ADP, Gusto, and Paychex.