Tolling the statute of limitations in North Dakota

Direct answer

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

In North Dakota, you generally toll (pause or extend) the statute of limitations when a claim is brought within the limitations period and a recognized tolling trigger applies—most commonly when the defendant is “out of the state” (absent from North Dakota), along with other triggers such as minority (under age 18). Because the result depends on the claim type, the accrual date, and the specific tolling trigger(s), you should model the facts you have rather than relying on a one-size-fits-all rule.

DocketMath’s statute-of-limitations calculator (with jurisdiction-aware rules for US-ND) can help you test scenarios and see how different tolling intervals affect the filing deadline. Since tolling can shift deadlines by days, months, or more, accurately capturing the key dates matters.

What you need to know

Before you run a North Dakota tolling calculation with DocketMath, gather these five date facts:

1. Claim type (e.g., personal injury, contract, fraud, injury to property). North Dakota’s limitations period varies by claim type.
2. Accrual date (when the cause of action “accrues”—i.e., when the claim arises under applicable North Dakota law).
3. Initial limitations deadline (the end date you’d get without tolling).
4. Tolling event(s) and their start/end dates (timing is the whole point of tolling—don’t enter “sometime last spring” if you can avoid it).
5. Jurisdiction confirmation: US-ND.

A practical way to think about tolling in this context: it changes how the “running clock” behaves between accrual and the deadline.

Two implications that help you avoid common errors:

• Wrong trigger = wrong deadline. For example, a minority-based rule won’t replace an absence-from-state rule if the statute requires a specific condition.
• Overlapping triggers matter. If more than one tolling event applies, the calculator should reflect how they interact over the timeline (so you’re not accidentally assuming they can’t overlap).

In DocketMath terms, treat tolling as an input set that modifies the effective time the statute of limitations allows for filing.

Step-by-step

Follow this workflow to toll North Dakota deadlines in DocketMath (US-ND).

1) Open the calculator and set jurisdiction

• Go to /tools/statute-of-limitations
• Choose North Dakota (US-ND) so the calculator uses North Dakota’s tolling and limitations framework.

2) Choose the claim category

• Select the claim type that matches your situation.
• This selection determines which North Dakota limitations period (and related tolling treatment) the tool applies.

3) Enter the accrual date

• Input the date the claim accrued.
• If you have uncertainty about accrual (for instance, when notice or discovery concepts may affect accrual), consider running multiple scenarios (e.g., an “earliest plausible accrual” run and a “latest plausible accrual” run) to see how much the deadline changes.

4) Add tolling inputs (when applicable)

Depending on your facts, add tolling event dates the calculator supports for US-ND. Common tolling inputs you may be able to model include:

• Defendant absent from North Dakota (often described as out-of-state/absence type tolling)
• Plaintiff under age 18 (minority tolling)
• Other claim-specific or status/location-based tolling triggers supported by the calculator’s US-ND logic

For each tolling trigger, enter:

• Start date (when tolling begins)
• End date (when tolling ends)
• Any setting that indicates whether tolling is continuous through that interval

5) Run scenarios and compare outputs

DocketMath can produce multiple useful outputs, such as:

• Base expiration date (no tolling)
• Tolling-adjusted expiration date
• The difference between them (how much the deadline shifts)

Use that comparison intentionally:

• If you adjust an absence start date by 30 days, and the adjusted deadline shifts by roughly 30 days, that behavior is consistent with “interval-based” tolling.
• If the direction seems counterintuitive, revisit the date inputs and the trigger selection first.

6) Document your timeline for review

Record the inputs you used:

• accrual date
• limitations period (implicitly, via claim category)
• tolling start/end dates
• adjusted deadline returned by DocketMath

This makes it easier to update the calculation if you later confirm dates with records (emails, travel logs, medical notes, or court filings).

Common trap: Using rough estimates for tolling intervals can create a misleading deadline. If the deadline is near-term, try to upgrade “approximate” dates to verified dates.

Key statutes and citations

North Dakota’s tolling and limitations rules sit partly in general tolling provisions and partly in limitations statutes by claim type within the North Dakota Century Code. When using a jurisdiction-aware tool like DocketMath (US-ND), these statutory anchors are often the key sources that drive the logic.

Key tolling-related sections to be aware of:

• Minority tolling (under age 18)
  North Dakota provides tolling for persons who are minors under certain circumstances. See N.D. Cent. Code § 28-01-25.

• Absence from the state / out-of-state tolling (defendant absence type rule)
  North Dakota has a general rule addressing tolling where a defendant is not within the state in specified circumstances. See N.D. Cent. Code § 28-01-27.

• Claim-type limitations periods (general limitations framework)
  Limitations periods vary depending on the kind of claim. These are set out across N.D. Cent. Code Chapter 28-01, with different subsections for different causes of action.

Because limitations periods differ by cause of action, the calculator’s “base expiration date” and the tolling adjustments will depend heavily on selecting the correct claim category first, and then applying the tolling triggers to the correct parties and time intervals.

Common pitfalls

Watch for these issues when calculating tolling in North Dakota with DocketMath:

• Using the wrong accrual date
  Tolling can’t fix a mis-started clock. If accrual is disputed or depends on a factual trigger, run multiple accrual scenarios and compare.

• Confusing tolling with post-filing extensions
  Tolling relates to the time before filing (i.e., whether the statute deadline is affected). Procedural events after filing (service timing, amendments, stays) may involve different doctrines and are not the same as limitations tolling.

• Entering tolling intervals in a way that breaks the timeline
  Make sure each tolling start date precedes its end date. If you reverse a date range, the calculator may not be able to apply tolling correctly.

• Assuming one tolling rule applies to everyone
  Many rules depend on who the tolling concerns (e.g., plaintiff status for minority) and where the relevant party is (e.g., absence from North Dakota for defendant-focused tolling).

• Failing to model overlapping tolling periods
  If two tolling triggers apply during the same span, model both instead of choosing only one. Your record of overlapping dates is often more important than your intuition.

Run the numbers

Use DocketMath’s outputs to sanity-check your modeling and plan around the deadline with confidence.

1) Compare base vs. adjusted deadlines

A simple checklist:

• Base expiration date (no tolling): Does it match your expectations for the claim type?
• Adjusted expiration date (with tolling): Does the shift match the tolling interval(s) you entered?
• Sensitivity check: If you change a tolling start date by a small amount, does the deadline move in the direction you’d expect?

2) Validate with “interval logic”

Even without reproducing every statute rule, you can confirm broad behavior:

• If a defendant was absent for N days during a relevant period, your adjusted deadline should typically shift by approximately N days, assuming the statute conditions are met.
• If minority tolling applies for M years (or a partial period), the adjusted deadline generally should extend rather than contract.

3) Run conservative vs. aggressive fact scenarios

When dates are uncertain, run at least two versions:

• Conservative scenario: earliest plausible tolling start, latest plausible accrual (or whichever combination produces the earliest deadline)
• Aggressive scenario: latest plausible accrual and/or latest plausible tolling end (whichever combination produces the latest deadline)

Then compare:

• If both scenarios still leave a “safe” filing window after your intended filing date, you have more buffer.
• If the result flips between “safe” and “unsafe,” you likely need to verify key dates before making a decision.

4) Use the adjusted deadline for operational planning

Treat the tolling-adjusted deadline as a “last-day benchmark.” Build time for:

• collecting documents,
• drafting the complaint,
• coordinating service logistics,
• internal review.

DocketMath models the legal deadline mechanics; your real-world workflow still needs margin.

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator