Flag hours do not replace the clock.

Question presented

A technician’s flag ledger measures credited repair output. A time record measures recorded work intervals. Neither record can substitute for the other. The bounded question is whether the plan and payroll calculation treated every category of compensable time under the rule that applies to that category, while preserving the output units used to calculate piece earnings.

That inquiry begins with the establishment, not the job title. Dealer-connected repair operations generally route to California Wage Order 7; standalone vehicle-repair garages generally route to Wage Order 9. The federal dealership route also requires a qualifying nonmanufacturing establishment and qualifying actual duties. Only after those predicates are mapped should an analyst test a particular pay period.

Rule architecture

A flag plan is ordinarily a piece-rate plan when compensation turns on credited repair operations rather than elapsed hours. The plan should identify the flag-rate table, who receives credit, when an operation is earned, and how warranty reductions, comebacks, split jobs, and later reversals are handled. Payroll terminology is not decisive; the operative formula is. Oman directs attention to the unit the compensation contract promises to cover and whether work falls outside it.

California Labor Code section 226.2 creates distinct branches when piece-rate work occurs in a pay period. Rest and recovery periods require separate compensation under the statute’s average-hourly-rate method, subject to the applicable minimum. Other nonproductive time requires separate compensation at no less than the applicable minimum wage. “Nonproductive” is not a synonym for every minute without a flag. The analyst must first decide whether the interval was hours worked and whether the activity was directly related to the piece-paid work. Diagnosis, required documentation, and tool setup may have a different relationship to the repair unit than a department meeting or assigned lot cleanup.

A genuine hourly base of at least the applicable minimum wage paid for every hour worked in addition to piece earnings can satisfy section 226.2’s other-nonproductive-time branch. A guarantee that merely compares total piece earnings with a pay-period floor is a different design. A high overall average does not, by itself, answer whether the statutory categories were paid in the required manner.

Overtime is another calculation. California generally tests daily and weekly overtime under Labor Code section 510. Federal law ordinarily tests overtime after forty hours using a workweek regular rate that includes piece and other nondiscretionary remuneration. A qualifying mechanic at a qualifying dealership may be exempt from federal overtime under section 13(b)(10), but that route does not erase federal minimum-wage or record duties and does not decide California overtime. The overtime regular rate, section 226.2 rest rate, and any section 226.7 break-premium rate must remain separate computations.

Finally, section 226 and section 226.2 specify wage-statement information, and section 1174 addresses hours, wages, and piece records. A statement can show what payroll reported without proving that all controlled or suffered-permitted work was captured.

Decision sequence

1. Fix the frame. Identify the employer entity, work location, pay period, workweek, local minimum wage, dealer connection, and Wage Order 7 or 9 route.
2. Reconstruct hours worked. Preserve raw punches and edits, then test opening, closing, training, waiting, documentation, and remote activity under the applicable hours-worked standards.
3. Reconstruct output. Match each flag entry to its repair order, technician attribution, rate table, completion event, and any later change.
4. Classify intervals. For each worked interval, distinguish rest/recovery time, activity directly related to a piece-paid unit, and other nonproductive time. Record uncertainty instead of forcing ambiguous gaps into one category.
5. Run separate calculations. Compute piece earnings, rest compensation, other-nonproductive-time compensation, and any state or federal overtime under their own rules. Then test the wage-statement fields.
6. Reconcile the packet. Follow the same dates from plan version to time record, system and repair-order activity, payroll register, wage statement, later true-up, and reimbursement.

Evidence map

The strongest analysis aligns records rather than selecting the most favorable ledger. Raw punches, edit history, schedules, and meal punches establish recorded intervals and facial timing. DMS logins, diagnostic uploads, OEM training, texts, and alarm events can show activity at particular moments; they do not prove continuous work across every gap. Repair orders, flag reports, warranty events, and comeback records establish output attribution and revisions, but not total hours worked.

The signed plan and every effective rate table show the promised pay unit and change rules. Payroll registers and wage statements reveal earning codes, rates, hours, gross amounts, and later adjustments. Establishment records support the wage-order and federal dealership predicates. Tool, device, and uniform records belong in the same dated packet because a pay-rate issue does not resolve whether a required expense or item was handled correctly.

Missing records should be described precisely. They may create uncertainty, support a reasonable inference when paired with credible evidence, or present a separate recordkeeping question. Their absence is not a substitute for proving the underlying activity and amount.

Worked example

Assume a dealer-connected California shop uses a $40-per-flag-hour plan. During one illustrative week, a technician records 40 clock hours and earns 30 flag hours, or $1,200 in piece earnings. The week includes five eight-hour shifts, ten authorized ten-minute rest periods, and four documented hours spent in a mandatory safety meeting and assigned parts inventory that the fact review classifies as other nonproductive time. Assume the statewide 2026 minimum of $16.90 applies and no higher local rate applies. These are assumptions, not findings about another shop.

The four classified nonproductive hours add $67.60 at $16.90. The rest time is 100 minutes, or 1.667 hours. In this simplified illustration with no overtime or other pay, the section 226.2 average rate is the $1,267.60 in non-rest compensation divided by 38.333 non-rest hours, approximately $33.07. Rest compensation is therefore approximately $55.11. The illustrative subtotal is $1,322.71 before testing statement presentation, expenses, or any other component.

Two plan changes produce different analyses. If payroll simply notes that $1,200 divided by 40 exceeds minimum wage and pays nothing for the four classified hours, the favorable average does not perform the separate section 226.2 calculation. If the plan instead pays $16.90 for all 40 clock hours plus the $1,200 piece earnings, the statutory hourly-base branch for other nonproductive time must be evaluated on that actual formula; rest compensation still has its own branch.

The example also does not prove that every unflagged interval was nonproductive. A repair operation can credit fewer flag hours than the clock time needed to complete it, and activities directly related to that unit require classification from the plan and work facts. If the technician had daily or weekly overtime, the analyst would add a distinct regular-rate calculation rather than reuse the $33.07 rest-rate figure.

Strategic implications

For a dealer, the practical control is a period-level reconciliation that preserves raw time, flags, pay codes, and plan versions before payroll closes. Managers should use defined activity categories, document why a flag changes, prevent known off-clock work, and keep rest, nonproductive, and overtime formulas distinct. This architecture can identify both underpayments and false positives caused by comparing incompatible ledgers.

For a technician, the useful record is not a private flag total alone. A dated log should connect start and end times, repair orders, waiting or assigned support work, rest opportunities, system events, and later flag reductions to the corresponding statement. A discrepancy is then a testable proposition: for example, a documented mandatory meeting appears in time and system records but has no identifiable treatment in the plan or payroll calculation.

Both sides gain more from testing a representative set of ordinary, slow, overtime, training, and comeback weeks than from extrapolating one unusual statement across an entire employment period.

Analysis limits

This framework does not determine whether a particular interval was controlled work, directly related piece work, or other nonproductive time. It does not select a local wage, decide whether an apprenticeship affects a tool rule, validate a reversal term, or calculate damages and penalties. Federal and California coverage, limitations periods, good-faith issues, statement injury, and willfulness require separate analysis. Current rules and numeric rates also require rechecking after the listed source-check date.

Primary authority

The principal federal nodes are FLSA section 13(b)(10), 29 C.F.R. section 779.372, Part 785, and Part 778. The principal California nodes are Labor Code sections 226, 226.2, 226.7, 510, and 1174; Wage Orders 7 and 9; MW-2026; DIR’s wage-order classification guide; and Oman v. Delta Air Lines. The authority panel for this guide supplies the official source, proposition, and stated limit for each node.