PAGA Representative Action Exposure for Delivery Misclassification
Single drivers can sue on behalf of entire contractor fleets under California law.
PAGA representative action exposure is the single biggest blind spot for California delivery operators running independent contractor fleets, and it has nothing to do with how good a company's contracts look on paper. The Private Attorneys General Act lets one driver sue on behalf of every similarly situated worker at the company, without ever certifying a class. Pair that mechanism with the ABC test, the strictest worker-classification standard in the country, and a delivery business built on contractor labor is carrying risk that compounds by the pay period. More than 5,000 PAGA suits get filed in California annually, and the delivery sector's operating model, dictated routes, app tracking, flat-fee pay, sits right in the blast radius. Managing that exposure requires understanding how it accumulates.
PAGA's structural dangers for delivery operators
PAGA lets a single employee step into the state's shoes and collect civil penalties for Labor Code violations on behalf of every other affected worker at the company, a mechanism the California Supreme Court laid out in Arias v. Superior Court back in 2009. That sounds like a class action with extra steps. It is a representative action with no certification requirement, which makes PAGA structurally worse for operators than ordinary aggregate litigation.
Class actions come with brakes built in: a plaintiff has to get the class certified, show the claims share common questions that predominate over individual ones, and convince a court the case can actually be managed at trial. PAGA has none of that. The California Supreme Court confirmed as much in Estrada v. Royalty Carpet Mills in 2024, ruling that trial courts cannot toss a PAGA claim just because it would be unwieldy to manage. No certification hearing, no predominance fight, no manageability defense. One driver with one wage statement can put the entire California workforce's penalty exposure on the table.
The standing problem compounds the procedural one. A plaintiff who settles individual claims against the company keeps PAGA standing anyway, under Kim v. Reins from 2020. A plaintiff forced into arbitration on individual claims keeps standing to pursue the representative action regardless, per Adolph v. Uber Technologies in 2023. Settling with the named plaintiff or routing the dispute into arbitration, the two usual escape hatches in employment litigation, does not make the representative claim go away in a PAGA case.
Operators tend to miss the notice step, so it deserves attention. A PAGA case starts with a letter filed with the state labor agency, and that letter often looks like routine correspondence, not the opening move in multimillion-dollar litigation. Operators get a narrow window to evaluate and respond before the plaintiff is free to file suit, a timeline laid out by the California Workplace Law Blog in April 2025. If an operator treats that letter like junk mail, the cure window closes before anyone on the operations side understands what it was.
The ABC test and delivery IC classification risk in California
California presumes a worker is an employee, and under the ABC test adopted in Dynamex Operations West v. Superior Court in 2018 and later written into Labor Code section 2775 through AB5, the hiring company bears the burden of proving otherwise on all three prongs. Missing one prong fails the whole classification.
Prong B is where delivery operators run into trouble: the company has to show the worker performs work outside its usual course of business. A driver delivering packages for a delivery company is not doing peripheral work. Delivery is the business. That is why Grubhub ended up facing a $24.75 million California settlement over delivery driver misclassification in 2026, resolved in court records tied to litigation that traces back to a complaint originally filed in San Francisco County Superior Court in 2015. A decade-long case arriving at that number says something about how long this kind of exposure can sit on the books before it comes due.
Dynamex itself was decided on facts from a same-day delivery company, so the test was built directly out of the delivery context, and its logic transfers cleanly onto last-mile carriers, delivery service partners, and courier fleets operating the same way today. The operational features that make a delivery business run well, assigned routes, live app tracking, performance scoring, required uniforms, company-issued equipment, are exactly the facts courts read as control, and control is what defeats independent contractor status under Prong B and Prong A alike. None of that is bad management. It is just also the evidence a plaintiff's attorney would want.
Operators sometimes point to Proposition 22 as cover, since it carves out app-based rideshare and delivery platforms and was upheld by the California Supreme Court in Castellanos v. State of California in 2024. Prop 22 only applies to platforms meeting narrow statutory criteria built around on-demand, app-based marketplace models. Traditional last-mile carriers, delivery service partners, third-party logistics providers, and courier fleets do not meet those criteria and sit fully inside the ABC test's reach, with no carve-out to fall back on.
The arithmetic of PAGA penalty exposure across a contractor workforce
PAGA exposure scales with headcount and pay frequency as much as with how serious any single violation looks.
The reform did raise the bar on the harshest penalty tier. What used to trigger an elevated penalty on any "subsequent" violation now requires either a prior agency or court finding within the past five years that the specific policy was unlawful, or a judicial determination that the conduct was malicious, fraudulent, or oppressive. That tier is harder to reach than it used to be, but an operator with a prior enforcement history has not escaped it.
Misclassification generates multiple violations at once, not one. A driver wrongly classified as a contractor generates a cluster of concurrent Labor Code claims at once: unpaid minimum wage, missed meal periods, missed rest periods, wage statements that are inaccurate because they were never issued like an employee's, and unreimbursed business expenses for mileage, fuel, and phone data. Each of those carries its own per-pay-period penalty before anything stacks on top. Post-reform, the "derivative stacking" of penalties under Labor Code sections 201 through 204 and section 226 on top of the underlying wage violation has been eliminated, a real cut to exposure. It does not touch the core problem: misclassification was never a single violation to begin with, it is five or six running in parallel.
Labor Code section 226.8 adds another layer on top of all of it: substantial per-worker fines for willful misclassification, where an operator knowingly and voluntarily classified employees as contractors. The look-back periods run one year for the PAGA claim itself, three years for the underlying wage violations, and four years if a plaintiff also pleads a related consumer-protection claim. Multiply that window by headcount, by pay periods per year, by the number of distinct violation types in play, and the total exposure for a mid-sized fleet is a running product of four variables, three of which (headcount, pay frequency, years of operation) the operator does not control by fighting the lawsuit, only by fixing the classification before the next pay period hits.
The reform also changed how recovered penalties get split, sending a larger share to the LWDA and a smaller share to the employees bringing the claim than the prior allocation did. The total pool still runs substantial enough to make these cases attractive to plaintiffs' counsel working on contingency, so the redistribution does not change the calculus for why suits keep getting filed.
Settlement patterns in practice
The 2025-2026 settlement record turns the arithmetic above from a hypothetical into a pattern, and the pattern includes operators of different sizes running different models.
PDX North, Inc., a last-mile automotive parts distribution company running hundreds of delivery drivers, reached a $7 million settlement with the New Jersey Department of Labor and the state Attorney General's office in March 2026, announced as a "landmark" resolution by the agency. What makes the PDX North outcome distinct is not just the dollar figure. The settlement requires PDX North to reclassify its delivery drivers as employees, with full reclassification required by January 1, 2027. A monetary settlement writes a check and moves on. A reclassification order rebuilds the company's labor model from the payroll system up, and that is a materially harder outcome to absorb than a one-time payment.
Dlivrd Technologies Inc. is a last-mile logistics and delivery technology company with a heavy focus on restaurant catering delivery, and it now faces a California class action filed in May 2026. The proposed class alleges that drivers pick up, transport, deliver, and set up catering orders entirely under the company's operational control, the same Prong B fact pattern that sank Grubhub and that underlies the PDX North settlement. The case remains unresolved, which matters on its own: it shows the pipeline of misclassification litigation has not slowed down under the post-reform PAGA regime, it has kept moving.
The two cases share the same common thread: Prong B. In each, delivery is the company's core service, so no operator in this position can credibly argue drivers are performing work outside its usual course of business. That is the fact pattern baked into the business model, not a drafting error in a contractor agreement.
Reclassification exposes a gap operators rarely budget for in advance: the insurance gap. Occupational accident policies written to cover independent contractors are built around the contractor relationship, so if a court or agency later determines that relationship was actually employment, those policies may not cover claims from that period. An operator that gets reclassified is not just rebuilding payroll: it is potentially facing retroactive workers' compensation obligations for a period when it believed, and had insured, a different relationship.
What the 2024 PAGA reform changed for delivery operators
AB 2288 and SB 92, the two bills that reformed PAGA in 2024, cut real exposure for employers who can show good-faith compliance efforts. They did not retire PAGA as an enforcement tool, and in at least one respect they gave plaintiffs a new weapon operators did not face before.
The reform's upside for compliant operators is concrete. Companies that took "all reasonable steps" to comply before ever receiving a PAGA notice now face penalties capped at a fraction of the statutory amount, and companies that act promptly after receiving notice, even without that advance compliance record, qualify for a somewhat higher but still reduced cap. The cure process got broader too: violations covering minimum wage, overtime, meal and rest breaks, business expense reimbursement, and wage statement deficiencies can now be fixed before a suit is even filed, the California Workplace Law Blog reported in April 2025. The elevated penalty tier, as covered above, now requires a prior finding or proof of malicious, fraudulent, or oppressive conduct, a meaningfully higher bar than before. Isolated, short-lived violations that do not extend across multiple consecutive pay periods face reduced per-employee penalties as well.
None of that touches the procedural core. PAGA remains a representative action that needs no class certification, the feature that made it more dangerous than ordinary litigation from the start. Standing still survives individual arbitration under Adolph v. Uber, and "headless" PAGA filings, where a plaintiff pursues only the representative claim and skips the individual one entirely, may narrow the arbitration defense even further. The underlying $100 per-employee, per-pay-period penalty for ongoing violations is still on the books, and systematic misclassification, running across an entire contractor fleet, pay period after pay period, is by definition not the kind of isolated, non-recurring violation the reform's reduced penalties were built for.
The reform also added something delivery operators did not have to contend with before: injunctive relief. PAGA plaintiffs can now ask a court to order operational changes directly, not just pay penalties after the fact. The California Governor's office has described this as allowing courts to compel businesses to implement workplace changes, and CALSAGA has noted that AB 2288 lets PAGA plaintiffs seek injunctive relief for the first time. For a delivery operator, that is a court with the power to order a new classification model, not just a bill for the old one. The reform tightened some penalty math in the operator's favor. It also handed the other side a tool that reaches further into day-to-day operations than anything PAGA plaintiffs had before 2024.
