Statute of limitations for rape in Tennessee
5 min read
Published October 11, 2025 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page includes a legal claim or source that failed the current primary-source review.
Rule or statute summary
Run this scenario in DocketMath using the Statute Of Limitations calculator.
In Tennessee, the statute of limitations (SOL) for rape is governed by the state’s criminal limitations framework (rather than a separate “civil” limitations clock). Based on the jurisdiction data provided, Tennessee’s general/default SOL period is 1 year for the applicable prosecutions.
DocketMath’s statute-of-limitations calculator is intended to apply that same general/default structure. Unless you have specific case details that point to a different procedural path (for example, a distinct statutory trigger/tolling event), the calculator will use the general/default criminal SOL period.
Key clarification (from the brief): no claim-type-specific sub-rule was found for “rape” in the data provided. So this article clearly states Tennessee’s general/default limitations period as the governing starting point.
Note: This post explains the SOL rule at a high level and shows how to use DocketMath’s calculator. It is not legal advice and cannot guarantee how a particular court will treat the facts of a specific case.
What “1 year” means in practice
A “1-year” criminal SOL generally requires the state to commence prosecution within one year of the relevant triggering event. The exact triggering event can depend on the statute’s language and the facts (and may be affected by procedural events or tolling doctrines). For this content, the practical takeaway is:
- The SOL “clock” is treated as running on a 1-year schedule under the general/default framework.
- When you compare dates, the most important step is making sure your trigger date matches the workflow you’re using (for example, commonly the offense date, unless your analysis uses a different trigger consistent with the governing rule).
Using DocketMath to estimate timing
To estimate whether a prosecution would fall within the SOL window, you’ll typically enter:
- Jurisdiction: Tennessee (US-TN)
- Trigger date: the date you’re using as the start point (often the offense date in a simplified workflow)
- Optional: filing/charging date, if you want a within/after comparison
Then the calculator outputs, in plain terms:
- Calculated deadline (based on the 1-year general/default approach)
- Whether your selected filing/charging date is before or after that deadline
Because SOL triggering language and tolling can vary by circumstances, treat the result as an estimate based on the general/default period—not a prediction of a particular court’s outcome.
Citations
The general/default SOL period framework reflected in the provided jurisdiction data is:
- Tennessee Code Annotated § 40-35-111(e)(2)
Source: Justia code text (Title 40, Chapter 35, Part 1, § 40-35-111)
https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/
General/default period used here: 1 year
General Statute referenced: Tennessee Code Annotated § 40-35-111(e)(2)
Brief finding stated in the prompt: no claim-type-specific sub-rule was found for “rape,” so this article uses the general/default period as the governing starting point.
If your situation involves additional procedural facts (such as whether a prosecution was already underway, or whether any tolling doctrine could apply), the general/default model may not fully capture the legal analysis. When in doubt, confirm the exact trigger and any tolling considerations.
Use the calculator
Use DocketMath’s statute-of-limitations tool to apply the Tennessee 1-year general/default SOL based on Tennessee Code Annotated § 40-35-111(e)(2).
Primary CTA: https://docketmath.com/tools/statute-of-limitations
Before you run it, confirm these inputs match your objective:
Run the Statute Of Limitations calculation in DocketMath, then save the output so it can be audited later: Open the calculator.
Inputs to enter (checklist)
How outputs change when you adjust dates
In a practical workflow, changing your dates affects the computed deadline like this:
| If you change… | Then the calculator typically does this… |
|---|---|
| Trigger/offense date moves forward | The SOL deadline moves forward by about the same time span |
| Trigger/offense date moves backward | The SOL deadline moves backward accordingly |
| Filing/charging date moves forward | The “within/after deadline” result becomes less favorable (closer to or beyond the deadline) |
| Filing/charging date moves backward | The “within/after deadline” result becomes more favorable |
Example workflow (basic date math)
If your trigger/offense date is 2025-01-10, a simplified 1-year general/default deadline would be 2026-01-10.
- If your filing/charging date is 2026-01-11, it would be after the computed deadline under this general/default approach.
- If your filing/charging date is 2026-01-10 or earlier, it would be within the computed window under this simplified model.
Again, SOL outcomes can turn on statute-specific triggering language and any tolling/procedural events—so use this as a calculation estimate built on the general/default period.
Related reading
- Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
- Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
- Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator
