Class-Action Proof Your California Startup

Adapted with permission from Class-Action Proof Your Business by Benjamin J. Treger, a California employment attorney and Story ally.

Why good startups get sued

Ben's central point is one founders resist: fair treatment is not a defense. California employment law is dense and technical, it changes often, and it pairs strict penalties with attorney's-fee awards. That combination means even a small mistake, repeated across a workforce and across pay periods, can become catastrophic liability.

The lawsuit usually starts with one disgruntled employee and one phone call. Plaintiff's counsel, who typically takes around 35 percent of any recovery, has every incentive to steer an individual grievance into a class action or PAGA claim. The PAGA notice that follows is often a template alleging violations of virtually every employment law imaginable, including some that cannot possibly apply. It is cheap for them to send and expensive for you to answer.

Discovery is where the damage happens. Plaintiff's consultants run your time and payroll records through software that treats every one-minute discrepancy, rounding issue, or miscalculation as a violation. Multiply by dozens or hundreds of employees and the numbers escalate quickly. Most cases settle, because trial is expensive, unpredictable, and public.

For an early-stage company, this is the difference between a survivable quarter and an unsurvivable one.

The nine places startups get hurt

1. Meal periods

Meal periods must be at least 30 minutes, must begin before the end of the fifth hour of work, and must be truly duty-free. Ben's practical moves: schedule meals to begin before the end of the fourth hour so you have a one-hour buffer for the inevitable slippage; schedule 35- or 45-minute breaks rather than exactly 30; configure lockouts so employees cannot clock back in early; and set real-time alerts when an employee has not clocked out for a meal by a defined threshold.

The hardest allegation to defend is that a break was interrupted, which can be made even when the time records show a timely, full-length break. The answer is end-of-shift and end-of-pay-period attestations: the employee confirms breaks were received, duty-free, and uninterrupted before clocking out, and any inability to attest routes automatically to HR.

Meal-period waivers and on-duty meal agreements are permitted only in specific conditions. If you use them, get them signed before the arrangement begins, track which employees have one on file, and periodically reconfirm that the arrangement is still voluntary and still justified.

2. Rest breaks

Rest breaks are paid and are not recorded on timecards, so there is no system data showing whether one occurred. That makes attestations the single most important rest-break tool, because they are often the only affirmative evidence breaks were taken. Build rest breaks into shift plans in your scheduling software, train managers to actively authorize and encourage them rather than making them theoretically available, and make sure employees can physically leave the work area.

3. Regular-rate calculations

The regular rate of pay (total weekly compensation divided by total hours worked) is the base for overtime, meal and rest premiums, sick pay, and other statutory payments. It changes week to week. Errors compound silently, and the proof is sitting in your own payroll records.

Ben's cautionary example: an employer's on-site meal allowance legally had to be included in the regular rate and was not. The underpayment was a few cents per employee per pay period, about $25,000 in total. The penalties exceeded $6 million.

The fix is a compensation audit: catalog every payment type (base wages, discretionary and nondiscretionary bonuses, shift differentials, stipends, allowances, commissions, piece rates, per diems, equipment reimbursements), classify each as included in or excluded from the regular rate, and document the analysis. Then translate the findings into payroll-system configuration and QA the output against a manual calculation for a sample of employees. Repeat whenever you introduce or restructure a form of compensation.

A warning that applies to every startup running on Gusto, Rippling, or Justworks: your payroll provider's service agreement almost certainly disclaims responsibility for legal compliance. Configuration is on you.

4. Overtime

California requires daily overtime, not just weekly: time-and-a-half after 8 hours in a day, double time after 12, and additional rules on the seventh consecutive day of a workweek. Configure timekeeping for California's daily thresholds, set approaching-overtime alerts at 8 hours daily and 40 weekly, and capture all compensable time, including travel between job sites (not ordinary commuting), mandatory training, and pre- and post-shift duties like booting up systems or attending briefings.

