Inputs you need for deadlines in California

Inputs you will need

Run this scenario in DocketMath using the Deadline calculator.

Use DocketMath’s Deadline calculator to generate California deadline dates. To get reliable results, gather the “inputs” below in advance—especially because this checklist is anchored to California’s general/default limitations period, not a claim-type-specific rule.

Core time rule (California default):

• General SOL period: 2 years
• General statute: CCP §335.1
• Source: https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html

Important: This guide uses the general/default SOL period of 2 years under CCP §335.1. In this checklist, no claim-type-specific sub-rule is included. If your matter has a different limitations period or a tolling/extension rule, your inputs (and therefore your output) may need to change.

Checklist: inputs for the Deadline calculator (California / US-CA)

• Select the calculation mode that corresponds to running the general/default SOL.

  • In this checklist, that means defaulting to CCP §335.1 (2 years).
  • The date that starts the limitations clock in your workflow (e.g., the event date you’re treating as “start” for this analysis).
  • Choose what the tool should calculate—typically the end of the SOL (often used as a “file by” deadline).
  • If DocketMath offers multiple output options, pick the one that matches your intended step.
  • Make sure the tool is set to US-CA so it applies California rules.
  • Only fill these if you have documented facts that support them (e.g., pauses or adjustments).
  • If you don’t have tolling data, leave them blank rather than guessing.

Where to find each input

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Case type / calculation mode (California default)

You don’t need to memorize every code section to use DocketMath—but you do need to pick the correct mode so the calculator applies the general/default framework.

• Use California default mode when you’re applying:

  • 2-year general SOL under CCP §335.1 (the rule used here)

Where to find your selection:

• Your intake notes, task checklist, or decision log for what you’re running:

  • General/default vs. something else

2) Trigger date (start date)

The trigger date is the most important factual input because it drives the tool’s calculated end date.

Where to find the trigger date:

• Incident/occurrence date (e.g., event date)
• Transaction date (e.g., contract/service date, if your workflow uses it as the start)
• Notice/demand date (if your workflow uses a notice-based trigger)
• “Discovered” / “knew or should have known” date (only if your methodology uses that type of start date)

Quick verification tip:

• If you have multiple candidate dates, write down which one you’re using and stay consistent.
• If your workflow normally uses a different trigger concept than “event date,” don’t switch it mid-stream without updating the methodology.

3) Deadline type to compute

Decide what output you actually need for your timeline.

• Common choice: SOL end date / file-by date
• Other choice: another tool-provided deadline category (if available)

Where to decide this:

• Your internal task step:

  • “Find the last day to file” vs. “Compute deadline for a particular action”

4) Jurisdiction confirmation (US-CA)

You should confirm the tool is set correctly before entering dates.

Where to find it in DocketMath:

• The calculator’s jurisdiction selector for **California (US-CA)

5) Tolling / modification flags (only if applicable)

Tolling and other modifications can change the output beyond a straight “2 years from trigger date” calculation.

Where to find tolling/adjustment facts:

• Court docket entries and case status notes (if already available)
• Documented events you’ve categorized in your workflow (e.g., documented pauses or legal events that affect timing)

Common pitfall to avoid:

• Don’t add tolling flags without documented support—small data-entry differences can move deadlines substantially.

Run it

1. Open DocketMath → Deadline

   • Primary CTA: /tools/deadline
2. Confirm Jurisdiction: US-CA (California).
3. Select the general/default limitation framework:

   • 2 years using CCP §335.1
   • This is the rule used by default in this checklist (no claim-type-specific sub-rule included).
4. Enter your trigger date (start date).
5. Choose the deadline type you want as the output (typically SOL end / file-by).
6. Review the calculated deadline and record it in your timeline.

How outputs change when you change inputs

Practical check: If the trigger date you used doesn’t match your chosen methodology (for this checklist, the general/default 2-year approach), the tool can produce a “clean” answer that’s still not aligned with your real-world deadline process.

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