Worked example: Wage Backpay in Washington

Example inputs

This worked example shows how DocketMath estimates wage backpay using jurisdiction-aware rules for Washington (US-WA)—specifically applying the general statute of limitations (SOL) provided for this calculation.

Because Washington’s backpay timing can depend on the claim type, the key constraint here is scope: no claim-type-specific SOL sub-rule was found for this example. So the calculation uses the general/default period.

Washington timing rule used in this example

• General SOL period: 5 years
• General statute citation: RCW 9A.04.080

Assumed facts (inputs)

Use the same style of inputs you’d enter into DocketMath’s wage-backpay calculator. For this example, assume:

• Jurisdiction: Washington (US-WA)
• Claim/payout date (“as of” date): 2026-04-15
• Work period start: 2020-03-01
• Work period end (last day worked or last date wages were owed): 2026-03-31
• Weekly gross wage rate (same each week in this example): $1,200
• Hours per week: 40
• Weeks with unpaid wages (derived): 250 weeks (the “allowed” weeks get reduced once we apply the SOL window; see Example run)
• Mitigation/off-sets: none entered for this run (DocketMath treats this as $0 adjustment)
• Any additional damages included: none (this example focuses on wages only)

In practice, you can choose whether to enter wage totals as an hourly rate, weekly wage, or weekly gross. Because the tool name here is wage-backpay, the key is that DocketMath scales the unpaid wage amount by the time window that is permitted under the SOL.

Quick sanity check on dates

• The work period starts before the 5-year SOL window.
• The work period ends within the 5-year window.
• So the backpay window should be truncated to the last 5 years before the “as of” date.

Example run

To run this in DocketMath, use the wage-backpay tool at:

• Primary CTA: /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: Determine the SOL-limited lookback window (WA general SOL)

With a 5-year general SOL under RCW 9A.04.080, the backpay window begins:

• As of date: 2026-04-15
• Lookback start: 2021-04-15 (5 years prior)

So, for this run:

• Work period start: 2020-03-01
• Allowed backpay start: 2021-04-15
• Work period end: 2026-03-31
• Allowed backpay end: 2026-03-31

Step 2: Compute number of unpaid weeks within the allowed window

The allowed window is 2021-04-15 through 2026-03-31.

In a wage-only example with a consistent weekly wage cadence (40 hours/week), DocketMath effectively counts the time intersection as “pay periods/weeks” for the purposes of multiplying by the weekly wage figure. In this worked example:

• Weeks with unpaid wages within the SOL window: 202.25 weeks

Why not the full 250 weeks? Because the portion from 2020-03-01 to 2021-04-14 falls outside the 5-year limit and therefore is excluded from the SOL-limited backpay estimate.

Step 3: Multiply weeks by the weekly wage rate

• Weekly gross wage: $1,200
• Unpaid weeks within SOL window: 202.25

Estimated wage backpay:

• $1,200 × 202.25 = $242,700

Step 4: Apply offsets/mitigation (none in this run)

• Offset/mitigation entered: $0
• Result remains: $242,700

Output summary (what you should see conceptually in DocketMath)

Gentle note: This is a worked example for budgeting and understanding how the calculator applies the SOL window. It isn’t legal advice, and real cases can involve different facts, different accrual theories, or different applicable provisions.

Sensitivity check

A wage-backpay number can move a lot when inputs affect either (1) the SOL-limited time window or (2) wage magnitude. Below are practical “what if” changes you can test in DocketMath.

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) Move the “as of” date by ±6 months

Because the SOL is 5 years under RCW 9A.04.080, shifting the as-of date changes how much time gets included.

Use the same facts as above (weekly wage $1,200, no offsets), and change only the as-of date:

• Scenario A: as-of = 2025-10-15 (6 months earlier)
• Scenario B: as-of = 2026-10-15 (6 months later)

Expected directional effect:

• Earlier as-of → shorter included window → lower backpay
• Later as-of → longer included window → higher backpay

When you re-run the tool, you should see the “allowed backpay start” shift accordingly, which changes the unpaid week count.

2) Change the weekly wage rate

Backpay scales roughly linearly in this simplified wage-only setup.

Example:

• Weekly wage: $1,200 → $1,300 (increase of $100/week)
• Unpaid weeks within SOL: unchanged at 202.25 weeks

Dollar change:

• $100 × 202.25 = $20,225

So the estimate would move from:

• $242,700 → $262,925 (assuming no other edits)

3) Extend or shorten the unpaid work end date

Because the model counts the intersection of your work window with the SOL window, changing the last unpaid day can have an outsized effect—especially when you’re near the SOL boundary (around 2021-04-15 in this example).

Practical test:

• Move work period end from 2026-03-31 → 2026-04-30
• Re-run and observe how the allowed overlap changes (and therefore the counted weeks)

4) Enter mitigation/off-sets

This example used $0. If you add offsets in DocketMath, the result should reduce accordingly (typically as a subtraction from the wage portion you computed).

Stress test:

• Add a mitigation/off-set of $15,000
• New estimate (conceptually): $242,700 - $15,000 = $227,700

Related reading

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