Wage Backpay reference snapshot for California

Rule or statute summary

California wage claims commonly involve a backpay request—how much an employer owes for unpaid wages. One threshold question is how far back you can reach to recover those wages, which depends on the applicable statute of limitations (SOL).

For this California “reference snapshot,” we use the general/default SOL period provided in the jurisdiction data:

• General SOL period: 2 years
• General statute: CCP § 335.1
• No claim-type-specific sub-rule was found in the provided data, so this snapshot applies the default/general period rather than narrowing by a specialized wage claim category.

Practical takeaway: in backpay math, the SOL effectively governs the lookback window—the slice of time you can include when calculating recoverable wages. The exact accrual/trigger date that starts the clock can vary based on facts (for example, when wages became due), so treat the tool output as an estimate to understand what dates might be reachable under the general 2-year rule.

Citations

Use these sources to confirm the authoritative text before finalizing the calculation.

• Primary authority reference

Capture the source for each input so another team member can verify the same result quickly.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Core statute (general/default SOL)

• California Code of Civil Procedure § 335.1 (general 2-year limitations period)
  Source (jurisdiction reference provided):
  https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html

How this impacts “wage backpay” calculations

Backpay is typically calculated as:

• **(pay rate) × (hours worked) × (time window)

Because the SOL controls the time window, changing the SOL length changes:

• how many pay periods/days are included,
• the total unpaid wages recoverable in your estimate,
• and any downstream amounts that depend on the included window (for example, if you later model interest—this snapshot focuses on the SOL-constrained backpay period).

Use the calculator

Use DocketMath as your structured estimator for wage backpay constrained by the California default/general 2-year SOL.

Primary CTA: /tools/wage-backpay

Run the Wage Backpay calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Inputs to consider (California, default/general SOL)

When you open /tools/wage-backpay, you’ll typically enter values like:

• Pay rate (e.g., $20.00/hour)
• Hours worked per pay period (or per week/day)
• Backpay start date (e.g., the first date you want to test)
• Backpay end date (e.g., last unpaid work date or your chosen endpoint)
• Jurisdiction: **US-CA (California)
• SOL assumption: default/general 2-year (per CCP § 335.1 from the provided jurisdiction data)

How outputs change when the SOL trims the period

As a general rule for interpreting the calculator results:

• If your entered backpay start date is within 2 years of the relevant lookback cutoff, the calculator will generally include most/all of the period you input.
• If your entered backpay start date is more than 2 years back, the tool will effectively trim the included portion to the 2-year window, reducing the estimated backpay total.

Caution (not legal advice): SOL lookback and the underlying accrual trigger can be fact-specific (for example, when wages became due, when notice was provided, or other timeline events). Use the calculator’s constrained window as an estimate under the general rule, then adjust if your case facts point to a different trigger or statute.

Quick “feel” example (see the SOL effect)

Assume:

• $20/hour
• 40 hours/week
• You input a backpay range: 2023-01-01 to 2024-01-01

If the relevant 2-year lookback cutoff is 2022-01-01, then your full 2023–2024 window falls within the general SOL window, so the tool output should compute close to the full amount.

If instead the relevant cutoff is 2023-01-15 (because the clock starts later based on your facts), then even though you entered 2023-01-01, only part of that range falls within the 2-year reach, and the estimated backpay would be lower.

What to do with the output

After you run DocketMath, consider using the estimate to:

• confirm whether your chosen date range aligns with the 2-year default/general lookback,
• compare scenarios (e.g., different end dates, different start dates, different pay/hour inputs),
• document assumptions so you can revise if you later confirm the correct accrual/trigger date for your specific situation.

Related reading

• Wage & Backpay Calculator Guide for Alabama
• Wage & Backpay Calculator Guide for Arizona
• Wage & Backpay Calculator Guide for Colorado