How statute of limitations rules vary in New Hampshire

5 min read

Published April 8, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

What varies by jurisdiction

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

In New Hampshire, statute of limitations (SOL) results can differ based on the specific claim being asserted, the procedural posture used, and the way key dates are defined (for example, “accrual” vs. “incident date,” where applicable).

Start with the baseline rule: for civil actions, New Hampshire’s general/default SOL period is 3 years under RSA 508:4. That general rule acts as the fallback when a more specific SOL provision does not apply. If you’re using DocketMath’s statute-of-limitations calculator for US-NH, treat RSA 508:4 as your “default layer” unless you identify a claim-specific rule that overrides it.

Key variations that can change the result

Even when the default is 3 years, the SOL expiration date can still shift because of:

Accrual date vs. incident date
- SOL “clocks” often start at claim “accrual,” which may not match the date the underlying harm or event occurred.
Tolling and pause mechanics
- Certain events can pause or extend SOL deadlines (depending on whether a statutory tolling rule applies).
Forum and procedural posture
- The same dispute can appear in different procedural forms (for example, different claim theories), and timing issues may be governed by different rules depending on what you’re actually filing.
Claim-type specificity
- If another statute (other than RSA 508:4) sets a different deadline for your claim type, the general rule may not control.

Note: In the materials used for this overview, no claim-type-specific sub-rule was found beyond the general/default period. That means RSA 508:4 is the baseline you should start with, but you should still verify whether your specific claim is governed by a separate SOL statute.

How this shows up in practice (example inputs)

DocketMath typically depends on the dates you provide, such as:

the event date (e.g., injury/transaction/breach date),
the accrual date (if you believe accrual is later than the event date), and
any tolling-related dates (if applicable).

When the accrual date is later than the event date, the calculator’s “end date” can move later—sometimes substantially. If the accrual date is earlier than expected (or you select the wrong start date), the SOL expiration can arrive sooner than your timeline suggests.

What to verify

To use DocketMath effectively for New Hampshire (US-NH), verify these items before relying on any calculator output.

The governing rule or statute for the jurisdiction.
Any local rule overrides or administrative guidance.
Effective dates and whether amendments apply.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

1) Confirm you’re using the correct default SOL rule

General SOL period: 3 years
General statute: RSA 508:4
Source overview: https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai

In other words, if you don’t locate a different statute covering the specific claim category, RSA 508:4 is the starting point for the SOL analysis.

2) Identify the “clock start” date you will enter

You’ll generally need to choose the date that best represents when the claim accrued in your situation. Depending on the facts (and what the applicable law ties to), that might be:

Incident/event date
Accrual date (if later due to accrual mechanics)
Discovery-related date (only if a governing statute makes accrual depend on discovery)

If you select the wrong start date, the expiration date can shift dramatically, because the SOL deadline is measured forward from the selected clock start.

3) Check for tolling or pause periods

SOL outcomes can change if any statutory tolling applies. While tolling isn’t always automatic, you should verify whether any statute in your fact pattern pauses the SOL, such as due to a qualifying status or pending legal circumstances.

If your situation involves possible tolling, gather the tolling trigger dates so you can enter them consistently in DocketMath.

4) Make sure the calculator output matches your procedural goal

DocketMath’s SOL expiration date is a timing benchmark—not a full case strategy. Also, if you’re evaluating more than one claim theory, run the calculator separately for each claim because different theories can point to different statutes (even when the baseline is the same).

5) Treat the result as an estimate, not legal advice

This is not legal advice. Use DocketMath’s statute-of-limitations output as a deadline estimate, and then verify:

whether RSA 508:4 truly governs your situation, and
whether a more specific SOL statute applies to your exact claim.

Warning: If a claim-specific SOL statute exists for your fact pattern and you rely only on the 3-year default in RSA 508:4, you could end up using an incorrect expiration date in decision-making.