How to run Structured Settlement in DocketMath for Utah

Step-by-step

This guide walks you through running a Structured Settlement calculation in DocketMath for Utah (US-UT). It also ties the output to Utah’s general statute of limitations so your planning aligns with the time window referenced in Utah Code § 76-1-302.

1) Open the Structured Settlement calculator

1. Go to https://your-site.com/tools/structured-settlement (your primary CTA).
2. Select the jurisdiction as US-UT (Utah).

Why this matters in DocketMath: DocketMath applies jurisdiction-aware rules, so the calculator can use Utah-specific assumptions—here, including the statute limitation framework described in this guide.

2) Enter case timing inputs (drives projections)

Structured settlement models typically require a start/anchor point and a payment schedule. In DocketMath, enter timing inputs that match your scenario, such as:

• Claim / injury date (or event date): the anchor date for when the claim accrued (as defined for your matter).
• Desired first payment date: when the first installment begins.
• Number of installments: total payments in the plan.
• Payment frequency: e.g., monthly, quarterly, annual.
• Payment amount pattern: whether payments are constant or change over time (if DocketMath supports a step pattern, use that).

How inputs change outputs: As you enter these values, the calculator updates the projected cash flow timeline. If the model includes discounting, the date spacing will also affect present value calculations (later payments generally reduce present value, holding other assumptions constant).

3) Enter economic assumptions (drives value)

Next, provide the economic inputs that affect valuation. Common fields include:

• Discount rate / present value rate (if prompted)
• Payment inflation adjustment (if prompted)
• Payment escalation (if your plan increases over time)

Output impact to expect:

• Higher discount rate → typically reduces the present value of future payments.
• Escalation / inflation adjustments → generally increase later nominal payments and can change present value depending on the discount rate used.

Tip: If you’re comparing scenarios (e.g., two schedules with the same nominal total), keep the discount and escalation inputs consistent so differences come from timing—not changed assumptions.

4) Run the calculator and review the structured settlement outputs

After completing your inputs, run the calculation. Review results in these buckets:

1. Schedule outputs

   • Dates for each installment
   • Payment amounts per period

2. Summary outputs

   • Total nominal payout
   • Present value (if included by the model)

3. Comparative outputs (if included)

   • Comparison between lump-sum and structured amounts
   • Any “equivalent lump sum” figure used by the model

Utah check: If jurisdiction settings influence downstream logic, confirm you’re actually running under US-UT during the run. The goal is to ensure the limitation window logic you’re referencing stays aligned with Utah defaults.

5) Tie the results to Utah’s statute of limitations (general default)

For planning purposes, align your key decision dates with Utah’s general statute of limitations period.

• Utah’s general statute of limitations period is 4 years under Utah Code § 76-1-302.
  Source (Utah Courts guidance page): https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

Important clarity for this workflow: No claim-type-specific sub-rule was found for this setup. That means you should use the general/default 4-year period as your baseline.

Workflow-friendly way to apply the 4-year rule (not legal advice):

• Compute the limitations cutoff window as: event date + 4 years
• Then compare your structured settlement schedule to that window:

  • Are key payments and decision milestones within or after the 4-year general default period?
  • Does the timing affect how you’re modeling value or planning next steps?

In short: use DocketMath to model the cash flows, and use the 4-year general default as the timing guardrail for a first-pass Utah SOL sanity check.

6) Sanity-check your dates against the 4-year window

To keep your structured settlement model coherent, do a quick checklist:

If you discover the scenario may involve a specialized limitation rule, you’ll need separate analysis beyond this general default workflow.

Common pitfalls

Structured settlement runs can look “correct” while still producing misleading conclusions because of small input or assumption mismatches. Watch for:

1. Using the wrong limitations baseline

   • This guide uses the general/default 4-year period under Utah Code § 76-1-302.
   • If your matter involves a claim type with a specialized SOL, the general default may not match reality.

2. Confusing the event/accrual anchor with the filing date

   • Structured settlements often focus on payment start dates.
   • SOL analysis depends on the accrual/event anchor used for the limitations computation.
   • If those differ, your comparison against the 4-year window can become unreliable.

3. Forgetting frequency and escalation settings

   • “Monthly” vs “quarterly” can materially change both:

     • Total nominal payout timing
     • Present value
   • Escalation assumptions can also significantly change late payments.

4. Discount rate drift

   • Even modest discount-rate changes can create large present value differences over longer schedules.
   • Keep discounting consistent across scenarios unless you intentionally test sensitivity.

5. Assuming DocketMath auto-applies every Utah rule

   • DocketMath’s jurisdiction-aware behavior supports Utah general/default alignment for this workflow.
   • It does not replace claim-type-specific legal analysis where specialized limitation rules exist.

Try it

Use this “do-this-now” sequence to validate the workflow quickly:

1. Open https://your-site.com/tools/structured-settlement.
2. Set jurisdiction to US-UT.
3. Start with a simple schedule to reduce variables:

   • Enter a single event date anchor
   • Set first payment date shortly after the event date
   • Use equal installments (for example, 12 monthly payments)
4. Run once using a single baseline discount rate you intend to use for the project.
5. Modify only one input at a time and watch the effect:

   • Change discount rate → observe present value shift
   • Change payment frequency → observe total nominal and timeline changes
   • Push payment dates later → observe present value drop

Finally, do a Utah SOL sanity check using the 4-year window from Utah Code § 76-1-302:

• Ask: “Do my key decision dates fall comfortably within or outside the 4-year general default timeframe?”
• Remember: this workflow uses only the general/default SOL because no claim-type-specific sub-rule was provided in this setup.

Related reading

• Structured Settlement Calculator Guide for Alabama
• Structured Settlement Calculator Guide for Arizona
• Structured Settlement Calculator Guide for Colorado