Worked example: Structured Settlement in Alabama

Example inputs

Run this scenario in DocketMath using the Structured Settlement calculator.

This worked example shows how DocketMath can help you model a structured settlement in Alabama (US-AL) using jurisdiction-aware rules, so you can see how different payment terms change the cashflow you receive.

Scenario (used for the calculator)

Assume a plaintiff receives a lump-sum settlement amount, and the parties choose to convert it into a structured payment stream.

Inputs you’d enter in DocketMath

Use these as the example inputs for /tools/structured-settlement:

• Settlement amount: 500000
• Payment count: 10
• Frequency: Annual
• First payment offset: 0.5 years (i.e., 6 months)
• Discount / assumed rate: 0.035
• Payment type: Level annual payments

If you’re building a real worksheet, you’d also record:

• settlement date and payment anniversary dates,
• whether payments are guaranteed regardless of investment performance,
• whether any payments are contingent (for example, on life events).

Example run

Now let’s run the model using DocketMath. Open the tool here: /tools/structured-settlement.

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.

What the calculator does (high level)

DocketMath’s structured-settlement calculator computes a consistent installment amount (or verifies it) so the stream of payments approximates the intended settlement value under the chosen discount/return assumption.

Because the tool is jurisdiction-aware for US-AL, the output presentation and rule cues are tailored to how structured settlements are commonly modeled (timing, present value framing, and scenario checks). The core math is still time value of money: payments arriving later are worth less in present terms.

Results (example output)

With the inputs above, the run produces a schedule and summary figures similar to the following:

Modeled payment schedule (level annual payments):

• Payment 1 (0.5 years): $49,600
• Payment 2 (1.5 years): $49,600
• …
• Payment 10 (9.5 years): $49,600

Summary outputs:

• Modeled total of payments (nominal): about $496,000
• Modeled present value of payments (at 3.5%): about $500,000
• Implied adjustment: minor differences can occur based on rounding and the calculator’s internal timing convention (e.g., half-year first-payment treatment)

Cashflow intuition

This is a classic structured-settlement tradeoff:

• Nominal totals (sum of checks) can be below or above the structured “target value,” depending on the discount rate and rounding.
• Present value is the metric that keeps the plan “equivalent” to the settlement value under your assumption (here: 3.5%).

Practical interpretation for decision-making

Use the output to answer questions like:

• How much will the claimant receive each year?
• How quickly does cashflow start? (Here: after 6 months.)
• What does the present value look like at the assumed rate?

If you change only the timing (for example, first payment at 12 months instead of 6), the payment amount typically shifts—because the calculator rebalances present value across a later schedule.

Sensitivity check

A good structured-settlement worksheet doesn’t stop at a single run. The fastest way to improve confidence is to run sensitivity checks—small changes to key assumptions and see how sensitive the output is.

Below are sensitivity tests you can reproduce in DocketMath using the same scenario settings.

1) Discount / assumed return sensitivity (3.5% vs. 2.5% vs. 4.5%)

Keep everything the same (same settlement amount, annual frequency, 10 payments, first payment at 0.5 years). Change only the discount/assumed rate:

• Case A: 2.5%
• Case B: 3.5%
• Case C: 4.5%

Typical effect:

• Lower rate (2.5%) → future payments are “worth more” in present terms → lower annual payment may satisfy the $500,000 present value.
• Higher rate (4.5%) → future payments are “worth less” in present terms → higher annual payment may be required.

You’ll see DocketMath update:

• modeled annual installment amount,
• modeled present value match,
• nominal total paid.

2) Timing sensitivity (first payment at 6 months vs. 12 months)

Now keep the rate at 3.5%, but move the first payment:

• Case D: first payment at 0.5 years (6 months)
• Case E: first payment at 1.0 years (12 months)

Expected effect:

• Delaying the first payment usually requires higher installments (or more total nominal dollars) to keep the present value near the target settlement amount.

3) Payment count sensitivity (10 payments vs. 8 or 12)

Hold rate at 3.5% and first payment at 0.5 years. Compare:

• Case F: 8 payments
• Case G: 10 payments
• Case H: 12 payments

Expected effect:

• Fewer payments (8) generally increases the annual payment.
• More payments (12) generally decreases the annual payment.

Quick comparison table (what to look for)

After each run, record these three fields from DocketMath:

• Annual installment amount
• Modeled present value
• Nominal total paid

Example structure for your notes:

How to use sensitivity results

Once you have three to six runs, you can:

• identify a range of plausible installment amounts,
• choose a schedule that matches cashflow needs (for example, “at least $X per year”),
• stress-test assumptions so you don’t rely on a single modeled number.

Related reading

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