Why small claims fees and limits results differ in New Hampshire

5 min read

Published April 15, 2026 • By DocketMath Team

The top 5 reasons results differ

Run this scenario in DocketMath using the Small Claims Fee Limit calculator.

If you ran the DocketMath “small-claims-fee-limit” calculator for New Hampshire (US-NH) and the small claims fee and small claims limit didn’t match what you expected, the mismatch usually comes from one of five predictable variables.

Below, I’ll connect each reason to a practical diagnostic step, using New Hampshire’s default civil statute of limitations rule as the foundation: RSA 508:4 sets a 3-year general statute of limitations for many civil actions. No claim-type-specific sub-rule was found for this brief, so treat this as the default/general period, not a guarantee for every claim category.

Warning: Fee/limit calculators often incorporate multiple filters (claim type, amount-in-controversy, procedural posture, and filing posture). A mismatch doesn’t necessarily mean your facts are wrong—sometimes the tool (or the form/workflow you’re comparing against) is using a different assumption.

1) You used the wrong “amount in controversy” number

Small claims limits and fee schedules typically track the dollar amount being sought (not the underlying transaction total). If you:

  • used the contract total instead of the amount demanded, or
  • included items you later removed (or forgot to remove), you can move the case above/below the threshold and see “different results” across tools or workflows.

2) You assumed a statute of limitations different from the default rule

For New Hampshire, the general civil statute of limitations is 3 years under RSA 508:4. The calculator output may assume the default applies, but your workflow might have used a different period based on how a claim is characterized elsewhere.

Default/general SOL baseline for this diagnostic:

3) You have a mismatch between filing type and the fee schedule the tool expects

Two common ways this happens:

  • mixing small claims procedure with a different civil track in your preparation, or
  • using a fee assumption meant for a non–small claims filing.

Even if the dispute “feels” small, the fee impact can change depending on the form you’re planning to file and what the system counts as the initiating claim.

4) Partial claims and amended demands change the limit comparison

If you:

  • filed/expected to file with a preliminary amount, then
  • later amended the demand, a limit calculation based on the later number can diverge from a fee calculation based on the earlier number (or vice versa).

5) Date math errors shift SOL or timing-based inputs

Small timing differences can alter outputs if a calculator does timing checks. Typical slips:

  • using the filing date instead of the triggering event date,
  • confusing receipt vs. demand dates, or
  • inconsistent calendar-day counting across your spreadsheet vs. the tool.

How to isolate the variable

Use this tight checklist to find the exact input that causes the divergence between fee and limit outputs in DocketMath.

  • Verify the number is the amount demanded (not the contract total, not “damages in theory”).
  • Keep amount constant; adjust only the date (or vice versa).
  • For this brief’s diagnostic scope, use the default/general 3-year period from RSA 508:4 as your baseline.
  • Decide which date your workflow treats as the trigger (e.g., breach occurrence, last performance, demand event).
  • Are you estimating for an initial filing under small claims handling, or for a later amended/different-track posture?

Quick diagnostic table

If your fee output changed but the limit output didn’t…Most likely variable
You changed a date/time inputSOL/timing assumption or trigger date
You changed a dollar number but not the trackAmount-in-controversy logic (requested vs. total)
You changed claim scope wording but totals stayed the sameForm/procedure mapping differences

Next steps

  1. Start with the DocketMath tool.
    Use: /tools/small-claims-fee-limit to re-run with your current inputs.

  2. Lock one variable and perturb the others one by one.

    • Keep the demanded amount constant.
    • Change only the SOL-related date you used (or the timing input).
    • Then change only the demanded amount.
  3. Anchor the timing baseline to RSA 508:4 (3 years).
    Since no claim-type-specific sub-rule was identified in this brief, treat 3 years as the general default for the diagnostic:

    • RSA 508:4 → 3-year general statute of limitations
  4. Document what changed between runs.
    Capture:

    • demanded amount used,
    • trigger date used,
    • filing posture assumption.
      This makes it much easier to tell whether the divergence is caused by inputs or by procedural mapping.

Pitfall: If you compare outputs from two different calculators—or two different versions of the same workflow—you may be comparing different assumptions, not different law.

Related reading