How to run Damages Allocation in DocketMath for California

5 min read

Published April 15, 2026 • By DocketMath Team

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for California (US-CA). It also shows how the tool’s jurisdiction-aware setup aligns with California’s general statute of limitations (SOL) rules for when claims can be filed.

Note: This walkthrough describes how to use DocketMath and interpret its outputs for planning purposes. It’s not legal advice or a determination of whether any specific claim is timely.

1) Open the calculator and confirm the jurisdiction

  1. Go to the primary CTA: /tools/damages-allocation
  2. In the calculator, set jurisdiction to California (US-CA).
  3. Verify that the calculator template being used is damages-allocation.

What you’re doing: You’re ensuring the calculator applies California-aware assumptions and time logic, rather than a different state’s defaults.

2) Enter the case fundamentals

In the Damages Allocation calculator, you’ll typically enter facts that drive allocation and timing logic. While the exact field labels may vary slightly by interface revision, the workflow is consistent:

  • Claim or incident date (e.g., date of injury or event)
  • Filing date (if the tool supports it)
  • Damage categories you want to allocate (examples commonly include economic and non-economic categories, depending on the tool’s structure)
  • Amount(s) for each damage component you want to distribute

Tip: If you’re uncertain about any category amount, run the calculator once with best estimates, then refine and compare outputs.

3) Understand the SOL timing logic the tool uses (California default)

DocketMath uses California’s general/default period unless a more specific rule is provided within the tool’s jurisdiction ruleset.

California’s general SOL period referenced here is:

DocketMath can only apply what it has. In this jurisdiction configuration, no claim-type-specific sub-rule was found, so the tool uses the general/default period as the controlling rule.

You should therefore expect the tool to treat the claim as subject to a 2-year general SOL for timing checks tied to the entered dates.

Warning: If your real-world claim is governed by a different SOL (for example, a statute with a different limitations period), a tool using only the general/default period will not capture that nuance.

4) Run the allocation and review outputs

After entering inputs, click Calculate.

You’ll generally see two kinds of outputs:

  1. Damages allocation results
    • How DocketMath distributes totals across categories based on the inputs you provided.
  2. SOL-related timing output (if the calculator includes it)
    • Date math using the 2-year general SOL default tied to CCP § 335.1.

How outputs change when you adjust inputs:

  • Change the incident/filing dates: the SOL/timing output can flip (timely vs. potentially time-barred under the tool’s default logic).
  • Change category amounts: allocation totals shift immediately, and any percentage breakdowns update accordingly.
  • Add or remove categories: the distribution structure changes, so totals will re-balance based on what’s included.

5) Validate the numbers before you export or record results

Before saving:

  • Ensure totals across categories equal the intended total (if the tool expects this).
  • Confirm that date fields are in the correct format and represent the correct events (incident vs. filing).
  • Check whether the tool assumes a single controlling SOL period (it does here, based on the general/default rule).

Common pitfalls

Avoid these issues when running Damages Allocation in DocketMath for California (US-CA):

  • Using the wrong controlling SOL without realizing it
    • Because this setup uses the general/default 2-year period under CCP § 335.1, it won’t automatically incorporate special SOL schemes for particular claim types.
  • Reversing dates
    • Filing date entered earlier than incident date can create misleading timing outcomes.
  • Entering category amounts that don’t reconcile
    • If you intend the sum of allocations to equal a known total, make sure each component is entered consistently.
  • Assuming the tool “knows” your claim type
    • In this configuration, no claim-type-specific sub-rule was found. The calculator follows the general default.
  • Treating sensitivity as optional
    • Run at least one “base” estimate and one “sensitivity” run (e.g., adjust amounts by ±10% or refine dates) so you can see how stable the output is.

Pitfall: Treating a SOL timing output as a definitive legal conclusion. In DocketMath, the SOL component reflects the calculator’s configured rule set (here, general/default under CCP § 335.1) rather than every possible exception or claim-specific statute.

Try it

Ready to run a California damages allocation quickly?

  • Open /tools/damages-allocation
  • Select **California (US-CA)
  • Enter:
    • Incident date
    • Filing date (if available in the tool)
    • Your damage category amounts (the categories the tool prompts for)
  • Click Calculate
  • Review:
    • The allocation breakdown across categories
    • Any timing/SOL output based on the 2-year general SOL under CCP § 335.1

If you want a quick sanity-check on the timing piece:

  • Count forward from the incident/event date using a 2-year window (the general/default rule).
  • Compare that with your entered filing date.
  • Remember: this is the tool’s default framework, not a capture of every specialized exception.

For additional workflows in DocketMath, explore related calculators from the /tools/damages-allocation area (for example, compare outputs with other calculators in your docket workflow).

Related reading