Worked example: Wage Backpay in Wyoming

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

Below is a worked example of a wage backpay calculation in Wyoming using DocketMath (jurisdiction code US-WY) and the general/default wage backpay lookback period that applies when a claim-type-specific statute isn’t identified.

Backpay lookback / statute of limitations (Wyoming)

For this workflow, DocketMath uses the general SOL period of 4 years for the Wyoming default wage backpay lookback rule set, based on:

• Wyo. Stat. § 1-3-105(a)(iv)(C) (general/default period used here)
  Source: https://www.wyoleg.gov/

No claim-type-specific sub-rule was found for this example workflow, so this example applies the general period as the default. In practice, that means the calculation limits backpay to earnings that accrued within 4 years before the relevant trigger date used by the tool (typically the filing date or another date you set as the “as-of” cutoff inside the calculator workflow).

Example scenario (assumptions)

Assume an employee alleges they were not paid wages they were owed and seeks backpay for the relevant period.

Use these inputs:

Weekly earnings math (what we’re modeling)

• Weekly unpaid amount = $22.50 × 6.0 = $135.00
• Total backpay = weekly unpaid amount × weeks in window

DocketMath applies the same structure while deriving the time window using the Wyoming default lookback.

Example run

Now run the wage-backpay calculator conceptually with the inputs above under US-WY default SOL logic. (If you want to reproduce the calculation, start at /tools/wage-backpay.)

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 lookback window using Wyoming’s general period

• General SOL: 4 years
• Source: **Wyo. Stat. § 1-3-105(a)(iv)(C)
• Trigger date: 2026-03-15
• Lookback start: 2022-03-15

So the tool window is:

• from 2022-03-15 through 2026-03-15

Step 2: Convert the date range into weeks used for backpay

For a quick worked example, treat the backpay window as:

• 4 years ≈ 208 weeks (tool logic typically uses exact day-count and converts to a weekly basis consistent with the calculator’s method)

So:

• Weeks in window: 208

Step 3: Convert hourly rate and unpaid hours into dollars

Unpaid dollars per week:

• $22.50 × 6.0 = $135.00

Total backpay:

• $135.00 × 208 = $28,080.00

Step 4: Output (what In DocketMath, this appears as for backpay)

For this example, the estimated wage backpay result is:

• Estimated wage backpay (before any adjustments not covered here): $28,080.00
• Lookback window applied: 4-year general/default period (per Wyo. Stat. § 1-3-105(a)(iv)(C))

Warning (non-legal advice): This example focuses on a clean “rate × hours” wage backpay model. Real disputes can involve additional components (e.g., different wage rates by period, overtime premiums, shift differentials, commissions, or damages beyond unpaid wages). Make sure your entered inputs match the underlying wage facts.

Sensitivity check

Small changes in the inputs and assumptions can materially affect the backpay number. This section stress-tests the result while keeping the model structure the same.

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) Trigger date sensitivity (SOL cutoff drives the time window)

Keeping hourly rate and hours constant, change only the trigger date by about ±90 days.

What this means: wage backpay scales with the number of weeks included. Under the default 4-year rule from Wyo. Stat. § 1-3-105(a)(iv)(C), even modest date shifts can change the included period.

2) Hours sensitivity (weekly unpaid hours is a linear multiplier)

If unpaid hours per week are overstated or understated, backpay changes proportionally.

Baseline:

• Weekly unpaid hours: 6.0
• Hourly rate: $22.50
• Weekly unpaid: $22.50 × 6.0 = $135.00
• Backpay: $135.00 × 208 = $28,080.00

Alternative scenarios:

• Weekly unpaid hours = 5.5

  • Weekly unpaid = $22.50 × 5.5 = $123.75
  • Backpay = $123.75 × 208 = $25,740
• Weekly unpaid hours = 6.5

  • Weekly unpaid = $22.50 × 6.5 = $146.25
  • Backpay = $146.25 × 208 = $30,420

Rule of thumb:
Backpay ≈ (hourly rate × unpaid hours/week) × weeks in lookback window.

3) Rate sensitivity (rate changes are linear—but fact-dependent)

If the wage rate changed during the period, the model generally needs segmented time ranges (e.g., different hourly rates across sub-periods). To keep this sensitivity check simple, compare two constant-rate scenarios:

• If rate is $20.00 instead of $22.50:

  • Weekly unpaid = $20.00 × 6.0 = $120.00
  • Backpay = $120.00 × 208 = $24,960
• If rate is $25.00 instead of $22.50:

  • Weekly unpaid = $25.00 × 6.0 = $150.00
  • Backpay = $150.00 × 208 = $31,200

4) Jurisdiction rule sensitivity (why “default” matters)

This workflow uses the general/default 4-year lookback because no claim-type-specific sub-rule was identified for this example.

• If, in a real case, a different or claim-specific limitations rule applies, the lookback window could be shorter or longer.
• That difference changes the weeks included, which then linearly changes the backpay in this simplified model.

Quick checklist to validate your run

Before finalizing outputs, confirm these inputs match your facts:

If you want to reproduce or iterate the calculation with different dates/hours/rates, you can start here: /tools/wage-backpay.

Related reading

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