How to run Wage Backpay in DocketMath for Wisconsin

Step-by-step

Run this scenario in DocketMath using the Wage Backpay calculator.

This guide shows how to run Wage Backpay in DocketMath for Wisconsin (US-WI) using jurisdiction-aware rules, so your backpay estimate aligns with Wisconsin’s general/default lookback approach.

1) Start your Wage Backpay calculation in DocketMath

1. Open the tool: /tools/wage-backpay
2. Select:

   • Calculator: Wage Backpay
   • Jurisdiction: Wisconsin (US-WI)

If the page shows other selectors (for example, claim types), leave them at their defaults unless your workflow requires you to change them.

2) Set the “as of” date (the measurement anchor)

DocketMath uses an anchor date (often labeled “As of,” “Through,” or similar) to determine the lookback window for backpay.

• Pick the date you want the estimate to measure through (commonly the filing date, hearing date, or a “through” date your workflow is using).
• Confirm the UI label that controls this anchor date.

How this affects output:
Changing the anchor date shifts the start of the lookback window. That means the same wage inputs (rate and hours) can produce a different backpay total if it includes more or fewer eligible months/weeks.

3) Enter the work period details

Next, enter the dates that represent the wage underpayment period.

Depending on how DocketMath structures inputs, you’ll typically provide some combination of:

• Start date for the underpayment period
• End date for the underpayment period (or you rely on the anchor/“as of” date)

How this affects output:

• If your work period start date is earlier than the allowed lookback window, DocketMath should effectively count only the portion within the lookback window.
• If your work period start date is later than the lookback start, the lookback window won’t change much because the actual work dates control.

4) Confirm Wisconsin’s default lookback period is being used

For Wisconsin, DocketMath should apply the general/default statute of limitations period for this workflow.

Based on the jurisdiction data you provided:

• General SOL Period: 6 years
• Wis. Stat. § 939.74(1) (general/default period)
  Source: https://codes.findlaw.com/wi/crimes-ch-938-to-951/wi-st-939-74/

Also note the constraint in your brief: no claim-type-specific sub-rule was found. That means DocketMath should treat the 6-year general/default period as the governing lookback for this calculator run (rather than a specialized shorter/longer period that could apply to a particular claim type).

What to verify in the UI:
Look for confirmation in the calculator summary (or breakdown) that a 6-year lookback window is being used as the default time window.

5) Add your wage inputs (rates, hours, and/or totals)

Now enter the wage details that drive the backpay amount. Typical inputs may include some combination of:

• Hourly rate or salary rate
• Hours per week (if hourly)
• Pay frequency (if required)
• Any optional schedule assumptions, if the UI offers them

DocketMath then calculates:

• Backpay for each eligible pay period (or month), and
• A total across the eligible timeframe defined by your dates and the 6-year lookback.

How this affects output:
Backpay totals typically scale directly with:

• wage rate, and
• hours worked (or the schedule assumption).

Even small input changes—like adjusting hours from 30 to 35 per week—can noticeably change the total because the wage amount is effectively multiplied by the number of eligible periods.

6) Review the calculation summary and output breakdown

Before saving or exporting, check the summary for these date-related elements:

• Start of the lookback window (computed from the anchor/as-of date using the 6-year period)
• End of the lookback window (aligned to the anchor date or your provided end date, depending on the tool)
• Number of periods included (months/weeks/days, depending on the UI)
• The computed backpay total

Practical check:
If the estimated timeframe seems too long or too short, revisit:

1. the anchor (“as of/through”) date, and
2. the work period start date.

7) Export or document the results for your workflow

If DocketMath offers export options (like PDF/CSV) or a share link:

• Export the results so you can attach them to your case timeline or internal review.
• Record the inputs you used, especially:

  • the anchor/as-of date, and
  • the work period start/end dates, and
  • wage rate and hours assumptions.

Practical tip: Saving a version after your dates are finalized can prevent confusion later if you update wage numbers for a revised estimate.

Common pitfalls

Here are common issues when running Wage Backpay in DocketMath for Wisconsin using the 6-year default approach tied to Wis. Stat. § 939.74(1).

• Using the wrong anchor (“as of”) date

  • Switching from a filing date to a later hearing date can shift the lookback window and change how many periods are included.
• Including wages outside the lookback window

  • If the work period starts before the lookback window, you generally want only the portion inside the window to count under the default approach.
• Forgetting it’s a default rule, not a claim-specific rule

  • Your brief notes no claim-type-specific sub-rule was found, so the tool should use the general 6-year period as the governing lookback for this workflow.
• Mixing up weekly vs monthly (or hourly vs salary) inputs

  • Example: entering a monthly figure into a field meant for an hourly rate (or vice versa).
• Assuming hours never changed

  • If overtime, seasonal reductions, intermittent work, or schedule changes occurred, a constant-hours assumption can skew results.
• **Conflicting end dates (period end vs anchor/as-of)

  • If both appear in the UI, mismatched dates can unexpectedly shorten or extend the included timeframe.
• Not reviewing the eligible period breakdown

  • The output may look plausible even with the wrong dates—always confirm the eligible start and end dates shown in the summary.

Try it

Use this quick checklist to run your first Wisconsin (US-WI) wage backpay calculation in DocketMath.

• Wis. Stat. § 939.74(1) is the cited basis for the default period used in this workflow
• Ensure dates outside the lookback window are excluded/truncated as shown in the eligible period
• Match the field labels (hourly vs weekly vs monthly)
• eligible period start/end dates
• number of periods included
• backpay total

Sanity test (optional):
Before finalizing, reduce hours or rate by a known amount (for example, 10%). If DocketMath is calculating as expected, the backpay total should drop by roughly a similar percentage (accounting for rounding and any period-count changes).

Related reading

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