Straight into the service manual page
WrenchQuarry
More

3 conditions set before a California on-duty meal break

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

A lunch counts as an on-duty meal break only when the employee is not relieved of all duty during the 30-minute period. California allows an on-duty lunch only when three conditions hold: the work prevents relief, a written agreement exists, and the revocation right is stated.

  • The nature of the work must prevent relief from all duty, judged on objective criteria — any employee in the role would have to be blocked by the necessary job duties
  • A written agreement between employer and employee must permit the on-duty lunch
  • The agreement must state the employee may revoke it in writing at any time
  • The on-duty lunch counts as hours worked and is paid at the regular rate of pay for the full 30 minutes
  • The next meal period must be called no later than six hours after the prior one ends

What makes a lunch an on-duty meal break in California

A lunch counts as an on-duty meal break when your tech is not relieved of all duty during the 30-minute period. The California Department of Industrial Relations, Division of Labor Standards Enforcement (DLSE) states that "Unless the employee is relieved of all duty during his or her thirty minute meal period, the meal period shall be considered an 'on duty' meal period that is counted as hours worked which must be compensated at the employee's regular rate of pay."

So the break stays on the clock and you pay for it. The meal periods come from IWC Orders 1-15, Section 11, Order 16, Section 10, as the same DLSE page sets out. That one condition — no relief from duty — is where most dispatch confusion starts. Your tech sits in the van with the radio on, waiting on a callback. Relief from duty has not happened, so the lunch is on duty.

The second condition is narrower. An on-duty meal period is allowed only when the nature of the work stops the employee from being relieved of all duty. And it needs a written agreement between employer and employee that sets the on-the-job paid meal period. The DLSE meal period FAQ states: "An 'on duty' meal period shall be permitted only when the nature of the work prevents an employee from being relieved of all duty and when by written agreement between the employer and employee an on-the-job paid meal period is agreed to."

The third condition is the revocation clause. The DLSE FAQ requires that "The written agreement must state that the employee may, in writing, revoke the agreement at any time." Your form needs that sentence. Without it, the agreement does not carry.

The first condition has a harder part to it: the objective criteria test. The DLSE FAQ says "An employer and employee may not agree to an on-duty meal period unless, based on objective criteria, any employee would be prevented from being relieved of all duty based on the necessary job duties." That test is where the arrangement stands or falls before the paperwork matters.


Why a duty-free 30 minutes is the default

The duty-free 30 minutes is the base rule, and the on-duty option is the exception built on top of it. If your tech is free to eat, off the radio, and not waiting on anything, the lunch is off duty. The DLSE meal period FAQ treats that as the starting point and lets the on-duty form apply only inside the narrow case above.

Counting matters here too. The DLSE FAQ states that "a subsequent meal period must be called not later than six hours after the termination of the preceding meal period." So the timing of the first lunch pushes the timing of the second one.

An on-duty lunch is still a meal period. It counts as hours worked and gets paid at the regular rate of pay. That changes nothing about when the second meal period must be called. Schedule accordingly.

There is a carve-out worth knowing if your crew overlaps with care settings. The DLSE FAQ notes that "Minor exceptions to this general rule exist under IWC Order 5-2001 regarding healthcare workers." Field techs at a clinic or hospital site may fall under that order, and your schedule would follow its terms instead.

What if a tech wants to skip lunch and go home early? The DLSE FAQ addresses the trade: "Is it permissible if I choose to work through my meal period so that I can leave my job 30 minutes early?" The answer runs through the same conditions above. The nature of the work has to block relief, and the written agreement has to be in place.

These rules come from the IWC Orders, which apply by operation of law under Labor Code Section 1171, as the DLSE exemptions page sets out. That means the orders reach the covered employees in your California schedule without a separate adoption step.


The three conditions side by side

Here is the checklist your schedule and your paperwork both have to satisfy, drawn from the rules above:

ConditionWhat it means for your schedule
Nature of the work blocks relief from all dutyOnly certain job sites qualify, judged on objective criteria
Written agreement between employer and employeeWritten agreement on file that permits the on-duty lunch
Agreement states the employee may revoke in writing at any timeKeep the revocation path open on the form itself

Two points to carry past the table. The objective criteria test is about the necessary job duties, not about a busy Tuesday. And the revocation sentence lives in the agreement text, so a form without it fails on its face.


The objective criteria test, and who fails it

The objective criteria test decides the case before you draft anything. Any employee in the role would have to be prevented from relief by the necessary job duties. If one tech in the same position could hand off and eat, the test does not pass.

The DLSE FAQ offers examples of jobs that fit: "a sole worker in a coffee kiosk, a sole worker in an all-night convenience store, and a security guard stationed alone at a remote site." Each one names a lone worker with no handoff available during the period.

Read those examples closely. The common thread is being the only person on site. Your solo tech at a remote pump station resembles that shape. Your tech working a two-person crew shift does not.

A radio turned down is not the same as no one to cover. If a partner or a dispatcher can take the call, the nature of the work does not block relief, and the objective criteria test fails. The paperwork would not save the arrangement.

Schedule with that in mind. When you build the day, look for the sites where the tech is genuinely alone for the full 30 minutes. Those are your applicants for an on-duty lunch, subject to the written agreement.


What the written agreement has to say

The agreement is short, and the content is fixed. The DLSE FAQ requires the agreement to cover the on-the-job paid meal period and to state the revocation right. First, the on-the-job paid meal period is agreed to by employer and employee. Second, the employee may revoke the agreement in writing at any time.

Keep the revocation language in the body of the form, not in a footnote. The DLSE FAQ ties the revocation right to the agreement itself. If the sentence is missing, the agreement does not meet the requirement.

