Employment Law

Solo Wage-and-Hour Claims: When the Math Works Without PAGA or a Class

Most plaintiff PI lawyers reflexively push wage claims toward class or PAGA. The single-plaintiff case still wins on many fact patterns — if you run the numbers honestly on liquidated damages, waiting-time penalties, wage statement penalties, and the fee-shift. Here is the framework.

Overhead view of a blank paper time card next to a calculator and pen on a wooden desk

A wage-and-hour intake walks in with two years of off-the-clock work, a missed-meal pattern, and a final paycheck three weeks late. The reflex on the plaintiff side is to ask whether the same fact pattern repeats across the workforce, then immediately route the file toward a class action or a Private Attorneys General Act representative case. That reflex costs money. For a meaningful share of California wage claims, the single-plaintiff case produces a better client recovery, a higher net fee, and a much shorter cycle time than the aggregation play.

The question is not whether class or PAGA work pays — it does, when the predicates line up. The question is which container fits the facts in front of you. Below is a working economic framework for that triage, oriented to plaintiff PI shops that take wage cases occasionally and want to stop reflexively over-engineering them.

What the Solo Case Actually Pays

The reason single-plaintiff wage cases survive in a class-dominant environment is the stacked statutory recovery. For one non-exempt worker over a three-year unpaid-wage window, the headline number is rarely just the unpaid hours. Labor Code §1194 supplies unpaid minimum wage plus interest and attorney's fees. Section 1194.2 adds liquidated damages equal to the unpaid minimum wage amount. Section 226.7 generates a premium hour per workday for missed meals and a separate premium for missed rest periods. Section 203 waiting-time penalties pay up to thirty days of wages when final pay is late. Section 226(e) wage statement penalties run $50 for the first violation and $100 per subsequent pay period, capped at $4,000, with fees on top.

Stack those on a $20-an-hour warehouse worker with consistent off-the-clock work and missed meals over twenty-four months, and the underlying damages calculation routinely lands between $35,000 and $70,000 before fees and interest. Add the §226(e) cap, §203 penalties, and a §218.5 or §1194 fee-shift, and the realistic settlement window — assuming reasonable proof — sits in the $60,000 to $130,000 range. That is a one-plaintiff case, not a class.

The PAGA and Class Tax

Aggregation looks attractive on the gross number and ugly on the net. A PAGA representative case demands a §2699.3 notice, the agency exhaustion period, the 65/35 split with the LWDA on civil penalties under the post-2024 reform structure, and — increasingly — a court willing to manage scope under Estrada v. Royalty Carpet Mills standards. A class action requires Rule 23-equivalent certification briefing under Code of Civil Procedure §382, a notice plan, opt-out mechanics, and a fairness hearing. Either container adds twelve to twenty-four months of cycle time and six-figure cost exposure for experts, notice administration, and motion practice.

The net-fee comparison is what matters. A solo case with a §1194 fee award and a forty-percent contingency on the merits portion often produces a higher hourly realization than a class settlement that yields a twenty-five to thirty-three percent common-fund fee after a year of certification fights. The same is true against PAGA: the 35% plaintiff share, distributed across aggrieved employees, frequently produces a low per-capita number, and the fee award rides on penalty math the LWDA and the court will both scrutinize.

When Aggregation Is the Right Container

Three fact patterns push toward PAGA or class. First, the violation is structural — a written policy, an auto-deduct meal break, a rounding rule, a uniform misclassification — that produces uniform damages across a defined group. Second, individual damages are small enough that no single worker has a viable case but the aggregate is meaningful (the classic minimum-wage rounding case). Third, the employer is judgment-proof on a single case but has insurance or capital that only responds to bet-the-company exposure.

If none of those three apply, the single-plaintiff case is usually the right call. The intake with a unique supervisor problem, an idiosyncratic schedule, or a fact-specific misclassification dispute does not benefit from class machinery. It benefits from a focused complaint, early written discovery, and a §998 offer timed to the defendant's first reserve revision.

Running the Cost-Benefit on Intake

