How to run Damages Allocation in DocketMath for Colorado

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Colorado (US-CO). The focus is on how to set up inputs and what the output typically represents—so you can validate results before you rely on them in a workflow.

1) Open the correct calculator in DocketMath

1. Go to the Damages Allocation tool: /tools/damages-allocation
2. Confirm you’re using the Colorado jurisdiction profile:

   • Look for a jurisdiction selector or a jurisdiction-aware rules toggle.
   • Choose US-CO if it’s available.

If DocketMath asks you to pick a jurisdiction first, selecting US-CO before entering numbers helps ensure jurisdiction-aware defaults (such as Colorado-specific labeling or interpretation) apply to your run.

2) Choose what you’re allocating

Damages allocation setups typically involve:

• Total damages (or categories that sum to a total)
• Multiple parties (and sometimes multiple theories/claims, depending on how the tool is designed)

In DocketMath, decide which model you’re using:

• One total → allocation across parties
• Multiple categories → allocation across parties (and possibly across time/claims, depending on the inputs available)

How this affects output:

• A single total setup usually returns a straightforward allocation table (party → dollars, and sometimes party → percent).
• A multi-category setup often returns category-level allocations plus roll-up totals.

3) Enter Colorado-appropriate allocation inputs

DocketMath will require the numeric inputs your allocation model needs. Common input patterns include:

• Party list (e.g., Plaintiff/Defendant/other responsible parties)
• Allocation basis values, such as:

  • Percent factors (if you model apportionment by weights)
  • Dollar amounts by category
  • Fixed percentages per party (if you already know the breakdown)
• Any caps, offsets, or attribution constraints the calculator supports (if those options are enabled)

Use this quick quality-control checklist while entering inputs:

4) Set allocation rules to “Colorado (US-CO)” when prompted

If the tool exposes a jurisdiction-aware rules selector:

• Select Colorado (US-CO) and keep it fixed for the run.
• If there are optional toggles (for example, “apply jurisdiction-aware labels” or “use Colorado default interpretation”), enable only the ones intended for a Colorado run.

Why this matters:

• Jurisdiction-aware rules can change how results are presented (labels and breakdown format) and, depending on the calculator’s design, may also affect how computations are performed.

5) Run the calculation and review outputs

Click Calculate (or the tool’s equivalent action button). Then review the results carefully.

A) Allocation table (party-level)

Look for:

• Each party’s allocated amount (dollars)
• Each party’s allocated percentage (if supported)
• Totals that tie back to your input total damages

Validate the math quickly:

• Sum of allocated dollar amounts should match your expected total (allowing for rounding).
• If the tool shows normalization, confirm it matches what you intended.

B) Category-level breakdown (if you used multiple categories)

If your setup included categories:

• Review category totals and the allocations per party within each category
• Confirm category subtotals roll up correctly into the overall total damages

C) Assumptions and rule summaries (if displayed)

Some DocketMath outputs include a short summary of:

• The allocation method chosen
• Whether any constraints were applied
• Any normalization logic

Capture these details in your workflow notes so you can reproduce the run later.

6) Iterate with “what-if” adjustments

A practical workflow is to run multiple scenarios:

• Baseline: your current numbers
• Scenario A: adjust one party’s factor
• Scenario B: reweight categories
• Scenario C: test rounding/caps/offsets (if supported)

When you change inputs, watch how outputs respond:

• If you alter a party weight, that party’s allocation should shift proportionally (or according to the selected rule).
• If you alter category amounts, allocations within each category should shift while overall totals remain consistent.

7) Export or copy results for your case workflow

Once results look right:

• Copy the allocation table
• Export/download if DocketMath provides an export option

Ensure your export includes:

• The jurisdiction setting (US-CO)
• The exact inputs you used (at minimum: party list + totals)
• Any output metadata shown (like timestamp), if available

This helps maintain internal consistency when you revisit or share your calculations.

Common pitfalls

Below are issues that commonly cause surprising allocation results in DocketMath runs for Colorado matters. Use this as a pre-flight checklist before you finalize a scenario.

• Running with a default jurisdiction (or forgetting to switch to US-CO) can change rule behavior or labeling.
• If the tool expects 100%, make sure your inputs sum to 100%.
• If you enter categories and also enter a total, confirm the sum of categories equals the Total damages number.
• Two-decimal vs whole-dollar rounding can cause small discrepancies in totals. If the tool rounds at the end, try entering whole-dollar amounts where possible.
• If you rerun with added parties, verify you removed or adjusted the previous party rows rather than layering them.
• Some setups take weights (then compute dollars). Others take dollars (then compute percentages). Make sure you’re feeding the tool what it expects.
• If your allocation setup includes caps or offsets, confirm the output indicates they’re active for the run.

Try it

Use DocketMath’s Damages Allocation tool and run a quick Colorado scenario:

1. Open /tools/damages-allocation
2. Set jurisdiction to **Colorado (US-CO)
3. Enter:

   • A total damages number (or a couple of categories)
   • 2–3 parties
   • Either percentages (if that’s your model) or dollar amounts by party/category
4. Click Calculate
5. Verify:

   • Party allocations sum to the total
   • Category roll-ups match (if applicable)
6. Adjust one variable and rerun:

   • Change one party’s weight by about 10% and confirm the allocation shifts accordingly

For a fast internal check, try this mini test:

If that behavior matches your expectations, you’re set up correctly to explore more realistic numbers.

Ready to start? Go to /tools/damages-allocation now, and run your first Colorado (US-CO) allocation.

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