Worked example: Wage Backpay in New Hampshire

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

This worked example shows how DocketMath calculates wage backpay for a New Hampshire (US-NH) matter using jurisdiction-aware rules based on the state’s general statute of limitations.

Facts used in this example

Assume an employee alleges they were underpaid and seeks back wages covering a specific lookback window.

Jurisdiction-aware limitations rule used (RSA 508:4)

For this example, DocketMath applies New Hampshire’s general statute of limitations for civil actions:

• General SOL period: 3 years
• General statute: RSA 508:4
  (Source: https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai)

No claim-type-specific sub-rule was found for wage backpay in this dataset. That means the default/general period (3 years under RSA 508:4) is used as the governing limitation window for the backpay calculation.

Pitfall / practical note: If your wage claim is governed by a different limitation rule (for example, a statute that expressly sets a shorter or longer deadline), the backpay lookback window could change. In this worked example, the calculation uses RSA 508:4 (3 years) because no more specific wage-backpay rule is provided here.

Example run

Below is the step-by-step logic DocketMath uses for this scenario: (1) establish the limitations lookback window using RSA 508:4, then (2) compute backpay using hours and underpayment per hour within that allowed window.

Run the Wage Backpay 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 SOL lookback period

• Filing date: June 1, 2026
• General SOL: 3 years
• Lookback start date: June 1, 2023

So, DocketMath limits recoverable backpay to wages accruing on or after June 1, 2023 (the “3-year window”), even though the alleged underpayment spans from March 1, 2023 to May 31, 2026.

Step 2: Determine how many pay periods fall inside the window

We assume biweekly pay periods (26 per year). For a practical worked example, we use clean math consistent with the “3 years ≈ 78 biweekly periods” framing.

• Allowed window: June 1, 2023 through May 31, 2026
• Pay periods: 3 × 26 = 78

Pay periods included: 78

Step 3: Compute total underpaid hours

• Hours per pay period: 80
• Pay periods: 78

Total hours within window:

• 80 × 78 = 6,240 hours

Step 4: Compute backpay based on hourly underpayment

• Underpayment per hour: $4.50

Backpay:

• 6,240 × $4.50 = $28,080.00

Step 5: How this maps to the DocketMath calculator

If you’re running this in DocketMath (tool name: DocketMath), your inputs will typically include things like:

• Filing date (drives the RSA 508:4 lookback)
• Alleged underpayment period start/end
• Hours per pay period
• Pay frequency (biweekly = 26/year)
• Underpayment per hour (or wage differential)

Then the tool applies RSA 508:4’s 3-year limitation to determine the recoverable portion.

To run it directly, use the primary CTA: /tools/wage-backpay.

Disclaimer (gentle): This is a math walkthrough using the general 3-year rule (RSA 508:4) and simplified assumptions. It does not determine whether the underlying wage claim is otherwise legally established.

Sensitivity check

Small changes can materially affect backpay outcomes because the limitation window determines how many pay periods are included. Here are three sensitivity scenarios showing how the result changes.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity A: Move the filing date later by ~60 days

Assume only the filing date changes:

• Filing date becomes August 1, 2026 (instead of June 1, 2026)

Lookback shifts forward, so fewer earlier pay periods fall inside the allowed window.

Approximate effect:

• ~2 months ≈ 4–5 biweekly pay periods
• For simplicity in this example: 4 fewer pay periods

Revised pay periods:

• 78 → 74

Revised estimate:

• Hours: 80 × 74 = 5,920
• Backpay: 5,920 × $4.50 = $26,640.00

Change: $28,080.00 → $26,640.00 (about -$1,440)

Sensitivity B: Increase underpayment per hour

Keep the same filing date (June 1, 2026) and pay-period assumptions, but increase the wage differential:

• Underpayment per hour increases from $4.50 → $6.00

Backpay scales linearly (hours in-window unchanged):

• Backpay: 6,240 × $6.00 = $37,440.00

Change: $28,080.00 → $37,440.00 (about +$9,360)

Sensitivity C: Alleged underpayment starts earlier, but SOL still controls

Assume the alleged underpayment start date moves earlier:

• Alleged underpayment start: January 1, 2023 (instead of March 1, 2023)

Even though the timeline expands, RSA 508:4’s 3-year window still caps recoverable wages. The lookback start remains June 1, 2023 for a June 1, 2026 filing.

Result in this example: included periods stay ~78, so the backpay total stays the same:

• 6,240 hours → $28,080.00

Summary table of estimated outcomes

Related reading

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