How to calculate Damages Allocation in Vermont

Quick takeaways

• Vermont generally applies comparative negligence: contributory negligence does not bar recovery if the plaintiff’s negligence is not greater than the defendant’s causal total negligence. This is codified at 12 V.S.A. § 1036.
• In DocketMath (“damages allocation”), you typically split a total damages figure into a plaintiff share and a defendant share based on causal negligence percentages.
• The key Vermont decision point is the statutory threshold: compare the plaintiff’s causal negligence (P) to the defendant’s causal total negligence (D).

  • If P ≤ D, recovery proceeds (subject to allocation).
  • If P > D, recovery is barred for the portion governed by that threshold.
• Use causal negligence inputs (as framed by the statute and the fact-finder instructions), not generic “fault” labels, to keep the calculator aligned with Vermont’s approach.

Inputs you need

To calculate damages allocation in Vermont with DocketMath, collect inputs that match the statute’s comparative negligence framework.

Required inputs (single plaintiff vs. single defendant)

• Total damages (T)

  • The total compensatory damages figure before allocation (often derived from a verdict or damages finding).

• Plaintiff causal negligence (%) — P

  • The plaintiff’s percentage of causal negligence.

• Defendant causal negligence (%) — D

  • The defendant’s percentage of causal total negligence attributable to the defendant side.

Optional inputs (more complex models)

• Multiple defendants (each with its own causal negligence %)
• Multiple plaintiffs (each with its own causal negligence %)
• Whether T already reflects any cap/offset/limit

  • If your damages base has already been reduced (e.g., by another step in your case workflow), don’t apply duplicate reductions in addition to the allocation unless your DocketMath fields are explicitly designed for that.

Vermont rule framing you’ll use in the calculator

Vermont’s comparative negligence statute establishes a threshold recoverability rule:

• Recovery is not barred when the plaintiff’s causal negligence is not greater than the defendant’s causal total negligence (P ≤ D).
• Recovery is barred when the plaintiff’s causal negligence is greater than the defendant’s causal total negligence (P > D).

Important note on sub-rules/periods

• No claim-type-specific sub-rule was found for this statute in the brief research used for this walkthrough.
• In other words, treat this as the default period/rule unless you later confirm a different, claim-specific statutory rule applies.

Practical implication: Your allocation logic should reflect the bar vs. no-bar threshold (P compared to D), not only a “percentage reduction” concept.

How the calculation works

In the DocketMath damages-allocation calculator for Vermont (US-VT), the workflow should follow a comparative negligence approach driven by 12 V.S.A. § 1036.

Step 1: Confirm your percentages match “causal negligence”

Before you run the numbers, make sure your inputs represent the same concept the court/fact-finder used—because Vermont’s statutory language keys off negligence tied to causation.

Check that:

• P represents the plaintiff’s portion of causal negligence, and
• D represents the defendant’s portion of causal total negligence as your workflow defines it, and
• The percentages are internally consistent (for example, whether you’re comparing only two sides, or whether the tool models more parties).

If the inputs don’t match the fact-finder’s framing, the calculator can produce a clean mathematical output that still doesn’t align with the legal basis.

Step 2: Apply the Vermont recovery threshold from 12 V.S.A. § 1036

Define:

• P = plaintiff causal negligence (%)
• D = defendant causal negligence (%)
• T = total damages

Vermont’s threshold rule (as described in the statute text) is:

• No bar when P is not greater than D
• Bar when P is greater than D

Decision rule

• If P ≤ D: plaintiff may recover allocated damages (subject to allocation mechanics).
• If P > D: plaintiff’s recovery is barred under 12 V.S.A. § 1036, so the plaintiff’s allocable recovery is $0 in the “barred” scenario.

Step 3: Compute plaintiff and defendant shares (when P ≤ D)

When P ≤ D, the allocation generally reduces plaintiff recovery in proportion to the comparative negligence relationship between P and D.

A common comparative-allocation approach that matches the “not greater than” workflow is:

• Plaintiff share = T × (D / (P + D))
• Defendant share = T × (P / (P + D))

This keeps the plaintiff’s recoverable amount tied to the defendant’s causal contribution relative to the combined causal negligence of the compared sides.

Concrete number example (recovery allowed)

• T = $200,000
• P = 30%
• D = 70%

Since 30% ≤ 70%, recovery is allowed.

• Plaintiff share = $200,000 × (70 / (30 + 70))
  = $200,000 × 0.70
  = $140,000
• Defendant share (as the remainder of T) = $60,000

Step 4: Handle the barred scenario (when P > D)

If P > D, Vermont’s statutory threshold bars the plaintiff’s recovery.

Concrete barred example

• T = $120,000
• P = 60%
• D = 40%

Since 60% > 40%, plaintiff recovery is $0 under 12 V.S.A. § 1036.

• Plaintiff share = $0
• Defendant share = $120,000 (the allocation effectively shifts away from plaintiff recovery)

Step 5: Enter values into DocketMath consistently

When using the DocketMath damages-allocation (US-VT) tool—here’s the target page to open it: /tools/damages-allocation:

• Enter plaintiff causal negligence (%) as P
• Enter defendant causal negligence (%) as D
• Enter total damages (T) as your damages base

If DocketMath prompts for party counts or multiple-defendant inputs, ensure the defendant-side totals you use correspond to the statute’s causal total negligence concept as your setup defines it.

Common pitfalls

• Ignoring the statutory threshold (12 V.S.A. § 1036)
  A “percentage reduction” approach might keep recovery non-zero even when P > D, but Vermont’s statute can bar recovery when plaintiff negligence is greater than defendant causal total negligence.

• Swapping plaintiff and defendant percentages
  Because the rule depends on comparing P to D, reversing them can flip the output from “recovery allowed” to “recovery barred.”

• Using non-causal “fault” percentages
  If your percentages aren’t actually causal negligence as framed by the fact-finder, the allocation may not reflect Vermont’s statutory basis.

• Double-counting adjustments inside T
  If your T already accounts for offsets, caps, or prior reductions, you may end up effectively reducing damages twice—unless the tool’s inputs are designed to handle that.

• Mis-modeling multiple defendants
  For multiple defendants, ensure the defendant-side percentage used for D aligns with how “causal total negligence” is meant to be treated in your tool workflow (e.g., summed across defendants vs. entered individually per the tool’s structure).

If your negligence inputs don’t track the legal definition used in the case, the calculation can be “correct” mathematically but incorrect legally.

Sources and references

• 12 V.S.A. § 1036 — Vermont comparative negligence standard; contributory negligence does not bar recovery when the plaintiff’s negligence is not greater than the defendant’s causal total negligence.
  Source: https://legislature.vermont.gov/statutes/section/12/185/1036

Next steps

1. Collect your inputs in causal terms: P (plaintiff causal negligence %) and D (defendant causal total negligence %), plus T (total damages).
2. Run the DocketMath damages-allocation calculator for Vermont on /tools/damages-allocation.
3. Check the threshold outcome after you enter numbers:

   • If P ≤ D, confirm the plaintiff share is non-zero and reduced by the allocation mechanics.
   • If P > D, confirm the plaintiff share becomes $0 (barred recovery).
4. For scenario comparisons, change one input at a time (for example, adjust P around the P ≤ D / P > D boundary) to see how sensitive the outcome is to the statutory threshold.

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