Worked example: Wage Backpay in Arizona

Example inputs

This worked example shows how DocketMath can estimate wage backpay using Arizona (US-AZ) jurisdiction-aware rules and a general statute of limitations (SOL) backdrop.

Key Arizona limitation rule used here (general/default):

• General statute of limitations (SOL): 2 years
• Statutory citation: A.R.S. § 13-107(A)
  Source: https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai

Important note (jurisdiction data constraint): No claim-type-specific sub-rule was found in the provided jurisdiction data. This example therefore uses the general/default 2-year period as the controlling limitation framework for demonstration purposes.

Scenario

An employee alleges they were underpaid by an employer and wants to recover wage backpay for the period of unpaid wages before filing.

Assume these facts for the calculator run:

• Filing date (when the claim is filed): 2026-04-15
• Last date wages were paid incorrectly / last underpayment date: 2026-02-01
• Hourly wage rate: $22.00
• Hours unpaid per week: 14
• Number of weeks with backpay: 10
• Any precomputed damages inputs: none (we calculate from rate × hours)

What the calculator needs (typical wage-backpay inputs)

When using DocketMath for wage-backpay, you’re generally providing:

• A time window (often anchored by filing date and the work periods you want covered)
• Wage rate and unpaid hours
• Any adjustments you want reflected (e.g., additional weeks, different wage rates)

Inputs used in this example

Primary CTA: Use DocketMath here: **wage backpay calculator

Gentle disclaimer: This is an educational example showing calculator mechanics and the general/default SOL framework. It’s not legal advice. Real cases can involve additional facts, different claim framing, accrual rules, or tolling that a generic example may not capture.

Example run

Let’s run the numbers using the inputs above and the Arizona general SOL period of 2 years from A.R.S. § 13-107(A).

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: Estimate eligibility window (limitation overlay)

Because the provided jurisdiction data includes only the general/default SOL period (2 years under A.R.S. § 13-107(A)), the calculator treats backpay coverage as limited to claims tied to wage events occurring within that general window.

In this demonstration:

• The “last underpayment date” (2026-02-01) is within two years of the filing date (2026-04-15).
• The 10 weeks of unpaid wages are assumed to fall between late winter/early spring 2026.

Result: Since all 10 weeks occur within the 2-year period, no pruning of weeks occurs due to SOL in this run.

Step 2: Compute raw backpay

The basic backpay math (as commonly modeled in wage-backpay calculators) is:

• Weekly unpaid wages = hourly wage × unpaid hours per week
• Total backpay = weekly unpaid wages × number of weeks included

Compute:

• Weekly unpaid wages = $22.00 × 14 = $308.00
• Total backpay = $308.00 × 10 = $3,080.00

Step 3: Report calculator output (expected)

A DocketMath wage-backpay run would generally show:

• A time-filtered amount (SOL-adjusted, if applicable)
• A gross backpay estimate based on rate and hours

Because this example assumes all 10 weeks are within the general/default 2-year SOL framework, the estimated backpay matches the raw computation.

Estimated wage backpay (SOL-adjusted under the general/default rule): $3,080.00

Example output summary (what you’d expect to see)

To run your own numbers, use: **DocketMath: Wage Backpay

Sensitivity check

Now let’s change one key variable at a time to see how the output behaves under the Arizona general 2-year SOL framework tied to A.R.S. § 13-107(A).

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.

Sensitivity A: Increase unpaid hours

Keep everything else the same, but increase unpaid hours per week from 14 to 16:

• Weekly unpaid wages = $22.00 × 16 = $352.00
• Total backpay = $352.00 × 10 = $3,520.00

Change: $3,080.00 → $3,520.00
That’s an increase of $440.00, calculated as:

• (16 − 14) hours/week × $22/hr × 10 weeks
• 2 × 22 × 10 = $440

Sensitivity B: Reduce covered weeks

Keep hourly wage and weekly hours the same, but reduce “number of weeks with backpay” from 10 to 7:

• Weekly backpay remains $308.00
• Total backpay = $308.00 × 7 = $2,156.00

Change: $3,080.00 → $2,156.00
Decrease of $924.00, equal to $308 × (10 − 7).

Sensitivity C: Move the filing date back (SOL pressure)

This is where SOL logic usually shows up in calculator behavior. Suppose the employee filed later, such that the claimed work falls outside the 2-year general SOL period under A.R.S. § 13-107(A).

Stress-test setup (simplified for demonstration):

• Keep wage rate = $22.00
• Keep unpaid hours/week = 14
• Keep “10 weeks with backpay” the same in the employee’s narrative
• Change filing date to 2024-03-15
• Assume the 10-week work period is immediately prior to 2026-02-01 (as in the base scenario), meaning those wages are older than 2 years relative to the new filing date.

Under the simplified assumption that DocketMath filters to the general 2-year window using A.R.S. § 13-107(A), those older weeks would be excluded.

Expected effect in calculator terms (demonstration):

• Weeks covered may drop from 10 to 0
• Estimated total backpay may drop from $3,080.00 to $0.00

Quick comparison table

*Based on the simplified assumption that all claimed work falls outside the 2-year general SOL under A.R.S. § 13-107(A) relative to the new filing date.

Related reading

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