Statute of Repose vs Statute of Limitations
8 min read
Published April 10, 2026 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
What this calculator does
Run this scenario in DocketMath using the tools directory.
DocketMath is a practical tool for comparing two common time-bar concepts in civil litigation: the statute of limitations and the statute of repose. Even though both restrict when you can bring a claim, they operate differently in ways that can dramatically change filing deadlines.
This guide (and the comparison framework behind DocketMath) helps you:
- Identify whether a time restriction is claim-based (limitations) or event-based (repose).
- Understand how each deadline typically begins to run (and when it stops).
- Spot scenarios where a claim may still be timely under the limitations window but barred by the repose window.
- Model a timeline in plain language so you can see the likely outcome before you draft, file, or respond.
Note: This article explains general legal concepts for workflow planning. It’s not legal advice and doesn’t replace jurisdiction-specific research—especially because states and claim types vary.
The two clocks in plain terms
| Concept | Typical trigger | Typical purpose | Common effect |
|---|---|---|---|
| Statute of limitations | Usually tied to when the claim accrues (often when injury/discovery occurs) | Prevents stale lawsuits while preserving fairness | May be tolled (paused) or extended depending on rules |
| Statute of repose | Usually tied to when a specific event happens (e.g., completion of construction) | Creates a hard outer limit regardless of fairness concerns | Usually not tolled and generally runs to completion |
In practice, courts often treat a statute of repose as a hard stop: even if you couldn’t reasonably discover the harm earlier, the repose deadline can still bar the claim.
Where to use DocketMath
You can use DocketMath at /tools to run a side-by-side timeline comparison between the two clocks for your fact pattern.
When to use it
Use DocketMath’s approach when you’re working with deadlines that could be governed by either clock. It’s particularly useful when any of these are true:
- You’re dealing with injury claims where discovery timing is disputed (limitations often enters the discussion).
- You’re dealing with construction, product, or design-related claims where an “outer boundary” often exists (repose often enters the discussion).
- You need to draft a motion or respond to an argument about timeliness and want a structured timeline.
- You’re comparing claims arising from the same set of facts but under different legal theories.
Quick decision checklist
If you answer “yes” to at least one item, the statute-of-repose vs statute-of-limitations comparison is worth doing early:
If your answers skew toward “event-based,” prioritize repose analysis first because it can act as the final barrier even if limitations could otherwise be extended.
Step-by-step example
Let’s walk through a concrete timeline. Imagine a claim involving a completed project and a later-discovered injury.
Assumed facts (for illustration)
- Event date (repose trigger): January 15, 2015 (construction completed)
- Injury/discovery date (limitations trigger): March 20, 2017
- Statute of limitations period: 2 years from accrual (discovery/injury-based)
- Statute of repose period: 5 years from event completion (event-based)
Warning: Exact durations and triggers depend on jurisdiction and claim type. This example shows how the logic works, not a jurisdiction-specific rule.
Step 1: Set the two start dates
- Repose starts: Jan. 15, 2015
- Limitations starts: Mar. 20, 2017
Step 2: Compute the outer deadline (repose)
- Repose end date = Jan. 15, 2020 (5 years after completion)
No matter what happens after Jan. 15, 2020, the repose window closes. The key practical effect is that later filing may be barred even if the plaintiff argues discovery delay.
Step 3: Compute the accrual-based deadline (limitations)
- Limitations end date = Mar. 20, 2019 (2 years after discovery)
So, for this set of assumptions:
- Claims filed before Mar. 20, 2019 are potentially timely under limitations.
- Claims filed after Jan. 15, 2020 are generally barred by repose (even if limitations might otherwise still be argued).
Step 4: Compare filing dates
Assume a party files a lawsuit on each of the following dates:
| Filing date | Timely under limitations (ends Mar. 20, 2019)? | Barred by repose (ends Jan. 15, 2020)? | Likely overall result (based on these clocks) |
|---|---|---|---|
| Feb. 1, 2019 | Yes | No | Timely on both clocks |
| May 1, 2019 | No | No | Likely time-barred by limitations |
| Dec. 15, 2019 | No | No | Still may be barred by limitations |
| Feb. 1, 2020 | No | Yes | Repose likely bars regardless of limitations arguments |
Step 5: Identify “tolling leverage”
Many limitations frameworks allow certain pauses (tolling) for specified reasons (for example, disability, some fraud-related doctrines, or procedural events depending on jurisdiction). Statutes of repose, by contrast, are often framed as not subject to tolling.
A practical workflow implication:
- If the case is close to the repose deadline, you generally can’t rely on tolling doctrines to rescue late filings.
- If the case is close to the limitations deadline but far from the repose boundary, tolling/discovery timing may be a more relevant fight.
Common scenarios
The statute-of-repose vs statute-of-limitations distinction comes up repeatedly. Below are common patterns you’ll see in case triage.
1) “We discovered it late” (limitations vs repose conflict)
Typical fact pattern
- Discovery occurs years after the underlying event.
- Plaintiff argues late discovery extends the limitations window.
How clocks usually clash
- Limitations: late discovery can delay accrual, potentially making the claim timely.
- Repose: if the claim type is subject to a repose period running from an earlier event date, repose may still extinguish the claim.
Workflow takeaway
- If the defense can identify a relevant event date and repose window, the “late discovery” argument may not be enough.
2) Construction and project-completion timelines
Construction defect disputes frequently include repose concepts. The event date often isn’t the injury date—it’s tied to completion or substantial completion.
What to look for
- The date of completion/substantial completion
- The date of the alleged defect manifestation (may matter for limitations)
Workflow takeaway
- Build a timeline with both dates. Then compare the filing date against the earlier “hard stop.”
3) Product-related claims with an event-based outer deadline
Some product liability frameworks include outer deadlines that can function like repose. Even where harm is discovered later, event-based time bars can still apply.
Workflow takeaway
- Identify the “event” that starts the outer clock (commonly sale, delivery, manufacture, or first placement into service, depending on the legal structure).
4) Multiple defendants, different event dates
Real cases often involve multiple parties who played roles at different times.
Practical issue
- Repose windows might differ per defendant depending on each defendant’s relevant event date.
- Limitations might also differ if each defendant’s conduct affects accrual.
Workflow takeaway
- Segment the timeline by defendant role and event date. A single global date can cause deadline miscalculations.
5) Amended complaints and relation-back arguments
Procedurally, parties sometimes amend after limitations has expired. Courts may apply “relation back” concepts in certain circumstances.
How this interacts with repose
- Relation back can matter for limitations issues.
- Repose often operates as a substantive bar; if repose has run, amendments may not resurrect the claim.
Workflow takeaway
- Don’t assume that fixing accrual or pleading details after the fact will overcome an event-based outer limitation.
6) Claims in multiple legal categories
A single set of facts can yield claims under different statutes or legal theories—some with repose, some without.
Workflow takeaway
- Treat each claim category as its own “clock set.” Even if they share facts, their deadlines can differ.
Tips for accuracy
Deadline analysis fails most often due to date selection errors or misunderstanding which event starts which clock. Use these guardrails.
Build the timeline like a docketing system
Create a simple list of dates before you calculate anything:
- Event date (repose trigger): __________
- Accrual/discovery date (limitations trigger): __________
- Filing date: __________
- Jurisdiction / claim type context: __________ (even if you’re just planning)
Then map each deadline to the correct date.
Validate the trigger language you’re using
Words matter. If a statute or rule says time begins at:
- “completion,” “substantial completion,” “first placement,” “sale,” or “delivery” → that’s commonly event-based (repose-style).
- “accrual,” “discovery,” “when injury occurred,” or “when plaintiff knew or should have known” → that’s commonly limitations-style.
Pitfall: Swapping the trigger dates is the fastest way to produce a deadline that looks plausible but is wrong. Always label each date with the clock it feeds.
Track whether a tolling argument is available
Because statutes of repose are often described as not subject to tolling, you should not assume the same tactics that help with limitations will help with repose.
A practical approach:
- If you’re relying on discovery rules, treat it as primarily limitations territory.
- If
