Statute of Limitations for FLSA Claims (federal wage/hour) in Maryland

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

The federal Fair Labor Standards Act (FLSA) sets minimum wage and overtime rules for covered workers. When an employee brings an FLSA lawsuit in Maryland, one of the first procedural questions is timing: how long after the wage/hour violation can a claim be filed?

Under the FLSA’s statute of limitations framework, the key timing rule is expressed in years, with different look-back periods depending on whether the conduct was “willful.” Maryland courts and federal courts sitting in Maryland apply the federal limitations periods to FLSA claims because the limitations period is part of the federal cause of action (not Maryland’s state wage law rules).

This guide focuses on the general/default FLSA statute of limitations period used by the DocketMath calculator for Maryland. If your facts involve allegations of willfulness, that may change the look-back window—see Key exceptions below.

Note: This page gives a practical timing roadmap for FLSA claims filed in Maryland. It’s not legal advice, and it can’t replace a case-specific analysis of facts and filings.

Limitation period

Default (general) limitations period in Maryland for FLSA claims

For the Maryland jurisdiction, the general/default limitations period is:

  • 3 years
  • General statute: Md. Code, Cts. & Jud. Proc. § 5-106

DocketMath’s statute-of-limitations calculator uses that 3-year default period when there is no claim-type-specific sub-rule indicated. Based on the jurisdiction data provided, no claim-type-specific sub-rule was found, so the 3-year period applies as the general/default rule.

How the “3 years” rule affects your filing timeline

Practically, the “3 years” period determines the earliest date from which wage/hour conduct may be recoverable when you file suit.

Use this mental model:

  • Pick an intake date (often the filing date or the date you’re planning to file).
  • Count back 3 years.
  • Wage/hour events occurring before that look-back date may fall outside the limitations period (subject to exceptions).

What inputs you’ll typically use in DocketMath

While every case has its own filing chronology, most statute-of-limitations workflows boil down to the same inputs:

  • Relevant event date (for example, the pay period or last date of the alleged violation)
  • Planned filing date (or actual complaint filing date)

Then the calculator determines whether the event date is within the limitations window.

Output interpretation (what changes when dates change)

In DocketMath:

  • If you file later, events near the beginning of the look-back period are more likely to become time-barred.
  • If you file sooner, more wage/hour events fall inside the limitations window.
  • A shift of even weeks or months can matter when you’re near the boundary.

If your case involves a willfulness theory, the “3 years” default may not be the final word; check the Key exceptions section.

Warning: Timing disputes often turn on the exact dates tied to pay practices (e.g., the dates of unpaid overtime calculations). Treat event dates carefully—“when the work happened” versus “when pay was processed” can create different timelines.

Key exceptions

The jurisdiction data provided identifies the general/default 3-year period and states that no claim-type-specific sub-rule was found. Still, FLSA limitations doctrine commonly involves the question of whether conduct was “willful,” which can expand the look-back period.

“Willful” conduct

FLSA litigation frequently distinguishes between ordinary violations and willful violations. When a claim is treated as willful, the limitations period can be longer than the default look-back window.

Because the user-provided jurisdiction dataset does not supply a specific willfulness-adjusted number in Maryland (and because this page must avoid unsupported external rules), this guide keeps the default rule front and center and explains where the willfulness concept can change the analysis.

Practical takeaway:

  • Start with the 3-year default.
  • Then, if your case alleges willfulness, re-run the analysis using the appropriate willfulness parameters in DocketMath (if available in your selected calculator mode) or double-check with your workflow for exception handling.

What “exception handling” means in practice

When an exception potentially applies, the calculator should reflect a different look-back rule, which changes outcomes like:

  • Whether certain pay periods are recoverable
  • Whether particular damages periods are excluded as untimely
  • How much evidence you need to document older pay practices

Pitfall: Don’t assume that “willful” is automatic. Allegations need a factual foundation. Overstating intent can also undermine credibility, while understating it can limit the available damages window.

Evidence that often matters for timing

Even without legal advice, you can think in terms of documentation that typically helps reconstruct timelines:

  • Pay stubs and wage statements
  • Timekeeping records (shift logs, punch records)
  • Employer pay policy documents (overtime rules, scheduling rules)
  • Payroll history showing dates and amounts

Having these organized by date can make the DocketMath timeline analysis cleaner and reduce the risk of using the wrong “event date.”

Statute citation

Maryland jurisdiction default period used for FLSA timing in this workflow:

  • Md. Code, Cts. & Jud. Proc. § 5-106 (general statute referenced for the default limitations period in this Maryland-focused calculator workflow)

The general/default limitations period applied here is:

  • 3 years

Per the dataset note: No claim-type-specific sub-rule was found, so the 3-year period is treated as the general/default rule for this page’s calculator workflow.

Source for the Maryland statute reference:

Use the calculator

DocketMath’s statute-of-limitations tool translates the Maryland default period into a concrete look-back window using dates you supply.

Primary CTA: Statute of Limitations Calculator

Suggested workflow

  1. Enter the relevant event date
    • Use the earliest date you consider part of the actionable wage/hour practice (commonly the start of the unpaid overtime conduct or the last noncompliant pay period, depending on your approach).
  2. Enter your filing date
    • Use the actual complaint filing date (or the target filing date if you’re planning).
  3. Confirm the default limitations mode
    • For this Maryland page, the calculator should default to 3 years unless your workflow includes an exception mode.

How output changes

After you run DocketMath:

  • If the event date is within 3 years of the filing date, the event is generally inside the default limitations window for this workflow.
  • If it’s more than 3 years earlier, it may fall outside the default window.
  • If an exception option (like willfulness) is enabled in the calculator workflow, the look-back period may expand—then you should re-check which pay periods move from “outside” to “inside.”

Quick checklist before you rely on the result

Note: Even with an automated timeline, double-check date inputs—calculator accuracy is only as good as the dates you feed it.

Related reading