Worked example: Wage Backpay in Montana

Example inputs

This worked example shows how to estimate wage backpay using DocketMath for Montana (US-MT), applying the general/default statute of limitations (SOL) rule.

Important scope note (jurisdiction-aware rule): For this example, Montana’s general SOL period is 3 years under Montana Code Annotated (MCA) § 27-2-102(3). Based on the jurisdiction data provided, no claim-type-specific SOL sub-rule was found for wage backpay. So this example uses the default period rather than a specialized one.

Scenario

A worker believes they were underpaid due to unlawful wage practices. They’re calculating backpay from when the underpayment began through a later end date, but they also want to reflect that only some portion may fall within the SOL window.

We’ll use a simple date range setup:

• Backpay start date: 2023-01-15
• Backpay end date: 2026-01-14
• Filing/claim date (anchor for SOL): 2026-01-14
• Hourly wage: $22.50
• Unpaid hours per pay period (assumed): 40 hours
• Pay frequency: Weekly
• Number of unpaid hours per week: 40
• Offsets included: 0 (for simplicity in this worked run)

Why the SOL matters in a wage backpay estimate

If the general SOL is 3 years, then the SOL concept typically limits recoverable periods to the 3 years immediately before the claim date (as applied to the facts). In this worked example, DocketMath applies a lookback window based on the claim-date anchor.

So the payable window used in the calculation is constrained to the earlier of:

1. the actual requested backpay start/end dates, and
2. the SOL lookback start calculated from the claim date.

DocketMath inputs you’ll enter

From a calculation standpoint, you’ll typically provide values like these in /tools/wage-backpay:

• Time window start (requested backpay start)
• Time window end (requested backpay end)
• Claim date (SOL anchor)
• Hourly pay rate
• Unpaid hours per pay period (and/or per week)
• Pay period frequency (weekly, biweekly, etc.)
• Any offsets/adjustments (optional)

You can launch the calculator here: **/tools/wage-backpay

Example run

Let’s run the numbers for Montana using the general SOL of 3 years under MCA § 27-2-102(3).

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 window

• Claim date (anchor): 2026-01-14
• General SOL period: 3 years (MCA § 27-2-102(3))

So the SOL lookback start is approximately:

• 2023-01-14 (three years prior)

Your requested backpay start is:

• 2023-01-15

Because 2023-01-15 is one day after 2023-01-14, the SOL constraint does not shorten the requested start date in this scenario.

Step 2: Determine the constrained payable period

• Requested backpay period: 2023-01-15 to 2026-01-14
• SOL-limited period: 2023-01-15 to 2026-01-14

Result: the full requested period is within the 3-year window (based on the date arithmetic used for the lookback cutoff), so DocketMath counts the full duration.

Step 3: Compute weekly unpaid hours and total hours

We assume a simple weekly schedule:

• Unpaid hours per week: 40
• Pay frequency: Weekly
• Duration from 2023-01-15 through 2026-01-14 (set up to be exactly 3 years in this example)

In a simplified weekly-count model, this is:

• 156 weeks

Total unpaid hours:

• 156 weeks × 40 hours/week = 6,240 hours

Step 4: Apply wage rate to estimate backpay

• Hourly wage: $22.50
• Total hours: 6,240

Estimated wage backpay:

• 6,240 × $22.50 = $140,400

Step 5: Output interpretation (what you should see)

A DocketMath wage-backpay run for US-MT using the general SOL constraint should align with the following structure:

Practical takeaway

Because the example’s backpay start date falls within the 3-year lookback window, the SOL constraint doesn’t reduce the payable period. In many real situations, requested backpay starts earlier than the lookback window; then the SOL limitation reduces the recoverable amount.

Sensitivity check

Now test how the estimate changes when the backpay start date shifts earlier than the SOL window. This shows what drives the output: the SOL cutoff and how weeks/hours are counted.

We’ll keep everything else the same:

• Hourly wage: $22.50
• Unpaid hours/week: 40
• Pay frequency: weekly
• Claim date anchor: 2026-01-14
• SOL: 3 years (MCA § 27-2-102(3))

Case A: Backpay starts after the SOL lookback

• Backpay start: 2023-02-01
• Constrained period: 2023-02-01 to 2026-01-14

Since the start remains within the lookback window, DocketMath will count fewer weeks than the baseline run.

• Estimated payable duration: ~142 weeks (approximate weekly count depending on boundary counting)
• Total hours: 142 × 40 = 5,680
• Backpay estimate: 5,680 × $22.50 = $127,800

Case B: Backpay starts before the SOL lookback (SOL truncation)

• Backpay start: 2022-12-01
• SOL lookback start remains about: 2023-01-14 (3 years prior)
• Constrained period: 2023-01-14 to 2026-01-14

Now the earliest recoverable portion begins at the SOL cutoff, not at the requested start date.

• Estimated payable duration: around the baseline (e.g., ~156 weeks if boundary alignment matches the calculator’s counting method)
• Backpay estimate: close to the baseline $140,400, but the exact total depends on whether boundary days cause a week-count difference.

Case C: Change the hourly rate (same constrained dates)

If dates (and therefore total counted hours) stay the same but the wage changes:

• Hourly wage: $22.50 → $25.00
• Total hours (from baseline): 6,240
• New estimate: 6,240 × $25.00 = $156,000

What to watch in practice

When you run sensitivity tests in DocketMath, focus on these practical levers:

• Whether your backpay start date is before the 3-year lookback from the claim date
• Whether the unpaid hours match your real schedule (e.g., 38 vs. 40)
• Whether the calculator’s method for mapping dates to weeks (or partial weeks) shifts the count
• Whether you need to include offsets (e.g., wages paid elsewhere during the same period), since offsets can materially reduce the net backpay

Pitfall example: If a one-week counting difference occurs in this example, the change could be 40 hours × $22.50 = $900.

Related reading

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