Alternative Work Schedule California: Employer Guide

In California, letting your team work four 10-hour days instead of five 8-hour ones sounds like a simple, popular perk. But California is not most states. Here, any day with more than 8 hours of work normally triggers daily overtime, so a 10-hour day would cost you two hours of overtime pay per person, per day, unless you do one specific thing: adopt a legally valid alternative workweek schedule. Get that process right and the 4/10 is free of daily overtime. Get it wrong and you can owe years of back pay.

An alternative workweek schedule, or AWS, is California's statutory mechanism for working longer daily shifts without daily overtime, but only if it is adopted through a strict election process under Labor Code section 511. This guide walks a small business through exactly how it works: the common 4/10 and 9/80 patterns, how overtime still applies, the step-by-step election, how to maintain and repeal it, and the pitfalls that quietly invalidate it and expose you to back pay.

This is written for the California small business owner or manager with no in-house legal team, because nearly every other guide assumes you have counsel on staff. I build compliance records and documentation into FirstHR, and an AWS lives or dies on documented process. This is general information for planning, not legal advice; because the stakes are high, have an attorney review your specific election before you rely on it.

What Is an Alternative Workweek Schedule?

An alternative workweek schedule is a California arrangement, authorized by Labor Code section 511, that allows non-exempt employees to work more than 8 hours in a day (up to 10) without the employer owing daily overtime for those hours, as long as the schedule is formally adopted by the employees. It is the legal exception to California's default rule that overtime kicks in after 8 hours a day.

The key thing to understand is why an AWS is even necessary, and it comes down to California's unusual overtime rules. In most states, overtime is a weekly matter (over 40 hours). In California, overtime is also a daily matter: non-exempt employees earn 1.5x for hours over 8 in a day and 2x over 12. That daily rule is what makes a 10-hour day expensive by default, and the AWS is the only lawful way to switch off the daily-overtime clock for those extra hours.

It is equally important to grasp what an AWS is not. It is not a document an employer can write and impose; it only exists if the employees vote it in. It is not a waiver of all overtime; weekly and double-time rules still apply. And it is not a permanent free pass; it can be repealed, and it must be maintained correctly. Understanding those boundaries up front prevents the most expensive mistakes, which nearly always come from treating an AWS as simpler than it is.

Common AWS Types: 4/10 and 9/80

Almost all alternative workweek schedules in California take one of two forms: the 4/10 and the 9/80. Both compress the workweek into fewer, longer days, and both require the full election process to be valid. Here is how each works.

The 4/10 is the simplest: four 10-hour days and a three-day weekend, every week. The 9/80 is cleverer but trickier: employees work eight 9-hour days plus one 8-hour day across two weeks, earning an extra day off every other week. The 9/80 depends entirely on defining the workweek boundary so that the 8-hour day is split across two workweeks, keeping each week at 40 hours; if that boundary is set wrong, weekly overtime is triggered by accident.

A quick note on healthcare: per the overtime exceptions guidance from the Labor Commissioner, only health care employers covered by Wage Orders 4 and 5 can schedule 12-hour AWS patterns without daily overtime, but those carry their own requirements and are outside the scope of a general small-business guide. For most small businesses, the practical choice is between the 4/10 and the 9/80, and either can be a genuine recruiting and retention advantage when done legally.

How Overtime Works Under an AWS

The most misunderstood thing about an AWS is that it does not eliminate overtime; it only shifts the daily threshold. A valid AWS lets the regularly scheduled hours (up to 10 a day) be worked without daily overtime, but overtime still applies in several important situations, and getting this wrong is a common source of liability.

Under a valid AWS, the statute is specific about when overtime is still owed. An employee earns 1.5x their regular rate for hours worked beyond the regularly scheduled shift (so past 10 hours on a 4/10 day) and for hours over 40 in a workweek. They earn 2x, double time, for hours over 12 in a day and for hours over 8 on any day worked outside the regularly scheduled days. The AWS switches off daily overtime only for the scheduled hours themselves; everything beyond that is still premium pay.

California employees cannot waive their overtime rights individually: the Labor Commissioner's overtime guidance says overtime is owed notwithstanding any agreement to work for a lesser wage. That makes the AWS election the only lawful route to adjusting the daily-overtime threshold, and it only adjusts it within these limits.

The AWS Election Process, Step by Step

Adopting an AWS is a formal, multi-step election process, and every step is mandatory: skipping or fumbling any one of them can invalidate the whole schedule. This is the heart of doing an AWS legally, so here is the full sequence a California small business must follow, drawn from Labor Code section 511 and the election procedure written into the IWC wage orders (section 3 of Wage Order 4, for example).

