How to run Damages Allocation in DocketMath for Vermont

Step-by-step

Follow these steps to run Damages Allocation in DocketMath for Vermont (US-VT) using jurisdiction-aware rules—specifically Vermont’s comparative negligence “not greater than” threshold under 12 V.S.A. § 1036.

1) Open the Vermont Damages Allocation tool

1. Go to /tools/damages-allocation.
2. Select Vermont (US-VT) as the jurisdiction (if the UI prompts you).

If you don’t set the jurisdiction, DocketMath may not apply 12 V.S.A. § 1036 correctly, which can change both the eligibility gate and the allocation amount.

2) Enter negligence percentages by party

In the calculator, you’ll typically enter:

• Plaintiff negligence (%)
• Defendant negligence (%)
• (Optional) Other parties’ negligence (%) if the tool supports multiple actors

How Vermont affects eligibility

Under 12 V.S.A. § 1036, contributory negligence does not bar recovery when the plaintiff’s negligence is not greater than the defendant’s causal total negligence. In practical terms, the threshold is:

• Plaintiff % ≤ Defendant % (as the tool computes the defendant’s “causal total negligence”)

So:

• If Plaintiff % > Defendant %, the statute’s “not greater than” language should lead to a barred recovery outcome (often reflected as $0 allocated recovery by tools).
• If Plaintiff % = Defendant %, the plaintiff is still not barred (because “not greater than” includes equality).

3) Provide the damages amounts you want allocated

Next, enter the damages basis you want DocketMath to allocate, such as:

• Total damages (or a total by category), e.g. medical expenses, property damage, wage loss

If the tool supports category-by-category allocation, you can input separate categories and the tool will apply the negligence allocation to each category based on the same Vermont eligibility gate.

4) Confirm whether negligence inputs must sum to 100%

Some allocation tools require negligence inputs to sum to a target (often 100%). If DocketMath enforces summation:

• Adjust your percentages so the tool’s internal “causal total negligence” denominator matches the model it uses for 12 V.S.A. § 1036.

If DocketMath allows “relative” weights without requiring a 100% total:

• Keep the inputs consistent (don’t mix percentages and non-percentage weights).
• Use the same measurement basis across plaintiff/defendant/others so comparisons are meaningful.

5) Run the calculation and review the allocation

Click Calculate.

Review the output for (wording can vary by UI), such as:

• Allocated recovery amount (what the plaintiff can recover after negligence allocation)
• Whether the eligibility gate was triggered under Vermont’s rule
• How the negligence percentages affected the result
• Any rule reference or brief explanation shown by the tool

The Vermont decision gate (the key logic)

The core issue under 12 V.S.A. § 1036 is whether the plaintiff’s negligence is:

• not greater than the defendant’s causal total negligence (eligible), or
• greater than it (barred)

If the tool output doesn’t appear to match that gate, double-check which inputs are treated as plaintiff vs defendant, and whether multiple defendants/other parties are aggregated as you expect.

6) Sanity-check with a quick threshold table

Before relying on the computed number, sanity-check eligibility:

If the tool gives the opposite behavior:

• Re-check that you entered plaintiff negligence and defendant negligence on the correct sides.
• Confirm whether the tool expects the “defendant” value to represent causal total negligence (which may require aggregation when there are multiple defendants).

7) Save/export your working allocation

If available, use Save, Export, or Report to preserve:

• The jurisdiction setting (US-VT)
• The negligence percentages you entered
• The damages total (or category breakdown)

That makes it easier to rerun the scenario if facts (e.g., negligence percentages) change.

Common pitfalls

Even when the interface is user-friendly, Vermont-specific threshold logic can produce surprising outputs—usually due to input framing.

1) Reversing plaintiff and defendant negligence

Because the statute uses “not greater than”, swapping the two sides can flip eligibility.

• Example error: entering plaintiff % as defendant % (or vice versa)
• Symptom: the tool returns $0 or a sharply reduced recovery

2) Misreading “not greater than”

“Not greater than” includes equality, so equality should not bar recovery.

• If you test or reason with Plaintiff % = Defendant %, the plaintiff should generally remain eligible under the threshold.

3) Mixing total damages with category inputs

If you enter both:

• a total damages figure and
• overlapping category damages,

you can accidentally double count—depending on how DocketMath is set up.

Checklist:

• Use either a single total or a clear category breakdown (whatever the tool expects).
• Ensure categories map to the same underlying event/time period.

4) Leaving the jurisdiction unset

If the tool does not apply US-VT, it may use a different state’s default negligence/allocation rule.

Always confirm the tool is set to Vermont (US-VT).

5) Entering negligence values that don’t match the tool’s model

Some tools:

• aggregate “other parties” into a causal total,
• cap at 100%,
• or prorate across multiple defendants.

If you include multiple actors, ensure your entries align with how DocketMath computes “causal total negligence” for the defendant side under 12 V.S.A. § 1036.

Try it

Use these quick tests in DocketMath → /tools/damages-allocation with Vermont (US-VT).

A) Run an “eligible” case (should allocate)

• Plaintiff negligence: 40%
• Defendant negligence: 60%
• Total damages basis: $100,000

Expected result under 12 V.S.A. § 1036: plaintiff is not barred because 40% ≤ 60%. The tool should allocate recovery based on the comparative split.

B) Run a “barred” case (should go to $0 or no recovery)

• Plaintiff negligence: 60%
• Defendant negligence: 40%
• Total damages basis: $100,000

Expected result: plaintiff is barred because 60% > 40% under the “not greater than” threshold—so the allocated recovery should typically be $0.

C) Confirm the gate behavior

After each run:

• Verify that changing the inequality direction (≤ vs >) changes the eligibility outcome as expected.
• If outcomes don’t change, re-check which fields are assigned to plaintiff vs defendant, and confirm the jurisdiction is truly set to US-VT.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance