Worked example: statute of limitations in New Hampshire

Example inputs

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

This worked example shows how DocketMath’s statute-of-limitations calculator can be applied to a civil dispute in New Hampshire (US-NH) using the state’s general/default limitations period.

Baseline rule used in this example (general/default period):

• 3 years
• RSA 508:4 (General statute of limitations for civil actions)
  Source: https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/

Scenario

A plaintiff discovers (and files) a claim tied to an event that occurred on a known date. To calculate whether the filing is timely, we track two dates:

What you’re trying to answer

• Did the plaintiff file within 3 years of the relevant trigger date?
• If the filing date is late, by approximately how long is it late under the general rule?

Additional input toggles (what they would affect)

Depending on the tool settings, a statute-of-limitations calculator may ask for inputs like:

• whether to treat the event date as the “accrual” date, and/or
• whether tolling or extensions are being applied.

For this example, we assume no tolling and use the baseline 3-year period.

If you want to replicate this run yourself, use DocketMath’s calculator here: /tools/statute-of-limitations.

Example run

Below is a straightforward run using the general/default rule in New Hampshire: 3 years under RSA 508:4.

Run the Statute Of Limitations calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Identify the limitations deadline

• Limitations period: 3 years
• Start date (event/accrual date): January 15, 2022

Deadline calculation (general rule):

• January 15, 2025 is the “3-year mark.”

Step 2: Compare the filing date to the deadline

• Filing date: March 1, 2025
• Deadline: January 15, 2025

Result:

• March 1, 2025 is after January 15, 2025
• Therefore, the claim would be outside the 3-year window under RSA 508:4, assuming the general/default period applies and there are no tolling/extension facts.

How the tool typically reports timing

DocketMath’s output is often easiest to interpret as:

• Timely / Untimely under the configured SOL period
• The calculated deadline date
• A gap measure (for example, days early/late)

For this scenario, an intuitive output would be:

• Calculated deadline: January 15, 2025
• Filing date: March 1, 2025
• Status: Untimely
• Approx. lateness: ~45 days (because March 1 is about 45 days after January 15)

Gentle reminder: this is a simplified illustration. Real-world SOL analysis can depend on more than just two dates.

Short timeline view

Practical takeaway

In case management, the quickest operational step is to:

• lock the event/accrual date you’re using, and
• add 3 years, then
• compare the resulting deadline date to the filing date.

That’s the “shape” of this example.

Sensitivity check

Statute-of-limitations outcomes can flip when you change inputs—especially the start date you use as “accrual.” Below are sensitivity variations showing how results change while staying within the general/default 3-year rule under RSA 508:4.

A. Move the event date forward by 1 month

Inputs

• Event date: February 15, 2022
• Filing date: March 1, 2025
• SOL: 3 years (RSA 508:4)

Recomputed deadline

• Deadline: February 15, 2025
• Filing: March 1, 2025

Outcome

• Filing is still after the deadline
• Likely still untimely, but the “days late” amount shrinks.

B. Move the filing date earlier (same event date as the main example)

Inputs

• Event date: January 15, 2022
• Filing date: January 10, 2025
• SOL: 3 years

Recomputed deadline

• Deadline: January 15, 2025
• Filing: January 10, 2025

Outcome

• Filing is before the deadline
• Under the general/default calculation, it would be timely.

C. Edge sensitivity: filing exactly on the deadline

Inputs

• Event date: January 15, 2022
• Filing date: January 15, 2025
• SOL: 3 years

Outcome

• Filing matches the deadline date exactly.
• Under many date-comparison systems, “on the deadline date” is typically treated as timely—but confirm the tool’s status logic in the actual run.

D. What to watch when you re-run the calculator

To keep your workflow consistent, focus on three outputs:

• Deadline date
• Timely / Untimely status
• Gap (days early/late)

When to re-check inputs in a real workflow

Before relying on a calculator result, verify:

• the event/accrual date you entered matches the date your legal theory treats as when the claim became enforceable, and
• the filing date you entered matches the actual commencement/filing date you care about.

Then run DocketMath again and compare the new computed deadline date to the new filing date using: /tools/statute-of-limitations.

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