Wage Backpay rule lens: New Hampshire

The rule in plain language

Run this scenario in DocketMath using the Wage Backpay calculator.

New Hampshire’s wage backpay timelines generally rely on the state’s general civil statute of limitations. Under RSA 508:4, many civil actions—including claims that seek unpaid wages and related backpay—are generally subject to a 3-year limitations period.

DocketMath uses jurisdiction-aware rules, so for New Hampshire (US-NH) the default rule lens is:

• General SOL period: 3 years
• Governing statute: RSA 508:4
• What this means practically: you generally count back 3 years from the relevant “trigger” date DocketMath uses for the wage-backpay calculation (typically tied to when pay became due or when the wage dispute accrued under the wage/backpay theory you’re modeling).

No claim-type-specific sub-rule found (default applies)

This lens uses the general/default period because no claim-type-specific sub-rule was found in the provided jurisdiction data for wage backpay. In other words: unless another more specific limitations rule clearly applies, the RSA 508:4 three-year period is the baseline.

Why it matters for calculations

Backpay calculations aren’t only about figuring out what wages were earned—they’re also about how much of that amount falls inside the limitations window. With a 3-year rule, the limitations period often becomes the boundary that determines the maximum recoverable portion of the wage-backpay total (for the portion treated as timely in the limitations lens).

Here’s how the 3-year lens affects outcomes in real calculations:

1) The limitations window sets a “lookback start” date

If you’re calculating backpay as of a specific evaluation date, the 3-year SOL typically creates a window like:

• Lookback period: the most recent 36 months
• Boundary: wages that became due outside that window may be excluded from the backpay total modeled under a limitations-based approach

2) Earlier problems usually reduce “recoverable” historical amount

If the wage issue started 4–5 years ago, only the most recent 3 years may be included under the general lens. Even if your underlying wage facts (hourly rate, hours, etc.) are unchanged, the limitations window can materially reduce the computed backpay.

3) The rule changes totals without changing the underlying wage facts

Your inputs—such as hourly rate and hours per week—can remain the same, but the output changes when the window shifts. For example:

• Same rate and same hours
• Different SOL lookback dates
• Different number of weeks/months counted
• Different total wage-backpay output

4) Date inputs are usually the biggest lever

Because this is a 3-year general rule under RSA 508:4, the most common calculation sensitivity is tied to dates, especially:

• the evaluation/claim date
• the date wages became due
• the accrual approach used in the model (i.e., how you treat when wages/backpay began to accrue)

Even a small change in date inputs can shift the window and move the computed total quickly.

Use the calculator

Use DocketMath’s wage-backpay calculator to apply the New Hampshire default 3-year limitations lens (RSA 508:4) to your scenario.

Start at: /tools/wage-backpay

Here’s a practical checklist of what you’ll typically enter and how the output changes:

Inputs to model (and what they affect)

• Jurisdiction: New Hampshire (US-NH)
• Hourly wage (or salary conversion): determines the earnings rate per time unit
• Hours worked per week (or per pay period): determines total earnings per week/period
• Evaluation date (the “as of” date): determines the end of the SOL lookback window
• Start/trigger approach: determines when the wage due date begins accruing in the model

  • Because the provided data establishes only the general 3-year rule, DocketMath will rely on the default limitations framework, while you supply the accrual/trigger logic for your scenario.

What the output usually represents in this lens

DocketMath will generally compute:

• Total wage-backpay in the limitations window (i.e., the portion counted within the 3-year lookback modeled under RSA 508:4)
• Time-based exclusion boundary (implicitly, through limiting the time period counted)

Quick “what if” scenarios (how results shift)

• If you move the evaluation date forward by 1 month: the 3-year lookback shifts, and you may add approximately ~4.3 weeks of additional modeled wages (depending on your pay schedule and how the trigger date is handled).
• If the hourly rate increases but the time window stays the same: output increases proportionally.
• If you change the trigger/accrual start date: you may shorten or lengthen the portion of time that lands inside the SOL window, changing totals even if the evaluation date stays constant.

Practical workflow (fast and consistent)

Sources and references

Start with the primary authority for New Hampshire and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Related reading

• Wage & Backpay Calculator Guide for Alabama
• Wage & Backpay Calculator Guide for Arizona
• Wage & Backpay Calculator Guide for Colorado