What this calculator does

Run this scenario in DocketMath using the Deadline calculator.

DocketMath’s Deadline Calculator helps you compute key California litigation deadlines using the state’s general default statute of limitations (SOL) framework. In this guide, the focus is on the baseline timing rule tied to CCP §335.1.

What you can calculate with DocketMath

You typically input a starting date (often the date a claim accrued or an event occurred). DocketMath then returns a deadline date based on the applicable SOL period.

• General SOL period (default): 2 years
• General statute: California Code of Civil Procedure (CCP) §335.1
• Source (general overview): https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html

Warning (important): This guide intentionally uses the general/default period (2 years) and does not apply claim-type-specific sub-rules. No claim-type-specific sub-rule was identified in the jurisdiction data provided. Real-world deadlines can be affected by different claim categories, discovery rules, tolling, or other timing doctrines.

What this calculator does not do

DocketMath is designed to help you model deadlines, not replace legal analysis. It may not automatically capture every nuance that can change SOL timing, such as:

• special statutory schemes for particular claim types,
• tolling that pauses or extends time due to specific legal conditions,
• multiple triggering dates (for example, discovery-based triggers).

If your situation involves more than the general baseline, use DocketMath as a starting point for organizing dates—not as a final answer.

When to use it

Use DocketMath’s Deadline Calculator when you want a reliable, repeatable way to turn a date you control (like an incident date or an accrual date) into a 2-year SOL deadline under the general default rule.

Good times to use the calculator

Check deadlines with DocketMath if you:

• are triaging whether a potential civil claim might be time-barred under the general rule,
• want a clear “calendar view” for a potential filing window,
• are building an evidence timeline and want deadlines aligned to it,
• want to compare “what if” scenarios (for example, two possible accrual dates).

What inputs usually matter

While the exact fields depend on the tool interface, the deadline logic generally relies on:

• Start date: the date you choose as the SOL “clock start” for the default model
• SOL length: 2 years under CCP §335.1
• Jurisdiction: **California (US-CA)

How outputs change based on your inputs

The output deadline changes predictably with your start date:

• If you select a later start date, the computed SOL deadline will also be later by roughly the same interval.
• If you select an earlier start date, the deadline shifts earlier, potentially reducing the time left to act.

Because this is a date-driven calculator, accuracy depends heavily on your starting date selection and consistency.

Step-by-step example

Here’s a practical walkthrough using the general default rule: 2 years under CCP §335.1.

Example: Modeling a general 2-year deadline in California

Assume the following facts for deadline modeling:

• Jurisdiction: California (US-CA)
• Starting date (accrual/event date for your model): March 1, 2025
• General SOL period: 2 years (default)

Step 1: Determine the “start” you’re modeling

In many deadline workflows, people start with the date the claim accrued or the key event date they believe triggered the SOL clock. In this example, you’ll use:

• Start date: March 1, 2025

Step 2: Use the calculator in DocketMath

Open the tool: /tools/deadline

Enter:

• Start date: 03/01/2025
• Jurisdiction: **California (US-CA)
• Rule basis: General default (2 years) under CCP §335.1

Step 3: Read the calculated deadline

DocketMath returns a computed deadline date using the 2-year SOL length.

For the example date, the deadline would fall around:

• March 1, 2027 (based on a straightforward “add 2 years” model)

Step 4: Translate the result into a work calendar

Once you have a deadline date, convert it into operational milestones:

• Deadline (modeled SOL end date): March 1, 2027
• Suggested internal buffer: plan earlier steps so you’re not working right up to the deadline

Treat this as a scheduling reference—not a guarantee that your specific legal facts match the general baseline.

Pitfall to avoid: Many people rely on event dates without verifying whether the “clock start” is the same date under the applicable legal framework. This guide uses the general default period only and does not adjust for claim-specific triggers or tolling.

Common scenarios

Below are common ways people approach deadline questions in California using the general/default 2-year model. Each scenario includes what changes (or doesn’t change) when you adjust your input dates.

Scenario 1: Two possible start dates

Sometimes you can identify:

• Date A: when the injury/incident happened
• Date B: when you discovered key facts

Because this guide uses the general/default rule without claim-type-specific sub-rules, a practical approach is to run the calculator twice and compare.

Checklist:

Output impact: the computed deadline shifts to match whichever start date you enter.

Scenario 2: The clock is “close” to expiring

If the computed date is within a few weeks or months, focus on input quality.

Practical steps:

Output impact: even small date entry errors can materially affect how much time remains.

Scenario 3: Planning based on a filing target

If you’re using the deadline as a filing target, build a timeline:

• evidence collection,
• drafting/review,
• final decision and filing preparation.

Output impact: the modeled SOL deadline stays the same; what changes is your internal schedule.

Scenario 4: Multiple related events across time

If multiple key events occurred on different dates, you may need multiple modeled deadlines.

Modeling approach:

Output impact: earlier event dates produce earlier deadlines; later event dates produce later deadlines.

Summary table: how the calculator behaves under the general default model

Tips for accuracy

Deadline math is simple; deadline accuracy depends on your inputs. Use these practices to improve the reliability of your DocketMath results.

1) Lock down your “start date” definition

Because this guide uses the general/default rule without claim-specific adjustments, define what you mean by “start date” in your notes. For example:

• “I’m modeling the SOL from the incident date.”
• “I’m modeling the SOL from the date we discovered key facts.”

Then keep that definition consistent across every run.

2) Use exact calendar dates

If your data only gives a month (not a specific day), the computed deadline will be less precise.

To improve confidence:

3) Watch for time zone and formatting mistakes

Common error types include:

• entering dates in the wrong format (for example, swapping day/month),
• quickly copying numbers without verifying the calendar date.

Quick checks:

4) Keep “2 years under CCP §335.1” front and center

The general/default basis for this guide is:

• CCP §335.1
• 2-year SOL period

This is what DocketMath models here. If your scenario uses a different timing framework (for example, a different triggering rule or tolling), the output may not be controlling.

Reminder: This guide uses the general default period of 2 years and does not apply claim-type-specific sub-rules because none were identified in the provided jurisdiction data.

5) Add a practical buffer

Even if the modeled deadline is correct, real-world steps take time. Consider planning backward so you’re not rushing at the end.

Example buffer approach:

This doesn’t change the legal deadline; it reduces deadline-risk.

Related reading

• Browse the blog

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations