Worked example: Wage Backpay in California

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

Below is a worked example of wage backpay in California (US-CA) using DocketMath. This walkthrough shows how a typical damages input set turns into a calculated backpay amount, and how changes in key variables can affect the output.

Scenario used for the example

Assume an employee claims they were paid less than they should have been because of an incorrect pay practice. They want unpaid wage backpay for a period starting at a chosen backpay start date, capped by the applicable statute of limitations.

Jurisdiction-aware limitation rule used

For California, DocketMath uses the general/default statute of limitations for this worked example:

• General SOL period: 2 years
• General statute: CCP §335.1
• Source reference used in DocketMath (jurisdiction data): https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html

Important: No claim-type-specific sub-rule was found in the provided jurisdiction data. So this example clearly uses the general/default 2-year period as the wage-backpay lookback window.

Inputs you’ll provide in DocketMath (wage-backpay)

You can plug values like these into the /tools/wage-backpay calculator:

• Pay frequency: Weekly
• Workdays per week: 5
• Hours per workday: 8
• Wrong (lower) hourly rate: $18.00
• Correct (higher) hourly rate: $22.00
• Backpay start date: 2023-03-01
• Backpay end date: 2025-03-01
• Filing/claim date (used to cap the lookback): 2025-06-15

How the limitation truncates the lookback window

DocketMath uses the claim/filing date to compute the latest allowable lookback window:

• General SOL = 2 years under CCP §335.1
• Lookback start = 2023-06-15 (two years before 2025-06-15)
• Backpay start provided = 2023-03-01
• Therefore, in this example, the counted period is from 2023-06-15 to 2025-03-01

Put differently: even though the user-provided backpay start date is earlier, the general/default 2-year cap prevents the calculation from counting wages outside that window.

Example run

Now let’s run the numbers conceptually the way the DocketMath wage-backpay logic operates: compute the hourly wage shortfall, convert it to a weekly shortfall, then multiply by the number of workweeks in the capped date window.

Run the Wage Backpay calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

1) Hourly shortfall

• Correct hourly rate: $22.00
• Wrong hourly rate: $18.00
• Hourly difference = $4.00

2) Shortfall per day and per week

Using 8 hours/day and 5 workdays/week:

• Daily shortfall = $4.00 × 8 = $32.00
• Weekly shortfall = $32.00 × 5 = $160.00

3) Apply the capped (SOL-limited) date window

• Claim date: 2025-06-15
• SOL lookback start: 2023-06-15 (2 years before)
• Provided backpay start: 2023-03-01
• Provided backpay end: 2025-03-01

So the effective calculation window becomes:

• Effective backpay window: 2023-06-15 → 2025-03-01

4) Convert the effective period into workweeks (example approach)

Because the calculator uses work schedule inputs (weekly cadence), it translates the date range into the number of workweeks that fall within the window.

With 5 workdays/week, and for illustration purposes, assume the window contains approximately:

• ~83.0 weeks (rounded)

(A real calculator run may compute the exact fractional timing depending on how it maps dates to workweeks.)

5) Compute total wage backpay (differential)

• Weekly shortfall: $160.00
• Weeks in window: 83.0
• Estimated wage backpay = $160.00 × 83.0 = $13,280.00

6) Output summary table (what the run produces conceptually)

Practical takeaways from this run

• The hourly difference ($4.00) drives the size of the shortfall.
• The general/default 2-year SOL cap under CCP §335.1 determines how much time is counted.
• The work schedule inputs (hours/day and days/week) scale the weekly shortfall.

Sensitivity check

Small changes to dates and rates can materially change the wage backpay estimate. here are a few “what-if” scenarios to show how outputs react when you adjust the key inputs.

A) Shift the claim date (SOL lookback changes)

Keep all other inputs the same, but change the claim date (the cap date):

• Case 1 (earlier claim date): claim date 2025-04-15

  • Lookback start becomes 2023-04-15
  • Covered time increases vs the original scenario
  • Expect higher backpay

• Case 2 (later claim date): claim date 2025-08-15

  • Lookback start becomes 2023-08-15
  • Covered time decreases vs the original scenario
  • Expect lower backpay

Checklist for your own worksheet:

B) Change the hourly discrepancy (linear effect)

Because the math is driven by the hourly difference:

• Original hourly shortfall: $4.00 → weekly shortfall $160/week
• If shortfall increases to $5.00:

  • Weekly shortfall = $5.00 × 8 × 5 = $200/week
  • Estimated backpay = $200 × 83.0 = $16,600 (higher)
• If shortfall decreases to $3.00:

  • Weekly shortfall = $3.00 × 8 × 5 = $120/week
  • Estimated backpay = $120 × 83.0 = $9,960 (lower)

Quick rule of thumb:

• With the same schedule, every $1.00/hour change in the discrepancy shifts backpay by:

  • $1.00 × 8 × 5 = $40 per week
  • Over 83 weeks: **$3,320 per $1.00/hour**

C) Change work schedule (hours/day changes weekly shortfall)

If the employee worked less time per day:

• Original: 8 hours/day and 5 days/week → $160/week
• Alternative: 6 hours/day and 5 days/week →

  • Weekly shortfall = $4.00 × 6 × 5 = $120/week
  • Expect the total backpay to drop proportionally

Checklist:

D) Confirm the SOL framework (general/default vs claim-specific)

In this example, DocketMath intentionally uses the general/default 2-year SOL because no claim-type-specific override was found in the provided jurisdiction data.

If, in your situation, a different claim category carries a different limitations period, the SOL lookback—and therefore the covered workweeks—could change. This worked example is limited to the 2-year CCP §335.1 general/default framework.

Related reading

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