Why Damages Allocation results differ in Vermont

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

When you run DocketMath → damages allocation for Vermont (US-VT), you may see materially different allocations for the same general set of facts—especially when inputs or assumptions differ. In Vermont, the biggest driver is that DocketMath applies jurisdiction-aware rules using the available default limitations framework.

Note (Vermont limitations): For Vermont, no claim-type-specific sub-rule was found in the provided materials. That means DocketMath uses the general/default limitations period, not a specialized period tied to a specific claim category.

Here are the top 5 reasons results differ in US-VT:

1. **Statute of limitations gating (default only, because no claim-type-specific rule was found)

   • The general/default limitations period indicated in your Vermont dataset is 1 year.
   • If DocketMath treats parts of the timeline as outside that applicable period, it will allocate fewer damages to the recoverable time window(s).

2. Date-range inputs don’t align across runs

   • Small changes in which date you use (for example, “incident/occurrence date” vs “notice date” vs “filing date”) can shift which months fall inside the 1-year default window.
   • Even if the dollar amounts are unchanged, the allocation basis can change because different slices become includable vs excludable.

3. Overlapping damages categories and attribution method

   • Allocation differences often come from how costs are assigned to categories (e.g., direct vs consequential, or past vs future).
   • If your category labeling or mapping changes between runs, the allocation math can produce different distributions—even when the total damages number looks the same.

4. Inconsistent treatment of totals vs components

   • If one run supplies a single total damages figure while another run supplies line-item components that sum to that total, the allocation can still differ due to how DocketMath weights/assigns those components and rounding behavior.

5. Missing or mismatched jurisdiction context

   • DocketMath’s jurisdiction-aware logic relies on the selected jurisdiction code (US-VT).
   • If any run accidentally uses a different jurisdiction (or a default/unset jurisdiction), the limitations-window logic can change and the allocation can shift dramatically.

How to isolate the variable

To pinpoint what’s driving the differences, use a “single-variable” approach in /tools/damages-allocation: keep everything constant except one input at a time. The practical goal is to make sure you can explain exactly why the output changed (window gating, category allocation, rounding, or jurisdiction logic).

Step-by-step isolation checklist

A practical test plan (fast and diagnostic)

What to watch in the output

When comparing runs, focus on two patterns:

• Recoverable time window expansion/reduction under the 1-year default limitations approach.
• Reallocation between categories (a sign that mapping/attribution changed rather than timeline gating alone).

Vermont-specific anchor (why this matters)

Your Vermont dataset indicates:

• General/default limitations period: 1 year
• No claim-type-specific sub-rule found

So, the most common source of differences is timeline gating—i.e., whether the relevant damages slices land inside vs outside the default 1-year window—rather than a specialized limitations rule by claim type.

Next steps

Once you identify the variable, apply the most practical fix:

• If the issue is timeline misalignment: standardize your date definitions. Use the same “incident/occurrence,” “notice,” and “filing” dates consistently across runs.
• If the issue is category mapping: align category names and ensure you’re entering damages in the same structure (totals vs components).
• If the issue is rounding/component handling: pick one input method (preferably totals or line items) and stick to it so comparisons are apples-to-apples.

Then do a final validation run:

Gentle reminder: this is an operational explanation of tool behavior and input sensitivity, not legal advice.

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