Inputs you need for Wage Backpay in California
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Wage Backpay calculator.
If you’re using DocketMath to estimate wage backpay in California (US-CA), you’ll get the most accurate estimate by gathering the right inputs before you run the wage-backpay calculator. Below is a practical input checklist for the /tools/wage-backpay workflow and a quick guide to what each input affects.
Gentle note: This is general information to help you organize calculations—not legal advice. Wage backpay rules can vary based on facts and claim type.
Core wage-backpay inputs (checklist)
Additional wage-related inputs (commonly used)
These can increase accuracy when you have payroll documentation showing these elements:
Jurisdiction-aware limitation window (what governs how far back you can go)
When estimating wage backpay in California with DocketMath, the key jurisdiction input is the lookback period that limits which time periods you include.
California’s general default statute of limitations is 2 years under CCP §335.1. Where no claim-type-specific wage deadline is identified, the default 2-year period applies.
- General statute of limitations period (default): 2 years
- General statute: CCP §335.1
- Source (jurisdiction data): https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html
Important: The brief specifies that no claim-type-specific sub-rule was found, so this workflow uses California’s general/default 2-year period (CCP §335.1) rather than a specialized wage claim deadline.
Practically, that means your inputs should be organized so you can show (or at least model) wage loss within the last 2 years from the date you choose as the filing/model anchor—because time older than the lookback window may not appear in the output.
Where to find each input
Gathering inputs usually comes from the same few documents. Use this “where to look” guide to locate each item quickly.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
Dates and pay periods
- Employment start/end dates
- Pay period frequency
Rates and hours
- Regular hourly rate
- Scheduled vs. paid hours
- Missed hours details
Bonuses/commissions and partial payments
- Bonuses/commissions
- Partial payments / offsets
Limitation window anchor (California default lookback)
To apply CCP §335.1 (2-year default) consistently in the DocketMath estimate, you’ll need:
If your employment spans longer than the lookback period, inputs before the window may be excluded from the calculator’s output.
Run it
You can run the wage backpay estimate using DocketMath here: /tools/wage-backpay.
Enter the inputs in DocketMath and run the Wage Backpay calculation to generate a clean breakdown: Run the calculator.
If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.
1) Set the California default lookback window (2 years)
Because California’s general default statute of limitations is 2 years under CCP §335.1, set your included date range using that default rule.
A practical way to define the model window:
- Start of backpay window: (your model/filing anchor date minus 2 years)
- End of backpay window: the alleged wage loss end date (often employment end date, or the last missed-wages date)
Since no claim-type-specific sub-rule was found for this brief, DocketMath’s workflow should follow the general/default 2-year period described above.
2) Enter the rate and hours gap
DocketMath estimates wage backpay based on how much you were supposed to earn versus how much you were actually paid for, for the periods included.
Use the approach that matches your documentation:
- Most defensible: missed hours by date/pay period
- Still workable: an average weekly shortfall, if that’s all you can support reliably
3) Add overtime/other wage components only if you can support them
If overtime, commissions, or bonuses are part of the missed earnings:
If you don’t input these items, the result will generally reflect the base wage shortfall only.
4) Interpret output based on what you changed
When you rerun, think in “cause → effect” terms:
| If you change this input… | Output typically changes… | Why |
|---|---|---|
| Missed hours increase | Backpay increases | More wage delta to quantify |
| Regular hourly rate increases | Backpay increases | Higher rate × same missed hours |
| Employment end date moves forward | Backpay window may expand | More eligible periods in the model |
| Your anchor/model date moves later | Lookback window shifts later | The 2-year (CCP §335.1) window is anchored to the model date |
5) Keep a short change log before finalizing
Backpay estimates often get refined. Track:
This helps you explain why one estimate differs from another.