Part VI · Scheduling and Predictability · Chapter 15

Reporting-Time Pay and On-Call Scheduling

Use when an employee reports or is required to call in for a shift and is then sent home or not put to work, triggering reporting-time pay under Wage Order 7.

Reporting-time pay is the wage order's answer to a retail-specific problem: the store that schedules an associate, then sends her home the moment foot traffic disappoints. The rule converts a wasted trip into a small guaranteed wage. The exposure is modest per occurrence and enormous in aggregate, because the practices that trigger it — call-in shifts, on-call windows, last-minute cuts driven by a scheduling app reading yesterday's sales — are run across an entire hourly workforce, every week, for years. A single mis-designed scheduling policy becomes a class-wide, PAGA-amplified liability that is far larger than the few hours of pay any one employee ever lost.

#§ 15.1 The rule: half the shift, floored at two, capped at four

Wage Order No. 7 fixes the obligation. IWC Wage Order No. 7

Three features deserve emphasis. First, the trigger is furnishing less than half the scheduled day — not zero work. An associate scheduled for eight hours and released after three has been furnished less than half and is owed the reporting-time differential, even though she worked. Second, the floor and ceiling are 2 and 4 hours: a four-hour scheduled shift cut short yields a two-hour minimum; a ten-hour shift cut short yields the four-hour cap, not five. Third, payment is at the regular rate of pay for reporting-time hours not actually worked — a straight-time obligation distinct from the "regular rate of compensation" that governs meal-and-rest premiums (see premium pay). Reporting-time pay for hours not worked is not "hours worked," so it does not itself count toward overtime.

#§ 15.2 The contested frontier: does a phone call count as "reporting for work"?

The classic case is the sent-home-early associate who physically appeared. The litigated frontier is the mandatory on-call call-in: the employer requires the employee to telephone the store a set time before a potential shift to learn whether to come in, and then tells her to stay home. Did she "report for work" by calling? The California Court of Appeal said yes — on the facts pleaded.

Case Ward v. Tilly's, Inc. (Cal. Ct. App. 2019) — [HIGH — Shepardize]

What it holds. "Report[ing] for work" under Wage Order 7, § 5(A) does not necessarily require an employee to physically appear at the worksite; it "is best understood as presenting oneself as ordered," in the manner the employer directs. Where an employer requires employees to telephone the store two hours before an on-call shift to learn whether to come in, and an employee does so but is not put to work (or is furnished less than half the scheduled day), the mandatory call-in triggers reporting-time pay. The court reversed an order sustaining a demurrer and remanded. 31 Cal.App.5th at 1185

What it does NOT hold. The holding is deliberately narrow. The court stated: "We do not hold that employees are entitled to reporting time pay whenever they contact their employer to determine what their schedule is. We hold only that if . . . the employer requires the employee to call in two hours before the start of a shift, and the employee does so but 'is not put to work . . . ,' then the employer is liable for reporting time pay." 31 Cal.App.5th at 1191 Merely letting (or asking) employees check their schedule does not, by itself, trigger pay. The court expressly reserved the prospective-versus- retroactive-application question and declined to draw the line on how much advance notice avoids the penalty.

Currency caution. This is a Court of Appeal decision (Second District, Division Three), fact-specific to a mandatory two-hour call-in, decided on a demurrer record (facts assumed, not proven), and it issued 2–1 with a dissent. Justice Egerton read the 1947 legislative history to mean "report for work" required physically appearing and urged that any fix is the Legislature's to make. dis. opn. (31 Cal.App.5th at 1199) Review was denied and the Ninth Circuit later followed Ward in Herrera v. Zumiez, but a contrary federal district decision had gone the other way. Confirm the decision's continued vitality and any line-drawing developments before relying on it.

The practical takeaway for an employer: a true sent-home-early scenario — the employee physically appeared for a scheduled shift and was released — rests on the plain text of § 5 and is on far firmer footing than the proposition that every on-call or call-in practice owes reporting-time pay. Ward extends the rule to one specific design (mandatory pre-shift call-in); it should not be read as a holding that any scheduling friction triggers the penalty.

#§ 15.3 Retail fact patterns

Call-in / on-call shifts. "Call two hours before; we'll tell you if we need you." Under Ward, if the call is mandatory and the answer is "stay home," reporting-time pay is owed on those facts. This is the squarely covered case.
Send-home-early. Slow Tuesday; cut the back half of the floor staff. Any associate furnished less than half her scheduled hours is owed the differential — the oldest and least contestable trigger.
Clopening and same-day double reports. An employee who closes, then is required to report a second time the same workday (e.g., an unscheduled call-back) and gets under two hours implicates the second-reporting provision. Clopening turnaround itself is governed by local fair-workweek rest-between-shifts rules, not the wage order.
Scheduling-app cuts. Algorithmic labor tools that trim shifts off yesterday's sales create exactly the "furnished less than half" event at scale — uniform across the workforce, which is what makes it a class problem.

#§ 15.4 Exposure anatomy

Reporting-time pay is a wage. That single fact is what turns a two-hour straight-time item into outsized liability, by the cascade developed in the exposure anatomy:

Aggregation. A few owed hours per employee, multiplied by a large hourly workforce and a multi-year limitations period, is the entire class-action premise.
Derivative claims. Unpaid reporting-time wages can make the wage statement inaccurate — supporting a § 226 claim where the knowing-and-intentional element is met — and, at separation, waiting-time penalties may run.
PAGA. Per-pay-period civil penalties stack on top, often dwarfing the underlying wages.
Interaction with split-shift pay. A schedule broken by a non-working gap can owe a split-shift premium and, if a segment is cut short, reporting-time pay; the two are distinct obligations analyzed separately.

#§ 15.5 Defense postures

Practice pointer

Design the schedule so the trigger never fires:

Drop mandatory call-in. Replace "call two hours before to find out" with a fixed, confirmed schedule. If on-call coverage is genuinely needed, make the call-in voluntary, or commit to pay the reporting-time minimum for any called-in associate who is released — pricing it in rather than litigating it.
Confirm-by, well in advance. Post and lock schedules far enough ahead that "checking your schedule" (not penalized under Ward) never collapses into a "report as ordered, then go home" event (penalized).
Right-size the scheduled shift. The penalty keys to scheduled hours. Scheduling realistic shift lengths shrinks the "half the scheduled day" exposure if a cut becomes necessary.
Stop sending people home early. Where labor must be trimmed, prefer voluntary early-outs and document them; involuntary release below the half line owes the differential.
Pay correctly when owed. Compute half the scheduled day, apply the 2-hour floor / 4-hour cap, pay at the regular rate, and show it on the wage statement — closing the derivative and PAGA routes above.

#§ 15.1 The rule: half the shift, floored at two, capped at four

#§ 15.2 The contested frontier: does a phone call count as "reporting for work"?

#§ 15.3 Retail fact patterns

#§ 15.4 Exposure anatomy

#§ 15.5 Defense postures

Authorities cited