Why statute of limitations results differ in New Hampshire

The top 5 reasons results differ

DocketMath’s statute-of-limitations calculator uses New Hampshire’s general/default rule for civil actions. In New Hampshire, the default civil statute of limitations is 3 years under RSA 508:4. As noted in your prompt, no claim-type-specific sub-rule was found for this diagnostic—so the calculator baseline is RSA 508:4’s general 3-year period.

If your DocketMath result doesn’t match another tool, prior worksheet, or filing deadline you saw elsewhere, it’s usually because of one of these assumption mismatches:

1. The other source used a claim-specific limitations period

   • If the other system hard-coded a different (claim-type-specific) deadline, its output will diverge even if the general rule is 3 years under RSA 508:4.
   • For this diagnostic, stick to the general/default 3-year baseline unless you have a clearly documented claim-type rule.

2. Different “start” (trigger) dates were used

   • Many calculators change the outcome based on which date is treated as the start, such as:

     • date of incident,
     • date of discovery,
     • date of last payment,
     • or another triggering event.
   • Switching the start date by days/weeks/months can flip whether an action is “still timely” vs. “expired.”

3. Different meanings of “commencement” vs. “filing”

   • Even when the statute text is the same, tools may use different procedural dates as the relevant comparison point (for example):

     • date the court receives the case,
     • date the case is filed,
     • or a mailing-related assumption.
   • If one tool compares the deadline to one date and the other tool compares it to another, results won’t match.

4. **Deadline counting conventions (including time zone / end-of-day)

   • Some systems effectively treat the deadline as ending at midnight in a specific time zone, while others may use local time, rounding, or “end-of-day” conventions differently.
   • Near a boundary date, a 1-day discrepancy can change the computed “last timely day.”

5. **Tolling or exceptions being applied (even if not actually triggered)

   • Some tools include automated logic for tolling, exceptions, or “paused clock” concepts.
   • If DocketMath is using the default general rule (RSA 508:4, 3 years) and the other tool applies a tolling concept, the output will differ.

Gentle caution: This is a diagnostic for mismatched assumptions, not legal advice. If you need advice about a specific claim, consult a licensed New Hampshire attorney.

How to isolate the variable

Use DocketMath as a controlled baseline for New Hampshire (US-NH) and change only one factor at a time until the discrepancy disappears.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Step-by-step isolation checklist

• DocketMath should be using RSA 508:4: 3 years (general/default).

  • Because no claim-type-specific sub-rule was identified for this diagnostic, do not mix in claim-specific periods unless you have a cited rule to justify it.

  • What start date did each tool use?

  • What end/deadline date did it compute?

  • How did it treat the last day (counting/rounding convention)?

  • If the other result appears “longer” or “shorter,” check whether it used a discovery-based or alternative trigger date.

  • If you can’t confirm a claim-specific rule, align both calculations to the general/default 3-year timeline.

  • Identify whether the other tool’s “commencement” is based on:

    • filing date,
    • receipt date,
    • or mailing assumptions.

  • Then mirror that convention in your comparison.

  • Re-enter the same dates in DocketMath using the same calendar-day format (e.g., avoid accidental swaps like MM/DD/YYYY vs. YYYY-MM-DD).

  • If the disagreement is within 1–2 days, strongly suspect end-of-day/time-zone or rounding conventions.

Quick comparison table (fill in what you find)

Next steps

After you identify the mismatch, align the assumptions rather than “forcing” the statute to change:

1. **Lock to the default general period (RSA 508:4)

   • For this diagnostic, the correct baseline is 3 years under RSA 508:4.
   • Since no claim-specific sub-rule was found in the setup, your comparison should remain on the general/default rule.

2. Re-run the diagnostic changing one input at a time

   • Adjust only the start date first, then only the filing/commencement date, then only the date-convention assumptions.

3. Document the exact assumption that explains the divergence

   • If the other system states it uses tolling or a claim-specific limitations period, that’s typically the root cause.
   • If both are using RSA 508:4 generally, the discrepancy is usually date selection or commencement/deadline counting conventions.

4. Use DocketMath as your consistency check

   • The goal is not to “beat” another tool—it’s to ensure the same rule and the same date assumptions produce comparable results.

Ready to run the diagnostic? Use DocketMath’s calculator here: /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