Two steps trip up small businesses most often. The first is the two-thirds threshold: because a non-vote works like a no, a schedule can fail simply from low turnout, so genuine communication and buy-in matter, not just a favorable count of those who show up. The second is the DLSR reporting and the 30-day gap: employers sometimes start the schedule too early or forget to file, and either mistake can invalidate an otherwise-clean election. Precision here is what protects you.

Maintaining a Valid AWS After Adoption

Winning the election is not the end; an AWS stays valid only if you maintain it correctly afterward, and several ongoing obligations quietly determine whether it holds up. Neglecting them can void a schedule that was properly adopted in the first place.

The core maintenance duties are these. Keep the scheduled days and hours fixed and regularly recurring; an AWS is not a license for constantly shifting schedules, and frequent changes can defeat the exemption. Do not reduce anyone's regular hourly rate because of the AWS. Make a reasonable effort to accommodate employees who cannot work the schedule, including for medical, childcare, or religious reasons, by finding them an eight-hour alternative. And keep meticulous records: the proposal, disclosure, ballots, tally, DLSR filing confirmation, and time records.

A useful and underused tool here is the state's own public database of alternative workweek elections. Employers can use it to confirm their own filing is on record, effectively self-auditing whether the schedule is properly registered. If your election is not findable there, that is a red flag worth fixing before it surfaces in a wage claim.

The Division of Labor Statistics and Research, which keeps that database, asks for the final results only and tells employers not to send the ballots or any records that identify individual workers. The ballots stay in your own files. Treating maintenance as seriously as adoption is what separates a durable AWS from one that collapses under scrutiny.

Repealing or Ending an AWS

An AWS is not permanent, and both employees and employers have paths to end it. Knowing the repeal mechanics matters because an improperly handled repeal, like an improper adoption, can create liability. Here is how ending an AWS works.

Employees can trigger a repeal. Under the wage orders, a petition signed by one-third of the affected employees requires a new secret-ballot election, held no more than 30 days after the petition is submitted but no sooner than 12 months after the same group last voted to adopt or repeal an AWS. If two-thirds then vote to repeal, the employer must comply within 60 days.

Employers have their own exit. The Labor Commissioner's 1999 guidance on AB 60 records the long-standing enforcement policy that an employer can end an AWS unilaterally, without a repeal election, after giving employees reasonable advance notice. The same memo cautions that the wage orders the Industrial Welfare Commission was then writing under AB 60 could restrict that route, so have counsel confirm it before you end a schedule this way.

The important compliance point on either path is the same as with adoption: when the AWS ends, you cannot reduce anyone's regular hourly rate because of it, and you return to standard daily-overtime rules for those hours. Document the repeal or termination just as carefully as you documented the adoption, because the transition period is another moment where pay errors and disputes tend to arise. A clean ending protects you as much as a clean beginning.

Pitfalls That Quietly Void an AWS

Most AWS liability does not come from bad intent; it comes from small procedural mistakes that invalidate an otherwise reasonable schedule. Because an invalid AWS means retroactive daily overtime, often years of it, knowing the common pitfalls is genuinely valuable. Here are the ones that most often catch small businesses.

The frequent invalidating errors are: the ballot was not actually secret, or not held during working hours at the worksite; the employer reduced hourly rates after adoption; the results were not filed with the DLSR within 30 days; the work unit was manipulated to reach two-thirds; the election records were not preserved; or the employer materially changed the schedule (hours, days, structure) without holding a new election. Each of these can void the schedule and expose the employer to back overtime for every hour over 8 a day, potentially for three to four years.

The through-line across every pitfall is that the AWS rewards careful process and clear records and punishes shortcuts. There is no version of an AWS that is safe to run casually. But there is also nothing here a diligent small business cannot handle: each pitfall has an obvious preventive, which is simply doing the corresponding step correctly and keeping proof that you did. That discipline is the whole game.

Doing This Without In-House Counsel

You do not need a full legal department to adopt an AWS, but you do need to treat it as the formal legal process it is, run it precisely, and keep audit-ready records. The reason most guides assume in-house counsel is that the downside of a mistake is serious; the good news is that a careful small business can meet the bar with the right process and tools, plus a focused attorney review at the key moment.

The practical approach for a small business is a hybrid: handle the legwork yourself (drafting the proposal and disclosure, scheduling the meeting, running the election, filing with the DLSR, keeping records), and use a modest, targeted legal review to check the proposal, the work-unit definition, and the ballot before you commit. That keeps cost down while ensuring the highest-risk judgment calls get a professional eye. The recurring theme is documentation, and a template to organize it follows.

This is genuinely where an HR platform earns its place. The disclosure, the ballots, the filing confirmation, the time records showing scheduled versus actual hours and premium pay, all of it needs to be captured, organized, and retrievable years later if a claim arises. Doing that by hand is exactly where small businesses slip; doing it with a system is how a company without in-house counsel runs an AWS as cleanly as a large one, which connects to keeping broader wage-and-hour compliance in order.

Frequently Asked Questions