title: "Donohue, four years on: what the per-period attestation actually looks like."
dek: "California's meal-period defense has lived or died on the per-pay-period record since 2021. Four years after Donohue v. AMN Services, here's what surviving the rebuttable presumption looks like in operating terms."
date: "2026-04-01"
pillar: "compliance"
author: "floburn"
tags: ["donohue", "meal-period", "attestation", "aegis-2699", "labor-code-226-7"]
The California Supreme Court decided Donohue v. AMN Services in February 2021. The holding has been settled law for four years. The operating implications still surprise the leadership team of nearly every California employer we walk into.
The holding, in plain language: noncompliant time records create a rebuttable presumption of meal-period violation. The records the Court was looking at were rounded-time records — clock-ins and clock-outs aggregated in five-minute or fifteen-minute increments. The Court did not say all rounding is illegal. It said the records the employer produced were insufficient on their own to establish that meal breaks were provided as required by §512 and the applicable Wage Order.
The presumption is rebuttable. That word is doing the work in every defense built on Donohue since.
What "rebuttable" requires
A presumption is a legal default. It tells the fact-finder which party loses if no further evidence is produced. With the rebuttable presumption Donohue established, the burden falls to the employer to come forward with evidence that the meal period was either taken, knowingly waived, or excused under one of the recognized exceptions. The employer doesn't have to prove the negative absolutely. It has to produce enough evidence to shift the burden back to the employee to prove the violation.
The form of evidence the Court contemplated, and that defense-side guidance has consolidated around since, is contemporaneous per-pay-period employee attestation. Each pay period, the employee affirms or disputes specific facts about meal and rest breaks taken during that period. The attestation is dated, signed, and stored.
This is not a clever workaround. It is the evidentiary tool the Court described in Donohue itself.
What the attestation has to capture
A defensible per-period attestation, in operating terms, captures four things at a minimum:
- Whether each meal break in the period was provided — by the employer's policy, on each shift of five hours or longer.
- Whether each break that was provided was actually taken — and if not, whether it was waived voluntarily by the employee.
- Whether the break was uninterrupted — that is, the employee was relieved of all duty for the full thirty minutes (or twenty for the second meal break, where applicable).
- Whether the time record for the period accurately reflects the breaks taken — including the start time, end time, and duration.
Each of these is a specific factual claim about a specific shift on a specific day, attested by the specific employee whose break it was. The attestation does not need to be a single document. It needs to be a record system that can produce, on demand, for any employee on any pay period in the relevant statute-of-limitations window, the four facts above.
What hire-day waivers actually do
The most common defense artifact we see employers point to is a meal-period waiver signed at hire. The waiver says some version of I acknowledge the company's meal-break policy and agree to take my breaks as required.
This is not a Donohue defense. It is a policy-distribution document. It establishes that the employee was informed of the rule. It establishes nothing about whether any particular break was taken on any particular day. The presumption is per-period; a one-time hire-day waiver is not.
Plaintiffs' counsel know this distinction. So do the courts. The presence of a hire-day waiver does not defeat a Donohue presumption; the absence of it is a separate problem on a separate claim.
What goes wrong in implementation
Three failure modes show up in nearly every audit we run:
Batch attestation. The employer collects attestations once a month, or once a quarter, summarizing what happened in the period. Late-batched attestations are weaker than contemporaneous ones. By the time a quarterly review prompts an employee to sign, the employee no longer remembers which shift on which day featured which break. The attestation devolves into a check-box exercise that does not survive cross-examination.
Manager-signed attestations. The employer collects a single signoff from the foreman, the supervisor, or the office manager, claiming that breaks were taken across the period. This is a witness statement, not an attestation. The Court was specific in Donohue about who has personal knowledge of whether a break was taken: the employee. A manager's signoff is not the rebuttal vehicle.
Aggregate attestations. In Q2, all my breaks were taken on time. The employer wants efficiency; the employee wants to finish the form; the law wants per-shift specificity. Aggregate attestations cannot rebut a per-shift presumption because they cannot speak to whether the specific shift the plaintiff identifies as the violation date was the one that was anomalous.
The structural fix is per-period, per-employee attestation tied to specific shifts, captured contemporaneously, stored in a way that produces a clean record on demand. Bilingual where the workforce is bilingual. Recorded against the time data, not separately from it.
What this looks like productized
This work is what Floburn ships as MicroForensics for California construction and logistics employers. The platform integrates with the timekeeping system the employer already runs (BusyBusy, ExakTime, ADP, Paylocity, Samsara, Motive) and routes a per-period attestation flow to every hourly employee. The output is a structured, queryable record that can produce the Donohue rebuttal evidence on demand.
The work has lived in custom-build form for years. In 2024 the §2699 reform changed the economics of getting it right — the 15% PAGA penalty cap is conditional on the same evidence that defeats the Donohue presumption. The two doctrines now point at the same record. The record we build for one is the record that satisfies the other.
What to do if you don't have this yet
The conservative move, on the day an employer realizes their attestation regime fails the Donohue test, is to implement a contemporaneous per-period attestation immediately, going forward, and to document the change. The historical record cannot be rewritten. The forward-going record can be built in days.
Most matters that hinge on Donohue turn on the period adjacent to the alleged violation. A clean attestation regime starting on Day 1 of the next pay period is a meaningful protection on Day 1 of the next matter. Waiting until counsel asks for the records is too late.
If you'd like to walk through how this looks against your current timekeeping stack, the discovery call is the right starting point. We won't recommend the work if your existing system already produces Donohue-defensible attestations. We will tell you what we find.