How to run Wage Backpay in DocketMath for New Hampshire

6 min read

Published April 15, 2026 • By DocketMath Team

Step-by-step

Run this scenario in DocketMath using the Wage Backpay calculator.

This guide shows how to run Wage Backpay in DocketMath for New Hampshire (US-NH) using jurisdiction-aware settings. You’ll see which inputs matter most, what outputs to expect, and how the 3-year general statute of limitations applies.

Note: This walkthrough is about using DocketMath and understanding the built-in jurisdiction rules. It’s not legal advice, and it doesn’t replace advice from a qualified professional.

1) Open the Wage Backpay calculator (New Hampshire)

Start at the primary CTA: /tools/wage-backpay.

In DocketMath, set the jurisdiction as:

  • Jurisdiction code: US-NH

If the UI asks for jurisdiction explicitly, confirm it’s set to New Hampshire rather than relying on a default.

2) Confirm the limitations window used for New Hampshire

For New Hampshire, DocketMath uses the general/default civil statute of limitations period for this setup because no claim-type-specific sub-rule was found for this calculator feature.

Use this rule as the basis for the lookback window:

What that means in practice: DocketMath typically includes wages owed within the 3 years before the relevant “anchor” date the tool uses (for example, a filing date or another “as-of” date captured in the tool).

So, if your alleged unpaid work period goes back farther than 3 years from that anchor, the earlier portion is typically excluded from the final SOL-adjusted amount.

3) Enter your wage backpay inputs

Depending on the DocketMath wage-backpay layout, you’ll generally enter inputs such as the employee’s pay rate and the period of unpaid work to evaluate.

Use this checklist to fill fields accurately:

Provide either:

  • hours per week/day, and the number of weeks/days, or
  • a date range that the tool can convert to time periods (if supported)

Enter:

  • an hourly rate (common for non-exempt employees), or
  • a salary-to-hour conversion method if the tool supports it

Match your payroll frequency so DocketMath can compute totals on the correct basis (weekly, biweekly, semi-monthly, etc., if requested).

Choose the alleged unpaid period you want to evaluate. Then the calculator applies the 3-year lookback using the New Hampshire rule (RSA 508:4).

If DocketMath asks for a “filed on” date, “as of” date, or “relevant date,” enter it carefully. This date typically determines the 3-year SOL window, which limits which portions of your claimed period are included.

4) Run the calculation and review how outputs change

After you click Calculate / Run, review three output areas:

  1. Gross backpay total (before limitations filtering)
    This is the raw calculation across the full date range you input.

  2. SOL-adjusted backpay total (New Hampshire)
    This reflects the 3-year general SOL window under RSA 508:4.
    If your alleged unpaid period starts more than 3 years before the relevant anchor date, the earlier portion is typically excluded from the final included total.

  3. Included vs. excluded time
    Many wage backpay tools show how much of your claimed range falls outside the SOL window.
    Use this to confirm DocketMath is applying the 3-year general rule, not an unexpected alternative.

Quick example to sanity-check the math

If you enter a wage backpay period from January 1, 2019 through December 31, 2022, and your relevant anchor date is any date in 2022, a 3-year lookback would generally include dates starting in 2020 and exclude 2019.

In the outputs, you should generally see:

  • a larger gross total, and
  • a smaller SOL-adjusted total,
  • plus a visible indicator of excluded time (if your tool version provides a breakdown).

5) Use the breakdown for drafting-ready outputs

When DocketMath produces a breakdown, record the values you’ll likely need downstream:

Even if you’re not preparing filings, these details help you check assumptions and keep your internal record consistent with the tool’s logic.

Common pitfalls

New Hampshire wage backpay runs through a jurisdiction-aware limitations filter. The most frequent errors come from inputs that don’t line up with how a 3-year general rule (RSA 508:4) is applied.

Warning: A date field entered “almost right” can materially change the SOL-adjusted total because the tool typically filters the backpay period to a rolling 3-year window.

Common mistakes to avoid:

If the tool anchors the SOL window to a filing/as-of date, even a small shift can change which months/weeks are included.

For this DocketMath wage-backpay setup, no claim-type-specific sub-rule was found. The calculator uses the general/default 3-year period under RSA 508:4.

You can still enter an entire alleged span, but the gross total may not match the SOL-adjusted total. The earlier portion may be excluded based on the 3-year rule—this difference matters when interpreting results.

Typical mismatch: hourly vs. salary inputs, or the wrong pay frequency (weekly vs. biweekly). If DocketMath supports conversions, make sure your conversion basis matches how you actually track pay.

If the tool requires hours per week (or an equivalent field), be consistent with how you apply those hours across the entire date range.

Some users focus only on the final SOL-adjusted number. Reviewing the included/excluded breakdown helps catch data-entry mistakes faster.

Try it

Ready to run your first New Hampshire wage backpay calculation?

  1. Go to /tools/wage-backpay
  2. Set Jurisdiction code: US-NH
  3. Enter:
    • your wage/pay details (hourly rate or salary conversion),
    • the backpay date range you’re evaluating, and
    • the relevant anchor date the tool uses to apply the 3-year general SOL window.
  4. Click Calculate / Run.
  5. Compare:
    • gross backpay total vs.
    • SOL-adjusted backpay total
  6. Confirm the tool is applying:
    • the general 3-year period under RSA 508:4
    • and that no claim-type-specific sub-rule is being substituted (for this setup, none was found).

When you’re satisfied, save or export your results if DocketMath offers that option—especially the SOL-adjusted totals and the included/excluded timeline details.

If you want to double-check the limitations logic, validate the timeline against this anchor rule:

  • New Hampshire general civil SOL: 3 years (RSA 508:4)

Related reading