The triage I use takes about twenty minutes per intake and asks five questions. What is the hourly rate and the unpaid hours per workweek? What is the duration of the violation window, capped at three years for wage claims and four for derivative UCL claims under Business & Professions Code §17200? Is there a final-pay violation that triggers §203? Are wage statements facially defective in a way that lets you plead §226(e) without parol evidence? And is the employer collectible — operating entity, payroll insurance, individual-officer liability under Labor Code §558.1?

If the answers produce a damages number above roughly $25,000 with statutory fees attached, the solo case pencils out. Below that, the file either belongs in small claims, in an aggregation play, or declined. The fee-shift under §1194 and §218.5 is what makes the low-five-figure case economically viable on the plaintiff side — the same way Code of Civil Procedure §1021.5 and contingency fee compliance under Business & Professions Code §6147 shape the rest of the plaintiff bar's economics. For shops that also handle PI work, the fee agreement mechanics overlap directly with the disclosures discussed in our note on California Business & Professions Code §6147 contingency fee compliance.

Discovery Posture and Cycle Time

The solo case wins on cycle time only if you actually run it as a solo case. That means not over-discovering. Standard form interrogatories adapted for wage cases, a focused request for production targeting time records, pay stubs, written policies, and final-pay records, and one deposition of the payroll custodian will usually generate the proof needed. The temptation to take supervisor depositions or expand into class-style sampling discovery should be resisted unless you have decided to convert to a representative action.

Plaintiff testimony matters more in the solo case than in class work because there is no common-proof shortcut. Prepare the client to testify in concrete daily detail about schedules, meal breaks, and the off-the-clock pattern. Defendants routinely move for summary judgment on the theory that the plaintiff's recollection is too vague to overcome the employer's records under Hernandez v. Mendoza-style burden-shifting. A specific witness defeats that motion. A vague witness does not.

Settlement posture follows the same logic. A §998 offer at a defensible damages number, served after written discovery and before depositions, captures the fee-shift asymmetry and either resolves the case or sets up the post-trial fee motion. The plaintiff PI bar has internalized this rhythm in other settings — the same instinct that drives early lien work in cases involving California hospital liens under Civil Code §§3045.1–3045.6 applies here: front-load the work that creates use at the resolution table, not after.

The Misclassification Wrinkle

Independent-contractor misclassification under the Dynamex ABC test, now codified at Labor Code §2775, complicates the solo-versus-class call. A misclassification finding opens up the full menu of non-exempt protections retroactively, which makes the damages calculation explode. It also makes the case look class-shaped because the misclassification is usually applied to a defined role or job code uniformly.

The judgment call is whether the role is sufficiently idiosyncratic to the plaintiff that class certification would fail on commonality, even though the legal theory is uniform. A salesperson with a custom commission structure, a creative-services contractor with bespoke deliverables, or a route-based worker with individualized customer relationships often reads as misclassified on the law but resists certification on the facts. Those are strong solo cases. The same fact pattern with a fleet of identically-situated drivers is a class.

When the File Should Move

Plaintiff PI lawyers who do not specialize in wage work should have a referral relationship with two or three wage-and-hour shops and use it. The signal that a file should move out is not the headline damages number — it is the structural-violation signal. A written policy, a payroll-system rounding rule, an across-the-board meal waiver, or a misclassified job code is a referral. An individual supervisor cheating one worker is not. The same triage discipline that plaintiff lawyers apply to deciding whether a lien-reduction fight justifies the work — discussed in our piece on Medi-Cal lien reduction under the Ahlborn process — applies here. Some files are worth the machinery. Most are not.

The wage-and-hour bar has spent fifteen years building class and PAGA infrastructure because the structural cases reward it. The unintended effect has been to under-serve the individual worker with a strong single-plaintiff case. For plaintiff PI shops with capacity for occasional wage work, that gap is where the economics still favor a focused complaint, a fee-shift, and a short cycle. Run the numbers on the intake. The solo case is usually smaller than the class on paper and larger than the class on net fee per hour worked.

The LawyersTrend Brief · Fridays

One weekly email. Every new article.

Friday mornings — every PI article we publish that week, plus rankings updates and key verdicts. Free. One-click unsubscribe.