How to calculate Structured Settlement in Michigan

Quick takeaways

• In Michigan (US-MI), calculating a structured settlement with DocketMath generally means modeling when payments will be made and how long they’ll last, then translating that schedule into a single present value using a discount rate and the correct timing conventions.
• Michigan law does not provide a separate, claim-type-specific “default period” rule for structured settlements in the way some jurisdictions do. If you don’t have a tailored rule from the settlement agreement, use the general/default period approach and rely on the contract schedule for duration.
• DocketMath’s structured-settlement calculator is designed to match your settlement terms: enter the payment pattern (start date, frequency, number of payments or end date), then choose the valuation method (typically present value) to produce comparable numbers.
• Keep an eye on timing: shifting a payment stream by even a few months can materially change present value.

Inputs you need

Use the DocketMath structured-settlement tool with a clean set of inputs. Before you start, gather the terms you want to model.

Core inputs (nearly always required)

• Settlement type (e.g., periodic payment stream, annuity-funded structure, or a hybrid with lump sum)
• Payment schedule

  • Start date (YYYY-MM-DD)
  • Payment frequency (monthly, quarterly, annual)
  • Amount per payment (fixed) or a timeline if amounts change
  • End condition (number of payments or end date)
• Discount rate to compute present value

  • Annual rate (e.g., 2.5%) and whether compounding is annual or per period
• Valuation date (the “as of” date for present value)

Michigan jurisdiction-aware setup

Even when the calculation is mostly math, Michigan-specific context matters for how you interpret the schedule:

• No claim-type-specific sub-rule was found for default periods. That means you should use the general/default period for duration assumptions when the agreement does not specify a tailored period rule.
• If your agreement contains an explicit term (e.g., “20 years certain, then contingent”), treat that as primary: the contract schedule controls the calculation inputs; Michigan’s general/default period handling fills gaps only when duration is unclear.

Optional inputs (use if your settlement has complexity)

• Inflation escalation (e.g., 2% yearly increases to future payments)
• Arrearages or partial first payment (if the first payment is pro-rated)
• Lump sum components

  • One-time payment amount
  • Date of the lump sum
• Contingencies (e.g., payments depend on a life event)

  • Note: if the structure is life-contingent, you’ll need an actuarial assumption set—DocketMath can still model scenarios if you provide the needed parameters.

How the calculation works

DocketMath’s structured-settlement calculation is built around three steps: (1) build the payment timeline, (2) discount each payment to the valuation date, and (3) sum to a present value.

1) Build the payment timeline from your schedule

Given:

• Start date: S
• Frequency: e.g., monthly
• Amount per payment: A
• End condition: end date E or number of payments N

DocketMath generates a list of payment dates:

• Payment 1: first payment date (often at/after S)
• Payment k: S + (k-1) * period_length
• The stream stops when it hits E or after N payments.

This timeline is where many mistakes happen, so verify:

• The first payment date (some agreements specify “within 30 days of judgment” rather than a calendar date)
• The last payment date (whether the end date is inclusive)

2) Apply discounting to compute present value

For each payment date D_i with amount P_i, compute the discount factor based on:

• Valuation date V (as of date)
• Discount rate r
• Compounding convention (annual or per period)

A typical present value form is:

• PV_i = P_i / (1 + r)^(t_i)

Where t_i is the time in years from V to D_i using the tool’s chosen convention.

Then:

• PV_total = Σ PV_i (plus any lump sums discounted as applicable)

3) Use Michigan general/default period handling when terms are not explicit

For this Michigan workflow, the key rule-of-thumb is:

• If the settlement agreement spells out duration, use it (e.g., “120 monthly payments” or “payments for 20 years,” including any specified conditions).
• If the agreement does not specify a claim-type-specific default duration rule, use the general/default period approach rather than inventing a special sub-rule tied to claim type.

Output you should expect

When you run DocketMath with the structured-settlement calculator, you typically get:

• Payment schedule summary (number of payments, first/last payment date)
• Present value (PV) of the periodic stream
• Breakout by component (periodic vs lump sum) if included
• Scenario totals if you run multiple discount rates or escalation assumptions

If you’re comparing settlement options, repeat the calculation with:

• Different discount rates (e.g., 2.0% vs 4.0%)
• Different start dates (e.g., delayed by 6 months)
• With/without inflation escalation

Common pitfalls

Use this checklist to avoid the most frequent calculation errors in Michigan structured-settlement modeling.

Timeline and date errors

• First payment date misread (calendar date vs “within X days”)
• Monthly vs quarterly frequency entered incorrectly
• Off-by-one on the number of payments (end date inclusive vs exclusive)
• Valuation date entered after some payments already occurred (which can lead to misleading PV depending on the tool’s conventions)

Discounting and compounding mistakes

• Discount rate provided as “2.5” when the tool expects “0.025”
• Wrong compounding convention (annual vs per period)
• Mixing escalation and discounting incorrectly (e.g., applying inflation twice)

Michigan jurisdiction-aware misassumptions

• Using a claim-type-specific default period that is not present in the available Michigan rule set for this workflow
• Applying a “default” duration instead of the agreement-defined schedule

Sources and references

• Michigan jurisdiction-aware setup for period handling: no claim-type-specific sub-rule was found, so apply the general/default period approach when the agreement does not specify a tailored duration rule.
• Tool workflow references:

  • DocketMath structured-settlement calculator (US-MI)
  • DocketMath inputs model: payment schedule → timeline → present value discounting

Next steps

1. Start the model in DocketMath via: /tools/structured-settlement
2. Enter your settlement schedule:

   • Start date, frequency, payment amount, and end condition.
3. Confirm the valuation date you want to compare against (e.g., “as of today” or a specific court date).
4. Choose a discount rate consistent with your valuation assumptions.
5. Run one baseline model, then stress test:

   • Shift start date by ±3 months
   • Change discount rate by ±1%
   • Toggle inflation escalation (if applicable)
6. If duration is unclear, decide whether you will:

   • Use the agreement’s duration (preferred), or
   • Apply the general/default period model due to missing terms (and document the assumption for transparency).

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