Deadlines rule lens: New Hampshire

The rule in plain language

Run this scenario in DocketMath using the Deadline calculator.

In New Hampshire, the default deadline to file many civil lawsuits is 3 years. This general rule comes from RSA 508:4.

The rule sets the starting point, the duration, and any exceptions that alter the calculation. It defines the logic DocketMath uses to translate inputs into outputs for New Hampshire.

The general (default) period

• General SOL period: 3 years
• General statute: RSA 508:4
• Where it shows up in practice: If a specific claim type doesn’t have its own dedicated limitations period, RSA 508:4’s general rule can be the starting point for the deadline calculation.

Key context for this article:

What “3 years” usually means in deadline calculations

A “3 years” rule typically means you count forward from a legally relevant start date—often the date the claim accrues. The exact start date can depend on the facts and accrual rules, so the most practical way to use this lens is as a timeline framework:

You usually need two dates:

1. a start date (the date you’re counting from), and
2. a deadline date (the last date to file, based on the 3-year window).

Then compare your expected filing date to that deadline.

Gentle disclaimer: This is an informational framework, not legal advice. Accrual timing, tolling, and any claim-type-specific statute (if it exists) can change the actual deadline.

Primary statute reference

• RSA 508:4 (General statute of limitations period) — described as a 3-year general statute of limitations for civil actions.
  Source used for this overview: https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai

Why it matters for calculations

Deadlines affect risk, planning, and settlement posture. Under New Hampshire’s default framework, a 3-year window can determine whether a case is filed in time or whether it’s potentially barred as untimely.

Here are the calculation issues this “3-year rule lens” most often impacts.

1) The deadline is driven by dates—not effort

Statutes of limitations are measured by time. That means small date mistakes can shift the deadline by the same amount:

• If your start date is off by weeks, the deadline shifts by weeks.
• If your filing date is misread (or delayed), you may cross the deadline without realizing it.

Before counting 3 years, confirm:

• the event/accrual date you’re using as the beginning of the count, and
• the date you plan to file (or the date you expect the complaint to be filed).

2) The “general rule” is not guaranteed for every claim type

A major trap is treating RSA 508:4 as automatically controlling every civil claim. The general rule is most useful when a claim type does not have a separate, claim-specific limitations period.

In other words:

• Use RSA 508:4 (general 3 years) as the default when no special timeline applies.
• Re-check whether a different statute (if applicable) could govern a narrower or different deadline.

This entry intentionally focuses on the general/default 3-year period because no claim-type-specific sub-rule was provided here.

3) You need a consistent method for adding time

“3 years” can be implemented in different ways depending on the calculator or counting convention (for example, how partial periods and “adding years” behave on the calendar). To reduce mistakes, use a single consistent method inside your workflow.

DocketMath’s deadline tool is designed for exactly this kind of consistent counting.

4) Practical decisions happen before filing

Even if you’re not ready to file right now, the deadline influences:

• when you must start evidence collection,
• whether you have time to negotiate,
• whether you should start drafting sooner,
• how much buffer you build into litigation planning.

A common operational approach is to work backward from the calculated deadline, rather than forward from the event.

Use the calculator

Use DocketMath (tool name: deadline) to translate the RSA 508:4 general 3-year period into a clear deadline date you can compare against your planned filing date.

Launch the tool: /tools/deadline

Run the Deadline calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

What to input (practical checklist)

To generate a deadline under the general/default 3-year rule, you typically enter:

• Start date (accrual/event date): the date you are counting from
• Duration: 3 years (the RSA 508:4 general SOL period)

If the tool asks about the counting method, select the method that matches your internal practice and stick with it across calculations.

How the output changes when inputs change

A simple “what-if” idea (illustrative only) is:

• Move the start date forward → the deadline moves forward.
• Move the start date backward → the deadline moves backward.

The exact computed dates depend on the tool’s calendar/date-counting approach, but the directional effect should be consistent.

How to compare against your filing date

After you calculate the SOL deadline date, compare it to:

• your planned filing date, and/or
• the date you expect the complaint to be filed.

A typical operational interpretation is:

• Filing on or before the deadline → you are within the general 3-year framework (subject to other legal factors not covered here).
• Filing after the deadline → the claim is more likely to fall outside the general 3-year period.

Quick workflow tip (buffer)

For project management, consider setting an internal “must-file” or “final review” date earlier than the SOL deadline—for example, 60 days before the calculated deadline—to absorb delays. The goal is to avoid last-minute scheduling surprises.

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Emergency deadline checklist for Canada — Emergency checklist and quick-reference inputs