The Scope of “Reporting”

What does it mean to report for work?

Reporting-time pay turns on the employee being "required to report for work" and doing so, but the wage order does not define what it means to report — and that definitional gap is where the contemporary disputes arise. When the rule was written, the paradigm was physical: the employee traveled to the workplace and presented for the shift, and "reporting" meant arriving at the door. Modern scheduling has detached the act of reporting from physical arrival. Employees are placed on call and required to telephone in before a potential shift to learn whether to come; they are required to monitor a scheduling application and respond to last-minute postings; they are told to hold themselves available within a window. In each of these arrangements, the employer has imposed a real obligation on the employee's time without the employee necessarily traveling anywhere, and the question is whether discharging that obligation — making the call, checking the app, holding oneself available — is "reporting for work" that triggers the pay.

The stakes of the definitional question are large for restaurants because on-call and call-in scheduling are common tools for matching labor to volatile demand. A restaurant that places servers on call for a busy weekend, requiring them to phone in two hours before a possible shift, is using the call-in to preserve scheduling flexibility — to staff up if the reservations materialize and to release the employees if they do not. Whether that flexibility is free or carries a reporting-time premium depends entirely on whether the required call-in counts as reporting, because if it does, the employee who calls and is released has reported and been furnished no work, triggering the pay. Ward v. Tilly's answered that question for the call-in case, and its answer reshaped on-call scheduling in California; Aleman supplies the countervailing limit through the scheduled-day measure. The sections below develop both and then map the harder modern arrangements that sit between them.

The call-in is reporting

Ward v. Tilly's confronted the call-in case directly and held that the required call-in is reporting for work. The employer scheduled employees for on-call shifts and required them to call in two hours before the start of a potential shift to learn whether they were needed; if told to come in, they worked, and if told not to, they did not, and were paid nothing for the on-call shift. The Court of Appeal held that requiring an employee to call in two hours in advance constitutes "reporting for work" within the meaning of the reporting-time provision, so that an employee who calls in as required and is told not to come has reported and been furnished no work, triggering reporting-time pay. The court reasoned that the on-call call-in imposes precisely the burdens reporting-time pay was designed to address — the employee must keep the time available, refrain from committing it elsewhere, arrange to be reachable, and stand ready to appear — even though no physical travel occurs, and that confining "reporting" to physical presence would let employers extract the benefits of the employee's availability while paying nothing for it.

The significance of Ward is that it ties the reporting-time obligation to the employer's imposition on the employee's time rather than to physical arrival, which is the analytic principle that governs the harder modern cases. After Ward, the question is not whether the employee traveled to the workplace but whether the employer required the employee to present, to call in, or to hold available in a way that constrained the employee's use of the time — if so, discharging that requirement is reporting, and being released without work triggers the pay. This reframing is what makes on-call call-in scheduling carry a reporting-time cost: the very flexibility the employer sought by placing employees on call is the imposition Ward treats as compensable when the employee is released. For the restaurant operator, Ward means that a mandatory call-in is not a free option to be exercised at will but a scheduling choice that owes reporting-time pay each time an employee calls in and is sent away — which fundamentally changes the economics of on-call staffing and is the holding the modern-problem section returns to.

Ward ties reporting to the employer's imposition on the employee's time, not to physical arrival. The on-call call-in is the imposition — and releasing the employee without work is what triggers the pay.

A scheduled short shift, worked in full, owes nothing

Against Ward's expansion stands the limit Aleman v. AirTouch Cellular supplies: reporting-time pay is measured against the scheduled day, so an employee scheduled for a short shift who works it in full has not been furnished less than half and is owed nothing. The plaintiffs in Aleman argued that when they were called in for a brief meeting, they were entitled to a minimum of reporting-time pay regardless of the meeting's scheduled length. The court rejected the argument as to scheduled meetings: because reporting-time pay compensates for being furnished less than half the scheduled day's work, an employee scheduled for a one-hour meeting who attends and works the full hour has been furnished the entire scheduled day, not less than half of it, and the rule is not triggered. The reporting-time guarantee is keyed to the relationship between what was scheduled and what was furnished, and when the employee works the whole of a short scheduled shift, that relationship is satisfied and no premium is owed.

The Aleman line is the crucial counterweight to Ward and the key to managing meeting and short-shift exposure, because it distinguishes the curtailed shift from the short-but-complete one. Reporting-time pay addresses the shift that is cut — the employee scheduled for eight hours and released after one, who was furnished far less than the scheduled day. It does not address the shift that is genuinely short by design and worked in full — the employee scheduled for a one-hour meeting who works the hour. The decisive variable is what the employer scheduled: a short scheduled shift, communicated as such and worked to completion, owes nothing, while a longer scheduled shift cut below half owes the guarantee. This gives the operator a precise and lawful tool: a brief obligation that is genuinely scheduled as brief — a meeting set and communicated as a one-hour meeting — does not trigger reporting-time pay when it runs as scheduled, whereas calling an employee in under an open-ended or full-day expectation and then releasing them early does. The line between the two is the scheduled length, honestly set and communicated, which the meetings section and the exceptions page both build on.

