Statute of Limitations for Class C / Petty Misdemeanor in Montana

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

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

Montana’s statute of limitations (SOL) sets deadlines for when a case must be filed or a charge must be brought. For Class C misdemeanors and other “petty misdemeanor”-type offenses, people often ask whether the clock is the same as for other criminal matters.

This page focuses on the general/default SOL period that applies in Montana as a baseline—because no claim-type-specific sub-rule for Class C / petty misdemeanor was found in the provided jurisdiction data. In other words, you should treat the period below as the starting point unless a specific rule clearly applies to your offense and procedural posture.

Note: SOL rules depend heavily on offense classification and how the matter is initiated (charging document vs. civil filing vs. appeal posture). This page describes the default rule using the Montana statute citation provided, but it’s not a substitute for reviewing the controlling code provisions for your exact situation.

If you want a quick way to compute an end date from key dates, DocketMath’s SOL calculator can help you apply the period to your timeline: /tools/statute-of-limitations.

Limitation period

Default SOL period: 3 years

Based on the jurisdiction data provided for Montana:

  • General SOL period: 3 years
  • General statute: **Montana Code Annotated § 27-2-102(3)

Because the brief explicitly notes that no claim-type-specific sub-rule was found, the 3-year period is presented as the general/default baseline.

How to use the 3-year period (timeline mechanics)

To make the SOL meaningful in practice, you typically need to identify:

  1. The event that triggers the start of the SOL clock (for many matters, this is tied to when the offense occurred; in other contexts, it may connect to discovery or other statutory triggers).
  2. The date the case is filed/charged (or another statutory “filing/commencement” date, depending on the category).

Once those dates are set, the basic method is:

  • End date ≈ Trigger date + 3 years
  • Then compare the actual filing/charging date to that computed end date.

Inputs and output changes in DocketMath

DocketMath’s SOL calculator is designed to turn your timeline into a concrete “deadline” date.

Common inputs you’ll enter include:

  • Start date (e.g., date of alleged offense)
  • SOL length (the tool will default to the Montana general period you select, including 3 years for this page)
  • Optional “as-of” date (to determine whether a filing is likely inside or outside the period)

Your output typically changes in these ways:

  • Earlier start date → earlier SOL deadline
  • Later start date → later SOL deadline
  • Changing the SOL length (if you override it) directly shifts the computed end date
  • Comparing a filing date against the computed deadline can determine whether the action appears timely under the default rule

Key exceptions

Even when a statute provides a default length, real timelines can be affected by exceptions and procedural doctrines. With the information provided for this brief, the only confirmed rule is the default 3-year period under § 27-2-102(3). Still, here are practical categories of issues that often matter when someone is checking an SOL deadline:

  • Tolling or pauses in the clock
    • Some legal events can stop or extend limitations periods.
  • How the SOL is “commenced”
    • Courts may treat the beginning of an action differently depending on whether the matter is initiated by complaint, information, indictment, or another mechanism.
  • Amendments or re-filing
    • Sometimes an amended charge or a later filing can affect timing analysis.
  • Different statutory regimes
    • Some offenses or procedures may be governed by other limitation statutes or specialized rules.

Warning: Do not assume the default “3 years” automatically survives every scenario. Procedural timing rules, tolling events, and how Montana counts the commencement of an action can materially change results.

Because no claim-type-specific sub-rule was provided for Class C / petty misdemeanor, the most responsible approach is:

  • Start with the 3-year default under Montana Code Annotated § 27-2-102(3).
  • Then verify whether any tolling, commencement, or classification-specific rules apply to your particular case facts and posture.

Statute citation

Montana general/default statute of limitations:

  • **Montana Code Annotated § 27-2-102(3)
  • General SOL period: 3 years

This statute is used here as the baseline for Class C / petty misdemeanor timing because the provided jurisdiction data indicates no claim-type-specific sub-rule was found.

Use the calculator

To compute your deadline using DocketMath:

  1. Open DocketMath SOL calculator: /tools/statute-of-limitations
  2. Select Montana (US-MT).
  3. Use the 3-year default period for the limitation length.
  4. Enter your start date (e.g., alleged offense date or another statutory trigger date you have identified).
  5. Optionally enter a filing/charging date to assess whether the filing falls before or after the computed deadline.

Example workflow (numbers, dates, and how results move)

If your start date is January 15, 2023 and you’re applying a 3-year default:

  • Computed SOL deadline would land around January 15, 2026 (subject to how the tool implements date counting).

Now change just the start date:

  • If the start date is January 15, 2022, the deadline shifts to around January 15, 2025.

That’s the calculator’s main value: it makes the deadline concrete, so you can compare it to the real-world date of charging or filing.

Note: SOL deadlines can hinge on exact date-counting conventions and whether statutory events toll or pause the clock. DocketMath helps with the baseline computation; it’s still worth checking any documented tolling or procedural triggers relevant to your matter.

Sources and references

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