How to run statute of limitations in DocketMath for California

7 min read

Published April 8, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Step-by-step

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

This guide walks you through running the statute of limitations (SOL) in DocketMath for California (US-CA) using the statute-of-limitations calculator. DocketMath is designed to help you model deadlines based on key dates—not to provide legal advice. Use the results as an analytical aid and double-check inputs against the facts of your case.

1) Open the calculator

Start at the primary call to action:

/tools/statute-of-limitations

If you’re navigating from the site, you can also reach DocketMath tools via the Tools area, then select the statute-of-limitations calculator.

2) Confirm the California SOL basis (default/general)

For this walkthrough, we’ll use California’s general/default SOL period of 2 years under:

California Code of Civil Procedure (CCP) § 335.1

Per the provided jurisdiction data, no claim-type-specific sub-rule was found for this calculator setup. In other words, treat this as the general rule for SOL timing unless your specific claim type requires a different statute elsewhere.

Note: When you model deadlines, the “2-year default” is a baseline. California has claim-specific limitations in other CCP sections, so ensure the general period applies to the scenario you’re analyzing.

3) Enter the core date(s)

Most SOL calculators require at least a start date and then compute the deadline by adding the SOL period.

In DocketMath’s statute-of-limitations tool, you’ll typically provide inputs such as:

Event date (the date the limitation clock starts, for the scenario you’re modeling)
SOL length (for California, this should be 2 years using the general rule)
Comparison date (often the filing date or the date you’re checking against)

If your version of the calculator asks for fewer or different fields, the logic remains the same: DocketMath adds the SOL period to your start date and then compares it to your target date.

4) Set SOL length to the California default (2 years)

Because the general/default period is 2 years, you should enter:

2 years for the SOL duration

This matches the provided jurisdiction data:

General SOL Period: 2 years
General Statute: CCP § 335.1
Source reference provided: https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html

5) Choose the date you want to test

Next, decide what question you’re answering. Common options:

“Has the SOL already run?” → compare the computed deadline vs. today or a specific filing date
“When was the last day to file?” → compute the deadline date from your event/start date

Enter the date that matches your goal.

6) Review the output and interpret it

After you run the calculation, DocketMath will generally output:

A computed SOL deadline date (start date + 2 years)
A determination like within time vs. time-barred, depending on the tool’s output format
Any intermediate steps it uses for transparency (if the UI displays them)

Use this output to drive your next action: revise dates, verify your assumptions, and rerun.

7) Iterate: change one input at a time

Deadline modeling is sensitive to dates. When you’re doing a “what-if,” change only one input per run.

Common iteration targets:

Move the event/start date forward/backward by weeks or months (to reflect disputed facts)
Switch the comparison date from “filing date” to “today” (to answer a different question)
Reconfirm SOL duration (make sure you’re still using the default 2-year rule)

A quick mental model helps:

Input you change	Typical effect on SOL deadline
Start/event date moves later	SOL deadline moves later
Start/event date moves earlier	SOL deadline moves earlier
Comparison date moves later	More likely to look time-barred
SOL duration changes from 2 years	Deadline recalculates using the new length

8) Document your assumptions (so you can defend your modeling)

Before you rely on the result, write down:

What date you used as the start date
Which SOL period you used (2 years under CCP § 335.1 in this default setup)
What date you compared it to (filing date, today, etc.)

This makes it easier to rerun the calculator if new facts appear.

Warning: SOL outcomes often hinge on “what is the correct start date.” If you’re unsure whether the start date is the date of the incident, the date of discovery, or another trigger used for your specific scenario, don’t assume—update the inputs to match the trigger you’re modeling and treat the result as a scenario estimate.

Common pitfalls

Even with the clean “2-year default” setup, SOL calculations go wrong for predictable reasons. Here are the top issues to watch for when using DocketMath (US-CA).

Using the wrong “start date”
- DocketMath computes the deadline from the date you enter. If your scenario’s trigger is not the one you chose, your deadline will be off.
Assuming the general rule applies to every claim type
- The provided jurisdiction data states a general/default 2-year period under CCP § 335.1 and notes that no claim-type-specific sub-rule was found here.
- If your claim falls under a different limitations statute, a 2-year model may be inaccurate.
Confusing “deadline date” with “filing acceptance date”
- Even if the tool returns the last permissible day under the modeled rule, real-world filing processing and court rules can matter. DocketMath is calculating based on your modeled dates.
Forgetting to rerun after date corrections
- If you update the event date, discovery date, or filing date, run again. A stale output is one of the most common ways teams waste time.
Not recording assumptions
- If multiple people touch the worksheet, you’ll need a clear trail: “We used start date X and compared to date Y using 2 years under CCP § 335.1.”
Treating “within time” as definitive legal advice
- DocketMath is a computation tool. It cannot adjudicate legal defenses, exceptions, tolling, or classification questions. Use it to structure questions and narrow uncertainty.

Try it

Here’s a simple way to practice with DocketMath using the California default rule (2 years / CCP § 335.1).

Open the Statute Of Limitations calculator and follow the steps above: Run the calculator.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Example workflow (scenario modeling)

Use this checklist for your run:

What to expect when you tweak inputs

Try a micro-experiment:

Run once with start date = March 1, 2023
Run again with start date = April 1, 2023

You should see the SOL deadline shift by about 1 month, because DocketMath adds exactly 2 years to the entered start date.

That behavior is the tool doing what it should: your inputs control the computed deadline, and a different start date changes the result.

If you want to explore more workflows, open the tool here:

/tools/statute-of-limitations