How to calculate Structured Settlement in Utah

Quick takeaways

• Utah structured settlements are governed by the Utah Structured Settlement Protection Act (Utah Code § 78B-6-1101 through § 78B-6-1108), which primarily affects whether a transfer of structured settlement payment rights is effective—not the basic math used to value an annuity stream.
• Use DocketMath’s structured-settlement calculator to compute a payment schedule and present value for the stream using inputs like payment frequency, payment amount, start date, end date (or number of payments), and your discount/interest assumptions.
• Utah’s rules here should be treated as general/default: no claim-type-specific sub-rule was found in § 78B-6-1101 to § 78B-6-1108, so you generally shouldn’t change the core calculation based on injury/claim category.
• The most common “Utah-specific” impact is whether your scenario involves a payment-rights transfer and whether it can be effective under statute, rather than changing the discounting formula.

Inputs you need

Before you open DocketMath’s Structured Settlement tool, gather inputs that drive both (1) the cash-flow schedule and (2) the calculation output. Utah law may affect whether certain transfers are effective under Utah Code § 78B-6-1101 through § 78B-6-1108, but the underlying annuity/payment schedule math usually relies on the same core data.

Cash-flow inputs (for the payment stream)

• Initial payment amount (e.g., $25,000)
• Payment frequency (annual, semiannual, quarterly, monthly)
• Number of payments or end date
• Start date (date the first payment is due)
• Payment timing convention

  • Example: “beginning of each period” vs. “end of period”
  • If your settlement agreement specifies timing, mirror it in your inputs.

Discounting / valuation inputs

• Discount rate (annual) that DocketMath should use for present value
• Compounding basis (if the tool asks—e.g., annual vs. monthly compounding)
• Valuation date (the date you’re measuring value “as of”)

Utah-aware constraint inputs (transfer modeling)

If your scenario involves a transfer (e.g., selling rights to future payments), collect enough detail to represent the situation as “payment stream” vs. “payment-rights transfer” in your workflow:

• Whether the transferee would receive payment rights directly or indirectly
• Relevant agreement dates tied to the transfer
• Whether the structured settlement obligor/issuer would be asked to pay the transferee

These inputs don’t usually change the numerical PV of the stream, but they help you apply the jurisdiction-aware question the Utah statute addresses—when a transfer is effective and when an obligor/issuer is (or isn’t) required to pay a transferee.

How the calculation works

DocketMath’s structured-settlement calculator converts your payment-stream inputs into outputs such as a payment schedule and a present value (PV) figure (depending on which fields you provide). Think of the process as two layers: (1) build the timeline, then (2) discount.

Step 1: Build the timeline of payments

Using your:

• Start date
• Payment frequency
• End date or number of payments

DocketMath generates a sequence of payment dates, for example:

• Payment 1: start date
• Payment 2: start date + 1 interval
• Continue until the end condition is reached

If you have escalating payments (e.g., increases by a fixed percentage over time), enter that escalation pattern if supported by the tool. Escalation can materially change PV even when frequency stays the same.

Step 2: Apply the discount rate to compute present value

To compute present value, each payment is discounted back to the valuation date. The general concept is:

[ PV = \sum_{i=1}^{n} \frac{PMT_i}{(1+r)^{t_i}} ]

Where:

• (PMT_i) = payment amount for payment (i)
• (r) = annual discount rate (as used by the tool)
• (t_i) = time from valuation date to the payment date (in years, per the tool’s timing convention)

How it affects outputs:

• Higher discount rate → lower PV
• Lower discount rate → higher PV

Step 3: Utah jurisdiction-aware checks (transfer effectiveness)

Utah’s structured settlement provisions (Utah Code § 78B-6-1101 to § 78B-6-1108) primarily address transfer legality/effectiveness and whether payment must be redirected to a transferee.

As a high-level summary of the statute’s approach:

• No direct or indirect transfer of structured settlement payment rights is effective, and
• no structured settlement obligor or annuity issuer is required to make payments to a transferee,
  unless statutory conditions are satisfied under Utah Code § 78B-6-1101 to § 78B-6-1108.

In a DocketMath workflow, that means:

• Your math still computes the PV/value of the payment stream (that’s the spreadsheet-style valuation).
• Your interpretation of whether a “transfer scenario” is operative should reflect that Utah law may make certain transfers ineffective until the statutory requirements are satisfied.

Default rule reminder: no claim-type-specific sub-rule found

You should model Utah’s rules as general/default rather than splitting the calculation by claim type. For the cited Utah act (§ 78B-6-1101 to § 78B-6-1108), no claim-type-specific sub-rule was found in the jurisdiction guidance you provided.

Common pitfalls

These issues can lead to incorrect results—especially if someone blends “contract math” with Utah transfer compliance.

• Using the wrong valuation date

  • PV changes materially if you shift the “as of” date, particularly when there are near-term payments.
• Mismatched payment timing

  • “Beginning of period” vs. “end of period” can shift discounted dates and PV. If the agreement is explicit, follow it.
• Discount rate format errors

  • Entering 6 instead of 0.06 (or vice versa) can drastically distort PV.
• Ignoring payment escalation

  • If payments increase by a stated percentage over time, treating them as flat can understate or overstate PV.
• Assuming Utah transfer rules don’t apply because you’re “only doing math”

  • Utah Code § 78B-6-1101 to § 78B-6-1108 restricts when transfers are effective and when obligors/issuers must pay transferees.
• Assuming claim type changes the calculation method

  • Per the available guidance, no claim-type-specific sub-rule was found in the Utah act—use general/default modeling logic.
• Forgetting that “transfer modeling” ≠ “payment-stream valuation”

  • DocketMath can compute the value of a stream, but Utah law can still affect whether the transferee can effectively receive the rights.

Pitfall to avoid: If you’re producing a worksheet for a transfer scenario, keep two outputs separate—(1) PV of the payment stream (math) and (2) transfer effectiveness assumptions (jurisdiction/legal constraints). Combining them into a single “final number” can mislead stakeholders.

Sources and references

• Utah Structured Settlement Protection Act, Utah Code § 78B-6-1101 through § 78B-6-1108
  https://le.utah.gov/xcode/Title78B/Chapter6/78B-6-P11.html

  • Statutory language summarized for this guide: no direct or indirect transfer of structured settlement payment rights shall be effective and no structured settlement obligor or annuity issuer shall be required to pay any transferee unless statutory requirements are met.

Next steps

1. Open DocketMath’s structured settlement tool: /tools/structured-settlement
2. Enter cash-flow inputs first

   • Confirm dates, payment frequency, number of payments or end date, and escalation (if any).
3. Set valuation date and discount rate

   • Use a rate consistent with your valuation methodology or stakeholder assumptions.
4. If modeling a transfer, tag the scenario

   • In your worksheet notes, reflect that Utah’s § 78B-6-1101 to § 78B-6-1108 restricts when transfers are effective and when payments to transferees are required.
5. Run sensitivity checks

   • Adjust the discount rate by a few points and observe how PV changes.
   • Re-validate payment timing against the settlement agreement.

Related reading

• How to calculate Structured Settlement in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Structured Settlement in Philippines — Worked example with real statute citations
• Inputs you need for Structured Settlement in Philippines — Input checklist with sourcing guidance