Statute of Limitations by State

What this calculator does

Run this scenario in DocketMath using the tools directory.

DocketMath’s “Statute of Limitations by State” guide is designed to help you quickly identify the limitations period that applies to a civil claim type by state—and then estimate the latest plausible filing date based on a known event date (such as an accident, breach, or discovery).

This guide is built for practical workflows: you pick a state, select a claim category, enter a relevant start date, and DocketMath produces:

• Statute of limitations length (in years) for the selected claim category and state
• Estimated expiration date based on the start date you provide
• A short list of factors that commonly shift deadlines (without turning into legal advice)

Typical “inputs” you’ll supply

Use this pattern when working through DocketMath:

• State: where the claim would be brought (the forum)
• Claim category: e.g., personal injury, breach of written contract, property damage, fraud, oral contract
• Start date: usually one of these:

  • Date of incident (e.g., accident)
  • Date of breach (contract)
  • Date of last payment or notice (contract)
  • Date of discovery (for claims that use a discovery rule)

Output you’ll get

DocketMath’s output generally includes:

• The baseline time period for the claim category in that state
• An estimated “outside date” for filing (computed from your start date and the statute length)

Because statutes differ widely by claim type and state, the same date can produce different outcomes depending on whether you choose “oral contract” versus “written contract,” or “personal injury” versus “property damage.”

When to use it

DocketMath is especially useful when you’re trying to answer a time-based question quickly, such as:

• You’re organizing a case intake and need an initial deadlines screen.
• You have a client/potential claimant with a known event date and want to determine whether the matter is likely time-barred under the baseline statute.
• You’re sorting potential causes of action and want to compare which claims are likely subject to longer or shorter limitations periods in the same state.

Best-fit situations

Check these boxes when DocketMath is likely a good first pass:

Situations where you’ll need extra context

Even with DocketMath, you may need more facts if any of the following are present:

• There’s a minority/age or disability-related exception
• The defendant allegedly concealed the cause of action (possible tolling)
• There are specific notice requirements for certain claim types
• The case could fall under a specialized statute (e.g., administrative procedures or claims against certain entities)

If you’re looking to run the analysis, start with the tool here: /tools.

Step-by-step example

Here’s a concrete walkthrough showing how DocketMath changes results when you adjust the state, the claim category, or the start date.

Scenario

Suppose someone was injured in a car crash on January 15, 2022 and wants to know the latest plausible filing date for a personal injury claim in one of two possible states.

We’ll compare State A and State B.

Step 1: Select the state

• Case filing state: State A
• Then repeat the same steps for State B

Step 2: Select the claim category

• Claim category: Personal injury

Step 3: Enter the start date

• Start date: 01/15/2022

Step 4: Review the estimated deadline

DocketMath then computes:

• Statute length (for that state and category)
• Estimated expiration date = start date + statute length (plus standard computation conventions used by the tool)

What you would see (illustrative structure)

Because statutes vary by state, your output may look like this in structure (exact numbers depend on the selected state/claim):

Step 5: Model an alternate start date (if relevant)

Now assume the injury wasn’t discovered until later—say, the claimant learned of a latent condition on October 1, 2023.

You could run an alternate calculation:

• Start date: 10/01/2023
• Claim category: still personal injury (but you may need to select a category that matches delayed-discovery timing in that state)

That change could shift the deadline by nearly 1 year or more, depending on how the state applies its discovery rules.

Common scenarios

Statute-of-limitations issues show up in predictable fact patterns. Below are scenarios DocketMath users often encounter, plus the key modeling choice that affects the output.

1) Written vs. oral contract disputes

Many states treat written contracts differently from oral contracts, often with different limitations periods.

Typical workflow:

• Select state
• Choose breach of written contract versus breach of oral contract
• Use the breach date (or sometimes the date of repudiation)

Checklist:

2) Personal injury claims (accident-based)

For many personal injury categories, the baseline start date is the date of injury. Some states apply special timing for certain injury types.

Quick actions:

• Enter the accident date as the start date if no discovery/tolling theory is being modeled.
• If there’s a latent condition, run a second scenario with a discovery-based start, but only under the category that fits the facts.

3) Property damage and related claims

Property damage claims often have different timing than personal injury claims—even if the same event caused both.

Workflow:

• Separate the claim category:

  • personal injury
  • property damage
• Use the same incident date for both, then compare results.

4) Fraud or misrepresentation claims

Fraud claims frequently involve discovery concepts because the plaintiff often couldn’t know of the wrong at the time of the act.

To model correctly:

• Choose the claim category that corresponds to fraud/misrepresentation
• Use a start date tied to when the claimant discovered (or should have discovered) the facts triggering the claim—if that category uses discovery timing

5) “Last payment” and ongoing performance contracts

In payment disputes, the start date can be contested—especially for continuing obligations.

Modeling approach:

• Run one calculation using:

  • the date of breach/repudiation
• Run another using:

  • the date of last payment (if that’s consistent with the category being modeled)

Then compare the estimated deadlines to plan fact gathering.

6) Tolling triggers (special circumstances)

Certain circumstances can pause or extend the limitations period:

• claimant’s legal incapacity (e.g., minority)
• defendant’s absence from the state (varies)
• concealment or misconduct
• pending administrative steps (for certain claim types)

DocketMath helps you flag these as timing variables, but exact applicability depends on the state and claim category.

Tips for accuracy

A few habits dramatically improve how reliable your DocketMath results are. Use these as a pre-flight checklist.

Choose the correct “start date” rule

Your most common error source is the start date, not the statute length.

Practical steps:

• Use the incident date when the claim category is event-based and no discovery exception applies.
• Use the discovery date only when the selected claim category uses a discovery rule and the facts align.

Match the claim category to the actual legal theory

Two claims can look similar on the surface but have different statutes.

For example, a lawsuit involving alleged wrongdoing might be:

• breach of contract (timing tied to breach)
• fraud (often tied to discovery)

If you select the wrong category, your expiration date will likely be misleading.

Run “compare scenarios” early

Instead of betting everything on one date, compute two versions when the facts support alternative theories:

• Scenario A: event-based start date
• Scenario B: discovery-based start date (or alternative breach-related date)

Then decide what additional facts you need to narrow the start date for the most accurate deadline.

Validate the state selection

Statutes run

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado