ORDER GRANTING IN PART MOTION TO DISMISS FIRST AMENDED COMPLAINT
In this putative class action, Plaintiffs Andrew Tan (“Tan”) and Raef Lawson (“Lawson,” and together, “Plaintiffs”) sue Grub Hub Holdings Inc. and GrubHub Inc. (“GrubHub” or “Defendants”), a service that provides food delivery to customers via an on demand dispatch system. The gravamen of Plaintiffs’ First Amended Complaint (“FAC”) is that the delivery driver plaintiffs were misclassified as independent contractors and denied the benefits of California wage-and-hour laws. (Dkt. No. 15.)
BACKGROUND
The following background is based on the FAC allegations and judicially noticeable documents.
Drivers receive a flat fee for each completed delivery plus gratuities, although Defendants do not provide an itemized wage statement showing as much. (Id. ¶ 12.) Defendants require drivers to sign up for shifts of blocks of hours in advance and require that drivers remain within a designated area and be available to accept delivery assignments during those shifts. (Id. ¶ 13.) Defendants also direct drivers’ work in detail, instructing them where to report for shifts, how to dress, where to go to pick up or await deliveries, and to follow requirements regarding food handling and delivery timing or risk termination. (Id.) As Defendants’ business is providing food delivery services, the drivers’ services are integrated into Defendants’ business, which would not exist without them. (Id. ¶ 14.)
As for the specific Labor Code violations, Lawson first alleges that Defendants have violated Section 2802 by failing to reimburse drivers for expenses they paid that Defendants should have borne, including expenses for their vehicles, gas, parking, phone data, and other expenses.” (Id. ¶ 15.)
Next, Lawson alleges that Defendants have violated Section 226(a) by failing to provide proper itemized wage statements. (Id. ¶ 12 & Count II.)
Lawson also alleges violations of Sections 1197 and 1194 for failing to pay the drivers the California minimum wage. Because drivers are paid by delivery and have been required to bear the expenses of their employment, “their weekly pay rates have fallen below California’s minimum wage in many weeks.” (Id. ¶ 16.) In particular, Tan’s wages fell below minimum wage- “during several weeks since he began working for GrubHub in June 2015, as a result of his fuel and vehicle maintenance costs.” (Id.). Lawson’s weekly wages have likewise fallen below minimum wage in “numerous weeks because of the expenses that he has been required to bear, such as fuel and vehicle maintenance costs.” (Id.)
Fourth, Lawson alleges that Defendants failed to compensate drivers for overtime hours worked in violation of Labor Code Sections 1194, 1198, 510, and 554. Lawson and other drivers “have regularly worked more than eight (8) and even twelve (12) hours per day and forty (40) hours per week” without receiving overtime pay. (Id. ¶ 17.) Tan has “regularly worked in excess of sixty hours per week” and “routinely worked more than twelve (12) hours in a day” without receiving time-and-a-half pay for the hours beyond 40 or twice his hourly rate, respectively. (Id.) Lawson worked 45 hours the week of November 30, 2015 and was not paid at time-and-a-half for the hours beyond 40. (Id.)
In Count Y, Lawson alleges that Defendants’ Labor Code violations also constitute unlawful business practices in violation of California’s Unfair Competition Law, Cal. Bus. & Prof. Code § 17200. Lawson and other drivers have lost money and property including business expenses and unpaid wages. Lastly, in the sixth count Plaintiffs seek penalties under PAGA for all of the Labor Code violations. Defendants move to dismiss all six counts.
DISCUSSION
Defendants do not dispute that Plaintiffs have adequately pleaded misclassifieation — that is, that the FAG includes sufficient allegations to plausibly establish that GrubHub classified its drivers as independent contractors when they were actually employees. Instead, Defendants contend that all six FAC counts fail because Plaintiffs have not included enough facts to state a claim for any of the alleged violations. Separately, Defendants urge the Court to abstain from adjudicating Plain
As a threshold matter, Plaintiffs did not substantively respond to Defendants’ argument regarding Count II, the Section 226 claim; instead, Plaintiffs state only that “Lawson will not press his claim for violation of [Section] 226(a).” (Dkt. No. 36 at 10 n.3.) The Court will therefore dismiss Plaintiffs’ Section 226 claim with prejudice.
I. Whether Plaintiffs’ Claims are Sufficiently Pled
A. Count I: Labor Code Section 2802
California Labor Code Section 2802 requires an employer to “indemnify his or her employee for all necessary expenditures or losses incurred by the employee in direct consequence of the discharge of his or her duties, or of his or her obedience to the directions of the employer.” Merely alleging failure to reimburse unspecified work-related expenses is not enough to state a Section 2802 claim. See, e.g., Lenk v. Monolithic Power Sys., Inc., No. 15-cv-01148-NC,
Here, Plaintiffs allege that they were required to bear expenses related to “their vehicles, gas, parking, phone data, and other expenses.” (Dkt. No. 15 ¶ 15 & Count I.) Drawing all reasonable inferences in Plaintiffs’ favor, these allegations are sufficient to state a plausible claim for relief because Plaintiffs have identified the type of expenses that GrubHub failed to reimburse. See Garcia,
Defendants’ insistence that Plaintiffs’ claim fails because they have not alleged that the expenses were necessary to the discharge of their duties ignores that the FAC allegations support such an inference: an app-based delivery service requires a vehicle and a phone and thus
Defendants’ argument that Plaintiffs failed to allege that Defendants knew or had reason to know of the expenditures fares no better. (See Dkt. No. 21 at 14-15.) Assuming that a Section 2802 plaintiff must plead such knowledge, the FAC allegations plausibly support an inference of GrubHub’s knowledge. It is plausible to infer that Defendants were aware that class members incurred these expenses from the nature of their business — an app-based food delivery service that requires drivers to use their cars and cell phones. Stuart v. RadioShack Corp.,
Finally, Defendants maintain that Landers v. Quality Communications, Inc., 771 .F.3d 638 (2014), as amended (Jan. 26, 2015), requires plaintiffs to specify a particular work week in which they incurred reimbursement-related losses. In Landers, the Ninth Circuit for the first time addressed pleading requirements for minimum wage and overtime claims under the Federal Labor Standards Act (“FLSA”), 29 U.S.C. § 207, in the wake of Twombly and Iqbal.
But even doing so, nothing in Landers suggests that to state a plausible claim for failure to reimburse business expenses a plaintiff must identify a particular calendar week; here, the allegation is that because GrubHub did not treat Plaintiffs as employees, they never reimbursed the identified expenses. As Plaintiffs have identified the expenses that Defendants failed to reimburse, the claim can proceed.
C. Counts III & IV: California Minimum Wage & Overtime Laws
The FAC alleges that because Plaintiffs are paid per delivery and have to bear them own expenses, Plaintiffs’ and other drivers’ weekly pay rates have fallen below state minimum wage requirements in many weeks. (Id. ¶ 16.) Further, Tan’s weekly wages “fell below minimum wage during several weeks since he began working for GrubHub in 2015, as a result of his fuel and vehicle maintenance costs” and Lawson’s wages likewise have fallen below minimum wage “in numerous weeks because of the expenses that he has been required to bear, such as fuel and vehicle maintenance costs.” (Id.) With respect to the overtime claim, the FAC alleges that Plaintiffs and other drivers have regularly worked more than 8 or even 12 hours in a day and 40 hours per week without receiving overtime pay. (Id. ¶ 17.) Tan “regularly worked in excess of [60] hours per week” without receiving time-and-a-half pay for the hours that exceeded 40 in a week, and “routinely worked more than [12] hours in a day” without receiving “twice his regu
As explained above, in Landers, the Ninth Circuit addressed pleading requirements for minimum and overtime wage claims and held the plaintiffs claims were insufficient because the plaintiff did not include “any detail regarding a given workweek when [he] worked in excess of forty hours and was not paid overtime for that given workweek and/or was not paid minimum wages.”
“In Landers’ wake, courts have offered varying and possibly inconsistent standards for stating wage-and-hour claims under California law.” Sanchez v. Ritz Carlton, No. No. CV 15-3484 PSG (PJWx),
On the other hand, Landers does not require the plaintiff to identify an exact calendar week or particular instance of denied overtime; instead, the allegations need only give rise to a plausible inference that there was such an instance. See Boon,
Plaintiffs have not done so. There are no . allegations about what period of time or type of conduct Plaintiffs are counting as hours worked. Without these basic factual allegations, the Court cannot conclude that Plaintiffs’ minimum wage or overtime claims are plausible. In them opposition, Plaintiffs allege that the drivers’ entire shifts were compensable. (See Dkt. No. 36 at 19 (“[T]he time that they are on shift is work time[J”) (citation omitted).) This allegation does not appear in the FAC, and the Court does not consider new facts alleged in a plaintiffs opposition to a motion to dismiss. See Broam v. Bogan,
Moreover, even if the FAC had alleged that the entire shift is compensable, such a conclusory allegation is not enough to state a claim. California law requires employees to be paid for “all hours” worked “at the statutory or agreed rate and no part of this rate may be used as a credit against a minimum wage obligation.” Armenta v. Osmose, Inc.,
“It is well established that an employee’s on call or standby time may require compensation.” Mendiola v. CPS Sec. Solutions, Inc.,
“California courts considering whether on-call time constitutes hours worked have primarily focused on the extent of the employer’s control.” Mendiola,
(1) whether there was an on-premises living requirement; (2) whether there were excessive geographical restrictions on employee’s movements; (3) whether the frequency of calls was unduly restrictive; (4) whether a fixed time limit for response was unduly restrictive; (5) whether the on-call employee could easily trade on-call responsibilities; (6) whether use of a pager could ease restrictions; (7) whether the employee had actually engaged in personal activities during call-in time.
Mendiola,
Here, the FAC alleges that drivers sign up for work shifts in blocks of hours, and during the shifts they “must be within an area assigned by GrubHub and must be available to accept delivery assignments.” (Dkt. No. 15 ¶ 13.) The FAC also alleges that GrubHub instructs drivers where to wait for deliveries and imposes timeliness requirements that drivers must follow or risk termination. (Id.) Plaintiffs urge that these allegations “establish the fact that if [drivers] are engaging in... non-work related activities... during their shifts, they will be fired.” (Dkt. No. 36 at 19.) Not so. There are no allegations about how large the assigned waiting area is, how many assignments Plaintiffs or drivers typically receive during each shift, or what, if anything, Plaintiffs and drivers generally engage in during their shifts when they are not responding to a delivery assignment. Absent allegations that give context to the waiting time, while it is possible that drivers’ waiting time is compensable and, thus, that the entire shift counts as hours worked for the purposes of their minimum wage and overtime claims, it is not yet plausible.
Indeed, a court in this District recently reached a similar conclusion in Yucesoy v. Uber Techs., Inc., No. 15-cv-00262-EMC,
Plaintiffs’ attempts to distinguish Yuce-soy are unavailing. They note that unlike the drivers there, who could log on or off the app at any time and did not have to accept all assignments offered to them, Plaintiffs here allege that drivers have to sign up for shifts in advance and must be available to accept assignments. (Dkt. No. 15 ¶ 13.) But Plaintiffs have failed to draw any distinction between the problem in Yucesoy and the one here: that there are no allegations about how many assignments the drivers received or what happens if a driver declines an assignment during a shift. The termination allegation in the FAC is only related to drivers’ timeliness in responding to delivery assignments and handling of food, not declining to take on an assignment altogether. And absent allegations about the number and timing of assignments, geographical restrictions, and what happens when a driver does not accept an assignment, there is no factual basis to support a plausible inference that drivers could not engage in personal activities during their shifts and thus that their entire shifts were compensable. As this is the foundation on which Plaintiffs’ minimum wage and overtime claims presumably rest, the Court will dismiss these claims with leave to amend.
D. Count V: Unlawful Business Practices
The UCL provides a cause of action for business practices that are (1) unlawful, (2) unfair, or (3) fraudulent. Id. § 17200. Each prong is independently actionable. Lozano v. AT&T Wireless Servs., Inc.,
“An unlawful business practice or act within the meaning of the UCL is an act or practice, committed pursuant to business activity, that is at the same time forbidden by law.” Pinel v. Aurora Loan Servs., LLC,
E. Count VI: PAGA Claims
Plaintiffs bring a representative PAGA claim seeking civil penalties for the same Labor Code violations alleged in Counts I through V.
1. Plaintiffs’ PAGA Claims Fail to State a Claim
Because these claims are derivative of Plaintiffs’ first five causes of action, some of which fail to state a claim, so too do the PAGA claims fail to the extent they are premised on insufficient predicate Labor Code violations. See Varsam,
But Plaintiffs’ PAGA claims fall short for another reason as well: failure to plead administrative exhaustion. To state a claim under PAGA, an aggrieved employee must first “give written notice by certified mail to the [Labor and Workforce Development Agency [’LWDA’] and the employer of the specific provisions of [the Labor Code] alleged to have been violated, including the facts and theories to support the alleged violation,” and then wait 30 days for the LWDA to declare whether it will investigate the alleged violations or, if the LWDA fails to give notice, wait 33 days from the notice date before filing suit. Cal. Labor Code § 2699.3(a)(1)-(2). After “exhausting these administrative remedies, a party bringing a civil action must plead compliance with the pre-filing notice and exhaustion requirements.” Thomas v. Home Depot USA Inc.,
Defendants also contend that Plaintiffs are barred from pursuing their PAGA claims because another GrubHub driver is already pursuing the same PAGA claims on behalf of the same group of allegedly aggrieved employees. (See Dkt. No. 21 at 18-19.) In other words, Defendants invoke a first-to-file rule. On June 12, 2015, Hakima Mitchell, a GrubHub driver since December 2014, filed an action in Los Angeles County Superior Court on her own behalf and all drivers who used the GrabHub software application in California from June 12, 2014 to the present. Hakima Mitchell v. Grubhub, Inc., No.
Not so. PAGA provides in relevant part: No action may be brought under this section by an aggrieved employee if the agency or any of its departments, divisions, commissions, boards, agencies, or employees, on the same facts and theories, cites a person within the time-frames set forth in Section 2699.3 for a violation of the same section or sections of the Labor Code under which the aggrieved employee is attempting to recover a civil penalty on behalf of himself or herself or others or initiates a proceeding pursuant to Section 98.3.
Cal. Labor Code § 2699(h) (emphasis added). The plain language of the statute bars an employee from bringing a PAGA action when the LWDA has cited an employer. But the statute is silent with respect to whether an employee may bring a PAGA action when another private plaintiff brings suit against the employer in a representative capacity. Defendants have not cited a single case that has held as much.
And in fact, a court in this District recently rejected this very argument. See Order re: First-Filed Rule and Uber’s Request for Stay/Dismissal Pursuant to Colorado River Abstention Doctrine, O’Connor v. Uber Techs., Inc., No. 13-cv-03826-EMC et al.,
[T]he issue at bar was not presented in those cases, and the statements therein are merely descriptive of section 2699(h); they were not holdings. Importantly, other than a one sentence description, none of those cases explain why section 2699(h) should be read to include deferring to a suit brought by private plaintiffs (as opposed to the LWDA) when the statutory language makes no such provision.
The other cases on which Defendants rely do not change the Court’s conclusion. True, a court in this District explained that “the real party in interest in a representative PAGA action is the government, which the plaintiff is deputized to represent.” Hernandez v. DMSI Staffing, LLC,
Nor does the legislative history change the Court’s conclusion. Defendants cite statutory analysis from PAGA’s authors in which they explain that due to the representative nature of PAGA actions, “[a]n action on behalf of other aggrieved employees would be final as to those plaintiffs, and an employer would not have to be concerned with future suits on the same issue by someone else.” (Dkt. No. 22 at 32.) But this reasoning does not compel a bar to filing a PAGA claim because of the mere pendency of another PAGA suit on the same issue by someone else. As the O’Connor court noted, it might have engaged in a different analysis had the earlier-filed PAGA claim already been decided, since- any judgment would be binding on government agencies and any aggrieved employee not a party to the proceeding, potentially including the plaintiff in the case. Id. at 3 n.l (citing Arias v. Super. Ct.,
At bottom, Defendants do not cite a single case in which the court held .that two PAGA representatives cannot pursue the same PAGA claims at the same time. The Court declines to be the first to so hold.
2. Colorado River Abstention
Defendants also contend that the Court should dismiss or stay the PAGA claims due to the pendency of Mitchell’s earlier-filed state court action under the abstention doctrine set forth in Colorado River Water Conservation District v. United States,
In determining whether to stay a case pursuant to Colorado River, courts in the Ninth Circuit consider eight factors:
(1) which court first assumed jurisdiction over any property at stake; (2) the inconvenience of the federal forum; (3) the desire to avoid piecemeal litigation; (4) the order in which the forums obtained jurisdiction; (5) whether federal law or state law provides the rule of decision on the merits; (6) whether the state court proceedings can adequately protect the rights of the federal litigants; (7) the desire to avoid forum shopping; and (8) whether the state court proceedings will resolve all issues before the federal court.
R.R. St. & Co.,
However, some of the eight factors are “dispositive.” Intel Corp. v. Advanced Micro Devices, Inc.,
The balance of the Colorado River factors weighs against a stay. The first factor is irrelevant, as there is no property at stake in this case. See, e.g., Sandoval v. M1 Auto Collisions Ctrs.,
“The Ninth Circuit has not yet addressed the propriety of issuing a partial Colorado River stay.” ScripsAmerica, Inc. v. Ironridge Global LLC,
However, at least one district court has concluded that “the third factor, desire to avoid piecemeal litigation, is not well-served ... by a partial stay.” Sciortino,
As to the fourth factor, the state court obtained jurisdiction first, which ordinarily weighs in favor of a stay. Some courts have found that this factor weighs little where there are differences between the two actions. See, e.g., Sandoval,
Sixth, there is no reason to suggest that the state court proceedings cannot adequately protect the rights of the federal litigants when it comes to the PAGA claims, which supports a stay. As for the seventh factor, Plaintiffs initially filed this action in San Francisco County Superior Court, and Defendants removed to District court. This case is therefore unlike the instances of forum shopping in the cases Defendants cite, which involved cases in which the same plaintiffs abandoned state court cases after lengthy litigation in favor of filing in federal court. Lastly, the eighth factor weighs against a stay: while the state court proceedings stand to resolve the PAGA claims at issue here in their entirety, it will not resolve all issues before the federal court because the underlying Labor Code violations will remain here to be litigated.
Considering all of these factors, this is not an “exceptional” case justifying Colorado River abstention. Ultimately, because the separate, predicate Labor Code violations are not in the state action and they will have to be addressed here anyway, there is little reason to dismiss or stay the PAGA claims in this action that are predicated on the same Labor Code violations. While the calculus may change if and when the state court enters judgment on Mitchell’s PAGA claims, under the circumstances presented now the Court declines to abstain on the basis of the Colorado River doctrine.
CONCLUSION
For the reasons discussed above, the Court GRANTS IN PART the motion to dismiss. Count II (the Section 226 claim) is dismissed with prejudice. Counts III, IV, and VI (the minimum wage, overtime, and PAGA claims) are dismissed with leave to amend. Count V (the UCL claim) is dismissed with leave to amend to the extent it is predicated on the insufficiently pled Labor Code violations alleged in Counts II, III, and IV. The Court declines to dismiss or stay the PAGA claims pursuant to Colorado River at this time. Plaintiffs must file any amended complaint within 21 days of this Order.
This Order disposes of Docket No. 21.
IT IS SO ORDERED.
Notes
. Record citations are to material in the Electronic Case File ("ECF”); pinpoint citations are to the ECF-generated page numbers at the top of the documents.
. When adjudicating a motion to dismiss brought pursuant to Federal Rule of Civil Procedure 12(b)(6), the Court generally cannot consider matters outside of the complaint without converting the motion into a motion for summary judgment. However/courts may consider documents alleged in a complaint and essential to a plaintiff’s claims. See Branch v. Tunnell,
. As discussed above, although Landers discussed overtime claims asserted under the FLSA, its reasoning applies to overtime claims asserted under the California Labor Code, as well. This is especially true for overtime and wage claims because the language of the FLSA and Labor Code provisions is strikingly similar. Indeed, other courts have reached the same conclusion, applying Lan-ders to state overtime claims. See, e.g., Boon v. Canon Bus. Solutions, Inc.,
. As Plaintiffs have dropped their Section 226 claim alleged in Count II, they have likewise abandoned their claim for PAGA penalties for violations of that statute.
