Worked example: Wage Backpay in Idaho

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

Below is a worked example for wage backpay in Idaho using DocketMath with Idaho’s jurisdiction-aware rules. This is a practical walkthrough of how the calculator applies Idaho’s general statute of limitations (SOL) to determine how far back wage recovery can reach.

Scenario (facts you’d enter into DocketMath)

Assume:

• Pay start date for the dispute: June 1, 2023
• Pay end date for the dispute: December 31, 2023
• Date you filed (or would file) the claim: June 15, 2025
• Regular wage rate: $20.00/hour
• Hours missed (per week): 20
• Bonus/other wage component: none
• Work pattern: steady weekly missed hours throughout the covered period
• Pre-judgment interest: excluded for this example (so the number shown focuses on the backpay base)

Gentle note: This is a simplified illustration to show how the SOL clipping works. It’s not legal advice, and real cases can involve additional issues (e.g., different wage components, rate changes, or other doctrines).

Jurisdiction-aware rule used (Idaho)

For this example, DocketMath uses Idaho’s general/default SOL period because no claim-type-specific limitations sub-rule was found for the wage backpay rule set used by this tool run.

• General SOL period: 2 years
• Statute: Idaho Code § 19-403
• Source: https://law.justia.com/codes/idaho/title-36/chapter-14/section-36-1406/?utm_source=openai

Because there is no separate claim-type-specific sub-rule identified here, the calculator applies the general 2-year default period. That means the “lookback window” is anchored to the filing date and does not automatically shorten or extend based on a specialized wage claim category.

Reminder: We’re using the calculator’s general/default SOL for this worked example specifically because the wage backpay rule set did not surface a separate claim-type-specific limitations rule.

Primary calculator link: /tools/wage-backpay

Example run

This is how DocketMath would compute the backpay “base” after applying the SOL lookback.

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: Determine the SOL lookback window

With a filing date of June 15, 2025 and a 2-year general SOL under Idaho Code § 19-403, the earliest recoverable date is:

• June 15, 2023 (beginning of the 2-year lookback)

So any missed wages before June 15, 2023 are outside the recovery window for this default calculation.

Step 2: Clip the backpay period to the SOL window

Your dispute period runs from:

• June 1, 2023 → December 31, 2023

But the SOL window begins June 15, 2023, so the recoverable period becomes:

• June 15, 2023 → December 31, 2023

Step 3: Compute total missed hours within the recoverable period

You stated a steady pattern of 20 hours/week.

For a worked “by-hand” estimate, it’s common to approximate the number of weeks between the clipped dates and then prorate. In this illustration:

• June 15, 2023 to Dec 31, 2023 ≈ 28.5 weeks
• Total missed hours ≈ 28.5 × 20 = 570 hours

In the actual calculator run, DocketMath typically handles the exact fraction based on the input dates (and the tool’s date-to-day mapping). The calculator is the source of truth for the proration.

Step 4: Convert hours to wages

• Hourly wage: $20.00
• Backpay base: 570 hours × $20.00/hour = $11,400

Output (backpay base)

Estimated wage backpay base (SOL-adjusted): $11,400

To compute the precise prorated amount using your exact dates and hours structure, run the model here: /tools/wage-backpay.

Sensitivity check

Wage backpay totals move quickly with two inputs: (1) the filing date (because it changes the SOL lookback window) and (2) the weekly missed hours / wage rate (because they scale the backpay base).

To make that concrete, here are three sensitivity checks showing how outputs change.

1) Filing date moves the SOL window (big effect)

Hold everything constant (same dispute dates and wage facts), but change the filing date. Because the calculator uses a fixed 2-year lookback under Idaho Code § 19-403, moving the filing date shifts which portion of the dispute period is “in-window.”

Why it matters: with a 2-year lookback anchored to the filing date, even a month shift can change recoverable time significantly. As a rough order-of-magnitude example:
$20/hour × ~80 hours/month ≈ $1,600 of potential swing depending on how many days fall inside the window.

Pitfall to avoid: Don’t compute totals from the full dispute span without clipping to the SOL window. In this example, including June 1–June 14, 2023 would overstate recovery under the default 2-year lookback.

2) Weekly missed hours scales linearly (predictable effect)

Keep dates the same and adjust hours.

• Original: 20 hours/week → ~570 hours → $11,400
• If hours were 18 hours/week:

  • Hours ≈ 28.5 × 18 = 513 hours
  • Backpay ≈ 513 × $20 = $10,260
• If hours were 22 hours/week:

  • Hours ≈ 28.5 × 22 = 627 hours
  • Backpay ≈ 627 × $20 = $12,540

Checklist for data quality:

3) Hourly wage changes scale linearly (easy to test)

Because this example uses a single wage rate:

• At $19/hour: $11,400 × (19/20) = $10,830
• At $21/hour: $11,400 × (21/20) = $11,970

If your facts include rate changes (raises, different roles, overtime/shift premium rules), DocketMath can be run using segmented assumptions (when supported by the tool inputs). A single-rate model may understate or overstate results.

Related reading

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