How to calculate deadlines in New Hampshire

Quick takeaways

Run this scenario in DocketMath using the Deadline calculator.

• New Hampshire general civil statute of limitations is 3 years under RSA 508:4 for the default case type (no claim-type-specific carve-out identified here).
• Deadlines typically depend on two things: (1) when the claim accrued and (2) which “trigger date” you use for accrual.
• In DocketMath’s Deadline calculator (/tools/deadline), you’ll usually provide an accrual/trigger date and the limitations period (3 years); the tool returns a latest filing date.
• New Hampshire date results can be affected by anniversary-date calendar handling (e.g., weekends/holidays), depending on your workflow’s filing-day convention.
• This post covers general/default SOL math only—it does not include claim-type-specific exceptions because none were identified in the provided jurisdiction data.

Inputs you need

Before you calculate anything in DocketMath, collect the facts needed to define your date range precisely. For New Hampshire’s general/default limitation period:

Use this intake checklist as your baseline for Deadline work in New Hampshire.

• trigger event date
• rule set (civil/criminal or local rule)
• court level or venue
• service method
• holiday/weekend calendar
• time zone and filing cutoffs

If any of these inputs are uncertain, document the assumption before you run the tool.

Required inputs for the general 3-year calculation (RSA 508:4)

• Jurisdiction: New Hampshire (US-NH)
• Statute of limitations period: 3 years (general/default)
• Accrual / trigger date: the date the claim “starts running” under your circumstances

Optional inputs that can refine the calendar result (use if your workflow needs it)

• Time zone / local calendar: helps keep “midnight” assumptions consistent with your internal records.
• Business-day vs. calendar-day convention: whether you treat weekends/holidays as valid filing days.
• “Clock starts” rule confirmation: whether your accrual date is the event date, discovery date, or another fact-specific trigger.

What not assumed here

• No claim-type-specific sub-rule was found in the provided data, so the calculator is using the default/general period from RSA 508:4.
• If a different SOL applies to your claim category (or if tolling/other exceptions apply), you may need a different rule set.

How the calculation works

DocketMath’s Deadline calculator (/tools/deadline) supports a straightforward workflow for the general/default SOL calculation:

1. Start with the accrual/trigger date
   This is the date when the limitations period begins to run.

2. Add the general limitation period: 3 years
   Under RSA 508:4, the general civil statute of limitations period is three (3) years for the default situation described in your provided jurisdiction data.

3. Set the “latest filing date” to the end of the 3-year window
   Practically, you calculate the anniversary of the trigger date after 3 years and treat that as the deadline’s endpoint, subject to your chosen filing-day convention (especially if the last day lands on a weekend/holiday).

A concrete example (general/default math)

Assume:

• Accrual/trigger date: March 15, 2023
• SOL: 3 years (RSA 508:4 general/default)

Calculation:

• Add 3 years → March 15, 2026
• That date is your latest filing date for the general/default SOL math, subject to how your system handles a weekend/holiday.

How outputs change when inputs change

With a fixed 3-year period, shifting the trigger date shifts the deadline by the same calendar amount. For example:

Key takeaway: With a 3-year SOL, the deadline is anchored to the month/day anniversary—but your “final filing day” may still vary by calendar convention (calendar vs. business-day handling).

Where “anniversary” math can surprise people

Even with clean inputs, the “last day” determination can feel tricky. Common surprises include:

• If the computed anniversary falls on a weekend, the practical last filing day may shift depending on filing rules.
• If your workflow uses calendar-day assumptions vs. business-day assumptions, the final recorded date could differ by about a day (or more, if holidays apply).

DocketMath’s Deadline calculator is designed to help you keep those conventions consistent—so apply the same rule every time you calculate and record what you used.

Common pitfalls

The following issues most often break deadline calculations for New Hampshire SOL work—even when the statute period itself is correct.

• counting from the wrong triggering event
• ignoring court-closed days or holiday rules
• mixing calendar days with court days
• missing time-of-day cutoffs for filing

1) Using the wrong period (claim-type mismatch)

You were given general/default SOL period: 3 years under RSA 508:4. That’s the right default only when no claim-type-specific rule applies.

• Pitfall pattern: assuming all claims are automatically governed by the general 3-year rule without checking whether a different SOL or special accrual rule applies.

Checklist:

2) Confusing the event date with the accrual/trigger date

Deadlines fail when the wrong date is treated as “clock start.”

• Pitfall pattern: using the date of an incident as the trigger even when the correct “clock start” is later under the governing accrual rule for that claim type.

Checklist:

3) Forgetting “last day” calendar handling

A correct anniversary date can still produce an incorrect practical filing date.

• Pitfall pattern: recording the raw anniversary date without considering weekend/holiday handling.

Checklist:

4) Ignoring operational timelines (filing and service buffers)

Even if the SOL deadline math is correct, the action might still need to occur earlier operationally due to:

• drafting time
• service/filing logistics
• internal review buffers

Checklist:

Sources and references

• RSA 508:4 — New Hampshire general statute of limitations for civil actions (3 years)
  https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai

Sources note:

• Provided jurisdiction data indicates a general/default SOL period of 3 years and references RSA 508:4.
• No claim-type-specific sub-rule was found in the provided data for this post, so the calculations shown apply to the general/default rule only.
• TODO: If you can share your claim category (e.g., contract vs. tort vs. statutory claim), update the rule set and verify any exceptions or alternative accrual rules that may apply.

Next steps

1. Open DocketMath’s Deadline calculator: /tools/deadline
2. Enter:

   • Jurisdiction: US-NH
   • SOL period: 3 years (general/default)
   • Trigger/accrual date: your defined start date
3. Review the output:

   • Record the computed latest filing date
   • Document your trigger date and your calendar convention (calendar-day vs business-day)
4. Sanity-check with your internal deadline ledger:

   • Add a line such as: “SOL (RSA 508:4 general/default): latest filing = ___”
5. If exceptions may apply:

   • Re-check eligibility for the general/default period and adjust the rule set once identified, then re-run the calculation in DocketMath

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