How to run Treble Damages in DocketMath for Utah

Step-by-step

Run this scenario in DocketMath using the Treble Damages calculator.

You can run Treble Damages calculations in DocketMath for Utah (US-UT) by using the Utah general statute of limitations (SOL) rule and entering the dates needed for DocketMath’s jurisdiction-aware limitations timeline. This walkthrough focuses on how to operate the tool—not legal advice or legal strategy.

1) Open the Treble Damages calculator (Utah)

Start with the tool page:

• /tools/treble-damages

If you’re already inside DocketMath, use the same path (or search for the tool name) and navigate directly to:

• /tools/treble-damages

2) Confirm jurisdiction is set to Utah (US-UT)

Next, make sure the jurisdiction is set to Utah (US-UT).

• In DocketMath, select US-UT (Utah) in the jurisdiction selector (the label may appear as “Utah” or “US-UT,” depending on the UI).
• If this tool is already locked to Utah, you can skip this step.

Why it matters: DocketMath’s limitations/timeline check is jurisdiction-aware, so selecting US-UT helps ensure the tool uses Utah’s SOL framework for the calculation workflow.

3) Enter the base amount to be trebled

Now enter the base damages amount—the non-trebled figure (the amount you want multiplied by 3).

A typical input workflow looks like this:

• Base damages ($): Enter the underlying damages amount before trebling.

DocketMath should then compute:

• Treble damages ($) = Base damages × 3

**How outputs change (multiplier effect)

• If you increase the base damages by a factor, the treble total changes proportionally.
• Example: If base damages doubles, the treble damages should also double (because the multiplier remains ×3).

4) Add timing inputs so DocketMath can apply Utah’s general SOL window

To reflect Utah’s general SOL framework, you’ll need to enter the relevant dates that the Treble Damages tool uses for its limitations timeline check.

Because the exact date fields can vary by tool design, look for inputs like:

• event/operative date
• filing date (or a similar “comparison” date)

Then enter the dates that apply to your timeline.

Utah’s general/default SOL period is:

• 4 years
• Utah Code § 76-1-302
• (General SOL overview source) https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

**How outputs change (limitations window)

• If the time between the operative/event date and the filing date is within 4 years, the tool’s timeline check should indicate it’s within limitations (wording may vary).
• If that lapse is more than 4 years, it should indicate outside limitations.

Gentle reminder: Treat the output as a computational check of the rule period you entered (general 4 years), based on the dates you provided—not as a final legal conclusion.

5) Review the calculator output fields carefully

After running the calculation, review the results in two buckets:

1. Damages math

   • Your base damages
   • The ×3 multiplier effect
   • The resulting treble damages total

2. **Utah timeline check (based on the general SOL)

   • The 4-year limitations window
   • Whether your entered dates fall within or outside that window

If the tool shows a status indicator (for example, “within/outside” or similar), interpret it as a rule-and-dates comparison. Confirm it matches:

• the date order you entered
• the SOL period being used (4 years under Utah Code § 76-1-302, general/default)

6) Capture your results for review and reruns

Before you move on, capture your key inputs and outputs so you can rerun quickly if you adjust dates or amounts.

A practical set to save in your notes:

• Base damages input
• Treble damages output
• The two dates you entered for the timeline check
• The computed “time elapsed” (if shown) and the SOL comparison status

This makes it easier to validate the tool’s behavior and to compare scenarios side-by-side (for example, if you test alternate dates).

Common pitfalls

Treble damages calculations can break down for reasons that have nothing to do with the ×3 multiplier. Here are the most common issues to watch for when using DocketMath for Utah (US-UT):

• Utah’s general/default period is 4 years under Utah Code § 76-1-302.

• Since no claim-type-specific sub-rule was found for this treble damages calculator workflow, you should rely on the general 4-year default rather than substituting another period.

• If you reverse the dates, the elapsed time can flip from “within 4 years” to “outside 4 years.”

• Double-check which date the tool labels as the “starting” date versus the “comparison” date.

• The tool expects base damages (non-trebled).

• If your base amount already includes trebling, then multiplying by ×3 will effectively treble an already trebled number.

• The calculator can only evaluate what you entered. Make sure you reviewed:

  • base damages
  • both dates (and the date order)
  • the SOL basis (general 4 years under Utah Code § 76-1-302)

• This guide uses Utah’s general/default 4-year SOL because no claim-type-specific sub-rule was identified for this setup.

• If your underlying facts truly require a different limitations/accrual framework, you’ll need a workflow adjustment beyond this general default.

Try it

Use this quick run-through to validate your DocketMath inputs and the Utah-specific SOL logic for the general 4-year window.

Open the Treble Damages calculator and follow the steps above: Run the calculator.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Quick sandbox checklist

• the operative/event date the timeline should start from

  • the filing date (or the tool’s equivalent comparison date)

What you should see

• Treble damages should equal base × 3
• The Utah limitations comparison should use:

  • 4 years
  • Utah Code § 76-1-302 (general/default)
• If your chosen dates are within 4 years, the timeline check should indicate within the general window; if they exceed 4 years, it should indicate outside.

Validation tip

Run two calculations back-to-back:

1. Use dates that are clearly within 4 years
2. Use dates that are clearly over 4 years

If the status doesn’t change between those two scenarios, re-check the date fields you used (especially the start/end date roles).

Related reading

• Treble Damages Calculator Guide for Alabama
• Treble Damages Calculator Guide for Arizona
• Treble Damages Calculator Guide for Colorado