Wage Backpay rule lens: Maryland

5 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

The rule in plain language

Run this scenario in DocketMath using the Wage Backpay calculator.

In Maryland, if someone wants wage backpay in court, the baseline deadline to file is generally 3 years. This “rule lens” is built around the general statute of limitations for civil actions, because no claim-type-specific sub-rule was found for wage backpay in this lens.

Maryland General SOL (default rule): 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

What this means in practice: the SOL typically limits the amount of unpaid wages a court may allow you to recover to a lookback window measured from the filing date. It does not decide whether wages are actually owed; it helps determine which periods are likely within the court’s timing limits.

Caution / not legal advice: This lens is about timing (when a lawsuit must be filed and how far back recovery may go). It doesn’t replace legal advice—especially because real cases can involve different legal theories, accrual details, or procedural rules.

Why it matters for calculations

Backpay calculations often focus on hours × rate, but Maryland’s SOL can change the result because it affects how many weeks/pay periods are “covered”.

Small differences in the rule text can change the output materially. Using the correct jurisdiction and effective date ensures the calculation aligns with the authority that applies to your matter.

The lookback window concept

When a limitations period applies, the court effectively asks:

When did you file the lawsuit?
How far back from that date does the statute allow recovery?

Using the 3-year default in Md. Code, Cts. & Jud. Proc. § 5-106, the recoverable portion often corresponds to a 3-year window ending at the filing date.

Practical examples of how timing changes results

Example A: Longer unpaid period, shorter recoverable period

Unpaid wages: 4 years total
Filing date: today
SOL window: last 3 years

Result: even if wages were unpaid for 4 years, your SOL-adjusted backpay may exclude the earliest 1 year because that portion falls outside the lookback window.

Example B: Filing earlier vs. later (same unpaid wages otherwise)

If two workers have the same unpaid work (same weekly hours and rate), but:

Worker 1 files 6 months earlier than Worker 2,

then Worker 1’s 3-year lookback window can include an additional 6 months of otherwise unpaid time. That difference can be significant even when pay rates and hours are identical.

Inputs that drive the math in this lens

In DocketMath, the biggest timing-sensitive inputs are:

Filing date (anchors the end of the SOL window)
Backpay start date (determines what portion is potentially too old)
Pay rate (hourly or equivalent rate used to compute wage amounts)
Work pattern (e.g., weekly hours used to build weekly backpay)
Wage components (if your tool separates base pay from other wage categories, totals can reflect that)

Because this Maryland lens uses the general/default 3-year SOL, the dominant effect typically comes from how your unpaid timeline lines up against the 3-year period preceding the filing date.

Warning: If your case involves a different cause of action or a special statutory limitations period (rather than the general default), the covered window could differ. This tool models the default 3-year rule; it can’t determine legal classification.

Use the calculator

Use DocketMath’s wage-backpay calculator to estimate the SOL-adjusted amount for Maryland under the 3-year default from Md. Code, Cts. & Jud. Proc. § 5-106.

Primary CTA: /tools/wage-backpay

Run the Wage Backpay calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Step-by-step: what to enter

In the wage-backpay calculator, enter (labels may vary slightly in the UI):

Jurisdiction: set to **US-MD (Maryland)
Filing date: the date you are modeling as the lawsuit filing date
Unpaid wages period: enter the start date and end date you want to analyze
Compensation rate: the hourly rate (or equivalent rate fields)
Hours: weekly hours (or total hours per period, based on what the calculator requests)

What to expect from the output

DocketMath typically generates results such as:

Total backpay (modeled) for the full period you enter
SOL-adjusted backpay (limited to the covered 3-year window)
A cutoff effect showing whether the early portion falls outside the SOL

Sanity checks you can do quickly:

If your unpaid start date is more than 3 years before the filing date, then you should expect that only the portion after the 3-year cutoff is counted.
If your unpaid start date is within 3 years of filing, then more (or all) of the entered period may be included—subject to how the tool defines coverage and period granularity.

Quick comparison checklist

Before relying on results, verify:

How output changes when you adjust inputs

Generally:

Earlier filing date → larger SOL window → higher SOL-adjusted backpay
Later filing date → smaller SOL window → lower SOL-adjusted backpay
Earlier unpaid start date → more time outside 3 years → lower SOL-adjusted backpay
Higher weekly hours or higher hourly rate → increases totals, but SOL still determines which weeks count

Pitfall to avoid: Don’t calculate “hours × rate” for the entire unpaid period and then manually subtract time outside the SOL. DocketMath’s approach is intended to apply the SOL cutoff within the covered range so you don’t accidentally double-count or misapply the window.