Structured Settlement rule lens: Colorado

The rule in plain language

Run this scenario in DocketMath using the Structured Settlement calculator.

Colorado generally regulates structured settlements through the Colorado Structured Settlement Act (the “Act”). The core idea is straightforward: when a claimant resolves certain personal injury claims with a structured settlement (payments over time rather than a single lump sum), the settlement is typically required to include specific terms and to be administered through a qualified structure that can reliably produce the promised payments.

In practical terms, the Act is designed to ensure that:

• the funding arrangement is set up to reliably produce future payments, and
• the settlement’s key payment mechanics (such as amount and timing, and related rights/terms) are consistent with the statutory framework.

Colorado’s approach is also jurisdiction-aware about situations where the arrangement must be reviewed (for example, when the settlement involves minors or protected persons). Where review is required, the structure and payment plan usually must be presented in a way that shows the arrangement is coherent and appropriately funded.

Why it matters for calculations

Structured settlement math isn’t just a basic discounting exercise. Colorado’s structured settlement framework affects calculations because it influences what cash flows you can (or should) model and which modeling inputs align with the actual deal terms.

Below are common calculation touchpoints where a Colorado “rule lens” can change outcomes.

1) Payment timing and “funding certainty”

If the settlement must follow statutory-style payment mechanics, your cash-flow schedule should reflect:

• the actual installment dates
• the stated payment amounts
• any permitted contingencies or changes that affect future payments (if used in the structure design)

Even a small timing change (for example, shifting from monthly to quarterly payment dates) can meaningfully change present value.

2) Structure funding cost vs. claimant proceeds

Many valuation workflows involve two sides:

• the structure’s funding price (what funds must be provided to support the stream), and
• the claimant’s payment stream (what the claimant receives over time)

Colorado’s requirements can affect how payment timing and structure terms are designed. When you model both sides, try to keep the inputs consistent—avoid mixing “claimant proceeds” assumptions with a “funding cost” model that implicitly assumes a different schedule.

3) Documentation-driven inputs you should capture

For results you can reuse (and defend internally), your DocketMath inputs should match the schedule the structure will deliver. Typical inputs include:

• total number of payments (or the end date)
• start date for the first payment
• payment frequency (monthly, quarterly, annual, etc.)
• payment amount (fixed or varying)
• any lump-sum component (if included)
• the discount rate (sometimes described as a required return) used for present value

4) Court review scenarios (when applicable)

If the settlement requires court review or special handling—often linked to protected persons—the calculation may need to support a clear, repeatable factual record. While the discounting “physics” doesn’t change, you’ll typically need:

• a precise schedule
• transparent assumptions
• outputs that are easy to reproduce and present

Use the calculator

DocketMath’s structured settlement calculator helps you model the present value and cash-flow profile of a structured payment stream using consistent assumptions. Use it to test: “What changes if we adjust timing, payment frequency, or the discount rate?”

Run the Structured Settlement calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Step 1: Choose your scenario type

In DocketMath, set up the structure you’re analyzing. Common scenario shapes include:

• Level payments (same amount each period)
• Step payments (changes after a certain date)
• Mixed schedules (payments plus a separate lump sum, if applicable)

Step 2: Enter the cash-flow schedule

Build the payment stream with inputs like:

• Payment amount (e.g., $2,500 per month)
• Start date (date of the first payment)
• Frequency (monthly, quarterly, annual)
• Number of payments (or the end date)
• Any additional/lump-sum payments (if your structure includes them)

Step 3: Add the discount rate (present value lens)

To compute present value, DocketMath requires a discount rate (often treated as the “required return” for discounting).

Because outputs can swing based on this assumption, a practical approach is to:

• run at least two rates (e.g., conservative vs. higher), and
• compare the present value results to gauge sensitivity

Step 4: Review outputs and sanity-check the schedule

After running the calculation, verify:

• the payment count matches your schedule
• the final payment date aligns with the intended end date
• the undiscounted total matches the documented structure (payment amount × number of payments), plus/minus any deliberate adjustments

What you’ll typically get

DocketMath structured settlement outputs usually include:

• Total undiscounted payments
• **Present value (discounted)
• a cash-flow timeline (or equivalent schedule view)

Step 5: Connect results back to Colorado compliance questions (without legal advice)

Once you have a clean payment model, use it to support the factual side of questions tied to Colorado compliance, such as:

• does the modeled schedule reflect the structure terms you intend?
• are payment intervals consistent with the documented structure plan?
• are any lump-sum or adjustment features captured (where applicable)?

If your workflow involves materials for court review or protected-person oversight, repeatability of the schedule and assumptions often makes the difference between a usable calculation and a schedule that can’t be clearly explained.

Quick sensitivity checklist (run in DocketMath):

You can start from a workflow like:

1. Model the base structure schedule.
2. Capture present value at a baseline discount rate.
3. Produce a second scenario with a different discount rate to show sensitivity.

Sources and references

Start with the primary authority for Colorado and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Related reading

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