Why deadlines results differ in California

The top 5 reasons results differ

Run this scenario in DocketMath using the Deadline calculator.

If your DocketMath “deadline” results don’t match what you expected in California (US-CA), the difference usually comes down to how the input date, the assumptions, or the procedural setup was handled—particularly when the system uses California’s default limitations rule.

California default timeline (what DocketMath uses unless you narrow further)

California’s general civil statute of limitations is 2 years under CCP §335.1. This is the default/general period when you don’t apply a more specific sub-rule. In this brief, no claim-type-specific sub-rule was identified, so you should assume 2 years under CCP §335.1 unless your situation clearly fits a different limitations rule.

Top 5 causes of mismatched deadlines

1. Wrong event/trigger date fed into the calculator

   • Common mix-ups: using the date of injury vs. the date of discovery vs. the date the defendant had notice (depending on how your workflow defines “start”).
   • A small shift (even a few days) can move the calculated deadline.

2. Confusion between “limitations period” and “filing deadline mechanics”

   • Some tools focus on the “last day of the limitations period,” while others apply practical calendar mechanics (like “next business day” or court-appropriate timing).
   • Differences in how the last day is treated can create mismatches.

3. Applying (or omitting) a tolling/extension assumption

   • If one workflow assumes tolling/extension and the other doesn’t, expiration dates will diverge.
   • In California, tolling is fact- and procedural-history dependent, so inconsistent assumptions are a frequent source of differences.

4. Using a claim-type-specific rule when the other workflow used the general rule

   • This brief uses the general default: 2 years under CCP §335.1.
   • If someone used a different limitations statute (claim-type-specific or otherwise), they’ll produce a different end date even with identical input dates.

5. **Different day-count conventions (inclusive vs. exclusive)

   • Tools may count the trigger day inclusively or exclusively.
   • That convention can change outcomes by one day (and can matter more around month/day boundaries).

Quick reference: default rule used for mismatches

(General SOL source: https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html — see CCP §335.1 for the statutory basis.)

How to isolate the variable

Use a short diagnostic loop to identify exactly what changed between the two results you’re comparing.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Step-by-step checklist (practical)

• Write down both workflows’ start date (the date the clock runs from).

  • If the start dates differ, you’ve found the cause.

  • Check whether one result explicitly uses CCP §335.1 (general 2-year period).

  • If one method used a different limitations statute, the result will differ even with the same start date.

  • Check whether each output treats the last day as:

    • the same calendar day, or
    • adjusted to a next court-appropriate business day.

  • DocketMath should be consistent within its own convention; mismatches often come from manual adjustments or using different tools/workflows.

  • If one workflow included a tolling trigger (or another extension factor), test the calculation with tolling removed.

  • If the results converge, tolling/extension assumptions were the mismatch.

  • The same set of facts can be categorized differently, which may change which limitations rule is selected.

  • If the category changes, the applicable statute may change, creating a deadline gap.

Use DocketMath as a controlled test

Run two DocketMath calculations using the same inputs except one:

• Run A: use the trigger date you believe is correct.
• Run B: use the alternative trigger date you suspect was used.

Then compare outputs. The difference tells you which variable matters most.

Gentle caution: Don’t “average” outcomes. If one workflow applies CCP §335.1 (general 2 years) and the other applies a different (claim-specific) limitations period, combining them can produce a misleading mid-date.

Next steps

1. Lock in your start date definition

   • Record why that specific date is the trigger for the limitations clock (event date, discovery date, or another defined trigger used in your workflow).

2. Run DocketMath with the general rule explicitly

   • Use the default baseline: 2 years under CCP §335.1.
   • If the mismatch disappears using the baseline, the problem is likely a tolling/extension or a claim-type substitution in the other workflow.

3. Create a one-page “deadline record”

   • Include:

     • the start date used,
     • the rule applied (CCP §335.1: general 2 years),
     • the computed last filing date from DocketMath,
     • any adjustments (calendar mechanics or tolling/extension assumptions).

4. If disagreement remains, compare procedural posture

   • Pre-suit vs. post-filing procedural steps can cause different clocks to be used.
   • Reconcile the workflows before relying on any single computed date.

Use the DocketMath calculator directly to standardize your calculation inputs and outputs: /tools/deadline.

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