Closing Cost rule lens: New Hampshire

The rule in plain language

In New Hampshire, the general statute of limitations for most civil claims is 3 years, set by RSA 508:4. DocketMath’s “closing cost” rule lens starts with that baseline because, based on the jurisdiction data provided, no claim-type-specific sub-rule was found for this lens. That means we treat RSA 508:4 as the default period for the timeline assumption used in this calculator workflow.

Here’s the clean version to anchor your calculations:

• New Hampshire (US-NH) general SOL: 3 years
• Statutory basis: RSA 508:4
• How to think about it: If your closing-cost-related dispute is governed by the general civil limitations period, you typically count three years from the claim’s accrual date—the date the claim “accrues,” meaning when it could first be brought.

**Sources and references (jurisdiction baseline)

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

Why it matters for calculations

Closing cost issues aren’t only about dollars paid—they’re also about timing. A limitations deadline can determine whether closing-cost recovery is still available, which affects both:

• Whether amounts should be included in a recovery model, and
• How long you need to hold back or discount expectations while you’re assessing timeliness.

Using a 3-year general period can change the math in a few practical ways.

1) The “lookback” window

If you’re building a closing-cost estimate tied to a potential claim, a 3-year lookback is a common planning window under the general SOL assumption. In practical modeling terms:

• Closing-cost line items that fall outside the 3-year accrual-to-filing window may be treated as not recoverable (under this general-SOL assumption).
• Items within the window may remain included in the modeled recovery.

2) Accrual date drives everything

A frequent modeling error is using the wrong start date. Your inputs should reflect the best-supported accrual date—the point at which the issue could first be asserted.

Depending on the facts, that may be related to events such as when the closing occurred and when the alleged responsibility for the closing costs became known or knowable. The key is that your scenario should use the most defensible accrual date you have.

3) Settlement planning and scenario comparisons

Most people don’t stop at one assumption. You can compare scenarios like:

• “If the accrual date is the closing date, what’s the timely window?”
• “If accrual is later due to discovery/knowledge facts, how does the window shift?”

Even if you never file, modeling deadlines helps you understand whether you may need more information to support timeliness.

4) Timing assumptions can affect damages-like estimates

Even when you’re not giving legal advice, it’s still worth flagging that many “closing cost” models behave like economic calculations. For example, some workflows may treat delay as an economic factor. In those situations:

• A longer or shorter timeliness window changes when you treat cash outflows as potentially recoverable (under the modeled assumptions).
• That can change outputs in a way that feels like “more or less damages,” even before considering any other legal components.

Practical takeaway: In this DocketMath closing-cost lens, RSA 508:4’s 3-year baseline operates as a timing filter. It turns your date and amount inputs into a SOL-aware result structure.

Use the calculator

Use DocketMath’s closing-cost calculator to apply the US-NH general 3-year SOL (RSA 508:4) as the governing timeline assumption. Start with the primary CTA:

• Open DocketMath closing-cost rule lens: /tools/closing-cost

What to input (and why it changes the output)

In a typical closing-cost SOL-aware workflow, you’ll provide at least these timing and amount inputs (the calculator labels may vary slightly in the UI):

1. Jurisdiction: New Hampshire (US-NH)
2. Accrual date (or best estimate of when the claim began):

   • This determines when the 3-year clock starts under the general RSA 508:4 period.
3. Relevant date for the event you’re modeling:

   • Common examples include a filing date, demand date, or a “model as of” date.
4. Closing cost amounts (by line item if your workflow supports it):

   • These are the dollars you want evaluated as potentially included or excluded based on the SOL timing structure.

How the 3-year SOL interacts with the dollars

Think of the calculator output as sorting your closing-cost amounts into a SOL-aware structure:

• Within the 3-year window: potentially included
• Outside the 3-year window: potentially excluded (under the general-SOL assumption)

That’s why the date inputs matter as much as the dollar inputs.

Quick scenario walkthrough (illustrative numbers)

Assume you input:

• Accrual date: 2023-06-15
• “As of” date (or filing date): 2026-07-01
• Closing costs:

  • $12,500 incurred in 2023
  • $9,000 incurred in 2021

Under a general 3-year SOL (RSA 508:4):

• The 3-year window runs roughly from 2023-06-15 through 2026-06-15.
• Items tied to the facts occurring after 2026-06-15 would be outside the window.
• Items tied to 2021 would also be outside the window.

Your exact result depends on how the calculator maps each line item to a timing attribute, but the overall effect is consistent: dates determine inclusion/exclusion under the 3-year baseline.

Checkbox checklist for cleaner inputs

Before you run the calculator:

Related reading

• Average closing costs in Alabama — Rule summary with authoritative citations
• Average closing costs in Alaska — Rule summary with authoritative citations
• Average closing costs in Arizona — Rule summary with authoritative citations