Labor Code §512 lets a meal period be waived by mutual consent when the day's work is six hours or less, and it never says the consent has to be written. Waiver is the employer's exception to invoke, so an unwritten one is proved from memory, and the shift with the short punch is the one you will be asked about.
"The meal was waived." Every employer who runs short shifts says it, and it is often true. Ask the next question, which is the one a plaintiff's firm asks, and the room goes quiet: show me the consent, for this employee, for that day.
What comes out of the file is usually one of two things. A form signed at hire that says the employee has read the meal-break policy and agrees to take breaks as the company requires. Or nothing, with the explanation that the statute does not require a waiver to be in writing.
The second statement is correct. It is also the reason the first document is the wrong one, and the reason the file matters more than the statute's silence suggests.
Labor Code §512(a), in full:
An employer shall not employ an employee for a work period of more than five hours per day without providing the employee with a meal period of not less than 30 minutes, except that if the total work period per day of the employee is no more than six hours, the meal period may be waived by mutual consent of both the employer and employee. An employer shall not employ an employee for a work period of more than 10 hours per day without providing the employee with a second meal period of not less than 30 minutes, except that if the total hours worked is no more than 12 hours, the second meal period may be waived by mutual consent of the employer and the employee only if the first meal period was not waived.
Three things are in that text. The employer must provide the meal period; that is the rule. The waiver is an exception to the rule, and it is available only inside a band: a day of six hours or less for the first meal, a day of twelve hours or less for the second, and the second only if the first was taken. And the exception is unlocked by mutual consent, the consent of both parties.
One thing is not in the text. The words "in writing" do not appear anywhere in §512(a). The construction wage order, Wage Order 16, repeats the section in its own §10(A) and (B) and adds nothing about writing either. Check the meal section of whichever order governs your crews; the words are not there.
So an employer who says the statute does not require a written waiver is reading it correctly.
The statute puts the obligation on the employer and hands the employer an exception. In any dispute, the party that relies on an exception is the party that has to establish it. A meal-period claim starts from the rule: a work period over five hours, no meal period provided. The employer's answer is "waived by mutual consent." That answer is the employer's to prove, and what it has to prove is a state of mind that existed on a particular day: that this employee, for this class of shift, agreed.
Now look at what the employer's own records contribute to that fight, because they contribute a great deal, in the wrong direction.
The wage order compels a time record that shows meal periods. Wage Order 16 §6(A)(1) requires records showing "when the employee begins and ends each work period," and adds: "Meal periods, split shift intervals, and total daily hours worked shall also be recorded." A 5.5-hour shift with no meal punch is a compelled record showing a meal period that was not taken. Under Donohue v. AMN Services (Cal. 2021), a time record showing a missed, short or late meal period raises a rebuttable presumption that the period was not provided, and the burden moves to the employer to rebut it. "Waived" rebuts it, if the consent can be shown.
An unwritten waiver is rebutted from testimony. The foreman remembers that everyone on the short crew preferred to leave early. The employee remembers being told that is how the short shift works. Whichever account the fact-finder believes, the employer has spent the presumption fight on memory, on a claim that a piece of paper would have settled.
That is the whole argument for writing it down. The statute does not demand the writing. The burden does.
The form most employers produce is a policy acknowledgment: the employee has read the meal-break policy and agrees to take breaks as required. We wrote about that document in April, and the point bears repeating in one sentence here. It establishes that the employee was informed of the rule. It does not waive anything, and it says nothing about whether any particular short shift was worked by agreement.
A waiver is the opposite instrument. It is the employee's agreement not to take a meal period the statute would otherwise require, limited to the shift bands §512(a) allows, given in advance of the shifts it covers. A document that does not say that is not a waiver, however many signatures it carries.
Two forms are in circulation. A per-shift waiver, signed each time a short shift is worked. And a prospective waiver, signed once and covering every qualifying shift until revoked.
Whether a single prospective waiver satisfies "mutual consent" for every later shift it covers has been litigated in the Court of Appeal, and how that authority applies to your form and your crews is a question for your counsel, not for us. What we can say is what makes either form provable, because that is a records question.
Our own practice is that a waiver is written, prospective, and revocable, and that each one carries four dates and facts: who signed it, which shift band it covers (six hours or less; ten to twelve hours), the date it was signed, and the date it was revoked, if it ever was. Not because the statute prescribes that form. Because the party who has to prove consent is the employer, and a waiver the employee could withdraw at any time is a waiver whose consent is easier to defend as the employee's own.
The second-meal waiver adds a condition the first does not have: it is available "only if the first meal period was not waived." For a crew on four ten-hour days, any day that runs past ten hours crosses into the second-meal band, and the file has to show both that the first meal was taken that day and that the second was waived. A waiver form that does not distinguish the two bands cannot show that.
Employers sometimes reach for "on-duty meal" as a synonym. It is a different mechanism with a different requirement, and the wage order is explicit. Wage Order 16 §10(D):
Unless the employee is relieved of all duty during a thirty (30) minute meal period, the meal period shall be considered an "on duty" meal period and counted as time worked. An "on duty" meal period shall be permitted only when the nature of the work prevents employee from being relieved of all duty and when, by written agreement between the parties, an on-the-job paid meal period is agreed to and complies with Labor Code Section 512.
Two conditions, both the employer's to show: the nature of the work prevents relief, and a written agreement exists. This one the order does require in writing. And the meal is paid, because it is time worked. An operator who describes the working lunch on a pour day as "on-duty" and has neither the written agreement nor the pay record for it has named the exception without meeting it.
A waiver file, however complete, answers one question: whether the short shifts and the long ones were worked by agreement. It says nothing about the shifts between six and ten hours, where no waiver is available and the meal period must be provided. It says nothing about whether a meal period that was scheduled was in fact taken, duty-free, before the end of the fifth hour; that is the per-period record the Donohue post is about. And it does not cure the premium: where a compliant meal period was not provided and no valid waiver covers the day, Labor Code §226.7 owes one hour of pay at the regular rate of compensation for that workday, and the waiver that fails does not reach it.
One more boundary. Construction employees under a qualifying collective bargaining agreement sit outside §512 by its own subdivisions (e) and (f), and outside Wage Order 16 §10 by its subsection (E). Which agreements qualify is a reading your counsel does, per agreement, before any of this applies to that crew.
The waiver register. Every signed waiver, by employee and shift band, with its signature date and its revocation date. The absence of an entry for an employee who worked short shifts is a finding.
The schedule and the punches. Which shifts fell inside the six-hour band and which inside the ten-to-twelve band, so the register can be read against the days it was supposed to cover. A waiver on file for an employee who never worked a qualifying shift proves nothing; a qualifying shift with no waiver behind it is the exposure.
The premium ledger. The §226.7 hour, paid under its own earning code and tied to the specific day, for every day a meal period was owed and not provided. The employer that pays the premium on the day has closed the item; the employer that discovers the day in discovery has not.
Bring the waiver file and one month of punches to a free 30-minute call and we will tell you which of your short shifts have a written consent behind them, which do not, and where the register and the schedule disagree. Whether any given waiver is valid, and which form yours should take, is your counsel's call.
Free · 30 minutes. If it fits, the next step is the records diagnostic, a fixed fee quoted on the call, and anything paid after that is a separate agreement you sign first.