Worked example: statute of limitations in California

6 min read

Published April 8, 2026 • By DocketMath Team

Example inputs

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Below is a worked example of how a California statute of limitations (“SOL”) calculation typically looks using DocketMath’s statute-of-limitations calculator. This example uses the general/default SOL period because no claim-type-specific sub-rule was provided for this scenario.

  • Jurisdiction: California (US-CA)
  • General SOL period (baseline): 2 years
  • General statute cited: CCP § 335.1
  • Source (for the general/default period provided in the brief): AllLaw’s discussion of California personal injury laws (used here only to corroborate the general period the brief provided): https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html

Important: The brief indicates no claim-type-specific sub-rule was found, so this is a default baseline model only. California can have different limitations periods for specific claims, and exceptions like tolling or different accrual rules may apply. This example is meant to show how the math looks, not to predict a specific legal outcome.

To make the math concrete, pick these example dates:

Scenario

A person claims they were injured due to an event that happened on a specific day, and they consider filing a lawsuit later.

Inputs (example)

InputExample valueWhat it represents
Event date (accrual/start date used by the tool)2024-03-15The date on which the clock starts for the example run
Filing date you’re evaluating2026-03-20The date you plan to file (or compare against)
SOL basis used by the calculatorGeneral/defaultThe tool applies the default 2-year period per the brief
Statute citation displayedCCP § 335.1The general SOL reference shown in the example

Note: This worked example uses a general/default 2-year SOL baseline. Use it as “clock math,” then verify whether your claim needs a different rule or whether exceptions apply.

Example run

Now we run the calculation in DocketMath using the inputs above.

You can launch the tool directly here: /tools/statute-of-limitations.

Run the Statute Of Limitations 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-by-step (illustrative)

  1. Start date (accrual/event date): 2024-03-15
  2. General SOL period (baseline): 2 years (CCP § 335.1)
  3. Compute the last day to file (baseline):
    • 2 years from 2024-03-15 is 2026-03-15
  4. Compare to proposed filing date:
    • Proposed filing date: 2026-03-20
    • Baseline last day: 2026-03-15
    • Result: Filed after the baseline SOL window

Output interpretation (baseline)

Using the general/default 2-year SOL:

  • Baseline SOL expires: 2026-03-15
  • Evaluated filing date: 2026-03-20
  • Timing result (baseline model): Likely time-barred under the baseline rule (because it is 5 days after the baseline expiration date)
ItemDate
Event date (start)2024-03-15
+ 2 years (baseline SOL period)2026-03-15
Proposed filing date2026-03-20
Difference5 days late vs. baseline

Gentle disclaimer: This demonstration does not apply tolling, discovery rules, or claim-specific exceptions. If any of those apply, the “real” filing deadline could move. Use this as a starting point for understanding how deadlines are calculated.

Sensitivity check

A statute of limitations calculation can hinge on details—especially the event/accrual date and the filing date. Below are several sensitivity tests using the same baseline rule (2 years under the general/default model) to show how small changes can change the result.

Sensitivity test A: Filing earlier by 10 days

  • Event date: 2024-03-15 (same)
  • Filing date: 2026-03-10

Result:

  • Baseline expiration: 2026-03-15
  • Filing date: 2026-03-10
  • Within the baseline window (5 days early)
TestEvent dateFiling dateBaseline expirationOutcome vs baseline
A2024-03-152026-03-102026-03-15Within

Sensitivity test B: Moving the event date forward by 30 days

  • Event date: 2024-04-14 (moved +30 days)
  • Filing date: 2026-03-20

Recompute baseline expiration:

  • 2 years from 2024-04-14 is 2026-04-14
  • Filing 2026-03-20 is before 2026-04-14
TestEvent dateFiling dateBaseline expirationOutcome vs baseline
B2024-04-142026-03-202026-04-14Within

Sensitivity test C: Filing on the last day (edge case)

  • Event date: 2024-03-15
  • Filing date: 2026-03-15 (exactly)

Result:

  • Baseline expiration: 2026-03-15
  • Filing equals the expiration date
  • On deadline under a simple baseline deadline model
TestEvent dateFiling dateBaseline expirationOutcome vs baseline
C2024-03-152026-03-152026-03-15On deadline

Sensitivity test D: Using the baseline when a different SOL rule might apply

This is the key “real-world” sensitivity given the brief.

  • The brief specifies: “No claim-type-specific sub-rule was found.”
  • That means the calculator here is using the default 2-year baseline, not a specialized rule for a particular claim type.

What changes?

  • If your specific claim category has a different limitations period (or a different accrual framework), then the 2-year baseline may not represent the true deadline.
  • Exceptions like tolling or discovery-based accrual could also extend (or alter) the timeline.

Pitfall to watch for: A baseline output like “time-barred” (or “within time”) could be wrong if a different rule or an exception applies. Treat this as a prompt to confirm fit with the tool’s default model.

Checklist: inputs to double-check before you rely on the output

Use this quick list to validate the assumptions you feed into the calculator:

Related reading