Train managers on "suffer or permit": if they know or should know an employee is working, that time must be recorded and paid. As Ben puts it, "just clock out and finish up" is one of the most expensive sentences in employment law.

5. Off-the-clock work

A written policy prohibiting off-the-clock work is necessary but not sufficient. Where feasible, enforce it technologically by disabling access to email, internal tools, and point-of-sale systems outside scheduled hours. Audit what employees routinely do before clocking in and after clocking out; if the company requires or controls it, it must be paid. Give employees a reporting channel they will actually use, and discipline managers who encourage or tolerate unrecorded work.

6. Exempt versus non-exempt classification

Misclassification is a class-action goldmine: if one job title is misclassified, every employee holding that title has the same claim. Startups are especially exposed because early hires wear many hats and titles inflate quickly.

Review every role against the applicable duties tests (executive, administrative, professional, computer professional, outside sales). Confirm every exempt employee earns at least California's minimum exempt salary, which is twice the state minimum wage for full-time work and rises as the minimum wage does. Document the analysis for each role, including the share of time spent on exempt versus non-exempt duties. Classify borderline roles as non-exempt. When the audit finds errors, handle reclassification carefully: calculate and pay any back wages owed and communicate the change transparently and non-punitively.

Independent-contractor classification is a separate analysis governed by California's ABC test, and it deserves its own audit.

7. Wage statements

Wage-statement violations carry independent penalties ($50 for the first violation, $100 for each subsequent one, per employee per pay period) and their own statute of limitations. Every statement must contain nine specific items: gross wages, total hours worked, piece-rate information where applicable, all deductions, net wages, the inclusive dates of the pay period, the employee's name and last four SSN digits or employee ID, the employer's legal name, and the employer's address.

Map each requirement to a specific field in your payroll output, QA a sample of statements before every payroll run, and pay particular attention to the legal entity name, which must be the registered name, not a DBA. Update the configuration whenever anything changes: a new entity, a new payroll provider, a new comp structure, a new location.

8. Expense reimbursement

California requires employers to reimburse all necessary business expenses, and every unreimbursed expense is a violation for every affected employee for every pay period. For a startup with a remote or hybrid team, the big categories are personal cell phone and data plans used for work, home internet, mileage, and required tools and supplies. Choose a method (actual costs with receipts, or a reasonable flat stipend), build a simple submission-and-approval workflow, and make sure every employee knows what is reimbursable and how to claim it.

9. Final pay

Late final paychecks trigger waiting-time penalties of up to 30 days of the employee's daily wages. For involuntary separations, the final check is due the same day. For resignations without 72 hours' notice, it is due within 72 hours. The most common failure is that payroll simply was not told in time. Build a termination checklist that triggers immediate final-pay processing, a 72-hour tracker for resignations, and a rule that the final check includes everything: all earned wages, all accrued unused vacation (which is earned wages in California and must be paid out), and all outstanding reimbursements.

Timekeeping is the backbone

Your timekeeping system is the operational foundation for both preventing violations and proving compliance. Record actual clock-in and clock-out times to the minute (the California Supreme Court has eliminated rounding for meal periods). Consider geofencing for multi-site workforces, biometric clocks to prevent buddy-punching, and app-based systems with attestation prompts and GPS or photo verification for remote and field employees. Above all, audit the configuration at least annually and whenever the system is updated or migrated. Your system is only as compliant as its settings.

Change the economics

Plaintiff's attorneys choose targets economically. They look for systemic violations, a large enough workforce to make the math work, and an employer without structural defenses. A company that has actually complied, can prove it, and has enforceable arbitration agreements in place is a poor target on every dimension. That is the goal: not merely reducing risk, but changing the economics so the case is never worth bringing.

This article is adapted from Class-Action Proof Your Business, by Benjamin J. Treger, originally published March 20, 2026, and is republished with the author's permission.

This article is for general informational purposes and does not constitute legal advice or create an attorney-client relationship. Wage-and-hour rules change frequently; consult counsel about your specific situation.