Statute of Repose vs Statute of Limitations: Key Differences

Quick takeaways

• Statute of limitations bars lawsuits after a deadline measured from a key triggering event (often the date of injury or the date of discovery/accrual).
• Statute of repose bars lawsuits after a deadline measured from a fixed historical event tied to the defendant’s conduct (often the date a product was sold, or the date construction was completed).
• Repose usually runs regardless of when harm is discovered, which is why a claim can be time-barred even if the plaintiff didn’t know about the injury until years later.
• Limitations may pause or reset (tolling), while repose generally does not (or does so only in narrow, statute-specific situations).
• In practice, you’ll want DocketMath to track both clocks—either one can defeat a claim.

Inputs you need

DocketMath can help you compare timelines consistently, but you’ll still need specific facts to run the math correctly. Gather these inputs before you calculate anything:

1) The claim type and governing state law

• State jurisdiction (or federal statute, if applicable)
• Cause of action category (e.g., negligence, products liability, construction defect)

2) Key dates (at minimum)

Use this checklist:

• Event date for repose (often one of these):

  • date of sale of a product
  • date of completion of construction
  • date of delivery/installation of an improvement
  • date of the defendant’s last qualifying act
• Start trigger for limitations (often one of these):

  • date of injury
  • date the plaintiff knew or should have known
  • date of accrual under the statute’s rules

3) Filing date (for both deadlines)

• Complaint filing date (or suit commencement date)

4) Any known tolling or exceptions (for limitations, not always repose)

• Fraudulent concealment allegations (if relevant to the limitations clock)
• Statutory tolling triggers (e.g., disability rules, certain proceedings)
• Whether any “savings” provision is at issue

5) Whether the statute says “years” or a specific calendar concept

Some statutes specify:

• “within X years”
• “not later than” a date tied to an event
• special cutoffs for minors, governmental entities, or repeated injury events

How the calculation works

To compare statute of limitations vs statute of repose, think in two separate clocks.

Clock A: Statute of limitations (“when can I sue?”)

Goal: determine whether the case was filed within the time allowed after a claim “accrues” (often linked to injury or discovery).

Common mechanics:

• A limitations period typically begins on:

  • the injury date, or
  • the discovery date (sometimes “knew or should have known”), depending on the statute.
• The clock may be affected by tolling (pause) or restarts in certain circumstances.
• Many limitations rules turn on plaintiff knowledge or when the claim became actionable.

Practical timeline method (generic):

1. Identify the limitations trigger event (injury/discovery).
2. Add the statutory period (e.g., 2 years, 3 years, etc.).
3. Adjust for any tolling or statutory exceptions.
4. Compare the adjusted deadline to the filing date.

DocketMath can structure this workflow so you consistently:

• store the trigger date,
• store the statutory length (years/months/days),
• compute the last permissible filing date.

For a jurisdiction-aware run, consider starting your workflow at DocketMath tools so you’re applying the correct rule set.

Clock B: Statute of repose (“how long after the defendant’s act can a claim be brought?”)

Goal: determine whether the case is barred because it was filed too long after a defendant’s last qualifying act.

Key features:

• The repose clock generally begins at a fixed historical event, such as:

  • product sale,
  • construction completion,
  • delivery/installation of an improvement.
• Repose typically does not care when harm is discovered.
• Tolling is limited because repose is designed to provide finality and cut off stale claims.

Practical timeline method (generic):

1. Identify the repose start event (defendant’s last act).
2. Add the statutory repose length (e.g., 6 years, 10 years, etc.).
3. Determine whether any statutory exceptions override the repose bar.
4. Compare the repose cutoff to the filing date.

Side-by-side: how the same facts can produce different outcomes

Below is an illustrative comparison framework you can use with DocketMath:

A quick example structure (without giving legal advice)

• Defendant sells a product on Jan 1, 2010
• Plaintiff discovers injury on Dec 15, 2016
• Plaintiff files suit on Nov 20, 2017

If the statute of limitations is discovery-based (e.g., 2 years from discovery), the case might be timely under Clock A.
If the statute of repose is product-sale-based (e.g., 10 years from sale), then Clock B may still be open.

Now flip the scenario:

• Product sale: Jan 1, 2000
• Discovery: Dec 15, 2016
• Filing: Nov 20, 2017

Clock A might still be timely depending on the discovery rule and tolling, but Clock B could bar the claim if the repose cutoff (e.g., 10 years from sale) already passed.

Common pitfalls

Here are issues that frequently break jurisdiction-aware deadline calculations:

1. Using discovery dates for repose

   • Repose clocks usually start from the defendant’s qualifying act, not from discovery.

2. Mixing up “accrual” and “last act”

   • Limitations often tracks accrual; repose tracks the act that triggers the statute’s finality framework.

3. Ignoring statutory exceptions

   • Some jurisdictions include narrow override mechanisms (for example, specific fraud provisions). Those are statute-specific and must be confirmed in the text.

4. Forgetting multiple claim theories

   • Different causes of action can have different limitations/repose regimes, even when arising from the same event.

5. Misstating the relevant “event date”

   • Construction disputes turn on “completion,” “substantial completion,” or “occupancy” depending on the statute.
   • Products cases turn on “sale,” “delivery,” or “first installation.”

6. Assuming one deadline controls

   • Either clock can bar the claim. A compliant limitations period does not automatically make the repose period irrelevant.

7. Using calendar math incorrectly

   • Jurisdictions can define time in years that are calculated by specific methods (e.g., anniversary dates). DocketMath should calculate using the consistent “last permissible filing date” rule your jurisdiction requires.

Sources and references

Statutes of limitations and statutes of repose are state-created concepts and vary by jurisdiction and claim type. A few foundational federal references (where applicable) include:

• Federal tort limitation/repose examples

  • 28 U.S.C. § 2401 (United States as a party—various timing rules)
  • 28 U.S.C. § 1658 (time limits for certain federal claims, including fraud-related accrual concepts)
• General public policy framing

  • Repose statutes are widely recognized for providing finality after a fixed period from the defendant’s last act, even if injury is later discovered.

Because the exact rule depends on the jurisdiction and cause of action, DocketMath’s value is in applying a consistent, documentation-friendly calculation workflow once you’ve identified the governing statute and its dates.

Next steps

1. Identify the two relevant “start” events

   • Clock A: limitations start trigger (injury/discovery/accrual rule)
   • Clock B: repose start trigger (defendant’s last qualifying act)

2. Collect the required dates

   • Repose start event date
   • Limitations start trigger date
   • Filing date

3. Run the comparison in DocketMath

   • Start from DocketMath tools to generate a clear “last permissible filing date” for each clock.
   • Export or document the inputs so you can explain the timeline to a team member or client without ambiguity.

4. Check for exceptions

   • Review whether the limitations clock has tolling provisions and whether repose has any narrow overrides in the specific statute governing your claim.

5. Use the result to drive case triage

   • If either clock has expired, the filing timeline likely fails on at least one statutory bar.
   • If both clocks are still open, the question becomes how factual disputes and exceptions affect the applicable trigger dates.

Related reading

• Why we started the DocketMath blog
• Introducing Explain++: step-by-step calculation breakdowns
• A practical workflow for jurisdiction-aware legal calculations (and how to document them)