Worked example: Structured Settlement in Connecticut

Example inputs

Run this scenario in DocketMath using the Structured Settlement calculator.

This worked example shows how to use DocketMath’s “structured-settlement” calculator for a Connecticut matter using jurisdiction-aware rules. The goal is to translate a structured settlement cash-flow plan into an analysis you can model—without treating this as legal advice.

Primary tool CTA: You can access the calculator here: /tools/structured-settlement

Scenario (Connecticut)

You’re modeling a settlement that will pay out in fixed installments rather than one lump sum. For illustration, assume the settlement documents specify:

• Total settlement amount: $120,000
• Payment schedule:

  • $80,000 paid in year 1
  • Remaining $40,000 paid in 10 equal annual installments (years 2–11)
• Expected start of payments: January 1, 2026
• Payment timing convention: payments occur at the end of each year (so year 1 payment is paid on 12/31/2026, year 2 on 12/31/2027, etc.)
• Discount rate used for present value modeling: 5.0% annually (for the calculator’s time value-of-money component)

Jurisdiction-aware limitation period used in the calculator

Connecticut’s general statute of limitations for certain civil actions is 3 years, referenced by Conn. Gen. Stat. § 52-577a. In this DocketMath run, the calculator uses the general/default period because no claim-type-specific sub-rule was found for this worked example.

• General SOL period: 3 years
• Statute: Conn. Gen. Stat. § 52-577a
  Source: https://law.justia.com/codes/connecticut/title-52/chapter-926/section-52-577a/?utm_source=openai

Inputs you would enter in DocketMath

Use the calculator to specify the settlement cash flows and timing assumptions. Typical fields for a structured settlement modeling run look like:

• Jurisdiction: US-CT (Connecticut)
• Total amount: 120,000
• Payments:

  • Year 1: 80,000
  • Years 2–11 (10 payments): 4,000 each
• Start date: 2026-01-01
• Discount rate: 5.0%
• Statute of limitations period used by tool (general): 3 years (Conn. Gen. Stat. § 52-577a)

If DocketMath provides a field for the limitations period override, keep it aligned with the general 3-year default for this example.

Example run

Below is an example of what a DocketMath structured-settlement run is designed to output: a breakdown of projected payments, an estimated present value (PV), and a timing window tied to the 3-year general SOL.

Run the Structured Settlement calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Build the payment timeline

Given January 1, 2026 as the start date and an end-of-year payment convention:

Total: $80,000 + (10 × $4,000) = $120,000

Step 2: Apply the 3-year general SOL window (Connecticut)

Using Conn. Gen. Stat. § 52-577a general/default 3-year limitations logic, the tool’s timeline analysis focuses on whether key events are modeled inside that 3-year window.

With the start of payments on 1/1/2026, the 3-year period runs through:

• Start + 3 years → through 1/1/2029 (the tool may present this as an end date or a “by” cutoff depending on its UI)

For this schedule:

• Inside 3 years (approx.): payments in years 1–3
• Outside 3 years (approx.): payments in years 4–11

Subtotal within ~3 years (nominal):

• Year 1 (12/31/2026): $80,000
• Year 2 (12/31/2027): $4,000
• Year 3 (12/31/2028): $4,000
  Subtotal: $88,000

Remaining nominal outside ~3 years:

• Years 4–11: 8 payments × $4,000 = $32,000

Step 3: Present value (PV) modeling (time value of money)

Assuming the calculator discounts at 5.0% annually, the PV is computed using each payment’s timing.

You can expect the PV to be meaningfully less than the $120,000 nominal total because most payments occur after year 1.

Result shape you should expect from DocketMath:

• Nominal total: $120,000
• Total PV: < $120,000 (discounted)
• PV allocated inside vs. outside 3-year window: a larger share inside the horizon because the largest payment ($80,000) occurs early (year 1), with additional payments in years 2–3.

Step 4: Output summary to capture

A typical DocketMath output summary for this run (conceptually) includes:

• Cash-flow chart / schedule
• Present value total
• Breakdown by time window relative to the 3-year general SOL
• Key dates used in the model

Reminder/checklist (for reporting):

• Start date (2026-01-01)
• Payment convention (end-of-year)
• Discount rate (5.0%)
• Limitations period used by tool (general 3-year period under Conn. Gen. Stat. § 52-577a)

Sensitivity check

Good modeling practice is testing which inputs move results the most. With structured settlements, the biggest levers are usually (1) timing, (2) payment distribution, and (3) the discount rate.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

1) Change the discount rate

Re-run the same schedule at two alternative discount rates, keeping everything else constant:

• Low rate: 2.5%
• High rate: 7.5%

Expected behavior:

• At 2.5%, PV increases (future dollars lose less value).
• At 7.5%, PV decreases more sharply (future dollars lose more value).

What to capture:

• PV difference between rates
• Whether the PV share within ~3 years grows or shrinks (it often stays larger inside because of early cash flow, but the relative mix can still change)

2) Shift installment years earlier or later

Try two alternative schedules while preserving the same nominal total:

• Earlier payments: move years 2–11 into years 1–10 (annuity shifts one year earlier)
• Later payments: move years 2–11 into years 3–12 (annuity shifts one year later)

Expected behavior:

• Earlier payments increase PV and increase the portion occurring inside the ~3-year window.
• Later payments decrease PV and reduce inside-horizon cash flow.

This is where the SOL window connection becomes visible: moving payments across the ~3-year line can materially affect the inside/outside breakdown produced by the tool.

3) Keep the schedule, but adjust the SOL assumption field

Because this example explicitly uses the general/default 3-year period under Conn. Gen. Stat. § 52-577a, changing that period (if the calculator allows an override) is a sensitive test.

• Set to 3 years (default): matches this worked example
• Set to 2 years: narrows the window; fewer payments fall “inside”
• Set to 4 years: widens the window; more payments fall “inside”

Practical disclaimer: overriding limitations inputs without confirming the correct Connecticut rule for your specific claim type can produce a model that is internally consistent but not legally accurate.

Practical output you should compare

For each sensitivity run, compare:

• Total PV
• PV within ~3 years vs. outside
• Nominal inside ~3 years vs. outside
• Which payments fall before/after the modeled cutoff

A simple comparison table can help you document changes:

Related reading

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