Statute of Limitations for Oral Contract in North Dakota

6 min read

Published April 8, 2026 • By DocketMath Team

Overview

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

In North Dakota, the statute of limitations for an oral contract claim is generally 6 years under N.D. Cent. Code § 28-01-16(1).

That 6-year window typically starts when the claim accrues—most often when the breach occurs (or when performance was due and didn’t happen). It usually isn’t based on when you first noticed you were owed money. If you’re tracking deadlines for a spoken agreement (no written terms, no signatures, etc.), this is often the starting point for a contract-style limitation analysis.

DocketMath uses the statute-of-limitations rules for your selected jurisdiction to help you convert the legal rule into a practical calendar deadline.

Note: Limitation periods often depend on how the claim is characterized. Even if the underlying deal started orally, if your dispute is really about something else (e.g., a statutory remedy or a non-contract theory), the applicable time limit may differ. This is general information, not legal advice.

Limitation period

The core rule is 6 years for actions “upon a contract, obligation, or liability… not founded upon an instrument in writing.” The relevant language is found in N.D. Cent. Code § 28-01-16(1), which sets the time to sue at six years.

How the timeline usually works

A practical way to model an oral-contract deadline is:

  • Trigger date (often the date of breach or the date performance was due and not performed)
  • Start of the limitation clock
  • 6-year filing deadline

In real cases, you may need to determine the most defensible trigger based on your facts—especially when:

  • there are multiple invoices or deliverables under the same overall agreement,
  • there were part payments,
  • there were ongoing obligations with different due dates,
  • the agreement involved conditions or installments (making the “due” date less straightforward).

What affects the output you get from DocketMath

When you use DocketMath’s statute-of-limitations calculator at /tools/statute-of-limitations, your main modeling input is typically the trigger date you choose.

Output change to expect:

  • If you enter a later trigger date, the computed deadline moves later by a similar amount.
  • If you enter an earlier trigger date, the computed deadline moves earlier—which can matter if a court later finds the claim accrued sooner than you assumed.

Quick example (calendar math)

If the alleged breach happened on March 1, 2024, a simple “6 years from the trigger” model points to a deadline around March 1, 2030 under § 28-01-16(1).

However, real-world filing timelines (preparing documents, filing, and service logistics) can require earlier action even if the statutory deadline appears later.

Key exceptions

The 6-year contract rule under N.D. Cent. Code § 28-01-16(1) is often the right starting point, but deadlines can shift based on how the claim fits the statute.

1) If your claim isn’t truly “upon a contract,” another period may apply

North Dakota limitation rules vary by claim type. If your dispute is framed as something other than enforcing a contract/contract-like obligation (for example, a specific statutory remedy or another legal theory), the time limit may be different than 6 years.

2) “Oral” doesn’t always control the written-instrument analysis

The statute’s key phrase is not only “oral,” but whether the action is “not founded upon an instrument in writing.”

So even when the agreement began orally, you may end up under a different limitation if the claim is actually founded upon written materials, such as:

  • written confirmations,
  • signed acknowledgments,
  • letters or documents the claim relies on,
  • other paperwork treated as an “instrument in writing” for the relevant analysis.

3) Accrual can turn on due date vs. breach date (fact-specific)

Even under the correct statute, the outcome can hinge on the trigger:

  • When was the other side’s performance due?
  • Was there a refusal to perform?
  • Were there conditions precedent?
  • Did separate deliveries create separate breach events?

4) Payments or acknowledgments may affect timing—but not automatically

Some jurisdictions treat certain payments or acknowledgments in ways that can change the limitation analysis. In North Dakota, any such effect is typically fact-dependent, including whether the conduct is tied to the same obligation and whether it qualifies as a legally recognized acknowledgment.

Practical takeaway: Don’t “lock in” a deadline using only “6 years” if you suspect written paperwork exists or if your facts suggest a different accrual trigger. Small changes in trigger date or legal characterization can move the result.

Statute citation

N.D. Cent. Code § 28-01-16(1) sets the limitations period for actions “upon a contract, obligation, or liability… not founded upon an instrument in writing” at six years.

For most oral contract timing questions in North Dakota, this is the anchor statute to model.

Use the calculator

Use DocketMath’s statute-of-limitations calculator here: /tools/statute-of-limitations.

What to enter (US-ND / oral-contract model)

For a North Dakota oral-contract model, you will typically provide:

  • Jurisdiction: **North Dakota (US-ND)
  • Trigger date: commonly the date the obligation was due and not performed, or the date of breach you can support with records
  • Claim type (if prompted): select the option that corresponds to a contract/obligation not founded upon an instrument in writing (exact wording depends on the tool interface)

How the output works (and how to sanity-check it)

The calculator applies the governing limitation period (generally 6 years under § 28-01-16(1) for oral-contract / not-in-writing situations) and produces a deadline date.

Before you rely on the result, sanity-check:

  • Does your trigger date match the contract timeline (due date/breach), not just when you realized you were owed?
  • Is your evidence better characterized as not founded upon an instrument in writing?
  • Are there multiple deliveries/installments that could create separate breach dates?

Checklist before you act

Pitfall to avoid: Using the date you noticed the issue (instead of the date the breach/accrual occurred) can lead to a later computed deadline that won’t match the legal accrual argument.

Updating outputs when facts change

If you uncover new facts—such as a written document that changes whether the claim is “founded upon an instrument in writing”—rerun the calculator using the updated characterization and/or trigger date. Because the computed deadline depends on those inputs, the deadline can shift accordingly.

Sources and references

Start with the primary authority for North Dakota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading