How to run Wage Backpay in DocketMath for Michigan

Step-by-step

This guide shows you how to run Wage Backpay calculations in DocketMath for Michigan (US-MI) using jurisdiction-aware rules. It’s designed to help you get consistent, defensible numbers faster—especially when Michigan’s general statute of limitations affects which part of a wage period is included.

1) Start in the Wage Backpay tool

1. Open the calculator: **/tools/wage-backpay
2. Confirm you’re using Michigan jurisdiction context (US-MI).

   • If the tool prompts for jurisdiction, select US-MI (Michigan).

2) Enter the wage timeline inputs

Use the tool’s wage backpay inputs to describe what wages were owed and when.

At minimum, you’ll typically provide:

• Start date: when the unpaid wage period begins
• End date: when the unpaid wage period ends
• Wage structure (based on the tool’s layout), such as:

  • Hourly rate or per-period wage amount, and/or
  • Hours worked (if the tool requires a quantity to multiply against your rate)
• Interim amounts / mitigation / offsets (if the UI includes optional fields)

As you enter dates and numbers, DocketMath updates the backpay calculation based on the wage structure you select.

3) Apply Michigan’s default statute of limitations window

For this Michigan setup, DocketMath uses the general statute of limitations period rather than a claim-type-specific sub-rule.

That’s because no claim-type-specific sub-rule was found for this calculator run. So the tool should default to the general period below.

• General statute of limitations (SOL): 6 years under MCL § 767.24(1) (Source: https://www.michigan.gov)

How this affects your output:

• If your unpaid wage period starts more than 6 years before the tool’s lookback anchor date, the calculator will effectively limit recoverable backpay to the portion that falls within the 6-year window.
• If your unpaid period is entirely within 6 years, the full period should be included.

Practical check before relying on totals: compare your entered

• Start date
  to the tool’s calculated “6-year lookback start” relative to the anchor date you provided (or that the tool collects as an “as of” / cutoff / filing-related field).

4) Verify which date DocketMath uses as the “lookback anchor”

This is one of the most important steps.

The calculator may ask for a date such as:

• As-of date
• Filing date
• Cutoff date
• or another “anchor” date tied to the SOL window

Why it matters: Michigan’s 6-year general SOL (per MCL § 767.24(1)) determines what portion of your unpaid wage timeline is included.

If the tool provides a covered period (included date range), verify:

• The covered period start is no earlier than the beginning of the 6-year window calculated from your anchor date.
• The covered period end matches your End date (or matches the tool’s cutoff logic, if it applies).

5) Read the output breakdown

After you run the calculation, review more than just the grand total.

Look for:

• Total wage backpay
• A covered period / included date range (confirm the dates)
• The math basis, such as:

  • rate × time, computed using the wage structure you entered
• Any reductions / inclusions the tool accounts for (for example, if the UI supports mitigation amounts or offsets)

If the covered period is shorter than your entered timeline: that’s typically expected when the earlier portion falls outside the 6-year limit under MCL § 767.24(1)—not necessarily a calculator bug.

6) Export or record your results for review

Once you have a stable run:

• Save/export the results if DocketMath offers that option.
• Record the key inputs so you can rerun confidently if anything changes:

  • Start date / End date
  • The anchor date you used (as shown in the UI)
  • Your wage inputs (rate/amount and hours, if applicable)
  • Confirmation that the output covered period aligns with the 6-year SOL rule

Keeping these details makes it easier to audit the run and replicate the number later.

Common pitfalls

Most mistakes in wage backpay runs come from inputs and timing, especially around SOL coverage. Watch for these:

In this setup, the calculator should use Michigan’s general 6-year SOL under MCL § 767.24(1). No claim-type-specific sub-rule was found for this run, so the general/default rule is expected.

If your unpaid wage period begins earlier than 6 years before the tool’s lookback anchor, DocketMath will limit recoverable wages to the part inside the window—changing the total.

The “as of” / filing-related / cutoff date can materially affect the covered period. Even a small difference can shift which days fall inside the 6-year range.

If the tool expects an hourly rate + hours but you input a different kind of wage measure, your computed backpay can be wrong even when your dates are correct. Stick to the tool’s input definitions.

If you don’t check the output’s included date range, you may not notice that only a portion of your requested timeline was counted due to the 6-year SOL.

Try it

Use this quick test to confirm the Michigan SOL behavior:

1. Open **/tools/wage-backpay
2. Choose a date range where the unpaid period spans more than 6 years.

   • For example: set an early start date more than 6 years before your anchor date, then set an end date within the more recent timeframe.
3. Set jurisdiction to US-MI
4. Run the calculation and then check:

   • The output covered/included date range
   • Whether the covered range begins at (or about) the expected start of the 6-year general SOL window under **MCL § 767.24(1)

If the covered period comes out near 6 years (subject to day-level counting and the exact anchor date you selected), that’s a good sign the tool is applying the Michigan default rule.

For ongoing workflows, you can also browse DocketMath materials starting at /blog.

Related reading

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