Worked example: Damages Allocation in Vermont

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

Below is a worked example for damages allocation in Vermont using DocketMath (jurisdiction-aware rules, code US-VT). This example is designed to show how the calculator treats common inputs and how the allocation output changes when you adjust assumptions.

Scenario (hypothetical)

A Vermont plaintiff claims two categories of damages arising from the same set of events:

1. Compensatory damages (e.g., economic losses such as medical bills, wage loss, and other out-of-pocket expenses).
2. Non-compensatory damages (e.g., damages calculated differently than purely economic loss in many claims, such as certain statutory or punitive-type categories depending on the claim theory).

For the calculator, you’ll enter totals by category and (optionally) how those totals map to the portion of damages that are allocated as “eligible” within the model.

Inputs you would enter in /tools/damages-allocation

Use the following example numbers:

Time-window context (Vermont default)

For this Vermont example, the tool uses the general/default period of 1 year. The jurisdiction data provided to this calculator reflects that the general SOL period is 1 year, and it does not identify a separate, claim-type-specific sub-rule for this example scenario.

In addition, the jurisdiction information points to Vermont’s legislative materials for this SOL period basis:

• Vermont legislature materials: https://legislature.vermont.gov/Documents/2020/Docs/CALENDAR/hc200226.pdf

Important clarification (per the brief): no claim-type-specific SOL allocation sub-rule was found in the provided jurisdiction data. So the model treats the general/default 1-year period as governing for both compensatory and non-compensatory categories in this run. That means you should not expect the calculator to differentiate eligibility by damage type in this example—both categories are processed under the same time-window logic.

Example run

To run this with DocketMath, use the primary CTA:

• /tools/damages-allocation

Before you click “calculate,” set the fields to match the example inputs above.

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: Compute the eligible window inside the tool

Given:

• claim_start_date = 2023-01-15
• filing_date = 2024-06-20
• general_sol_period_years = 1

The filing date occurs more than 1 year after the claim start date. In a typical allocation model, that means the portion of damages tied to events outside the SOL window is treated as ineligible for the allocation result (within the logic the tool implements).

Step 2: Allocate between damage categories

In this example, the calculator starts from:

• Compensatory total: $120,000
• Non-compensatory total: $45,000
• Combined total requested: $165,000

Because the time-window check is central to allocation, the results will reflect that the filing is beyond the general 1-year period used in this jurisdiction setup.

Step 3: Read the allocation output (what you should expect)

Even though exact percentage outcomes depend on the tool’s internal modeling of “when” damages accrued, a jurisdiction-aware SOL step usually drives one of two common result patterns:

1. More of the damages are eligible when filing is within the time window, or
2. A reduced eligible amount when filing is outside the time window, with the reduced amount depending on accrued timing assumptions.

In this scenario, you should expect the tool to output a reduced eligible damages amount relative to $165,000 because the filing date is beyond the 1-year general period used in this example.

Below is a representative way to interpret the output (numbers shown for illustration of reading the output, not a legal conclusion). Look for fields like:

Why the “general/default” rule matters here

Because the jurisdiction data explicitly indicates no claim-type-specific sub-rule was found, DocketMath applies the general/default 1-year period to the full set of categories in this example. That means you won’t see category-specific SOL behavior—both compensatory and non-compensatory amounts are governed by the same time-window logic in this run.

Sensitivity check

Now adjust inputs to see how the allocation result changes. This is where DocketMath helps you stress-test assumptions quickly.

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 A — Move the filing date closer to the 1-year window

Change only:

• filing_date from 2024-06-20 → 2023-12-20

Keep the rest the same:

• claim_start_date = 2023-01-15
• compensatory_total = $120,000
• non_compensatory_total = $45,000
• general_sol_period_years = 1
• eligibility_rule = General/default

Expected direction of change: the filing date is more favorable relative to the 1-year window, so total_eligible_damages should increase versus the original run.

Quick checklist:

Sensitivity B — Reduce timing pressure by changing the claim start date

Change only:

• claim_start_date from 2023-01-15 → 2023-07-15
• keep filing_date at 2024-06-20

Keep the rest the same.

Expected direction of change: because the start date is later, the filing date becomes closer to (or potentially within) the 1-year window used by the model. Therefore, the eligible portion should rise.

Sensitivity C — Change the mix of damages categories (holding SOL pressure constant)

Return to the original dates so the SOL pressure remains consistent:

• claim_start_date = 2023-01-15
• filing_date = 2024-06-20

Then change totals:

• compensatory_total = $80,000
• non_compensatory_total = $85,000
• Keep combined requested damages at $165,000

Expected direction of change: if the SOL allocation logic is applied uniformly across categories under the general/default rule, the overall eligible total may change with the mix, and the tool should generally reflect a proportional shift between:

• eligible_compensatory vs. eligible_non_compensatory, and
• the resulting total_eligible_damages.

This sensitivity helps you confirm whether:

• the same SOL window is applied to both categories (as the general/default setup suggests), and
• the calculator’s allocation responds to mix changes through category eligibility rather than by altering the underlying time window.

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