Worked example: Wage Backpay in Iowa

7 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

This worked example shows how DocketMath’s wage-backpay calculator can be used for Iowa (US-IA) using the general/default statute of limitations (SOL). Under Iowa law, the general SOL period is 2 years, found in Iowa Code § 614.1 (source: https://www.legis.iowa.gov/).

We’re using the general rule because no claim-type-specific sub-rule was found for this calculator run. In other words, this example assumes the calculator applies the default 2-year SOL and not a shorter or different SOL tied to a specific type of wage claim.

Before running any numbers, collect the inputs that drive wage backpay calculations:

  • Employment timeline
    • Last day worked (often the end date for backpay accrual)
    • Claim filing date (used to determine whether earlier weeks are within the SOL window)
    • Start date / anchor date (if needed for your pay-rate assumptions)
  • Pay structure
    • Hourly wage (or a daily/weekly equivalent)
    • Weekly scheduled hours (typical hours at the original job)
    • Pay frequency is not required if you supply wage loss and mitigation as hour/week totals, but it can help validate your assumptions
  • Backpay earnings mitigation
    • Whether you have reasonably equivalent earnings during the period (for example, wages from a new job)
    • Mitigation treatment: whether those earnings are treated as offsets against gross backpay (common approach in backpay calculations)
    • Mitigation hours and rate during the mitigation period
  • Jurisdiction
    • Use US-IA so the calculator applies Iowa’s general/default 2-year SOL from Iowa Code § 614.1.

Example scenario (numbers you can copy)

Assume the employee’s backpay period is determined as follows:

  • Last day worked: June 30, 2024
  • New earnings (mitigation): $18/hour for 20 hours/week beginning September 1, 2024
  • Weekly scheduled hours at the original job: 40 hours/week
  • Original hourly wage: $25/hour
  • Claim filing date: July 1, 2026

General SOL timing logic used in this example

Because Iowa’s general/default SOL is 2 years under Iowa Code § 614.1, the calculator uses the filing date to define the earliest potentially recoverable backpay date (subject to how the accrual window is defined in the inputs).

  • With a filing date of July 1, 2026, the SOL cutoff implies an earliest recoverable anchor around July 1, 2024 (24 months earlier).
  • You still need to enter the backpay start and end dates that match your fact pattern and the accrual dates you want the tool to compute over.

Note: This example uses Iowa’s general/default 2-year SOL under Iowa Code § 614.1 because no claim-type-specific sub-rule was identified for this calculator run.

Example run

You can run the calculation here: /tools/wage-backpay.

Enter inputs in DocketMath consistent with the scenario:

  1. Jurisdiction: US-IA
  2. General SOL period: DocketMath will apply 2 years consistent with Iowa Code § 614.1.
  3. Backpay start anchor (based on SOL and filing date):
    • Filing date: July 1, 2026
    • SOL period: 2 years
    • Earliest potentially recoverable date: July 1, 2024
  4. Backpay period end (based on the example facts you set):
    • Last day worked: June 30, 2024
    • For a concrete worked example, assume the computed backpay window for gross wage loss runs through a defined end date.
    • Set the backpay end date to December 31, 2024 for this example.

To keep the example concrete, split the timeline into two parts:

  • Gross wage loss window (before mitigation offsets): July 1, 2024 → August 31, 2024
  • Mitigation offsets window: September 1, 2024 → December 31, 2024

Calculating gross backpay (before mitigation)

Backpay period (gross wage loss): July 1, 2024 → August 31, 2024 (8 weeks)

  • Original job wage: $25/hour
  • Weekly hours: 40 hours/week
  • Weekly gross wage loss: 40 × $25 = $1,000/week
  • Gross backpay for 8 weeks: 8 × $1,000 = $8,000

Applying mitigation offsets (new wages)

Mitigation period: September 1, 2024 → December 31, 2024 (17 weeks in this example)

  • New job wages (mitigation):
    • $18/hour
    • 20 hours/week
  • Weekly mitigation earnings: 20 × $18 = $360/week
  • Weekly gross wage loss (same hours/rate comparison): $1,000/week
  • Net backpay after mitigation (weekly): $1,000 − $360 = $640/week
  • Net backpay for 17 weeks: 17 × $640 = $10,880

Total backpay estimate (within this example’s chosen accrual windows)

  • Gross (July–Aug 2024): $8,000
  • Net after mitigation (Sep–Dec 2024): $10,880
  • Estimated wage backpay total: $18,880

What DocketMath is doing conceptually in this run

  • It uses Iowa’s general 2-year SOL (Iowa Code § 614.1) to set an earliest recoverable date based on your claim filing date.
  • It then computes wage loss over the backpay window you specify.
  • Finally, it applies mitigation by offsetting (reducing) the wage loss using your mitigation earnings inputs.

Gentle note: This is a math walkthrough using assumed dates and offsets. It’s not legal advice, and real cases may involve additional factual or procedural details that affect the recoverable period.

Sensitivity check

Backpay outcomes can change quickly when you adjust dates or mitigation assumptions. Below are practical sensitivity checks you can run in DocketMath using the same Iowa setup (US-IA, Iowa Code § 614.1, general 2-year SOL).

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.

1) Filing date moves the SOL window

Because the SOL is anchored to the filing date, shifting that date changes the earliest potentially recoverable backpay anchor.

Try changing the claim filing date from your baseline (July 1, 2026) to:

  • Filing date: June 1, 2026 (earlier)
  • Filing date: August 1, 2026 (later)
  • Filing date: July 1, 2025 (earlier by a year)

Expected effect:

  • An earlier filing date generally expands the recoverable window backward (more weeks, higher total).
  • A later filing date generally narrows the recoverable window (fewer weeks, lower total).

2) Mitigation timing and level

Mitigation usually has a strong impact on net backpay because it offsets gross wage loss.

Try:

  • Mitigation start: August 15, 2024 instead of September 1, 2024
  • Mitigation start: September 15, 2024 instead of September 1, 2024
  • Mitigation hours: 10 hours/week instead of 20 hours/week

Expected effect:

  • Earlier mitigation start → more weeks offset → lower net backpay.
  • Later mitigation start → fewer offset weeks → higher net backpay.
  • Fewer mitigation hours → smaller offsets → higher net backpay.

3) Hours and rate assumptions

Even if mitigation stays the same, changing wage inputs changes both gross loss and (depending on how offsets are applied) net loss.

Try:

  • Original weekly hours: 40 → 35
  • Original hourly wage: $25 → $28
  • Mitigation rate: $18 → $20 (hours unchanged)

Expected effect:

  • Lower original hours typically reduces gross wage loss and net backpay.
  • Higher original wage can raise gross loss and may increase net backpay (even with mitigation offsets), depending on the offset mechanics.
  • Higher mitigation wages increase offsets and can reduce net backpay.

Warning: Keep your “accrual window” definition consistent with your underlying fact pattern. A one-week shift in start/end dates can materially change totals because weekly loss rates can be large.

Related reading