Worked example: Wage Backpay in Oklahoma

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

This worked example shows how DocketMath’s wage-backpay calculator can estimate wage backpay in Oklahoma (US-OK) using jurisdiction-aware rules for the statute of limitations (SOL).

Scenario snapshot (Oklahoma)

• Employer: Private company in Oklahoma
• Claim type: Wage backpay (no claim-type-specific SOL sub-rule was identified for this calculator run)
• Alleged underpayment period: 6 months
• Date the worker files: Today (used here as the filing date input)
• Hourly wage: $18.50
• Scheduled hours: 40 hours/week
• Weeks impacted: 26 weeks (≈ 6 months)
• Underpayment amount (shortfall): $6.00/hour

  • Example: worker was actually paid $12.50/hour, but should have been paid $18.50/hour (a $6.00/hour shortfall)

Jurisdiction-aware limitation used by DocketMath (US-OK)

For Oklahoma, DocketMath uses the general SOL period provided in the jurisdiction data:

• General SOL period: 1 years
• General statute citation: 22 O.S. § 152
• Source: https://www.findlaw.com/state/oklahoma-law/oklahoma-criminal-statute-of-limitations-laws.html

Important: The provided jurisdiction data indicates no claim-type-specific sub-rule was found. So DocketMath applies the general/default period (rather than a narrower, wage-theory-specific timeline).

Inputs you would enter in DocketMath (typical wage-backpay workflow)

Use these as the same “knobs” you’ll adjust in your own run:

• State / jurisdiction: US-OK
• Hourly wage shortfall (or underpayment rate): $6.00/hr
• Weekly hours: 40
• Impacted weeks: 26
• Filing date: today (for this example)
• Claim period start: 26 weeks before filing date
• SOL period (lookback constraint): 1 year (applies to limit the lookback window)

If your facts differ—such as wage rates changing over time—replace the $6.00/hr shortfall and/or re-scope the affected weeks to match your record.

Quick grounding: how SOL affects “how many weeks count”

In wage-backpay math, you’re typically doing “hours × rate,” but SOL can also limit how far back the calculator counts.

In this example:

• Alleged period = 26 weeks (about 6 months)
• SOL lookback window (general SOL) = 1 year ≈ 52 weeks

Because 26 ≤ 52, all 26 weeks should be included in the backpay total for this run.

Example run

Below is a step-by-step calculation that mirrors what DocketMath will be doing internally: (1) apply the relevant SOL lookback window under 22 O.S. § 152 using the general 1-year period, then (2) multiply the covered weeks by the weekly underpayment.

Step 1: Determine the covered weeks under Oklahoma’s general SOL

• General SOL used: 1 year
• Underpayment period length: 26 weeks
• Result: all 26 weeks are covered (because the full period is within the 1-year window)

Step 2: Compute weekly underpayment

• Weekly hours: 40
• Hourly shortfall: $6.00

Weekly underpayment:

• 40 × $6.00 = $240/week

Step 3: Compute total wage backpay over the covered weeks

• $240/week × 26 weeks = $6,240

Step 4: What the output should show (high-level)

In a typical DocketMath wage-backpay run, you’d expect a result consistent with:

• Estimated wage backpay (covered period): $6,240
• Covered period: full 26 weeks (since it falls within the general 1-year SOL)

Practical warning: If your real underpayment period spans longer than 1 year (for example, 18 months), older weeks can become excluded by the SOL constraint—changing the total even if your weekly underpayment stays the same.

Sensitivity check

Now adjust one variable at a time to see what most strongly affects the Oklahoma result in this setup: (1) how many weeks are covered under the SOL, and (2) the shortfall rate, with hours acting as a multiplier.

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.

A) Change the underpayment length (SOL impact)

Keep:

• Hourly shortfall = $6.00
• Weekly hours = 40
• Shortfall rate pattern = constant

Case A1: 6 months (baseline)

• Impacted weeks = 26
• Covered weeks = min(26, 52) = 26
• Backpay = 26 × (40 × $6.00) = $6,240

Case A2: 18 months

• Impacted weeks ≈ 78
• Covered weeks = min(78, 52) = 52 (SOL cuts off the rest)
• Backpay = 52 × (40 × $6.00) = 52 × $240 = $12,480

Takeaway: In this Oklahoma scenario, the SOL functions like a lookback cap: once you exceed ~52 weeks, extra weeks may stop contributing to the total.

B) Change the hourly shortfall (rate impact)

Keep:

• Underpayment period = **6 months (26 weeks)

• Weekly hours = 40

• Case B1: $6.00/hr → 26 × (40 × 6) = $6,240

• Case B2: $4.00/hr → 26 × (40 × 4) = $4,160

• Case B3: $8.00/hr → 26 × (40 × 8) = $8,320

Takeaway: With hours and covered weeks fixed, results scale linearly with the shortfall rate.

C) Change weekly hours (workload impact)

Keep:

• Covered weeks = 26

• Hourly shortfall = $6.00

• 30 hours/week: 26 × (30 × 6) = 26 × $180 = $4,680

• 40 hours/week: 26 × (40 × 6) = 26 × $240 = $6,240

• 50 hours/week: 26 × (50 × 6) = 26 × $300 = $7,800

Takeaway: Hours are another direct multiplier—small changes in reported hours can noticeably affect total backpay.

D) Claim-type-specific SOL note (what this example does and does not do)

This jurisdiction data explicitly says:

• No claim-type-specific sub-rule was found, so
• DocketMath uses the general/default SOL period

So all totals above rely on the general 1-year SOL under 22 O.S. § 152.

If a court or specific statutory scheme applies a different limitation period for a particular wage theory, the covered weeks (and thus the total) could change. This example is therefore illustrative, not legal advice.

Related reading

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