Why Damages Allocation results differ in California
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
If you run the Damages Allocation calculator in DocketMath for California matter facts and you see different outputs across runs or between users, the difference is usually traceable to inputs and jurisdiction-aware rules—not “mystakes in the math.”
Note: California’s general/default statute of limitations (SOL) period is 2 years, using CCP §335.1. No claim-type-specific sub-rule was found for this guide, so the analysis below uses that general SOL period as the default baseline.
Below are the five most common causes in US-CA.
You selected different “damage components”
- Allocation results shift when the calculator treats amounts as separate components (for example: economic vs. non-economic, or other internal damage buckets).
- Two people can both be “allocating damages,” yet input different component totals—so the final allocation changes even if the overall story sounds similar.
The date inputs changed
- Allocation logic often uses a timing window (for example, when conduct occurred, when accrual is assumed to start, and/or when a case is filed).
- Because the default SOL is 2 years under CCP §335.1, a small change in the modeled dates can move some portion of damages into/out of the limitations window—changing the allocation.
Different assumptions about “when damages accrued”
- Many allocation workflows require an accrual pattern: one-time accrual vs. ongoing accrual, or different accrual-start timing.
- If two runs assume different accrual timing, the same total damages can allocate differently across categories.
Different deductions or offsets are applied
- If you include/exclude items such as settlements, insurance-related reimbursements, or other offsets (depending on the calculator’s available toggles/fields), the net amounts used for allocation can differ.
- Even when gross numbers look the same, inconsistent offsets can shift category weights.
Jurisdiction-aware labeling caused different SOL handling
- DocketMath applies California (US-CA) rules, including the default SOL under CCP §335.1.
- If a run was created under the wrong jurisdiction code (even accidentally), the SOL-window logic can change and the allocation outputs may differ.
If you keep these five buckets in mind, you can usually explain the discrepancy quickly.
How to isolate the variable
Use this as a diagnostic workflow. The goal is to change one input at a time until the outputs match.
- Make sure the run is using California SOL logic under CCP §335.1 (general period: 2 years).
- Keep the same gross total and only vary the suspected field(s).
- Identify the specific dates DocketMath uses in your run (commonly: event date, accrual start, filing date).
- Since the default SOL is 2 years, check whether the relevant period crosses the “within 2 years” vs. “more than 2 years” boundary.
- If there is a choice for accrual pattern or timing, use the same mode across runs (e.g., “one-time” vs. “ongoing” accrual).
- Confirm both runs include the same deductions (or both exclude them). A single offset change can alter how damages are allocated across buckets.
Quick “difference map” (practical approach)
| Suspected variable | What to change in DocketMath | What to look for in output |
|---|---|---|
| Date boundary effect | Move event/accrual start by ±30–90 days | Allocation changes around the “within 2 years” vs. “outside 2 years” break |
| Accrual timing | Switch accrual model, keep totals constant | Category weights rebalance across buckets |
| Component mix | Keep the same total but edit component breakdown | Component totals change the allocation |
| Offsets | Toggle include/exclude offsets | Net allocation shifts (totals may appear similar if offsets are internal) |
| Jurisdiction | Verify the run uses US-CA | SOL-window-based allocation changes |
If the outputs diverge after your first single change, repeat with the next checkbox. This method converges quickly because you’re not guessing—you’re running controlled comparisons.
Next steps
Once you find the input/assumption that causes the mismatch, stabilize your workflow:
- Create a “California baseline” run
- Use US-CA and the default 2-year SOL under CCP §335.1 as the reference point.
- Document your input assumptions
- Record the chosen accrual assumption, the key dates, and whether offsets were included.
- Re-run with controlled changes
- Only change one field per iteration so each new run has a clear cause.
- Share a run summary
- When collaborating, share enough detail (jurisdiction, key dates, accrual setup, and offset toggles) that another user can reproduce the same logic.
Caution / not legal advice: This guide uses the general/default 2-year SOL under CCP §335.1 for California and does not identify claim-type-specific sub-rules. If your matter involves a different limitations period, allocation results may differ even with perfectly consistent inputs.
For easy access, you can start here: Damages Allocation.