Worked example: Wage Backpay in Massachusetts

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

Below is a worked example of wage backpay in Massachusetts using DocketMath (wage-backpay) with jurisdiction-aware rules.

Here is a simple illustration for Massachusetts. These values are for demonstration only and should be replaced with your actual inputs.

• Principal or amount: $100,000
• Rate or cap: 10%
• Start date: 2025-01-15
• End/as-of date: 2025-09-30

Scenario (what you’re calculating)

An employee claims they were paid less than they should have been for a period because of an employment pay dispute. For illustration, assume:

• Pay cycle: weekly
• Hours per week: 40
• Regular hourly rate: $25.00
• Correct hourly rate: $30.00
• Start date of underpayment: January 1, 2019
• End date of underpayment: June 30, 2020
• Prior payments already made (credited): $1,500.00
• Interest handling: for this example, the calculator is run without adding a separate interest figure (you can run separate versions depending on your workflow)

Massachusetts time limit used by the tool (default)

DocketMath applies a general/default statute of limitations period because no claim-type-specific sub-rule was found in the jurisdiction data you provided.

• General SOL Period: 6 years
• Mass. Gen. Laws ch. 277, § 63 (general limitation)

How the example maps to calculator inputs

Use the following inputs in DocketMath → wage-backpay:

• Jurisdiction: US-MA
• Regular hourly rate: $25.00
• Correct hourly rate: $30.00
• Hours per week: 40
• Start date: 2019-01-01
• End date: 2020-06-30
• Credits / prior payments: $1,500.00
• SOL period: 6 years (default/general)

To make it concrete, the “missed wages per week” before credits is:

• Underpayment rate difference: $30.00 − $25.00 = $5.00/hour
• Weekly underpayment: $5.00 × 40 hours = $200/week

Example run

Let’s run through what DocketMath is doing conceptually for the example dates and then show the final backpay number.

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 compensable window (SOL filtering)

Your underpayment period runs from 2019-01-01 through 2020-06-30.

Because the scenario dates are within 6 years of the end date (and well within a typical “lookback” window), the full period is assumed to be within the default general SOL under:

• Mass. Gen. Laws ch. 277, § 63 (6 years)

So, for this example run, DocketMath uses the full date span provided.

Step 2: Compute total weeks in the backpay period

From 2019-01-01 to 2020-06-30, the period is:

• 2019: 365 days
• 2020 (through June 30): 182 days
• Total days: 365 + 182 = 547 days

Convert days to weeks using 7-day weeks:

• 547 ÷ 7 ≈ 78.14 weeks

DocketMath will typically convert using its internal day-count approach. For a practical estimate in this worked example, we’ll use the weekly conversion above.

Step 3: Convert weeks to total unpaid wages (before credits)

Weekly underpayment was $200/week, so:

• $200 × 78.14 weeks ≈ $15,628.00

Step 4: Apply credits / prior payments

Subtract already-credited payments:

• $15,628.00 − $1,500.00 = $14,128.00

Example output (what you’d expect from DocketMath)

A reasonable worked-example result is:

Quick sanity checks (useful while reviewing tool output)

Check the numbers against these expectations:

• If correct hourly rate equals regular hourly rate, the wage difference becomes $0, so backpay should be $0 (minus any negative-credit issues, if your worksheet has them).
• If you extend the end date beyond 6 years from the relevant “filing/trigger” date your workflow uses, DocketMath’s SOL filtering (based on the default ch. 277, § 63) may reduce compensable time.
• Credits shouldn’t increase backpay; they should only reduce it.

Sensitivity check

This section shows how the output changes when key inputs move. Use it to pressure-test the DocketMath result and confirm you’re modeling the facts you intend.

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) Change the correct rate by $1/hour

Holding everything else constant:

• New hourly difference: $30.00 − $25.00 + $1.00 = $6/hour
• New weekly underpayment: $6 × 40 = $240/week
• Gross backpay: $240 × 78.14 ≈ $18,754.00
• Net after credits: $18,754.00 − $1,500.00 ≈ $17,254.00

Impact: about +$3,126 versus the baseline (~$14,128).

✅ Practical takeaway: rate differences are the biggest lever.

2) Change hours per week from 40 to 35

Baseline hourly difference is still $5/hour.

• Weekly underpayment: $5 × 35 = $175/week
• Gross backpay: $175 × 78.14 ≈ $13,674.50
• Net after credits: $13,674.50 − $1,500.00 ≈ $12,174.50

Impact: about −$1,954 from baseline.

✅ Practical takeaway: if the dispute concerns scheduling, hours changed over time can materially affect results.

3) Extend the start date beyond the 6-year window (default SOL)

Because your jurisdiction default is 6 years under Mass. Gen. Laws ch. 277, § 63, DocketMath may cut off earlier dates once they fall outside the compensable window.

To see the sensitivity, rerun with (for example) a start date 8 years earlier while keeping the end date fixed. The output should drop because DocketMath will only count weeks within the default general SOL window.

4) Vary credits / prior payments

Suppose credits increase from $1,500 to $2,500:

• Net backpay: $15,628.00 − $2,500.00 = **$13,128.00**

Impact: about −$1,000 (one-for-one with credits, assuming credits don’t trigger any caps/normalization inside your worksheet).

✅ Practical takeaway: credits should be entered carefully because they translate directly into reduced backpay.

Related reading

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