Tolling the statute of limitations in Utah

7 min read

Published October 12, 2025 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Direct answer

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

In Utah, the general/default statute of limitations (SOL) period is 4 years, under Utah Code § 76-1-302. “Tolling” generally means the SOL clock may be paused (not running for a period) and, in some situations, may restart or reset depending on the specific legal trigger and procedural posture.

This guide shows how to use DocketMath to model Utah SOL timing using jurisdiction-aware rules for US-UT. It’s a practical workflow for organizing dates and comparing deadlines under different tolling assumptions—not legal advice.

Note: The SOL period above is the general/default period. No claim-type-specific sub-rule was identified for this brief, so use Utah Code § 76-1-302 as the baseline unless you have reason (from the specific cause of action or charge) to apply a different SOL.

What you need to know

“Tolling” is about timing mechanics. In practical terms, it can change one or more of the following components of the SOL calculation:

Start date: When the limitations clock begins running.
End date: The last day the case/proceeding can be filed.
Paused duration: Periods when the clock does not run.
Pause vs. reset: Some events may merely pause the clock, while others can effectively restart/reset it.
Interruptions/other procedural effects: Certain procedural events may affect whether the clock runs as expected.

For this Utah-focused workflow, you can anchor the calculation to the general 4-year limitations period under Utah Code § 76-1-302 and then test whether particular tolling theories change the effective deadline.

How DocketMath helps: DocketMath is the tool name used here. You provide the US-UT jurisdiction setting plus the relevant event dates (including any dates you believe toll the clock), and it calculates SOL deadlines so you can compare scenarios.

Because tolling depends on facts and legal triggers, treat this as an input-and-output timing model:

change the dates you enter,
rerun,
see how the “deadline delta” changes.

Step-by-step

Use this workflow to toll the SOL in Utah using DocketMath. The goal is to build a date timeline first, then run alternate scenarios.

1) Confirm the baseline SOL period for your timeline

Set jurisdiction to US-UT
Use the general SOL period: 4 years
Anchor to Utah Code § 76-1-302 as the default SOL period for this brief

2) Build a timeline with “clock-relevant” dates

Create a list of dates you might need. Even before you identify a specific tolling trigger, you can still run a baseline model and then update your assumptions later.

Typical timeline entries include:

Event date (the applicable “start point” for SOL under your situation—often tied to accrual or the end of conduct; your facts control)
Filing date (when you intend to file)
Potential tolling trigger dates (start and end of any period you think pauses/restarts the clock)

3) Identify likely tolling categories from your facts

Even though this brief does not identify a claim-type-specific tolling sub-rule, you can still organize potential theories into categories to test them.

Pause-the-clock events (tolling/pausing)
Restart-the-clock events (reset)
Clock-interruption/procedural effects (may change how the clock operates)

If you’re unsure whether your facts match any specific tolling trigger, start with the baseline model first.

4) Enter dates into DocketMath (run baseline first)

Run models in this order:

**Model A: Baseline (no tolling)
- Use your event/start date
- Apply the 4-year SOL length
- Note the computed deadline
Model B: One tolling trigger
- Add the tolling event date(s)
- If your theory is “pause,” the effective SOL should extend by the paused duration
- Recalculate the new deadline
Model C: Multiple tolling triggers
- Add multiple tolling periods (if applicable)
- Watch for overlap—two tolling periods that overlap usually shouldn’t be double-counted
- Recalculate and compare again

5) Compare the “deadline delta” caused by tolling

Track two outputs:

Baseline deadline (Model A)
Tolling-adjusted deadline (Models B/C)

Then compute:

Delta = Adjusted deadline − Baseline deadline

If the Delta is positive and your intended filing date is on/before the adjusted deadline, your chosen tolling assumption is consistent with the timing outcome within the model.

Gentle disclaimer: This workflow helps compute deadlines based on dates and assumptions you enter. It does not replace legal analysis of whether a tolling trigger applies to your specific facts.

Key statutes and citations

Utah general SOL (baseline used in this brief)

Utah Code § 76-1-302
- Provides the general/default SOL period of 4 years used as the baseline in this guide.

Utah Courts self-help reference (general procedural guidance)

Utah Courts’ legal help provides general information about statute limitation procedures and filing concepts:

https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

Warning: SOL rules can vary by claim type or offense/charge category and by the specific tolling trigger. This brief uses the general/default period under Utah Code § 76-1-302 because no claim-type-specific sub-rule was identified here.

Common pitfalls

Tolling calculations often fail because of date selection and counting the wrong time. Common issues include:

Using the wrong start date
- Even a short shift can change whether a filing is timely.
Assuming tolling applies automatically
- Not every investigation delay, communication gap, or negotiation delays the SOL clock by default.
Double-counting overlapping tolling periods
- If two proposed tolling periods overlap, you must ensure overlap isn’t counted twice (or confirm how DocketMath treats overlaps based on its logic).
Relying on general guidance without matching procedural posture
- Courts decide tolling based on statutory conditions and case-specific procedural facts.
Not running multiple scenarios
- If you’re missing early facts, run at least:
  
  baseline,
  
  one-tolling-trigger,
  
  multi-trigger.

Pitfall: People sometimes attempt to “toll from when they learned about the issue.” Under Utah’s general framework, the clock usually depends on the applicable accrual/start point—unless a specific tolling basis changes that.

Run the numbers

Use DocketMath to see how tolling can extend the effective SOL window under the 4-year baseline in Utah Code § 76-1-302.

Scenario table (illustrative structure)

Your exact results depend on your entered dates and selected assumptions.

Scenario	Baseline SOL	Tolling adjustment	Effective deadline outcome
Model A: No tolling	4 years	0 days	Deadline = start + 4 years
Model B: One pause	4 years	+X days	Deadline = start + 4 years + X
Model C: Multiple pauses	4 years	+ (X + Y − overlap)	Deadline moves forward by net paused time

Practical checklist for DocketMath inputs

Before running:

Use the primary CTA

Open DocketMath here:

/tools/statute-of-limitations

As you test different tolling inputs, focus on the outcome comparison:

If tolling (as modeled) adds time and your filing date is still before the adjusted deadline, the timing supports timeliness under that modeled theory.
If your filing date is after both the baseline and adjusted deadlines, tolling (as modeled) likely won’t help.