Worked example: Wage Backpay in Maryland

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

This worked example shows how DocketMath’s wage-backpay calculator can model a Maryland wage backpay amount using the general statute of limitations (SOL) rule.

Because the provided jurisdiction data did not identify a claim-type-specific backpay sub-rule, this example uses the default/general SOL period:

• General SOL period: 3 years
• Statute: Md. Code, Cts. & Jud. Proc. § 5-106
  Source: https://codes.findlaw.com/md/courts-and-judicial-proceedings/md-code-cts-and-jud-pro-sect-5-106/?utm_source=openai

Scenario (what we’ll calculate)

Assume an employee is seeking backpay for lost wages after a termination-related wage interruption. For modeling purposes:

• The employee’s last day of work (or last day wages were correctly paid): 2023-04-15
• The employee files on: 2026-02-01
• The employer pays wages at:

  • Hourly rate: $28.50
  • Hours per week (typical): 40
  • Weeks with unpaid wages: inferred from the SOL “lookback” window below

DocketMath inputs (wage-backpay)

Use these inputs as the calculator would for US-MD jurisdiction-aware SOL:

1. Jurisdiction: US-MD
2. General SOL (years): 3 (from jurisdiction data)
3. General SOL statute: Md. Code, Cts. & Jud. Proc. § 5-106
4. Last paid / last day of correct wages: 2023-04-15
5. Filing date / complaint date: 2026-02-01
6. Pay rate: $28.50/hour
7. Typical schedule: 40 hours/week
8. Assumption for weeks: count weeks in the eligible “lookback” period (the portion not time-barred by SOL)

To follow along, you can also run the same calculator here: /tools/wage-backpay.

Example run

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: Apply Maryland’s general 3-year lookback window

With a general SOL of 3 years under Md. Code, Cts. & Jud. Proc. § 5-106, the calculator models an eligible backpay window starting 3 years before the filing date.

• Filing date: 2026-02-01
• Start of SOL lookback: 2023-02-01 (3 years prior)

Now align that window with the employee’s wage interruption start. In this scenario, the last day of correct wages was 2023-04-15, so eligible backpay should begin after the interruption begins (not before).

That means:

• Eligible period start = 2023-04-15
• Eligible period end = 2026-02-01 (the filing date, consistent with a “through filing” modeling convention)

Step 2: Compute total eligible weeks

From 2023-04-15 to 2026-02-01, the span is approximately:

• 1 year, 9 months, and ~17 days
• That’s roughly 1.80 years
• Converted to weeks: 1.80 × 52 ≈ 93.6 weeks

DocketMath’s wage-backpay calculator will translate this into a week-based count based on its internal date-to-duration method (commonly using whole-week logic or prorating depending on settings). For a worked example, we’ll show the model result using ~93.6 weeks as the basis.

Step 3: Convert weeks into unpaid hours

• Hours/week = 40
• Unpaid hours ≈ 93.6 × 40 = 3,744 hours

Step 4: Multiply by hourly rate

• Hourly rate = $28.50
• Backpay ≈ 3,744 × $28.50 = $106,704

Output (modeled)

Estimated wage backpay (Maryland, US-MD, general 3-year SOL):

• ≈ $106,704

If you run this in DocketMath, you’ll typically see a breakdown that mirrors these components:

• eligible date window (based on Md. Code, Cts. & Jud. Proc. § 5-106 / 3-year general SOL),
• total eligible duration,
• unpaid hours,
• and the gross wage backpay total.

Sensitivity check

Small changes to key inputs can materially change the backpay number. Below are practical adjustments and how they affect the calculation.

Sensitivity A — Filing date moves by 3 months

Keep everything else the same (rate $28.50/hour, 40 hours/week, last correct wages 2023-04-15), but change the filing date.

Because the interruption starts 2023-04-15, filing earlier than 2023-04-15 + ~3 years typically truncates weeks faster than people expect. In the baseline, the interruption start is after the SOL window start—so the SOL window fully “covers” the beginning of the interruption. Move the filing date far enough earlier and some of that interruption becomes time-barred.

Sensitivity B — Hourly rate change of $2/hour

If the hourly rate changes while the eligible weeks and hours remain constant:

• Baseline unpaid hours ≈ 3,744
• Rate increase by $2.00/hour
• Change in backpay ≈ 3,744 × $2 = $7,488

So a +$2/hour adjustment yields roughly +$7,488 in gross modeled backpay.

Sensitivity C — Hours/week changes from 40 to 35

If schedule is not 40 hours weekly:

• Hours/week: 35 instead of 40
• Unpaid hours ≈ 93.6 × 35 = 3,276 hours
• Backpay ≈ 3,276 × $28.50 = $93,366

That’s a reduction of about $13,338 from the baseline (~$106,704 − $93,366).

Sensitivity D — Eligible duration method (whole weeks vs prorating)

If the calculator counts whole weeks rather than prorating partial weeks, the total weeks could drop (or rise slightly). That affects backpay by:

• per-week backpay = 40 × $28.50 = $1,140
• each whole week difference shifts totals by roughly $1,140

Related reading

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