Under California's manufacturing wage order, double time applies to hours over 12 in a workday and to hours over 8 on a seventh consecutive day. If you set hourly schedules for a California hire, two double-time triggers belong on your checklist before the first shift is posted. The first applies when hours in a single workday go past 12. The second applies on the seventh consecutive day of work in a workweek, once hours go past eight. Both come from the California manufacturing wage order, and both can add cost to a week that looks ordinary on a schedule grid. This post explains the wording, walks through a few counts, and suggests how to set up schedules so the triggers show up before the shift starts rather than on the payroll report.
Key takeaways
- Count hours worked, not hours planned, against the 12-hour line in every workday.
- Track consecutive days worked for each person, since a scheduled day off breaks the run.
- Review each seventh-day shift before you confirm it, because hours past 8 on that day are paid at double time.
- Write your workday start time and workweek start day in one place that scheduling and payroll both use.
- Confirm the full text of Title 8, Section 11010 before you publish a schedule that relies on either trigger.
What counts as a workday and a workweek in California?
Under the manufacturing wage order, a workday is a fixed 24-hour window, and a workweek is a fixed run of seven days. Both definitions tie the count to a start point, so the clock you use matters as much as the hours you add up.
The order defines the workday this way:
> (P) "Workday" and "day" means any consecutive 24-hour period beginning at the same time each calendar day.
The workweek is defined in the next paragraph of the same section:
> (Q) "Workweek" and "week" means any seven (7) consecutive days, starting with the same calendar day each week. "Workweek" is a fixed and regularly recurring period of 168 hours, seven (7) consecutive 24-hour periods.
Both quotes come from California Code of Regulations, Title 8, Section 11010.
Two practical readings follow from those definitions. A workday starts at a set time, so a shift that begins at 6:00 a.m. and runs into the next morning belongs to the 24-hour period that started at 6:00 a.m., not to whatever calendar date appears on the timesheet. A workweek starts on the same calendar day every week, so your payroll week and your scheduling week should begin on that same day. If they do not match, a double-time count can land in the wrong week and make a correct schedule look wrong on paper, or the reverse.
Small teams often keep scheduling in a spreadsheet or a simple app that counts days by the calendar. That works until a shift crosses midnight or a payroll week starts on a different day from the posted schedule. Write down your workday start time and your workweek start day in one place, and make sure the people who build the schedule and the people who run payroll use the same two facts.
What is the first trigger: hours over 12 in one workday?
Hours worked in excess of 12 in any workday are paid at double the employee's regular rate of pay. The order states the rule in a single subsection that also contains the seventh-day trigger, so read the two parts together:
> (b) Double the employee's regular rate of pay for all hours worked in excess of 12 hours in any workday and for all hours worked in excess of eight (8) hours on the seventh (7th) consecutive day of work in a workweek.
Source: California Code of Regulations, Title 8, Section 11010.
Here is a count to test your own schedule against. Suppose a line worker's workday starts at 6:00 a.m., and every hour of work from that start point counts toward the day. If the worker is still on the job for two hours beyond that line, those two hours are paid at double the regular rate. The first 12 hours are not covered by this trigger, though other parts of the order may still apply to them.
Two details make this trigger easy to miss. First, it counts hours worked in the workday, not the hours a manager planned. A shift that was planned as a shorter day can cross the 12-hour line once a handover runs late or a task spills over, and nobody sees the extra time until the timesheet is in. Second, the extra hours arrive at the end of a long day, which is when people are most tired and most likely to accept an extension without thinking about the cost. A rule that is easy to explain to a supervisor is one that gets checked before the shift, so put the 12-hour line on the schedule itself.
When you build a schedule, record the planned start and end time for each shift and calculate the hours worked, not the hours paid, against the 12-hour line. If a shift can run past 12 because of a process that often overruns, change the planned end time or split the work across two people rather than leaving the overrun to chance.
What is the second trigger: the seventh consecutive day of work?
On the seventh consecutive day of work in a workweek, hours past eight are paid at double the regular rate. This is the second half of the subsection quoted above, and it stands on its own: it applies only when the worker has reached the seventh day in a row inside one workweek.
Take a worker scheduled for seven days in a row within a single workweek. Suppose the first six days run at a normal length, and on the seventh day the worker works nine hours. The one hour past eight is paid at double the regular rate. The first eight hours on that seventh day are outside this trigger.
The word "consecutive" does most of the work here. A scheduled day off breaks the run. A worker who works six days, takes one day off, and then works two more days has not reached a seventh consecutive day in that pattern. That is a useful fact for planning, because it means a rest day in the middle of a week can prevent the trigger from applying at all. It is also a reason to check the count against the actual days worked, not against the days a planner assumed would be worked.
Because the order ties the count to a workweek, check how your timekeeping system handles a run that crosses from one workweek into the next. Set the week start in the system to match the order's definition, then run a test with a sample schedule that includes a streak across the boundary before you rely on the report. For setup steps, see Time clock setup: 7 gaps to fix before payroll export. The table that follows summarizes the double-time and overtime rules quoted in this post.
| Rule in the quoted text | Hours that count | Pay the order requires |
|---|---|---|
| Workday over 12 hours (subsection (b)) | Hours past 12 in one workday | Double the regular rate |
| Seventh consecutive day of work in a workweek (subsection (b)) | Hours past 8 on that day | Double the regular rate |
| Workweek over 40 hours | Hours past 40 in the workweek | One and one half (1 1/2) times the regular rate |
| Regularly scheduled alternative workweek of up to 10 hours per day within 40 hours | Up to 10 hours per day under the adopted schedule | No daily overtime rate, if adopted under the order's election procedures |
Sources for the rows are the manufacturing wage order, Title 8, Section 11010. Use the table as a quick reference, and check the full text before you rely on any row.
Illustrative example: a 14-hour day and a 10-hour seventh day
A worker starts at 6 a.m. and works 14 hours on the first day of a workweek. The last 2 hours fall past the 12-hour line and are paid at double the regular rate. The worker then works 8 hours on each of days two through six, and 10 hours on the seventh consecutive day. The 2 hours past 8 on that seventh day are also paid at double the regular rate. Confirm each shift against the order before you publish the schedule.
Does the 40-hour weekly rule change how I count double time?
The weekly overtime rule is separate from the two double-time triggers, and many people already know it from basic overtime practice. The same section sets a limit on daily and weekly hours and then gives the rate for hours beyond the weekly line:
> Such employees shall not be employed more than eight (8) hours in any workday or more than 40 in a workweek unless the employee receives one and one half (1 1/2) times such employee's regular rate of pay for all hours worked over 40 hours in the workweek.
The rate for hours over 40 in a workweek is one and one half times the regular rate. How it combines with double-time hours on the same days is a separate question. A week can contain both kinds of hours, so the combination matters when you price a schedule. One way to organize the check is to first mark the hours that fall under a double-time trigger, then look at the weekly total against 40 and price the remaining hours by the order's weekly rule. Confirm that method against the full section before you put it into payroll, because this post quotes only the parts it needs. For the weekly rule on its own, see State overtime rules from 4 pages before the offer.
The practical lesson is to avoid stacking the two sets of hours in one week without reviewing them together. A worker who has a long day, a seventh day, and a total above 40 for the week can have hours that need careful pricing. A review that checks only one of the three measures can miss a cost that shows up in another.
Can an alternative workweek schedule avoid daily overtime?
A regularly scheduled alternative workweek can avoid the daily overtime rate, but only when it is adopted under the order's election procedures and stays within a 40-hour workweek. The order states the condition directly:
> (1) No employer shall be deemed to have violated the daily overtime provisions by instituting, pursuant to the election procedures set forth in this wage order, a regularly scheduled alternative workweek schedule of not more than ten (10) hours per day within a 40 hour workweek without the payment of an overtime rate of compensation.
Read the quote closely. It speaks to the daily overtime provisions. Before you schedule 10-hour days under this approach, confirm with the full text whether the double-time triggers still apply to the hours in those days.
The quote also sets a ceiling. A schedule of up to 10 hours per day fits the wording, but a 12-hour day falls outside the alternative schedule described in this quote. The regular-schedule requirement matters too. A schedule that changes from week to week is a different situation from one that is regularly scheduled, so an alternative schedule is easier to defend when it is posted in advance and kept stable for the workers it covers.
How do salaried nonexempt workers fit into these counts?
Salaried nonexempt workers are still covered by the hours rules, and the order gives a separate formula for their overtime rate. That formula does not automatically settle their double-time pay. The order describes the overtime calculation this way:
> (c) The overtime rate of compensation required to be paid to a nonexempt full-time salaried employee shall be computed by using the employee's regular hourly salary as one fortieth (1/40) of the employee's weekly salary.
The formula sets the overtime rate, so do not assume the same arithmetic carries over to the double-time hours in this post. If you hire salaried nonexempt staff, ask payroll how double-time hours are priced before you publish a schedule that relies on them. A schedule that looks cheap for a salaried role can still carry extra hours that are paid at a different rate than the base salary suggests.
Salaried roles can also hide long days, because the base salary stays the same whether a day runs 8 hours or 13, even though hours past the order's thresholds still carry premium pay for nonexempt staff. For that reason, keep hours worked in the schedule even when the salary is fixed. Recording the hours does not change the pay formula, but it shows whether a role is regularly running past the 12-hour line.
How should a recruiter build a schedule that avoids surprise double time?
Start with the shift length, not the headcount, because both triggers are set by how many hours a person works in a day and how many days in a row they work. A schedule grid that shows only the names and the days can hide both problems. A grid that shows start times, end times, and the running count of consecutive days makes them visible.
Build the grid around four habits. First, write each shift with a fixed start and end time, so the workday can be counted from a known start point. Second, keep a running count of consecutive days worked for each person, reset by any scheduled day off, so the seventh day is visible before the schedule is published. Third, when a streak reaches its sixth day, review the seventh day shift before it is confirmed, since that shift is where the eight-hour line applies. Fourth, set a planned end time that leaves room for handovers, so a shift planned to finish just under the 12-hour line does not cross it because of a late task.
A short weekly review keeps the grid honest. Pull the workers with the longest consecutive streaks, read the planned start and end times for any shift that comes close to the 12-hour line, and compare the seventh-day shifts with what the timesheet report shows. A short check each week is cheaper than correcting pay after it has gone out.
These habits take a few minutes for each schedule, and they help catch cases before the worker is in the building. They also make the conversation with a hiring manager simpler. Instead of arguing about whether a shift was too long, you can point to the planned start and end times and the consecutive-day count that were agreed in advance.
What should a small staffing team check before it offers an hourly schedule?
Before an offer goes out, confirm three facts: which wage order covers the role, when the payroll workweek starts, and how the timekeeping system counts consecutive days. If any of the three is unclear, the schedule is not ready to promise to the applicant.
Next, have payroll flag two kinds of shifts automatically. The first is any workday with hours past 12. The second is any seventh-day shift with hours past 8. A flag on the timesheet report catches the cases the scheduler missed, and it gives you a record that the check was done. Ask whether the system can flag both conditions, or whether a person must review them each week.
Finally, write the schedule rule into the job record or the offer letter so the hiring manager and the worker see the same plan. A shared written schedule reduces disagreement later about how many hours a shift should run or whether a seventh day was expected. If the plan changes, update the record and tell the worker in writing. The point is not to add paperwork but to make sure the people who create the schedule, approve it, and pay for it are working from the same facts.
When does a different rule apply?
A different rule applies when the hire falls under another wage order, because every quote in this post comes from the manufacturing industry order in Title 8, Section 11010. If your hire works in a different industry, that other order may apply, and its text may differ from what is quoted here. Check which order covers the role before you rely on any number in this post.
Also check whether any other rule covers the worker. A schedule that passes one check can still fail another, and a single source rarely tells the whole story for a particular role. The Title 8, Section 11010 text is the place to confirm the wording quoted here, and it is a good starting point for the questions your payroll team and counsel will ask. Keep the source open beside your schedule, and check the text before you publish a shift that runs past 12 hours or a seventh day that runs past 8.
Your next step today
Open the schedule you plan to post and mark every shift that runs past 12 hours and every seventh consecutive day of work. Check the planned start and end times for each marked shift before you confirm it.
Frequently asked questions
What hours earn double time in California?
Under the manufacturing wage order, hours past 12 in one workday, and hours past 8 on the seventh consecutive day of work in a workweek, are paid at double the regular rate.
Does a scheduled day off reset the seventh-day count?
Yes. A scheduled day off breaks the run of consecutive days, so a worker who works six days, takes one day off, and then works two more days has not reached a seventh consecutive day in that pattern.
Where should I check the wording before I publish a schedule?
Check the full text of California Code of Regulations, Title 8, Section 11010 before you publish a schedule that relies on either trigger.
General information, not legal or tax advice.