Deadlines rule lens: California

The rule in plain language

Run this scenario in DocketMath using the Deadline calculator.

California generally gives plaintiffs 2 years to file a lawsuit under the state’s general statute of limitations (SOL) framework.

This article uses the default rule lens: a general 2-year period that does not attempt to identify or apply a claim-type-specific deadline. No claim-type-specific sub-rule was found for this brief—so CCP § 335.1 is treated as the baseline.

The default timeline: 2 years from the trigger event

California’s general SOL period is set out in California Code of Civil Procedure (CCP) § 335.1. A commonly cited summary also describes California’s general SOL as 2 years, consistent with the CCP framework.

Key takeaway (default rule):

• General/default SOL period in California: 2 years
• Primary cited statute: CCP § 335.1
• No claim-type-specific sub-rule applied (this post treats CCP § 335.1 as the baseline)

What the “2 years” number means in practice

Practically, “2 years” usually shows up as a calendar deadline calculation:

1. Identify the trigger date (the start date for counting time).
2. Add 2 years (calendar time).
3. The resulting date is your deadline target—often described as the “last day to file.”

The biggest source of error is usually not the math—it’s picking the wrong trigger date. Even with the correct 2-year length, the end date will be off if the start date is off.

Why it matters for calculations

SOL deadlines affect more than filing eligibility—they affect how you plan work long before the lawsuit is actually filed.

Small differences in the rule text can change the output materially. Using the correct jurisdiction and effective date ensures the calculation aligns with the authority that applies to your matter.

The calculation chain: trigger date → filing deadline

When you use a “2-year deadline rule lens,” you’re converting the rule into a specific calendar date.

In a typical workflow (including with DocketMath), the chain is:

• Input: Your chosen trigger date (e.g., date of injury, date of discovery, or another legally relevant event)
• Rule lens: Apply CCP § 335.1 default 2-year period
• Output: A computed “file by” deadline date

If the trigger date changes by weeks, the deadline shifts by weeks—potentially impacting scheduling for evidence collection, drafting, review, and service steps.

Common timing pitfalls (and how to avoid them)

Most deadline mistakes come from assumptions about timing rather than incorrect period length. Common pitfalls include:

• Using an everyday date that doesn’t match the legal trigger (for example, substituting “when you first noticed” for the legally defined accrual/discovery trigger)
• Treating “two years” as a fixed day count (such as assuming 730 days). SOL calculations are typically better treated as calendar-based rather than a rough day total.
• Assuming “discovery” timing automatically applies
• Overlooking that amendments, tolling, or other procedural circumstances can change the timeline

Planning with a deadline buffer

Even if you compute a deadline accurately, real-world casework takes time:

• Drafting and review
• Evidence gathering
• Preparing and executing service of process
• Court intake and procedural processing

So many teams create an internal buffer earlier than the computed statutory deadline. This buffer is not a legal substitute—it’s a practical project-management safeguard. When DocketMath outputs a deadline, consider also creating a “workback” date so you’re not relying on last-minute readiness.

Use the calculator

Use DocketMath to convert the default California general 2-year rule into a concrete “file by” date.

Start here: /tools/deadline

Because this article uses the default rule lens, configure DocketMath to apply the 2-year general period consistent with CCP § 335.1.

Step-by-step inputs (what to enter)

Set up DocketMath like this:

• Jurisdiction: California (US-CA)
• Deadline basis: General/default period (2 years)
• Start date (trigger date): Enter the date your timeline treats as the start of the SOL clock
• Optional: Add a filing buffer for internal planning only (not as a change to the legal rule)

To keep your calculations auditable, write down:

• the trigger date you chose, and
• a brief note stating why (e.g., “event occurred on ___” or “discovery occurred on ___”).

What the output means

After you run the calculation, DocketMath returns a:

• Computed deadline date (the target last day for filing under the default 2-year rule lens)

From there, you can:

• compare that deadline to internal milestones,
• select an earlier internal “file by” date for readiness,
• and prioritize evidence collection and drafting earlier.

How changes to inputs affect the result

Use this quick mental model:

• If you move the start date forward by 1 month, the computed deadline typically moves forward by about 1 month (because you’re still adding 2 years from the start).
• If the start date is wrong, the deadline will be wrong—even if the 2-year period length is correct.
• If the correct rule isn’t the general default, the correct deadline may not be 2 years. In that situation, treating CCP § 335.1 as the baseline could misstate the deadline.

Practical example (default rule lens)

Assume your chosen trigger date is March 15, 2024. Under the default rule lens:

• 2 years from March 15, 2024 → March 15, 2026

If you later determine the correct trigger date was actually April 1, 2024, then:

• 2 years from April 1, 2024 → April 1, 2026

That shift can matter for how much time you have to finalize filings and supporting materials.

Sources and references

Start with the primary authority for California and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Cal. Civ. Proc. Code § 904.1

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