Statute of Limitations for Class A / 1st Degree Felony in Florida

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Florida, the statute of limitations (SOL) sets a deadline for the State to file criminal charges or prosecute certain offenses. For a Class A felony / 1st degree felony, Florida uses a general limitations framework found in Florida Statute § 775.15.

DocketMath’s statute-of-limitations calculator is designed to help you translate those rules into a concrete date—by taking key timeline inputs (such as the alleged offense date and tolling or exception dates, if applicable). This article explains the applicable default period and the main situations that can extend it.

Note: No claim-type-specific sub-rule was found for Class A / 1st degree felony in Florida beyond the general/default limitations rule described in § 775.15(2)(d). Treat the period below as the baseline unless a recognized exception or tolling event applies.

Limitation period

Default SOL for Class A / 1st degree felony (baseline rule)

For felony prosecutions covered by § 775.15(2)(d), the general SOL period is:

  • 4 years

This is the default period when no exception or tolling applies. Under the baseline rule, you count from the relevant starting event recognized by the statute (often framed around the time the crime was committed; the statute’s structure governs when the limitations clock begins for the category of offense).

How to use the clock in practice (timeline inputs)

When you use DocketMath, think in terms of these inputs:

  • Alleged offense date (the “start” of the timeline for baseline calculations)
  • Any tolling/exception event date(s) (if the case involves something that pauses or extends time under Florida’s rules)
  • Date charges were filed or the date you’re evaluating (the “end” you want to test against the deadline)

If you enter only the offense date, DocketMath will apply the 4-year baseline. If you add tolling/exception dates that match recognized Florida circumstances, the calculated deadline will shift accordingly.

What changes the output?

Here’s a practical way to think about it:

  • No exception/tolling entered → Output deadline is offense date + 4 years
  • Tolling/exception entered → Output deadline is extended by the amount of time tolled (or otherwise adjusted per the legal effect of that event)

Because SOL calculations can be sensitive to how dates align, always double-check you’re using the correct “event date” for any pause or extension.

Key exceptions

Florida’s SOL framework includes multiple provisions that can affect how long the State has to prosecute. Even if your offense falls under the 4-year general rule, the deadline may change if an exception or tolling event applies.

Below are common categories to watch for in Florida SOL analysis, expressed as decision points you can feed into DocketMath.

1) Tolling due to the defendant’s status or location

Certain circumstances can pause the running of limitations. For example:

  • Defendant is absent from Florida
  • Defendant is otherwise unavailable for prosecution

If the factual record supports a statutory tolling trigger, your effective deadline can move beyond “offense date + 4 years.”

2) Substantive criminal procedure events

Florida also recognizes that particular procedural situations can affect SOL timing depending on how the case proceeds. These aren’t “automatic add-ons”; they depend on the specific statutory basis and timeline.

Checklist idea for your own record review:

3) Multiple counts or related incidents

When a case involves multiple alleged offenses, each count may have its own SOL question. DocketMath can help you run separate deadline calculations per incident, but only if you provide the correct offense date and any relevant exception/tolling dates per count.

Warning: SOL deadlines are highly date-driven. A one-day error in an “event date” (for example, confusing arrest date with charging date) can flip the result from “within time” to “time-barred.” Use the most precise date available in the record you’re working with.

4) Keep the baseline rule clear when exceptions are uncertain

If you can’t confirm the facts needed for a tolling or exception, it’s safer to calculate using the baseline first. DocketMath’s approach (baseline + optional adjustments) supports that workflow:

  • Step 1: Compute baseline 4-year deadline
  • Step 2: Add only those adjustments you can tie to a specific statutory exception/tolling trigger
  • Step 3: Compare the filing date to the adjusted deadline

Statute citation

The general/default SOL period for this category is grounded in:

  • Florida Statute § 775.15(2)(d)4 years

Reference link: https://www.flsenate.gov/Laws/Statutes/2004/775.15?utm_source=openai

This article is built around the general rule for the limitations period. It does not assume an additional Class A–specific sub-rule unless you can identify a separate statutory tolling/exception basis that applies to your timeline.

Use the calculator

Use DocketMath’s statute-of-limitations tool to turn the legal rule into a deadline you can test against filing dates.

Suggested workflow

  1. Enter the alleged offense date
  2. Confirm the applicable baseline (4 years under § 775.15(2)(d))
  3. Add tolling/exception date(s) only if you have specific timeline support
  4. Enter the charging/filing date (or the date you’re assessing)
  5. Review the calculator output:
    • Baseline SOL deadline
    • Adjusted deadline (if tolling/exception inputs were used)
    • Whether the filing date falls before or after the deadline

Input/output example structure (how outputs change)

ScenarioInputs you provideExpected effect on DocketMath output
Baseline onlyOffense date; no tollingDeadline = offense date + 4 years
Tolling supported by factsAdd tolling/exception event date(s)Adjusted deadline = baseline deadline shifted later
Multiple incidentsRun per count with different offense datesDifferent deadlines for different counts

Practical data hygiene tips

  • Use the actual calendar date rather than approximate ranges when possible.
  • If you have multiple related dates (arrest vs. filing), calculate using the date that matches the SOL question you’re testing (commonly the charging/filing date).
  • Keep a short timeline note alongside your calculation so it’s easy to audit later.

Note: DocketMath helps with the math of deadlines. SOL questions can still hinge on legal interpretation of factual circumstances, so treat the output as a timeline screen—not a final legal determination.

Related reading