Statute of Limitations for Class A / Gross Misdemeanor in Utah

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Utah, the statute of limitations (SOL) sets a deadline for the state to file certain criminal charges. For Class A misdemeanors and gross misdemeanors, the relevant SOL is generally 4 years under Utah Code § 76-1-302.

DocketMath’s Statute of Limitations calculator can help you translate that deadline into a concrete “latest filing date” based on the timeline facts you have (for example, the date of the alleged offense and whether any tolling or exceptions might apply). This guide explains the baseline rule first, then the key exception to watch for—without offering legal advice.

Note: An SOL rule tells you when charges must be brought, but it does not determine guilt or whether a case will ultimately be dismissed. Courts can also address other procedural issues beyond the SOL.

Limitation period

Baseline SOL for Class A / gross misdemeanor

For charges covered by Utah Code § 76-1-302, the general SOL period is:

  • 4 years

That means the prosecution must file the case within 4 years from the triggering date the statute uses (often the date of the offense, though the exact “starting point” can be affected by the statute’s terms and any applicable exception).

How DocketMath’s calculator changes the result

Use DocketMath to compute a deadline you can work from:

  1. Enter the “start date” for the SOL calculation (commonly the offense date you’re tracking).
  2. Confirm the charge category (Class A misdemeanor / gross misdemeanor, as applicable to the offense classification you’re working with).
  3. Select whether an exception applies (especially “exception P4,” described below).
  4. Review the calculated SOL end date (the latest date the state can timely commence the prosecution under the selected rule set).

Because the SOL is time-based, even a small change to the starting date can shift the end date. For example:

Start date used4-year SOL end date (baseline)
2021-03-152025-03-15
2021-09-012025-09-01
2022-01-102026-01-10

If you’re comparing two offense dates or alleged conduct dates, run separate calculations—DocketMath will show you how each date changes the deadline.

Quick practical checklist (baseline)

Use this checklist to keep your timeline organized:

Key exceptions

Utah’s SOL framework includes exceptions that can extend or modify the baseline deadline.

Exception P4

Your jurisdiction data flags:

  • Utah Code § 76-1-302 — 4 years — exception P4

When “exception P4” applies, the deadline can differ from the baseline 4-year calculation. The calculator is designed to reflect that by changing the rule applied to compute the end date.

Practical way to decide whether to consider the exception

Because SOL exceptions turn on specific statutory triggers, use your case facts to decide whether the exception might plausibly be in play. Common “exception questions” to sort through include:

If you’re unsure, run the baseline calculation first, then run the calculation again with the exception selected. The difference between the two results can help you frame follow-up questions for review of the charging timeline.

Warning: SOL exceptions aren’t “choose-your-own-adventure.” They depend on statutory conditions and case-specific facts. Treat exception toggles in DocketMath as a way to model possibilities—not as a final determination.

Statute citation

The controlling statute for the SOL period discussed here is:

DocketMath uses the jurisdiction rule above (US-UT) for the Statute of Limitations calculator workflow, so the computed deadline aligns with the 4-year baseline and the flagged exception option.

Use the calculator

You can model the Utah deadline using DocketMath here: /tools/statute-of-limitations.

Recommended input workflow

  1. Open DocketMath Statute of Limitations calculator.
  2. Enter the start date for the SOL clock (commonly the alleged offense date).
  3. Select the relevant misdemeanor category (Class A / gross misdemeanor).
  4. Apply exception P4 if your fact pattern aligns with the calculator’s exception setting.
  5. Save the result and compare it to the filing / charging date you have.

How to interpret the output

After you run DocketMath:

  • If the charging date is after the computed SOL end date, that generally indicates a stronger “timeliness” issue under the selected rule set.
  • If the charging date is on or before the computed end date, the case is modeled as timely under that calculation path.

To reduce mistakes, double-check these items before relying on the result:

Pitfall: Mixing up “incident date” and “report date” is one of the most common reasons SOL computations come out wrong. Use the date that matches the SOL statute’s starting point for your scenario—then verify any exception effects.

Related reading