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.