Revocation is a live feature of the arrangement. Your tech can hand back the signed form and the default duty-free break applies again from that point. Build a path for that in your scheduling process so the change shows up on next week's roster.

Set your own policy to have the tech sign the agreement before the first on-duty lunch is worked. The DLSE FAQ frames the agreement as the thing that permits the arrangement. A retroactive signature answers a different question than the one you are trying to settle.

One caution on scope. The objective criteria test in the DLSE FAQ is objective. Two employees in the same job title should land on the same answer. If one tech's site passes and another's does not, look at the job duties, not the individuals.


How the on-duty lunch plays out across a shift

Let a shift run from 7:00 am to 3:30 pm with a first meal period at 11:00 am. If that lunch is on duty and ends at 11:30 am, the second meal period must be called no later than 5:30 pm under the six-hour count.

Now move the first lunch later. Say it runs 2:00 pm to 2:30 pm. The six-hour count from 2:30 pm runs to 8:30 pm, past a 3:30 pm end of shift, so again nothing further is triggered. The timing of the first meal period changes what the rest of the day requires.

An on-duty lunch stays on the clock either way. Your tech is paid at the regular rate for the full 30 minutes, and the roster shows the meal period rather than unpaid time. Budget the hours that way when you cost out the day.

Late lunches shift everything downstream. If the first meal period is called at 4:00 pm and ends at 4:30 pm, the next one is due by 10:30 pm. For an evening crew, that lands inside the shift and needs a slot on the roster.

The same six-hour count applies after any meal period, on duty or off. Work backwards from the end of the shift when you lay out the day, then confirm each slot against the conditions above.


Where the labor code and the orders meet

The IWC Orders carry the meal period rules, and they reach covered employees by operation of law. The DLSE exemptions page states "All Orders by operation of law (see Labor Code Section 1171)." Nothing extra is needed for the orders to apply.

For scheduling, that means the meal period requirements in the order apply to the covered employees on your California roster as written. The written agreement is what permits an on-duty meal period in place of the default duty-free one, so it changes what the schedule may do.

The meal period timing itself comes from IWC Orders 1-15, Section 11, Order 16, Section 10. Check which order covers each crew when you set up the schedule, since the text of the order governs the shift in question.

Order 5-2001 carries the healthcare carve-out. If part of your roster works under that order, treat those shifts as their own line in the schedule rather than folding them into the rest.

The practical habit is simple: name the order for each crew, then read that order against the three conditions. One order, one set of answers, no mixing across crews.


Scheduling choices that satisfy all three

Your roster needs the on-duty lunch marked, the site must pass the objective criteria test, and the signed agreement with the revocation sentence in its body must be on file. Hold all three or schedule a duty-free 30 minutes.

Pick sites for on-duty lunches where the tech is alone for the full period. A solo worker at a remote location matches the shape of the examples in the DLSE FAQ. A paired crew does not.

Pay the on-duty lunch at the regular rate of pay for all 30 minutes. The DLSE FAQ counts those minutes as hours worked, so the timesheet shows paid time rather than a deduction.

Watch the six-hour count when a first lunch runs late. The DLSE FAQ requires the next meal period within six hours of the prior one ending. Shift the whole afternoon block when you move the first slot.

Keep the revocation path visible to the crew. When a tech revokes in writing, the next schedule reverts to duty-free lunches at that assignment without waiting for a contract cycle.

Note your open questions early. The sources above do not say how an on-duty meal period interacts with short-shift rules under the order covering a given crew; raise that with the employer's counsel when you set up the form.


What to hold in the file

Hold the signed written agreement for every tech on an on-duty lunch, with the revocation sentence in the body of the form. The DLSE FAQ makes the agreement one of the conditions for the arrangement, along with the work-prevents-relief test and the revocation statement.

Hold the site notes that support the objective criteria finding. The test in the DLSE FAQ looks at whether any employee in the role would be blocked from relief by the necessary job duties. A short note on each site shows how the crew reached that answer.

Hold your rosters with meal periods marked on or off duty and the times they were called. The six-hour count in the DLSE FAQ works from the termination of the prior meal period, so the recorded times carry the proof.

Hold any written revocation the moment it arrives, and update the next schedule. The revocation right belongs to the employee under the agreement text the DLSE FAQ requires.

Keep the order name with each crew's file. The meal period rules come from IWC Orders 1-15, Section 11, Order 16, Section 10, and Order 5-2001 covers the healthcare exception the DLSE FAQ mentions.


A dispatcher's pass before the week locks

Run this list once the draft roster exists:

  • Site check — is the tech alone for the full 30 minutes with no handoff available?
  • Agreement — is the signed form on file with the revocation sentence in the body?
  • Timing — does the six-hour count from each meal period fit inside the shift?
  • Order — does this crew fall under the order whose text you have read for the shift?
  • Pay code — does the timesheet show the on-duty lunch as hours worked at the regular rate?

Each line maps back to one condition or one requirement from the pages linked above. If a line cannot be answered, schedule a duty-free 30 minutes for that shift instead.

The arrangement only stands when all three conditions hold at once: the work blocks relief, the written agreement exists, and the revocation sentence is in it. A lunch that fails any condition cannot be scheduled as an on-duty meal period, and if the employee is not relieved of all duty it still counts as on duty and is paid at the regular rate.

Keep the pattern visible in your roster notes so the next week builds on solid ground. A duty-free lunch remains the default for every shift where the conditions do not all hold.

Related guides: Meal and rest break limits for crews: 5 state rules · California denied milk-break penalties: 2 types · California outdoor heat rules: 3 duties for crews.

Sources

More field guides