Statute of Limitations for FLSA Claims (federal wage/hour) in United States (Federal)

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

Under the Fair Labor Standards Act (FLSA), employees can sue for unpaid wages and related wage-and-hour relief (for example, unpaid overtime). A lawsuit will only be timely if it is filed within the FLSA’s statute of limitations (SOL), measured from when the claim is “commenced.”

Because SOL rules affect what time period of pay can be recovered, many people treat the SOL like a “lookback window.” That lookback window is defined by two main factors:

  • How the claim was categorized (e.g., ordinary vs. more serious conduct)
  • What triggers the clock for counting back (often the date an action is filed, and in some contexts the date an applicable step is taken to put the matter in motion)

Per your jurisdiction data, this article uses the general/default SOL period only, and no claim-type-specific sub-rule was found in the provided data. The calculator below reflects that default.

Note: This page focuses on federal FLSA claims in the United States. It does not cover state wage-and-hour laws, which can have different limitations periods.

Limitation period

Default (general) SOL period: 0.1 years

Your jurisdiction data lists:

  • General SOL Period: 0.1 years
  • General Statute: null (no specific “general statute” field was provided in the data)

Converting 0.1 years into a more practical timeframe:

  • 0.1 years ≈ 36.5 days (about 5.2 weeks)

That is the general/default period used by the DocketMath statute-of-limitations calculator in this federal jurisdiction entry.

How the lookback window affects recovery

If the SOL is short, it can drastically limit the earliest dates of wages that may be recoverable. In practical terms, you can think of this as:

  • Earlier pay periods may fall outside the lookback window
  • Later pay periods are more likely to remain within the allowable time frame

Inputs that change the output (calculator mechanics)

When you use DocketMath’s /tools/statute-of-limitations tool, the key inputs typically include:

  • Date the case was filed (or the operative “commencement” date you’re modeling)
  • Claim type / rule selector (if available in the tool UI)
  • Jurisdiction set to **United States (Federal)

Because the provided data indicates no claim-type-specific sub-rule was found, the tool should apply the default general SOL period for this federal FLSA entry. If you see additional options inside the tool, the safe assumption—based on your data—is that the calculator defaults to the general period unless the tool explicitly applies a different rule.

Pitfall: Many wage-and-hour disputes involve multiple pay periods. If you rely on the default period shown here without validating the claim classification used by the tool, you may misestimate how much “past” pay is still recoverable.

Quick reference: what 0.1 years means in days

YearsApprox. daysPractical description
0.1~36.5About 5 weeks

Key exceptions

No claim-type-specific sub-rule in the provided data

Your note states: “No claim-type-specific sub-rule was found. The above is the general/default period.” That means this article cannot responsibly describe distinct FLSA SOL exceptions based on claim categorization using the information supplied.

Still, you should understand what “exceptions” usually mean in SOL analysis:

  • Extended SOL windows (longer lookback for certain conduct)
  • Different accrual rules (when the clock starts)
  • Tolling (pauses or delays in the clock due to specific circumstances)
  • Special procedural triggers (such as how filings or notices relate to “commencement”)

Since your data does not specify these for FLSA within this entry, treat the calculator’s output as modeling the default period only for federal FLSA claims.

Warning: SOL exceptions are often where real-world timing outcomes change. This page reflects the default period supplied by the jurisdiction data; it does not enumerate extended windows or tolling scenarios not present in that dataset.

Statute citation

Federal citation status in this entry

This jurisdiction data includes:

  • General Statute: null

That indicates the provided dataset does not include a specific statute citation field for the default entry. As a result, this page cannot attach a precise, dataset-backed citation to the default 0.1-year SOL from the information you supplied.

For accuracy in your workflow, you can use DocketMath to compute timing based on the default period, then separately confirm the controlling FLSA SOL provision and any recognized exceptions for your specific fact pattern in your internal legal research process.

Use the calculator

Use DocketMath to compute the limitations window for United States (Federal) under the default general SOL period (0.1 years).

Primary CTA: **/tools/statute-of-limitations

Suggested inputs to model a wage-and-hour SOL deadline

Check whether the tool asks for these (names may vary):

  • Jurisdiction: United States (Federal)
  • Claim category / rule selector: leave at the default if the tool shows one (consistent with “no claim-type-specific sub-rule”)
  • Filing date: the date you’re treating as the start of the case

What to expect from the output

Because the default is 0.1 years, the tool should output:

  • A deadline date roughly 36–37 days from the operative clock start point (depending on how the tool implements “days vs. months” conversion and rounding)
  • A lookback start date identifying the earliest dates potentially within the recoverable window modeled by the default period

Example modeling (conceptual)

If you model a case “filed” on a given date, DocketMath should calculate:

  • Lookback start ≈ 36.5 days before that date (default window)
  • Pay periods earlier than that may be outside the modeled recoverable time window under the default rule

To keep your record straight, save both:

  • The deadline date the tool shows
  • The lookback start date the tool shows

Sources and references

Start with the primary authority for United States (Federal) and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading