Statute of Limitations for Continuing Violation Doctrine in Missouri

6 min read

Published March 22, 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.

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Missouri’s “continuing violation” concept often comes up when a plaintiff alleges wrongful conduct that repeats over time rather than occurring in a single, discrete event. In practical terms, the question is whether the statute of limitations (SOL) starts running at the time of the first act, or whether later acts within the alleged pattern keep the claim alive.

For Missouri, the reliable starting point is the general limitations framework in the criminal code for “time limits” and related procedural constraints reflected in Mo. Rev. Stat. § 556.037. Per the jurisdiction data provided for this reference page, Missouri uses a 5-year general SOL period, and no claim-type-specific sub-rule was found in this context for a different baseline period. That means the default SOL period you should plan around is 5 years.

Note: This page is a reference for how Missouri’s general SOL period is set up in Mo. Rev. Stat. § 556.037. It does not resolve every “continuing violation” dispute, because whether conduct is treated as continuing can depend on the specific allegations and the timing of the last wrongful act.

Limitation period

The default SOL baseline (Missouri)

Based on Mo. Rev. Stat. § 556.037, the general limitations period is:

5 years (general/default SOL period)

Because no claim-type-specific sub-rule was found in the provided jurisdiction data, the safest way to apply the statute to a continuing-violation scenario is to treat 5 years as the default starting period for the relevant limitations analysis.

How “continuing violation” affects timing (conceptual mechanics)

Continuing-violation arguments typically work by shifting the “trigger” from an earlier event to a later one. Practically, people use one of these timelines:

Discrete-act view: SOL runs from the date of the first alleged wrongful act.
Continuing-violation view: SOL runs from the date of the last act in the continuing course, or at least a later “end point,” so long as the conduct qualifies as a continuing violation.

Missouri courts do not treat every repeating harm the same way. So, even though the baseline SOL is 5 years, what changes in a continuing-violation dispute is the date you argue should start the clock—often the earliest vs. latest date covered by the alleged continuing conduct.

Planning the key dates you need

To use DocketMath effectively for a continuing-violation-style timeline, assemble:

Last alleged wrongful date (often the “end point” you argue)
First alleged wrongful date (sometimes the opposing side’s “trigger”)
Filing date (or intended filing date)
Optional but useful:
- Any tolling facts you believe apply (equitable or statutory tolling can affect results, but the availability depends on the specific posture and claims)

Then you can model both scenarios:

Scenario A: SOL measured from the first alleged act
Scenario B: SOL measured from the last alleged act

The difference between A and B is where the continuing-violation theory usually lives.

Quick example of how the clock changes

If an alleged pattern began on January 10, 2019 and allegedly continued through March 5, 2023, then:

Under a discrete-act approach, the SOL clock might be argued to start January 10, 2019.
Under a continuing-violation approach, the SOL clock might be argued to start closer to March 5, 2023.

With a 5-year baseline, both approaches can land differently relative to a filing date—especially when the filing date falls within the final 60–180 days before 5 years would expire under the discrete-act framing.

Key exceptions

Because this page focuses on Missouri’s general/default limitations period, exceptions are best thought of as “things that change the clock.” Common categories that can alter outcomes include:

Different triggering dates: whether the court views the conduct as having a definable end point versus discrete separate acts.
Tolling: circumstances that legally pause or extend time periods.
Procedural timing issues: when notice, service, or other procedural prerequisites affect “when” a claim is considered filed for limitations purposes.

Even with these caveats, the core planning rule remains straightforward:

Start with 5 years from Mo. Rev. Stat. § 556.037
Then adjust the analysis based on:
- the date you argue starts the SOL
- any tolling or procedural facts that apply to your situation

Warning: Continuing-violation theories can fail if the alleged conduct is characterized as multiple discrete events rather than a single continuing course. That characterization can materially change the “clock start” date, which in turn changes whether the claim appears timely under the 5-year baseline.

To keep the analysis practical, use a checklist before you rely on any “continuing” framing:

Statute citation

Mo. Rev. Stat. § 556.037 (General limitations framework used here as the default period)
Source: https://law.justia.com/codes/missouri/title-xxxviii/chapter-556/section-556-037/

Default period used in this guide: 5 years.

Per the provided jurisdiction data, no claim-type-specific sub-rule was found that would create a shorter or longer default SOL period for a different category under this reference page. Accordingly, this content uses 5 years as the general baseline.

Use the calculator

DocketMath’s statute-of-limitations calculator helps you model the timing that matters most in continuing-violation arguments: the date the clock starts and how it compares to the filing date.

Inputs to enter (for a continuing-violation timeline)

Use these inputs in the calculator:

Start date (Scenario A): first alleged wrongful date
Start date (Scenario B): last alleged wrongful date
End date / filing date: the date you’re evaluating for timeliness

Then repeat the run for both scenarios to compare results.

What to expect from the outputs

Because the default SOL period in Missouri for this reference framework is 5 years, the calculator will effectively answer:

“If the SOL starts on the start date I selected, what is the last day it would be timely under a 5-year clock?”

When you shift from Scenario A (first act) to Scenario B (last act), you typically see:

More time remaining under Scenario B
A potentially timely classification for filings that fall within the final 5-year window measured from the last alleged act

Practical comparison workflow

Run #1: Start = first alleged wrongful act, End = filing date
Run #2: Start = last alleged wrongful act, End = filing date
Compare the “timely/late” output (and the calculated SOL deadline) across both runs

Note: If the calculator outputs a tight deadline (for example, within 30–90 days), timing details become especially significant. Small date differences—like the exact last date of alleged conduct—can shift the outcome.

If you want to formalize the “continuing violation” timeline into your document work, keep your date list consistent:

Use the same filing date in both scenarios
Keep the SOL basis aligned (the 5-year general period from the Missouri general framework referenced above)

Primary CTA

Use DocketMath here: /tools/statute-of-limitations