Worked example: Damages Allocation in Virginia

Example inputs

Below is a worked example showing how DocketMath can allocate damages in a Virginia matter using jurisdiction-aware rules. This is a “how-to” walkthrough of the calculator workflow—not legal advice and not a substitute for case-specific review.

Scenario

A contractor sues for unpaid work and related damages after a project dispute. The plaintiff seeks:

• $180,000 for unpaid invoices (contract damages / principal)
• $12,000 for storage/handling costs (incidental damages)
• $25,000 in claimed pre-judgment interest (interest damages)
• $40,000 for attorneys’ fees and costs (claimed, depending on fee entitlement)
• $8,000 for mitigation-related expenses (claimed)

The defendant argues some categories are duplicative and that only certain portions qualify as recoverable damages.

Jurisdiction-aware setup (Virginia)

For this example, we apply practical, jurisdiction-aware allocation principles that keep the workflow consistent and auditable:

1. Distinguish principal damages from interest so interest is not inadvertently affected by unrelated reclassifications.
2. Treat attorneys’ fees as a separate line item because fee recovery often depends on entitlement and the claim structure.
3. Avoid mixing “cost-like” items with principal damages when your goal is to compute different totals cleanly (and to explain what each dollar represents).

Inputs entered into DocketMath (damages-allocation)

Use the /tools/damages-allocation calculator in DocketMath. To mirror this example exactly, enter the following inputs.

Overlap adjustment

To make the example concrete, assume the overlap adjustment of $6,000 reduces the principal side (contract + incidental), not the interest category. In real litigation, the “right” overlap logic depends on the parties’ theory and how the court treats the components. For this walkthrough, we’ll use that common allocation structure so the example stays consistent.

Example run

Start the worked run by navigating directly to the tool: DocketMath damages allocation.

Run the Damages Allocation 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.

Step 1: Establish category totals before overlap

• Contract damages: $180,000
• Incidental damages: $12,000
• Interest damages: $25,000
• Attorneys’ fees & costs: $40,000
• Mitigation-related expenses: $8,000

Pre-overlap subtotal (excluding overlap):
180,000 + 12,000 + 25,000 + 40,000 + 8,000 = $265,000

Step 2: Apply overlap adjustment

Apply the $6,000 overlap adjustment to the “principal side” (contract + incidental), leaving the interest line unchanged in this example.

Principal-side before overlap:
180,000 + 12,000 = $192,000

After overlap:
$192,000 − $6,000 = $186,000

If DocketMath uses proportional allocation across the principal categories, split the $6,000 reduction based on each category’s share of the $192,000 principal-side base:

• Contract share = 180,000 / 192,000 = 93.75%
  Reduction to contract = 6,000 × 93.75% = $5,625
• Incidental share = 12,000 / 192,000 = 6.25%
  Reduction to incidental = 6,000 × 6.25% = $375

Post-overlap category figures become:

• Adjusted contract damages: $180,000 − $5,625 = $174,375
• Adjusted incidental damages: $12,000 − $375 = $11,625

Step 3: Compute allocation totals

Now DocketMath rolls up categories:

So the allocation reduces the original $265,000 claim to $259,000 after overlap handling.

Step 4: Separate “principal vs. non-principal” for clarity

DocketMath (or your interpretation of its output) is typically used to highlight the distinction that matters when interest is at issue:

• Principal-side total (adjusted): $174,375 + $11,625 = $186,000
• Non-principal: interest $25,000 + fees $40,000 + mitigation $8,000 = $73,000
• Grand total: $186,000 + $73,000 = $259,000

This split helps you explain:

• which dollars form the conceptual base for interest calculations (here, principal-side after overlap), and
• which categories are fees/costs that are often treated distinctly in damages presentation.

Sensitivity check

A useful next step is to test how sensitive the outcome is to the overlap assumption and to whether fees are included in the “damages” total you care about.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity 1: Overlap adjustment changes

Keep all inputs the same, but vary the overlap adjustment applied to the principal-side categories.

Takeaway: in this structure, every $1,000 change in overlap (applied to principal-side categories) changes the grand total by $1,000.

Sensitivity 2: “Fees included” vs “fees excluded” totals

Some presentations need two views:

• Damages-only (exclude attorneys’ fees & costs), and
• All-in (include them)

Using the baseline adjusted numbers:

• Damages-only (exclude fees & costs):
  $174,375 + $11,625 + $25,000 + $8,000 = $219,000
• With fees & costs included: $259,000

In the baseline, attorneys’ fees account for:

• 40,000 / 259,000 ≈ 15.4% of the total allocated.

Sensitivity 3: Treat mitigation as principal-like vs separate

If you reclassify mitigation-related expenses (kept separate in the baseline) into principal-like buckets, the grand total often stays the same, but the principal vs. non-principal split changes—which can matter for interest workflows that rely on a principal base.

To stay audit-friendly:

• keep mitigation separate in the allocation output, then
• decide the principal classification only when aligning with the interest theory or claim formulation.

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