Spreadsheet checks before running small claims fees and limits in New Hampshire

What the checker catches

If your small-claims spreadsheet is off by even one row—or if a fee/limit input is mapped to the wrong column—you can end up with a filing amount that doesn’t match New Hampshire’s rules. DocketMath’s small-claims-fee-limit checker is designed to catch the kinds of errors that typically slip into spreadsheets before you run numbers.

Here are the specific problems a good pre-flight check is meant to detect:

• Wrong statute period assumption

  • For New Hampshire civil actions generally, the general statute of limitations is 3 years under RSA 508:4.
  • The key spreadsheet risk: someone may accidentally bake in a different timeline (for example, 1 year or 5 years) while calculating whether something is timely.
  • Important: no claim-type-specific sub-rule was found in the materials provided for this checker, so RSA 508:4 is treated as the default/general period (not a claim-specific rule). If your situation involves a different, claim-specific limitation period, this tool’s default baseline may not match.

• Date math mistakes

  • Common spreadsheet issues include:

    • Using “days between” instead of “years” (or converting inconsistently) and rounding incorrectly.
    • Converting dates to text, which can break comparisons and YEAR/TIME logic.
    • Off-by-one errors when comparing “filed date” vs. “event date.”

• Fee/limit column mismatches

  • The checker can validate that your numeric inputs align with the right labels (for example: principal vs. interest vs. costs).
  • It also helps catch cases where a spreadsheet cell containing 1,000 is stored as text like "1,000", which can cause the checker to misread totals.

• Incorrect totalization logic

  • A frequent error: totals double-counting or excluding a component (e.g., adding both “principal” and “requested damages” that already include principal).
  • Another: interest calculated twice—once in a line item and again in a summary formula.

• Hidden formatting issues

  • Negative numbers shown with parentheses (which some parsers interpret differently).
  • Currency symbols embedded into cells (like $1,200 rather than a numeric value).
  • Mixed units (dollars vs. cents) across rows.

To ground the checker in a New Hampshire baseline: the general limitations period is 3 years under RSA 508:4 (the default/general rule). Your spreadsheet should reflect that default unless you’re intentionally applying a different, claim-specific rule (which isn’t included in the generic assumptions described here).

When to run it

Run the checker before you finalize either of these:

• The amount inputs you plan to submit in a small-claims packet
• The date-based computations that determine whether the claim falls within the default 3-year general statute under RSA 508:4

A practical workflow that reduces rework:

1. Build the spreadsheet first, but don’t trust it yet

   • Enter raw inputs (event date, filing date, principal/requested amount components).
   • Avoid hand-editing computed totals.

2. Run the sanity check immediately after you finish formulas

   • This catches mapping errors early (wrong column references, missing rows, formula drift).
   • It also detects obvious unit/format problems before they propagate into downstream totals.

3. Re-run after every structural change

   • Adding new rows/columns, changing headers, or copying formulas into new sections can quietly break references.

4. Lock the worksheet version you used

   • Save a copy with a timestamp (e.g., “NH small claims fee/limit check — 2026-04-15”).

If your spreadsheet includes a limitations/timeliness section, ensure the default is explicitly the 3-year general period from RSA 508:4 (not a claim-type-specific rule). That aligns the checker’s baseline assumptions with the general rule referenced here.

Gentle disclaimer: this is a spreadsheet sanity check, not legal advice. If your matter may involve exceptions or claim-specific timing rules, consider reviewing the details with a qualified professional.

Try the checker

You can test your workflow directly with DocketMath’s small-claims-fee-limit tool.

Primary CTA: /tools/small-claims-fee-limit

Before you press any “calculate” or “run” button in the tool, do a quick checklist to prepare your spreadsheet data. This helps the checker focus on substantive issues rather than formatting problems.

Spreadsheet pre-check checklist (fast)

What to expect from the checker output

Most checkers follow a pattern: they report either status or warnings. Use those results to decide whether to correct inputs or revise formulas.

A typical output interpretation strategy:

• If you see a “date outside default period” message

  • Re-check: event date, filing date, and how you compute the time gap.
  • Confirm the baseline assumption is the general 3-year default under RSA 508:4.
• If you see a “total mismatch” warning

  • Verify summation ranges and whether any component is included twice.
• If you see “non-numeric input” or “unparseable value”

  • Convert the cell to a number and remove formatting artifacts (quotes, commas-as-text, currency symbols).

A quick example of how errors show up

Note: this page is about sanity-checking spreadsheets—not about legal strategy. While RSA 508:4 provides the general/default 3-year period, some situations may involve nuances not covered by the default baseline used here.

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
• Small Claims Fee & Limit Calculator Guide for Alabama