Spreadsheet checks before running Wage Backpay in California

What the checker catches

Before you run a Wage Backpay calculation in California with DocketMath, a spreadsheet sanity check can help you avoid common errors that otherwise ripple into the final backpay totals—especially when your sheet is built from payroll exports.

In this California setup, DocketMath’s wage backpay checker is aligned to the general/default statute of limitations (SOL) reference provided for California: 2 years under CCP §335.1. Importantly, your jurisdiction data indicates no claim-type-specific sub-rule was found, so this checker uses the general period as the default timing assumption.

The main issues the spreadsheet checker catches

Use the checklist below to confirm your spreadsheet matches the inputs and assumptions the calculator expects.

• Confirms the “backpay start” and “backpay end” you’re using align to the 2-year general SOL window referenced under CCP §335.1 (general/default period).

• Flags problems like:

  • end date earlier than start date, and/or
  • missing/blank dates that can cause rows to be treated as if they belong in the wrong window.

• Detects when some rows are effectively “weekly” while others are “monthly,” but the spreadsheet treats them as the same kind of “per period” wage input—leading to inflated or deflated totals.

• Warns when two rows cover the same time span, which can result in double-counting unpaid wages.

• Looks for classic spreadsheet mistakes, such as:

  • entering annual salary numbers into hourly-rate fields, or
  • applying a factor (like a “*1000” scaling) in one row but not another.

• Ensures the sheet includes the inputs the checker/calc expects (at minimum: dates plus wage fields and/or per-period wage quantities—structured consistently across rows).

Pitfall to avoid: A model can look “mathematically correct” while still being incorrectly scoped legally if your sheet’s date range doesn’t reflect the 2-year general SOL basis under CCP §335.1. The checker is meant to catch that before you run the calculator.

Legal timing rule the checker is aligned to (California)

This checker is aligned to the provided jurisdiction timing rules:

• General SOL period: 2 years
• General statute: CCP §335.1

Your jurisdiction data explicitly states that no claim-type-specific sub-rule was found, so treat 2 years (general/default) as the default rule for this workflow.

Source basis for the 2-year general SOL reference: the provided jurisdiction data summary indicates CCP §335.1 is commonly presented as a 2-year limitations period for general claims in this civil context.

Reference: https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html

When to run it

Run the spreadsheet checks before you run the Wage Backpay tool in DocketMath—ideally right after you clean and structure your raw payroll data, not after you start iterating on your results.

Run the checker before importing a spreadsheet into the Wage Backpay workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Recommended workflow (practical order)

1. Import or paste your time and wage rows into the spreadsheet you’ll use for DocketMath.
2. Normalize date formats

   • Convert dates so they’re consistent (for example, YYYY-MM-DD) and ensure they’re true date values (not text).
3. Define your calculation window

   • Set the “backpay start” and “backpay end” cells you intend to use with the Wage Backpay tool.
4. Run the spreadsheet checker

   • Fix flagged items first: date logic, overlaps, scaling/unit issues, and missing columns.
5. Run DocketMath Wage Backpay

   • Then review the outputs for plausibility (for example, hours totals and overall backpay totals).

Timing based on the 2-year general SOL window

Because this workflow uses the general/default 2-year period (no claim-type-specific sub-rule was found in your jurisdiction data), the checker is most valuable when your dataset includes wage activity older than 2 years relative to your model anchor date (often the filing/notice “as-of” date you’re using in your worksheet).

Quick “Should I run it again?” checklist

• backpay start/end dates

  • payroll frequency assumptions (weekly vs. biweekly)
  • wage input fields (rates vs. totals)

Try the checker

You can test this workflow with DocketMath’s Wage Backpay tool.

1. Open the Wage Backpay tool: **DocketMath /tools/wage-backpay
2. In your spreadsheet, make sure you have columns for:

   • pay period start date
   • pay period end date (or a single consistent “period date” approach)
   • wage inputs (choose one approach and keep it consistent—e.g., hourly rate or per-period totals)
   • any additional unpaid fields your sheet design uses (hours/unpaid amount, depending on how you model it)
3. Run the spreadsheet checks in the checker flow.
4. Apply fixes in this order:

   • Date-range problems first (so your window matches the intended 2-year general SOL basis)
   • then overlaps (so nothing is double-counted)
   • then scaling/unit issues (so numbers match the wage inputs the tool expects)

How input changes usually affect outputs (intuition)

• Move the start date forward (keeping unit assumptions consistent):

  • totals typically go down because fewer pay periods are included.
• Fix an overlap:

  • totals often drop because duplicated time/wages are removed.
• Fix unit mismatch (for example, hours vs. dollars; or annual vs. hourly):

  • totals can change drastically—treat large swings as a sign to re-check units before trusting the output.

Output expectations aligned to the 2-year general rule

Given the jurisdiction setup here uses the general/default 2-year SOL under CCP §335.1, your effective in-scope interpretation should be:

• Include only pay periods within the last 2 years relative to your anchor “as-of” date for the general timing assumption.
• Exclude older periods from the worksheet logic the checker helps enforce.

Related reading

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