How to interpret Damages Allocation results in Colorado

What each output means

DocketMath’s Damages Allocation calculator is designed to convert the inputs you provide into a jurisdiction-aware allocation output for Colorado (US-CO). When you review the results, treat the outputs as answering: “How does the calculator split the damages figure into buckets, and how should I use those buckets in my next documents?”

The exact output labels can vary slightly based on what you entered, but the interpretation logic below will help you read the damages-allocation results consistently.

1) Total allocated damages

This is the sum of the calculator’s allocated buckets.

• How to use: Use it as a cross-check against the overall damages premise you intended to model. If the total feels off, the issue is usually in one or more upstream inputs (category amounts, date/duration assumptions, or mode/toggles).

2) Economic damages allocation

This bucket represents measurable financial losses, typically the kind of damages you can support with documentation (for example: medical bills, invoices, payroll/wage records, or other quantifiable expenditures).

• How to use: Treat this as the portion that usually needs the strongest itemized support. If your economic assumptions are too low or too high, the economic bucket will be the first place you’ll notice it.

3) Non-economic damages allocation

This bucket represents non-financial impacts such as pain, suffering, and related effects—based on how you parameterized the scenario inputs.

• How to use: If you’re trying to defend why non-economic damages are higher or lower, revisit the severity/intensity and duration/impact assumptions first. Non-economic allocations are often more sensitive to assumption changes than economic ones.

4) Colorado-specific rule-driven components (if shown)

Some outputs may include Colorado-specific allocation components or “mechanics” that the tool applies when certain inputs imply a scenario type or category mapping.

• How to use: Don’t treat these as automatic guarantees of legal entitlement. Instead, use them as document-ready labels for what your selected model inputs implied.

5) Reduction/offset lines (if shown)

If the tool shows reduction factors, offsets, or “net” amounts, these generally reflect the calculator’s jurisdiction-aware netting logic applied to your inputs.

• How to use: Use net/reduction lines to understand how the model translated your scenario. Then make sure your narrative and supporting records match the modeling assumptions you selected.

Pitfall to watch: If you entered overlapping information (for example, both a broad damages total and also detailed line items that effectively sum to that total), reduction or net lines can look inconsistent even when the calculator is reflecting the inputs you provided.

6) Supporting explanations / rationale text (if present)

Some results include brief rationale or explanation text—often indicating which inputs caused a bucket to shift.

• How to use: Screenshot or export the output so you can trace what drove the result. This makes later revisions faster and helps you avoid re-guessing which field mattered most.

Re-run directly

To regenerate allocations after you adjust assumptions, use /tools/damages-allocation:

• Internal link: Run the damages allocation tool

What changes the result most

To change (or defend) the Colorado damages allocation outputs, focus on the inputs that determine category sizing and any rule-based reduction/netting logic the tool applies. In most modeling workflows, the biggest swings come from a small set of “assumption knob” fields.

Highest-impact inputs (common drivers)

Review the inputs you entered and look for items like:

• Economic components

  • Larger medical/wage-loss figures typically increase the economic bucket.
  • Whether those figures are itemized vs. summarized can affect how cleanly the model maps them into the economic categories.
• Duration or time-period inputs

  • If the tool uses time periods (weeks/months/years), extending duration often increases both economic and non-economic modeled components.
• Severity / intensity / impact factors

  • Non-economic allocations are commonly the most sensitive to these settings.
• Scenario mode / category mapping toggles

  • A different scenario mode can change how Colorado-jurisdiction logic maps your inputs into buckets.
• Offsets, reductions, or attribution assumptions

  • If your tool inputs allow you to represent offsets, those can materially affect net totals and sometimes the relationship between gross and net lines.

Practical “sensitivity” checklist

Before finalizing your narrative, run through these checks:

Colorado-aware rule mechanics—how to think about them

Colorado-specific logic usually shows up in how amounts are categorized and/or how computed components are reduced or netted, depending on what your inputs imply.

A simple way to interpret the mechanics without guessing:

1. Start with the raw allocation buckets (economic vs. non-economic).
2. Then check any reduction/offset/net lines.
3. Adjust only one driver at a time (for example: duration first, then severity).
4. Confirm what changed: total allocated, economic, non-economic, and/or net.

This approach helps you attribute changes to the correct input and makes your output easier to explain.

Next steps

After you interpret the allocation results, use them to improve your drafting workflow—without relying on the calculator as a substitute for legal strategy.

After you run the Damages Allocation calculation, capture the inputs and output in the matter record. You can start directly in DocketMath: Open the calculator.

1) Turn model buckets into document language

Create a “model-to-document” mapping:

• Economic damages: connect to bills, receipts, pay stubs, invoices, and similar documentation.
• Non-economic damages: connect to narrative support such as symptoms, duration of impact, functional changes, and how severity/duration assumptions align with your factual timeline.

2) Re-run with controlled edits

If the outputs don’t match your expectations, don’t overhaul everything at once:

• Change one input at a time
• Keep notes on before vs. after
• Stop when the output aligns with the assumptions you believe are defensible

3) Export or screenshot for auditability

If your DocketMath output includes any breakdowns or rationale text, capture it. Keeping a snapshot makes later revisions easier and reduces the risk of unintentionally drifting assumptions.

4) Use net/reduction lines carefully in drafts

If the tool shows a net amount after reductions:

• explain what your model represented (e.g., modeled offset)
• ensure the story in your draft matches the same inputs you selected

Gentle reminder: Results are structured modeling outputs based on your inputs. They can help you organize and test assumptions, but they aren’t a guarantee of court outcomes.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules