Statute of Limitations for Breach of Warranty in Utah

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Utah, a lawsuit for breach of warranty is generally governed by the state’s general statute of limitations (SOL) rather than a special, warranty-specific time limit. DocketMath uses this same default rule in its statute-of-limitations calculator so you can quickly estimate the last day to file based on key dates.

For Utah, the general SOL period is 4 years, and Utah’s general limitation framework appears in Utah Code § 76-1-302. Utah courts also provide a plain-language help page on statutes of limitation (including how the “general rule” is applied).

Note: For breach of warranty claims, this page reflects the general/default 4-year period. The jurisdiction data provided does not identify a separate warranty-specific SOL sub-rule, so the general rule controls for the scenarios described here.

Because warranty disputes frequently involve documents, deliveries, inspections, repairs, and related correspondence, the specific date you start the clock (often the date of breach or tender of goods/services) can matter as much as the number of years.

Limitation period

Utah’s general SOL: 4 years

Utah’s general rule provides a 4-year limitations period for many civil claims that are not otherwise assigned a different time limit. Using the provided jurisdiction data:

  • General SOL period: 4 years
  • General statute: Utah Code § 76-1-302
  • Default applicability: The calculator and this guide treat breach of warranty as falling under the general rule when no warranty-specific sub-limit is identified.

How to think about “when the clock starts”

When you run DocketMath’s statute-of-limitations tool, you’ll typically enter:

  • the date of breach (or the date the warranty was allegedly violated), and/or
  • the relevant transaction date (such as delivery or tender, depending on your facts)

Those inputs change the output because SOL deadlines run from the triggering event, not from when you discover the problem—unless a specific exception applies.

Here’s a practical way to frame inputs when you’re assessing warranty disputes:

  • If the warranty was tied to a specific performance date
    Use the date the warranted performance was due and allegedly failed.
  • If the warranty related to goods delivered
    Use the delivery/tender date connected to the warranty.
  • If warranty obligations continued through repairs or replacement
    Use the event date tied to the alleged breach (for example, a failed repair cycle), not the date you first contacted the seller.

Warning: Many warranty timelines turn on factual dates (delivery vs. repair vs. refusal to cure). A small change to the “breach date” input can shift the calculated deadline by months or years.

Quick reference table

Scenario fact you chooseLikely “start date” to enterHow the result changes
Goods delivered with a stated warrantyDelivery/tender dateEarlier start → earlier SOL deadline
Repair or replacement failsDate the failed remedy occurredLater start → later SOL deadline (if still within 4 years)
Express promise about future performanceDate performance was dueIf performance date is later, clock may start later

Key exceptions

Utah’s general 4-year rule is not always the end of the analysis. Several “time” doctrines can effectively pause, extend, or shift the filing deadline. This section highlights the most common categories to review when you’re using DocketMath (without giving legal advice).

1) Tolling (pauses that extend the deadline)

A “tolling” event can stop the clock temporarily. Depending on the circumstances, tolling may be available where:

  • a party is prevented from bringing a claim due to a recognized legal doctrine, or
  • a statutory tolling rule applies to the claimant or situation.

DocketMath’s calculator is designed for straightforward default calculations. If tolling is relevant to your facts, you may need a second pass beyond the basic 4-year calculation.

2) Accrual changes (when the “breach” date is disputed)

In warranty cases, parties may disagree about:

  • when the breach occurred, or
  • whether the claim accrued upon delivery, tender, non-conformity, or a later refusal to honor warranty obligations.

Because the calculator relies on the date you enter, disputes about accrual can change the outcome substantially. If you’re not sure which date to use, consider running multiple calculations to bracket the range of possible deadlines.

  • Example approach (for planning only):
    • Run with delivery date
    • Run with failed repair date
    • Compare the resulting deadlines to understand the timing risk

3) Contractual limitations (time limits inside the warranty)

Some warranty documents include shorter filing windows than the general SOL. Whether and how those provisions apply can depend on enforceability rules and specific drafting. Since DocketMath focuses on the statute-based deadline, treat contractual shortening provisions as a separate constraint to check.

Pitfall: Don’t assume a warranty letter or contract language automatically controls the SOL timeline. If the warranty documentation includes a “must bring claim within X months” clause, compare it to the statutory 4-year floor rather than choosing blindly.

Statute citation

Utah Code § 76-1-302 is the provided general statute of limitations citation for the 4-year default period referenced in the jurisdiction data.

For plain-language guidance on Utah’s statutes of limitation procedures, Utah courts also publish a helpful overview here:
https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

Use the calculator

DocketMath’s statute-of-limitations calculator is built to convert the 4-year general rule into a specific “file by” deadline.

Inputs you’ll typically provide

Check your case facts and enter the most defensible dates:

  • Breach date (or the date you believe the warranty was violated)
  • Jurisdiction: US-UT (Utah)
  • Claim type selection: If your interface asks for one, choose the option that maps to the general breach of warranty treatment (when no warranty-specific SOL sub-rule is identified)

How output updates

As you adjust inputs, the calculated deadline changes in these ways:

  • Later breach date → later deadline (up to the 4-year cap)
  • Earlier breach date → earlier deadline
  • If you re-run with a different “start date” (e.g., repair failure instead of delivery), compare results to see how sensitive the deadline is

Practical workflow (fast and measurable)

Note: The calculator gives a statutory deadline estimate based on the general/default SOL rule. It does not replace a case-specific legal assessment of accrual, tolling, or enforceability issues.

Primary CTA

Use DocketMath here: **/tools/statute-of-limitations

Related reading