Statute of limitations rule lens: Florida

6 min read

Published April 8, 2026 • By DocketMath Team

The rule in plain language

In Florida, the default statute of limitations (SOL) for criminal actions is generally 4 years under the general limitations statute.

Specifically, Florida Statutes § 775.15(2)(d) sets out a 4-year period for the prosecution of certain offenses. In this statute-of-limitations rule lens, that 4-year period acts as the general starting point for SOL timing when a more specific rule doesn’t apply.

Important context (as reflected in the materials used for this overview):

  • No claim-type-specific sub-rule was found that would replace this 4-year general period.
  • So this article treats the 4-year period as the general/default SOL rule for Florida in the lens framework below.

What the 4-year clock means (high-level)

SOL timing is usually modeled around three basic ideas:

  • When did the clock start?
  • How long does it run before the State is time-barred from prosecuting (or bringing) the case?
  • Are there any recognized interruptions, tolling, or extensions?

Because SOL “clock” mechanics can depend on the procedural history and the offense details, treat the steps below as a planning tool—not a guarantee about what will happen in any particular case.

Note: Florida SOL analysis can turn on procedural events (like tolling/interruptions) and offense classification details. This lens focuses on the general/default 4-year rule and how to model it in DocketMath.

Why it matters for calculations

SOL is one of the few timing rules that can substantially change case outcomes. Even if the underlying facts stay the same, SOL can change whether prosecution is still timely because it sets a deadline for initiating the case.

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.

Practical effects you can model with a timer

When you’re using this Florida 4-year default SOL lens, the period can affect:

  • Deadlines for filing/charging (the timing window)
  • Early case assessment (whether older conduct may already be time-barred)
  • Document and evidence review scope (you may focus on the relevant time window)
  • Risk evaluation for next steps based on how close dates are to the SOL boundary

The inputs you’ll typically need

To run a meaningful SOL calculation under the default 4-year model, you usually need:

  1. Start date (date the clock begins): Often tied to the offense date or another statutory trigger used in the relevant context.
  2. End date (date the relevant action occurs): Commonly the date of filing/charging (or another procedural milestone you choose as the endpoint for the analysis).

Because the “start date” trigger can be case-sensitive, the most practical approach is to:

  • clearly choose the date you’re using as the trigger, and
  • run alternative scenarios if there are multiple plausible offense dates or trigger events.

How outputs change when dates shift

With a fixed 4-year default period:

  • Moving the end date forward by months can push the matter past the 4-year boundary.
  • Moving the start date backward by weeks or months can expand the window and potentially move the matter from “outside” to “within” the time period.

Example logic (boundary orientation):

ScenarioStart dateEnd date4-year window elapsed?
AJan 15, 2020Jan 15, 2024Yes—at 4 years (boundary case)
BJan 15, 2020Jan 16, 2024Yes—over 4 years
CJan 16, 2020Jan 15, 2024No—under 4 years
DFeb 1, 2019Feb 1, 2023Yes—exactly 4 years

Why DocketMath helps: it turns these date comparisons into a consistent, repeatable calculation using the same rule lens each time.

Warning: Showing “outside the 4-year window” under the default rule lens does not automatically mean the case is barred. Florida SOL doctrine may involve additional doctrines (for example, tolling/interruptions) that are fact- and procedure-dependent.

Use the calculator

DocketMath’s statute-of-limitations calculator supports the kind of timeline math that comes up when applying SOL rules.

For this Florida lens, use:

  • General SOL period: 4 years
  • General statute reference: **Fla. Stat. § 775.15(2)(d)
  • Rule lens model: default 4-year period (no claim-type-specific sub-rule identified here)

Open the calculator here: **/tools/statute-of-limitations

Suggested way to run the calculation in DocketMath

  1. Select jurisdiction: **Florida (US-FL)
  2. Select SOL rule lens: “General/default 4 years (Fla. Stat. § 775.15(2)(d)).”
  3. Enter your trigger/start date (the date you’re treating as when the SOL clock begins).
  4. Enter your procedural end date (the date you’re treating as when the relevant action occurred—often the filing/charging date used in your review).
  5. Review the output window and whether the calculator indicates the end date is inside vs. outside the default period.

Inputs to double-check

Before relying on the output, verify:

  • Are you using the correct start date for your scenario?
  • Are you using the correct end date (filing/charging/procedural milestone)?
  • Does your scenario involve any known interruptions/tolling events? (If yes, you may need a more expanded approach than the default lens.)
  • Are you comparing dates using the same convention (to reduce boundary/off-by-a-day misunderstandings)?

What to expect from the output

When you run the 4-year general period model, the calculator typically provides:

  • the deadline date (start date + 4 years), and
  • an indication of whether your end date is:
    • before the deadline,
    • on the deadline, or
    • after the deadline

Boundary cases can matter. If your end date lands exactly on the computed deadline day, procedural rules may affect the ultimate conclusion—so treat the result as a time-window orientation step, not a final determination.

Sources and references

Start with the primary authority for Florida 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