The common restaurant triggers, and how to manage them

Two recurring restaurant practices sit at the intersection of Ward and Aleman, and managing them is the practical payoff of the scope analysis. The first is the required meeting — the pre-shift lineup, the periodic staff meeting, the training session. Calling an employee in for a meeting is requiring the employee to report, so the meeting triggers reporting-time analysis; whether pay is owed turns on Aleman's scheduled-day measure. A meeting genuinely scheduled and communicated as a short meeting — a one-hour lineup that runs an hour — owes nothing, because the employee works the full scheduled short shift. A meeting called in on a day off, or appended to a day with an open-ended expectation, where the employee is furnished less than half a usual day, owes reporting-time pay of at least two hours, and if it is a same-day second appearance it may implicate the second-reporting rule or a split shift as well. The operator's tool is the schedule: set and communicate the meeting's length honestly and run it as scheduled, and the Aleman line controls; call employees in open-endedly and release them, and the premium attaches.

The second practice is the on-call or call-in arrangement, which Ward governs and which the modern-problem section develops further. After Ward, a mandatory call-in before a potential shift is reporting, so each time an employee calls in as required and is released, reporting-time pay is owed. The operator who uses on-call scheduling must therefore price the premium into the practice: the flexibility of placing employees on call is not free, and the cost is a reporting-time payment for each released on-call employee. The disciplined alternatives mirror those for the send-home — schedule against realistic demand so that fewer on-call employees are needed, give definite schedules rather than open-ended on-call status where possible, and, where availability genuinely must be preserved, recognize that the call-in carries the premium and budget for it. The two practices together — meetings managed by the scheduled-day measure, and on-call call-ins priced under Ward — are where a restaurant's reporting-time exposure is concentrated, and the classifier below tests the line between what triggers the pay and what does not.

Each arrangement against Ward and Aleman

Each example is tested against Ward's call-in holding and Aleman's scheduled-day measure. Select a scenario:

Fig. 1. The scope of "reporting" under Ward v. Tilly's (2019) 31 Cal.App.5th 1167 and Aleman (2012) 209 Cal.App.4th 556. A mandatory call-in or required presentation is reporting; a scheduled short shift worked in full, or a self-initiated voluntary check, is not. Outcomes are fact-specific and the modern boundary is evolving.

App-based scheduling and the unsettled boundary

The frontier of the reporting-time inquiry is the modern, technology-mediated on-call arrangement, where the boundary Ward drew is still being mapped. Restaurants increasingly schedule through applications that post shifts on short notice, request confirmations, and require employees to indicate availability or to respond within a window — arrangements that impose obligations on the employee's time in ways that resemble, but are not identical to, the two-hour telephone call-in in Ward. The unsettled question is how far Ward's principle extends: whether requiring an employee to monitor an app and respond to last-minute postings is reporting, whether holding oneself available within a designated window is reporting, whether a required text-in is the call-in by another medium. Ward's reasoning — that reporting tracks the employer's imposition on the employee's time, not physical travel — points toward treating genuine, mandatory availability obligations as reporting, but the precise line between a compensable availability requirement and a non-compensable convenience has not been comprehensively drawn, and it is litigated case by case.

The practical posture this counsels is conservative, because the asymmetry of the uncertainty favors caution. Where the employer genuinely requires the employee to call in, text in, or hold available before a potential shift — imposing a real constraint on the employee's time that the employee must honor — the prudent course is to treat that requirement as reporting under Ward and to pay reporting-time pay when the employee is then released, rather than to wager that the particular medium or format escapes Ward's principle. The downside of erring toward payment is a modest premium; the downside of erring against it is unpaid wages across every released employee under a recurring arrangement, with the wage-statement, waiting-time, and PAGA cascade that unpaid premiums carry. The operator who wishes to avoid the premium altogether should avoid imposing mandatory pre-shift availability obligations — giving definite schedules instead of open-ended on-call status — rather than imposing them and hoping the format is not "reporting." As the boundary is mapped, the safe assumption is that a real, employer-required availability obligation is reporting; the exceptions page addresses the separate question of when a reporting obligation, once triggered, is nonetheless excused.

Price the call-in, use the scheduled-day measure, and treat real availability obligations as reporting