Worked example: small claims fees and limits in New Hampshire
7 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
This worked example walks through how DocketMath’s small-claims-fee-limit calculator can model New Hampshire small claims fee and jurisdiction limits using the statute of limitations baseline.
Jurisdiction: New Hampshire (US-NH)
Statute of limitations baseline used by this calculator:
- General SOL period: 3 years
- General statute: RSA 508:4
Important note (how the example chooses the SOL rule): The calculator uses the general/default limitation period because no claim-type-specific sub-rule was found in the available jurisdiction data. That means this example assumes RSA 508:4’s 3-year period without narrowing to a special category (for example, certain contract- or injury-specific time limits).
To make the example concrete, imagine a plaintiff filing a small claims case after an unpaid purchase.
Scenario facts (the “inputs”)
Use the inputs below as the basis for the run:
- Claim amount (principal): $900
- Filing date (day you plan to file): 2026-04-15
- Last transaction / accrual date (when the claim became due): 2023-04-14
- Requested relief includes: principal only (no separate special damages category added in the inputs)
- Late fees / interest included in claim amount: assumed $0 for simplicity (some people add interest; this example keeps the amount clean)
How these inputs typically affect fee + limit outputs
Even when you’re focused on “fees and limits,” the calculation often depends on two gating concepts:
Is the claim time-barred?
Using the general 3-year limitation from RSA 508:4, the tool can flag cases filed after the limit period.Is the claim amount within the small claims threshold?
Many small claims systems impose an amount cap for what can be heard in that track. The tool’s fee/limit model uses your claim amount to compute whether you’re inside the small claims lane and what that means for the expected filing cost structure.
DocketMath is built to make those linkages explicit rather than burying them in spreadsheets.
Example run
Let’s run the example with the inputs above.
Run the Small Claims Fee Limit calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Compute the age of the claim at filing
- Accrual date: 2023-04-14
- Filing date: 2026-04-15
- Time elapsed: 3 years + 1 day
Because the general limitation period is 3 years under RSA 508:4, a strict “3 years from accrual” model treats this as outside the limitation window.
Step 2: Apply the general SOL period (RSA 508:4)
- General SOL period: 3 years
- Result under the model: Time-barred (filed 1 day after the 3-year window)
Cautionary takeaway (not legal advice): This worked example illustrates how SOL timing can change the outcome. In many systems, a “1-day” difference is enough to flip a time-bar status.
Step 3: Evaluate small claims fee/limit implications with the claim amount
- Claim amount: $900
For this illustration, the tool checks whether your amount qualifies for the small-claims track (amount-based gating) and then combines that with the SOL timing result.
For this example:
- Assume the calculator’s amount threshold logic allows a $900 claim to sit in the small claims track if it is otherwise procedurally viable.
- Because the SOL flag is triggered, the tool’s output will typically reflect that the claim may be treated differently due to timing—even if the amount would otherwise fit.
What the calculator output would look like (conceptual)
While DocketMath’s exact fields depend on how the calculator is configured, a typical “worked example” output for small-claims-fee-limit includes:
- SOL status: time-barred vs. within limitation
- SOL cutoff date: the last date you could file under the modeled period
- Small claims limit status: within vs. outside the amount cap
- Estimated filing-fee treatment: derived from the track/limit eligibility state
Here’s a compact “readout-style” table consistent with the logic described above:
| Output category | Modeled value for this scenario |
|---|---|
| General SOL under RSA 508:4 | 3 years |
| Filing age at 2026-04-15 | 3 years + 1 day |
| Time-bar flag | Yes (outside 3 years) |
| Claim amount | $900 |
| Small claims amount eligibility | Likely within cap (amount-based) |
| Fee/limit combined status | Amount-eligible but SOL-problematic |
A quick calendar sanity check
The modeled SOL cutoff date under a clean “3 years from accrual” approach would be:
- Accrual: 2023-04-14
- Cutoff: 2026-04-14 (last day within 3 years)
- Filing on: 2026-04-15 → exceeds by 1 day
That cutoff date is the kind of detail you want visible before you spend time on filing steps.
Primary CTA (use the tool directly)
If you want to reproduce this result with your own dates and amount, go to DocketMath’s calculator:
Sensitivity check
Now change one input at a time and watch how the outputs flip. This is where worked examples become genuinely useful—especially when you’re deciding whether a case is “close enough” on timing or whether fees/limits could change.
Sensitivity 1: Move the filing date by 1 day earlier
Keep everything the same, but change:
- Filing date: 2026-04-14 (instead of 2026-04-15)
Expected effect under RSA 508:4 model (3 years):
- Claim age at filing: exactly 3 years
- Time-bar flag: No (within limitation window)
- Combined status: now timing is aligned, so amount/track eligibility would matter more
Checkbox-style summary:
- Claim amount stays: $900
- Accrual date stays: 2023-04-14
- Filing date changes: 2026-04-15 → 2026-04-14
- SOL status flips: time-barred → within limitation
Sensitivity 2: Keep the filing date, change the accrual date by 10 days
Assume the filing date remains 2026-04-15, but the last due date/trigger is later:
- Accrual date: 2023-04-24
- Filing date: 2026-04-15
Expected effect under the 3-year rule:
- Claim age at filing: approximately within 3 years
- Time-bar flag: No
- Combined status: amount/track eligibility matters more than timing
Sensitivity 3: Increase claim amount to test fee/limit gating (amount-driven)
Now keep dates fixed at the original scenario (accrual 2023-04-14, filing 2026-04-15), but increase principal:
- Claim amount: $1,500 (instead of $900)
Expected effect:
- SOL status: still time-barred (timing didn’t change)
- Small claims amount eligibility: could become “outside cap,” depending on the small claims threshold your jurisdiction uses
- Fee/limit treatment: could change even if SOL is already failing
This illustrates why you shouldn’t focus on only one variable:
- SOL can block the case regardless of amount.
- Amount can block placement even if timing is fine.
Small “cause-and-effect” matrix
| Change you make | SOL status (RSA 508:4 3-year baseline) | Amount/track status | Likely combined result |
|---|---|---|---|
| Filing date moves 1 day earlier | May flip | No change | Timing-driven flip |
| Accrual date moves later | May flip | No change | Timing-driven flip |
| Claim amount increases | No change | May change | Fee/limit gating flip (if any) |
| All inputs unchanged | Same | Same | Same outcome |
Related reading
- Small claims fees and limits in Rhode Island — Full how-to guide with jurisdiction-specific rules
- Small claims fees and limits in United States (Federal) — Full how-to guide with jurisdiction-specific rules
