Labor Code §552 does not say an employer may not let employees work seven days. It says the employer may not cause them to. Peak season, weather recovery, and a shutdown schedule are where that distinction stops being academic.
This is a small statute that produces large per-employee counts, and it is typically discovered the same way: opposing counsel gets the schedules in discovery, sorts them, and finds every instance of seven consecutive worked days across three years. Nobody had to complain. The schedules complain on their own.
The guarantee itself is two sections and four lines. The sections around it are what decide cases.
Labor Code §551: every person employed in any occupation of labor is entitled to one day's rest therefrom in seven.
Labor Code §552: no employer of labor shall cause his employees to work more than six days in seven.
Labor Code §553: "Any person who violates this chapter is guilty of a misdemeanor." One line, on the same page as the rest.
Labor Code §556 carries the exemption, in one sentence: "Sections 551 and 552 shall not apply to any employer or employee when the total hours of employment do not exceed 30 hours in any week or six hours in any one day thereof."
Two limits, joined by an "or" that sits under a negation — and how the two combine is genuinely unsettled. Read as two ceilings that both have to hold, §556 describes a light part-time schedule: under 30 hours across the week, and no single day in that week over six. Read as a choice between two tests, an employee working only 30 hours could sit inside the exemption even with some shifts longer than six hours. California courts have construed the daily limit without resolving which reading governs the pair, so we are not going to tell you which one does — that question goes to your counsel before anyone relies on the exemption at all.
What does not depend on the answer is the size of the door. Section 556 is written for genuinely light schedules, and a crew working ordinary full shifts is not walking through it on either reading.
Labor Code §558 supplies the civil penalty, and the condition attached to it is easy to skim past. The penalty is "fifty dollars ($50) for each underpaid employee for each pay period for which the employee was underpaid in addition to an amount sufficient to recover underpaid wages," and one hundred dollars for each subsequent violation on the same terms. A seventh day that was worked and paid, at premium, correctly, does not obviously produce an underpaid employee or an underpaid pay period. That is not a reason to relax. It is a reason to know that the penalty theory in a day-of-rest claim is a live question, not a foregone multiplication, and it is a question for your counsel rather than for a spreadsheet.
Where §558 does not carry the claim, PAGA's default civil penalty runs per aggrieved employee per pay period, distributed 65 percent to the LWDA and 35 percent to employees.
Notice what is not in any of this: a premium. There is no "seventh-day pay" that cures a §552 violation. Section 510 prices the seventh day — time and a half for "the first eight hours worked on the seventh day of work in any one workweek," double time beyond — and that is an obligation about how much the work is paid, not about whether it was lawful to schedule. Paying the premium correctly and violating §552 are entirely compatible.
Read §510's phrasing again, because it is doing something this whole subject turns on. It counts the seventh day of work in any one workweek. Not the seventh consecutive day. The workweek is the unit.
Sections 551 and 552 say "in seven." Neither says week. So the question is whether the seven means the seven days of a defined workweek or any rolling span of seven — and the difference is not small. An employee who works Wednesday through the following Tuesday has worked seven days in a row. If the workweek runs Sunday to Saturday, that run straddles two of them, and each of the two contains a day off.
The chapter those sections live in supplies a definition. Labor Code §500 opens Division 2, Part 2, Chapter 1 — which contains §§551, 552, 553, 554, 556, and 558 — with this: "'Workweek' and 'week' mean any seven consecutive days, starting with the same calendar day each week. 'Workweek' is a fixed and regularly recurring period of 168 hours, seven consecutive 24-hour periods."
Be precise about what that settles. It governs §556 directly, which conditions its exemption on hours "in any week," and it governs §510 in the same chapter. It does not appear in §551 or §552, which say "seven," not "week." So the definition is context, not a conclusion. California courts have answered how they read together; we do not characterize a holding we have not verified against the opinion, so ask your counsel for that answer by name rather than taking a reading from us.
What survives whichever way the answer runs is the operating consequence: how your workweek is defined, and whether that definition is written down, is a compliance fact, not a bookkeeping detail. Whether a given run is a problem on your facts is a legal conclusion and your counsel's. Whether you can produce the count at all is not — that is a data question, and it has an answer today.
If nobody at your company can name the workweek boundary and point to where it is written down, that is the first thing to fix, and it is a one-page fix.
Section 552 does not say an employer may not let employees work seven days. It says the employer may not cause them to — and "cause" is a word about the employer's conduct: what it required, asked for, scheduled, rewarded, or made clear it expected. Whether a given seventh day was caused or chosen is a question about what happened in one particular week, on one particular crew, in front of one particular foreman. It is a factual line, which means it is decided on evidence.
Which produces the operational point of the whole post: the paper trail is the defense. If an employee genuinely volunteered for the seventh day, that fact exists in someone's memory unless somebody wrote it down that week. Two years later, the plaintiff's account is that the foreman made clear who was expected on Sunday, and the employer's account is a supervisor who does not remember the conversation.
Schedule-critical work is where seven-day weeks come from, and it usually comes from a real operational reason.
In construction: pours that cannot be interrupted, shutdown windows with a hard restart date, and weather recovery — the three rainy weeks in February that have to be made up in March, on a schedule that was already tight.
In freight and warehousing: seven-day operations by design, where the exposure is not an exceptional push but the ordinary rotation. Peak season is where violations cluster, because the rotation that works at normal volume gets suspended and nobody re-checks it against the workweek boundary when it is restored.
In both, the person who builds the schedule is solving for coverage and is not thinking about §552, which is entirely reasonable — it is not their job, and nobody has ever given them a rule to schedule against.
Labor Code §554 is where employers reach when the pour cannot stop, and it is worth knowing exactly what it offers. Three things, in one section.
First, an exception. Sections 551 and 552 "do not apply to cases of emergency or to work performed in the protection of life or property from loss or destruction, or to any common carrier engaged in or connected with the movement of trains." That is about emergencies. It is not about a tight schedule.
Second, accumulation. Nothing in the chapter "shall be construed to prevent an accumulation of days of rest when the nature of the employment reasonably requires that the employee work seven or more consecutive days, if in each calendar month the employee receives days of rest equivalent to one day's rest in seven." Read that twice, because it carries two conditions and a third time period: the nature of the employment has to reasonably require the consecutive run, and the make-up is measured across the calendar month — which is neither the workday nor the workweek the rest of the chapter runs on.
Third, §554(b): the Chief of the Division of Labor Standards Enforcement "may, when in his or her judgment hardship will result, exempt any employer or employees from the provisions of Sections 551 and 552." That is a discretionary agency exemption somebody has to ask for. It is not a status a schedule falls into.
Whether a pour, a shutdown window, or three rainy weeks made up in March is work whose nature "reasonably requires" seven or more consecutive days is a legal conclusion on your facts, and it is your counsel's. What an operator can do without reaching any legal conclusion is keep the records that question runs on: what the run was, why it happened, when it started, when it ended, and what days of rest each calendar month actually contained.
A documented workweek definition. Which day it starts, applied consistently, written down, and dated. Changing it later is possible and has its own consequences; not knowing it is the problem.
Schedules and time records mapped to that workweek, so the seven-day question can be answered from the employer's data rather than reconstructed from the plaintiff's.
A contemporaneous volunteer record where seventh-day work happens by employee choice — dated, specific to the week, and capturing that the employee knew the day off was available and took the shift anyway. The knowledge half is what makes it a record of a choice and not merely of a shift: an employee who did not know a day off was on offer did not turn one down, and a §552 question is about what the employer did to produce the seventh day. Not a blanket acknowledgment signed at hire, which establishes that someone was told a rule existed and nothing about any particular Sunday.
A monthly rest-day accounting wherever a run of seven or more consecutive days is being carried on §554's accumulation language — because that provision measures the make-up by calendar month, and the workweek reports that answer everything else in this post do not answer it.
A recurring schedule audit that flags seven-day sequences before they happen instead of after. This is the whole difference between a compliance program and a filing cabinet: the flag that fires while next week's schedule is still editable costs nothing, and the same finding after the fact is a wage claim with a documented notice attached to it.
That last point is worth being blunt about. Section 2699(g)(2)'s first enumerated example of a reasonable step is not "conducted periodic payroll audits." It is "conducted periodic payroll audits and took action in response to the results of the audit." An audit that identifies seventh-day sequences and records nothing about what was done with them is not the enumerated example. It is the first half of it, in writing, in a file that gets produced. If you are going to look, decide first who closes the item and what closing it requires.
Three questions for whoever builds your schedules. All three are answered from files that already exist.
What day does our workweek start, and where is that written down?
Show me every employee who worked seven or more days in a row last quarter, and which workweeks those runs fall in.
For each of those runs, what does the file say about why it happened?
The first question gates the second: a count taken against a workweek nobody has defined is a count of something else. The third is the one nobody has ever been asked, and it is the one §554 and §552 both run on. None of the three requires a legal conclusion, and none of them requires us.
If you'd like your last quarter of schedules mapped against your defined workweek, the discovery call is the right starting point. We can tell you where the seven-day runs are, which workweeks they fall in, and whether any volunteer documentation exists for them. Whether any of those runs violates §552 is your counsel's call on your facts, and we will not make it for you.