Statute of repose in North Dakota

Statute of repose in North Dakota

7 min read

Published June 8, 2025 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Direct answer

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In North Dakota, the statute of repose for certain construction-related claims is 8 years under N.D. Cent. Code § 28-01.1-06 (often described as a “contractor/owner construction repose” rule). Once that 8-year period expires from the statute’s triggering event, the claim is generally time-barred even if the injury or defect is discovered later.

Note: A statute of repose is designed to provide an absolute end to certain liability after a specified time. In practice, this can cut off claims earlier than a discovery-based statute of limitations would.

Repose rules are different from statutes of limitation: statutes of limitation often focus on when the claim accrues (frequently tied to discovery), while statutes of repose focus on a fixed outer deadline tied to a construction/project-related event.

What you need to know

Before you enter dates into DocketMath (and before you interpret the output), make sure you’re answering the key question: Which deadline are we measuring—repose (absolute cutoff) or limitation (relative deadline)?

1) Repose vs. limitation (why your timeline may be shorter than expected)

  • Statute of repose (outer cutoff): starts from a statute-defined event (often tied to completion/substantial completion or another specified construction milestone). It can bar the claim even if the injury is discovered after the repose period ends.
  • Statute of limitations (relative deadline): typically starts at accrual, which can be affected by discovery or other accrual rules.

Takeaway: With repose, “we didn’t know until later” often doesn’t change the outer cutoff for covered construction-related claims.

2) The 8-year anchor in North Dakota

For many construction-related actions covered by N.D. Cent. Code § 28-01.1-06, the repose period is 8 years. The statute’s text controls the triggering event—often the date tied to construction completion/substantial completion or the project milestone the statute identifies for that claim category.

3) Your inputs matter more than you might think in DocketMath

DocketMath’s statute-of-limitations calculator converts your entered dates into a calendar deadline using jurisdiction-aware rules (set by choosing North Dakota (US-ND)).

In practice, the single most important input is the repose trigger date (the construction/project event that starts the repose clock). If you accidentally use a discovery date instead of the statute’s construction-related trigger, your calculated deadline may look later than it should.

4) Not every claim fits the same “timer”

Repose statutes generally apply to specific categories of construction/improvement-related claims. If your claim doesn’t fit the covered category (or the trigger event doesn’t match your facts), relying on § 28-01.1-06 may produce the wrong deadline.

Step-by-step

Here’s a practical workflow you can follow to use DocketMath for a North Dakota repose-focused timeline.

Step 1: Confirm the claim category

Ask: is this a construction-related claim that falls within N.D. Cent. Code § 28-01.1-06?

  • If your dispute is about design/construction/installation or an improvement to real property, you’re more likely in the covered zone.
  • If the claim is unrelated to construction/improvements, you may need a different statute/time framework.

Step 2: Identify the repose “start event” date

Repose depends on the statute-defined trigger, not on discovery (for covered repose rules).

Look for a date such as:

  • the date of substantial completion, or
  • another construction/project completion milestone specified by the statute structure.

Step 3: Select North Dakota in DocketMath

When you open the calculator, choose:

  • jurisdiction: US-ND

This is what makes the tool apply the correct North Dakota time rules.

Step 4: Calculate the outer deadline in DocketMath

Use the statute-of-limitations calculator and input:

  • the repose start date (the construction/improvement trigger date),
  • and any other fields the calculator requests for the relevant claim setup.

You can start here: /tools/statute-of-limitations

Step 5: Compare the calculated deadline to the filing date

Once DocketMath returns a computed deadline:

  • If your filing date is after the computed repose deadline, the claim is likely barred by repose.
  • If the filing date is on or before the deadline, you may be within the repose window (subject to the accuracy of your trigger-date facts and the claim category fit).

Warning: Repose can defeat claims even when there’s a credible discovery timeline. If your only “late” date is the discovery date, that may not rescue a repose-expired claim for covered categories.

Step 6: If repose doesn’t end the inquiry, check limitation too

Even if the claim survives the repose cutoff, a statute of limitations deadline may still apply. A complete timing check typically evaluates:

  • the outer repose deadline (absolute cutoff), and
  • the relative limitations deadline (often accrual/discovery-driven).

DocketMath is designed to help you map those time windows in an organized way.

Key statutes and citations

For North Dakota, the central citation to anchor a construction-related repose analysis is:

TopicNorth Dakota citationKey takeaway
Construction-related statute of repose (outer deadline)N.D. Cent. Code § 28-01.1-06Provides an 8-year repose period for covered construction/improvement claims.

While DocketMath helps compute calendar deadlines, the statute text controls what the trigger event is and whether your claim category is covered.

Common pitfalls

These are the mistakes that most often cause confusion when calculating repose timelines:

  • Using the wrong start date
    • Example: entering the discovery date as the repose start date instead of the statute’s construction completion/substantial completion trigger.
  • Assuming discovery extends repose
    • Repose is designed to run even if discovery happens later (when the claim is within the covered repose category).
  • Treating limitations as if it were the only clock
    • Some claims may still be constrained by limitation deadlines even if they are not barred by repose.
  • Mixing up court-forum differences
    • If a federal case includes state-law claims, the timing can still depend on state substantive filing deadlines for those claims.
  • Assuming all construction-related theories share the same timing
    • Contract, negligence, and other theories can map to different statutes/time triggers.
  • Assuming coverage
    • If the facts don’t involve covered construction/improvements (as defined or understood by the statute’s scope), applying § 28-01.1-06 may be incorrect.

Pitfall: Courts often treat repose as a categorical cutoff for covered claims. If the filing is late relative to the repose deadline, equitable arguments typically won’t override the statute’s text.

Run the numbers

Below is an illustrative example showing how an 8-year repose window can operate. These are sample dates for demonstrating the math—not a substitute for applying § 28-01.1-06 to your facts.

Example timeline (8-year outer deadline)

  • Repose start event (construction completion date): March 10, 2016
  • Repose period: 8 years under N.D. Cent. Code § 28-01.1-06
  • Calculated repose deadline: March 10, 2024

If the lawsuit is filed:

  • March 9, 2024 → likely within the 8-year repose window
  • March 10, 2024 → on the deadline day (tool output and exact rule application matter)
  • March 11, 2024 → likely repose-expired (too late under the outer cutoff)

What to adjust in DocketMath

Try changing just one input to see how outcomes shift:

Input you changeWhat happens to the outcome
Earlier completion/trigger dateDeadline moves earlier (more risk of repose expiration)
Later completion/trigger dateDeadline moves later (more room for filing)
Filing dateDetermines whether the computed deadline has been exceeded

Quick checklist before you click calculate

Primary CTA to run your timeline: /tools/statute-of-limitations

Related reading