How to run Wage Backpay in DocketMath for Arizona

Step-by-step

Here’s a practical walkthrough for running Wage Backpay in DocketMath for Arizona (US-AZ) using jurisdiction-aware rules.

1) Open the Wage Backpay calculator

• Go to the primary CTA: **/tools/wage-backpay
• Confirm the jurisdiction selector is set to **Arizona (US-AZ)

If your interface lets you pick a jurisdiction, make sure US-AZ is active before you enter any dates—Arizona’s time limits affect what portion of the period the calculator includes.

2) Enter the core dates for the backpay window

DocketMath’s wage backpay workflow typically depends on the start and end of the period you’re evaluating. Enter:

• Backpay period end date (often the date of filing or the end of employment/compensation period—whatever you’re modeling)
• Backpay period start date (the earliest date you want included in the estimate)

If you’re unsure of the exact start date, begin with the earliest reasonable date supported by your records (pay stubs, employment/contract dates, scheduling records). You can tighten the range after you see how the output changes.

3) Review the Arizona time limit DocketMath applies

For Arizona, DocketMath uses the jurisdiction’s general/default statute of limitations (SOL) concept for this wage-backpay calculation.

• General SOL Period: 2 years
• Statute cited for the general/default rule: **A.R.S. § 13-107(A)
• Important scope note: No claim-type-specific sub-rule was found, so the calculator treats this as the general/default period.

How this affects your results

• If your start date is earlier than 2 years before your end date, DocketMath may cap the recoverable portion, so the effective earliest included date aligns to the 2-year lookback.
• If your start date falls within 2 years, the calculator can include the full window you entered.

4) Confirm wage inputs (if your template section requires them)

Depending on the wage-backpay template, you may need to enter one or more of the following:

• Hourly rate (for hourly workers)
• Weekly or biweekly hours (or an average weekly schedule)
• Pay frequency (sometimes used to align earnings periods)
• The wage change logic you’re modeling (what was paid vs. what should have been paid)

What to watch for:

• If the tool supports a “difference” or delta-style input, the output often reflects backpay from the underpayment gap (not total wages).
• If it supports a “gross” or full-earnings mode, it may compute total amounts and then apply the SOL time cap afterward.

If you’re unsure which mode the calculator expects, try a small test run and compare whether the result looks like a “delta” or a “full earnings” number.

5) Run the calculation and capture the outputs

Click Calculate after entering dates and wage figures. Record:

• Backpay window start / end (often shown as the effective period after any SOL adjustment)
• Computed backpay amount
• Days/weeks included (useful for sanity-checking)
• Any SOL-related adjustment note indicating that Arizona’s 2-year general period (A.R.S. § 13-107(A)) affected the window

Practical interpretation:

• If the effective start date is later than what you entered, the 2-year default is likely being applied.
• If totals seem off, double-check hours, rates, and whether you entered the delta you meant to model (rather than both the base and the delta).

6) Iterate with multiple scenarios (quick what-if comparisons)

A good workflow is to run several reasonable date windows and compare the differences:

• Scenario A: earliest start date you can support with records
• Scenario B: start date aligned exactly to the 2-year lookback
• Scenario C: a narrower range based on your best proof or strongest evidence

You’ll usually see meaningful changes when the effective SOL-capped start date changes or when the wage inputs change. Use results as decision support, not a guarantee of the final legal outcome.

Common pitfalls

Wage backpay calculations are sensitive to time-window framing. These are the issues that most commonly distort results:

• Forgetting the SOL cap

  • If your period start date predates Arizona’s 2-year general period under A.R.S. § 13-107(A), the calculator may limit the effective recoverable start date—reducing the backpay total.

• Mixing up general/default SOL vs. claim-specific rules

  • In this DocketMath workflow, the calculation uses the general SOL period (2 years) because no claim-type-specific sub-rule was found. That means the calculator may not match deadlines that could apply under specialized circumstances.

• Using inconsistent end dates

  • Switching between a filing date in one run and a settlement/end date in another changes the distance between start and end, and therefore changes the 2-year lookback. Keep scenario labeling consistent.

• Entering mismatched work schedules

  • If you enter average hours that don’t reflect the period you selected (for example, averaging in high-hours months but estimating a short window), your backpay amount can be skewed.

• Double-counting wage differences

  • If you provide both a “base” wage adjustment and a separate “difference” figure, you may overstate the delta. If the calculator expects only the delta, enter only what it asks for in that specific field.

Quick checklist before you hit Calculate

Try it

Use this quick hands-on test to see how the Arizona 2-year rule changes the result:

1. Open **/tools/wage-backpay
2. Set jurisdiction to US-AZ
3. Enter:

   • End date: a specific date (for example, today or your filing date)
   • Start date: use two different values:

     • one older than 2 years
     • one within 2 years
4. Run the calculator for both runs and compare:

   • Whether the effective start date changes
   • Whether the total backpay amount changes significantly

If your outputs don’t change between the two runs, re-check:

• that the calculator is applying the SOL adjustment for US-AZ
• that the tool is interpreting your fields correctly (start vs. end)
• that your wage inputs are identical across scenarios

Related reading

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