Worked example: Damages Allocation in California

Example inputs

This worked example shows how DocketMath can allocate damages in a California (US-CA) case using jurisdiction-aware rules—specifically, the general statute of limitations (SOL) that affects which damages accrual period may be included.

Because your brief indicates no claim-type-specific sub-rule was found, this example uses the general/default SOL period for California:

• General SOL Period: 2 years
• General Statute: CCP § 335.1
• Source context: California general limitations framework is commonly summarized in consumer legal guides that reference CCP § 335.1 (see: https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html)

Note (important): This example uses the general/default 2-year period from CCP § 335.1. In a real case, a different, claim-specific limitations rule (or a different accrual trigger) could change the damages window and therefore the allocation. This is not legal advice.

Scenario (what we’re allocating)

Assume a plaintiff seeks damages for a continuing injury where damages accrue over time. We’ll model a damages allocation that depends on the included accrual period, meaning: only damages that accrue within the limitations window are counted as included for purposes of this example.

Inputs for the DocketMath damages-allocation calculator

Use these concrete dates so you can reproduce the run:

• Jurisdiction: California (US-CA)
• Applicable SOL rule: General/default (CCP § 335.1)
• Alleged injury start date (accrual begins): 2023-01-15
• Case filing date: 2024-02-20
• Damages accrue daily: Yes
• Daily damages amount (illustration): $150/day
• Damages cap/ceiling: None in this example
• Events that might truncate accrual: None in this example

Why the date inputs matter

The SOL effectively determines the earliest date from which damages can be counted. With a 2-year general period, damages accruing before the cutoff typically fall outside the included window.

To set that cutoff in this demonstration:

• Filing date: 2024-02-20
• Lookback: 2 years → start of allowable window: 2022-02-20 (simplified “2 years prior” approach for illustration)

In a real docket review, you’d validate the precise accrual/limitations mechanics for the claim’s facts. Here, the point is to show how DocketMath allocates damages once the window is established.

Example run

You would run the calculator at DocketMath’s damages-allocation tool here: /tools/damages-allocation.

Run the Damages Allocation 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.

Step 1: Determine the allowable accrual window

Based on the inputs:

• Injury start: 2023-01-15
• Allowable window start (2 years before filing): 2022-02-20
• Filing date: 2024-02-20

Because the injury begins after the window start, the modeled included accrual period starts at the injury start:

• Included accrual start: 2023-01-15
• Included accrual end: 2024-02-20 (through the filing date in this simplified model)

Step 2: Compute days in the included period

Count days between 2023-01-15 and 2024-02-20. Different calculators sometimes handle boundaries (inclusive vs. exclusive) differently, but DocketMath’s implementation will be consistent for your run.

For this illustration, assume DocketMath’s daily count yields:

• Total included days: 401 days

Step 3: Allocate damages across the included period

Given:

• Daily damages: $150/day
• Included days: 401

Then:

• Total allocated damages = 401 × $150 = $60,150

Output summary (what you should expect to see)

A typical DocketMath output for this run should reflect:

• SOL rule applied: **CCP § 335.1 (general/default)
• Included accrual window: 2023-01-15 → 2024-02-20
• Total allocated damages: $60,150
• Excluded portion: $0 in this scenario (because the injury began inside the allowed window)

Compact view:

Sensitivity check

Use DocketMath to see how output changes when you modify one input at a time. This helps identify which levers (dates vs. rates) drive the damages allocation most.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

1) Shift the filing date later by 30 days

• Original filing date: 2024-02-20
• New filing date: 2024-03-22

With a 2-year window, the injury start is already inside the window, so the main effect is the included end date moving later.

Approximate effect:

• Additional ~30 days × $150/day = +$4,500

Approximate recalculated allocation:

• $60,150 + $4,500 = $64,650 (approx.)

2) Move injury start earlier (before the SOL cutoff)

Change:

• Injury start from 2023-01-15 → 2022-01-15

Now the injury begins before the allowable window start (2022-02-20). That means an earlier portion of accrued damages would become excluded.

In this case, DocketMath should reflect something like:

• Included start: 2022-02-20
• Included end: 2024-02-20

Conceptually, the change is:

• Excluded damages = (excluded days) × $150
• Included damages = (included days) × $150

This scenario tends to swing allocation more sharply than changing the filing date—because it changes the start of the included period.

3) Change daily damages rate

If daily damages increases or decreases, allocation scales linearly (under the same included days).

Example:

• Daily damages: $200/day instead of $150/day
• Included days: 401

Then:

• Total = 401 × $200 = $80,200

This confirms the model behaves as expected under a constant accrual assumption.

Quick sensitivity table

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules