California restaurant break audit checklist for timecard exports

This checklist is written for HR consultants, payroll consultants, bookkeepers, and restaurant operators who need to turn restaurant timecard exports into a reviewable California meal and rest break audit. It is a vertical companion to the broader California break audit checklist.

1. Start with the shifts most likely to drift

Restaurant risk is rarely evenly distributed across the schedule. Before you run every row through the same summary table, segment the export so the client can see where the operational pressure is coming from.

• Opening and closing shifts: check whether meal periods are pushed late by prep, closeout, cash handling, or manager coverage.
• Doubles and long service days: isolate shifts over ten hours so second-meal records and waiver assumptions are visible.
• Short shifts near the five-hour line: confirm whether the export has actual clock times or rounded totals before flagging first-meal exposure.
• Role and location clusters: group findings by cook, server, host, runner, bar, and location so the report points to a fixable staffing pattern.
• Manual edits: preserve edit markers and source rows; edited punches need review before being treated as final facts.

2. Request restaurant-specific export fields

An anonymized export can usually support the first pass. The key is preserving stable identifiers and enough shift context for payroll or counsel to re-check the source system.

• Employee identifier, location, department, role, and source row ID.
• Work date, clock in, clock out, total hours, and any split-shift markers.
• Meal start, meal end, meal duration, and second-meal records.
• Rest-break attestations or rest-break records if the system captures them.
• Waiver fields, missed-break attestations, manager edits, and automatic meal-deduction flags.
• Regular-rate inputs, meal/rest premium pay codes, correction rows, and payroll-register references.

For many restaurants, Homebase timecards are the starting point. Larger operators may need exports from ADP, Paychex, Gusto, or a point-of-sale-linked scheduling system.

3. Run the California timing checks

California’s DLSE summarizes the meal-period baseline: a 30-minute meal period is required for work periods over five hours, and a second meal period is required for work periods over ten hours unless a valid waiver applies. DLSE also explains that required first and second meal periods generally must be provided by the end of the fifth and tenth hours of work.

• First meal: flag shifts over five hours with no meal, a short meal, or a meal that begins after the fifth hour.
• Second meal: flag shifts over ten hours with no usable second meal, then separate rows that need waiver review.
• Premium pay: credit premiums already paid and identify rows where the export supports a possible unpaid-premium review.
• Rounding and edits: show when the finding is based on rounded time, raw punches, or a manager-edited row.

4. Treat rest breaks as evidence-sensitive

California rest periods are usually paid, net 10-minute breaks for every four hours worked or major fraction. Restaurant systems often do not punch rest breaks, so the audit should not turn every missing rest row into a violation by default.

• If the system has missed-rest attestations or premium-pay codes, map them explicitly.
• If the system has no rest-break record, mark the shift as a record gap unless another field supports a finding.
• Group rest-record gaps by role, location, and time of day so the client can review whether coverage practices are the real driver.
• Keep rest-period findings separate from meal-period findings because the evidence and fixes may differ.

5. Package what restaurant operators can act on

The output should be practical enough for the owner, controller, HR lead, or outside payroll partner to work through without rebuilding the analysis.

• Summary by location and role: issue counts, premium exposure ranges, already-paid premiums, and record gaps.
• Correction table: employee identifier, date, shift, issue category, source row, estimated premium, and review status.
• Assumptions log: waiver handling, rest-record handling, rounding, rate source, and excluded rows.
• Client questions: rows that need payroll, HR, manager, or counsel review before any correction.
• Monitoring cadence: whether the restaurant needs a one-time cleanup or a monthly review before payroll closes.

6. Use the first report to create monthly monitoring

A one-time audit can identify historical exposure. Monthly monitoring is more useful when the restaurant is still changing schedules, opening locations, or training managers. The best cadence is before payroll closes, while supervisors still remember why a meal was late, a second meal was missed, or a premium was paid manually.

For consultants, this is the serviceable wedge: collect a fresh export, run the same assumptions, send a short exception list, and keep a record that the client is reviewing timekeeping data instead of waiting for a notice.

7. Keep official references close

Use official sources for rule background and keep legal conclusions out of the audit deliverable. Start with the DLSE meal-period FAQ, the DLSE rest-period FAQ, the Labor Code section 512 text, and the LWDA PAGA FAQ for current PAGA cure and reasonable-steps background.