How to run Damages Allocation in DocketMath for Virginia

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Virginia (US-VA) using jurisdiction-aware rules. You’ll see exactly what to set, what the calculator needs, and how outputs should change as you adjust inputs.

1) Start the calculator from the primary CTA

• Open the tool here: /tools/damages-allocation
• You should land on the Damages Allocation calculator entry point.

2) Confirm the jurisdiction setting is Virginia (US-VA)

Inside the calculator:

• Look for a jurisdiction selector.
• Choose Virginia (US-VA).

Why this matters in the workflow:

• Jurisdiction-aware rules change how certain categories are handled and which allocation logic applies.
• Even when you enter the same numbers, the output can differ if the jurisdiction logic differs.

3) Select the allocation scenario template (if prompted)

Depending on your UI version, you may see a choice such as:

• Damages categories vs. a single totals approach
• Including/excluding specific components (e.g., compensatory vs. other components)

Pick the option that best matches how you’re breaking down your damages in the case record. If you’re unsure, start with a breakdown by category—it’s usually easier to audit.

4) Enter damages components and amounts

Add damages lines for each component the calculator asks for. Typical categories you may see in a damages-allocation workflow include:

• Economic damages (e.g., out-of-pocket losses)
• Non-economic damages (e.g., pain and suffering)
• Other damages (if the tool supports additional buckets)

For each component:

• Enter the amount you want allocated.
• Ensure all currency fields are in the same unit (e.g., dollars, not thousands).

Output impact:

• The total allocated and the allocation proportions will shift as you add or remove categories and as you change component amounts.

5) Add party-specific allocation factors

Next, DocketMath will ask for information that influences how totals get allocated. In a jurisdiction-aware tool, this is often framed as:

• Who is receiving what portion (party A vs. party B, etc.)
• Allocation weights (percentages or factors)
• Constraints (e.g., any component-level limits)

Common inputs to look for:

• Allocation percentages (sum-to-100% fields)
• Damages share weights (the tool may normalize these)
• Adjusters (if the tool allows reducing/raising certain categories)

Make sure:

• Percentages total 100% if the form requires it.
• If the tool doesn’t require totals to equal 100%, it may normalize automatically—watch for the “effective allocation” output.

6) If the tool supports multiple claims/components, allocate per bucket

Some DocketMath calculator versions let you allocate damages at the component level (not just one combined total).

If you see per-component controls:

• Allocate within each category where available.
• Keep your approach consistent with how you plan to report allocations.

Output impact:

• Component-level allocation can produce different results than a single overall allocation, especially when you apply different party weights or limits by category.

7) Run the calculation and review the allocation summary

Click the action that triggers computation (commonly “Calculate” or “Run Damages Allocation”).

Then review:

• Allocation summary table (party-by-party and/or category-by-category)
• Total allocated and any reconciliation checks
• Any “validation” messages (for example, totals not matching)

If the tool shows mismatches:

• Re-check that currency amounts are entered as numbers (not strings with commas/extra characters).
• Re-check whether the tool expects percentages to sum to 100%.

8) Audit results by changing one input at a time

To verify your allocation logic before you finalize anything:

• Change only one variable (e.g., adjust a party’s allocation weight).
• Re-run the tool.
• Confirm the output moves in the expected direction.

Quick sanity checks you can do:

• If Party A’s share increases, does Party A’s allocated amount increase?
• If you remove a damages component (set to 0), do related outputs drop accordingly?
• If you alter a category weight, does the category-level allocation change while totals remain consistent with the inputs?

9) Export/copy results for your workflow

Depending on the DocketMath interface, you may have options like:

• Copy summary
• Export view (PDF/CSV may vary by interface)

Use whatever export option is available to:

• Save the allocation table
• Keep the input set you used (if the tool supports saving scenarios)

Common pitfalls

These are the issues that most often cause allocation outputs to look wrong or inconsistent in US-VA runs.

If you leave the jurisdiction on a default (e.g., US-OTHER), the calculator may apply the wrong rule set.

Some forms enforce a strict sum. Others normalize silently—either way, the output won’t match your intended allocation unless you verify the results.

Entering “250” when the tool expects “250,000” changes totals drastically. If your UI uses labels like “$” or “Enter amount,” follow them closely.

If the tool provides per-category allocation fields, using only a single total allocation may mask category-specific differences.

Example pattern: you enter a “total damages” figure plus also enter the subcomponents that make up that total. The calculator will allocate what you entered, even if that means totals are inflated.

After changing inputs, always click Calculate/Run again. Some interfaces update live; others require a rerun.

Try it

Use DocketMath to run a Virginia (US-VA) Damages Allocation scenario in under 5 minutes:

1. Go to /tools/damages-allocation
2. Set jurisdiction to **Virginia (US-VA)
3. Enter two damages components (for example: economic and non-economic)
4. Create an allocation split for Party A and Party B

   • If percentages are available, try 60% / 40%
   • If weights are used, try a clear ratio like 3:2
5. Click Calculate
6. Review:

   • Total allocated per party
   • The allocation table by component
7. Make one controlled change:

   • Increase Party A from 60% to 70%
   • Re-run and confirm Party A’s allocated amount increases while Party B decreases

What to expect when you change inputs:

• Moving allocation shares should change party-by-party totals proportionally (or according to the tool’s allocation logic).
• Adding a new damages component should increase totals and expand category-level outputs (if the tool supports it).
• Zeroing a component should remove that component from allocation outputs while keeping other categories unchanged.

If your results look counterintuitive:

• Check jurisdiction (US-VA)
• Check sums (if percentages are enforced)
• Check for double-counting of totals vs. components
• Re-run after every edit

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