How to calculate pain and suffering damages in Vermont

Direct answer

In Vermont, contributory negligence does not bar recovery for negligence claims involving personal injury, death, or property damage as long as the plaintiff’s negligence is not greater than the defendant’s causal total negligence. This comes from 12 V.S.A. § 1036 and it directly affects how DocketMath allocates fault before pain-and-suffering damages are applied.

Practically, your pain and suffering result in DocketMath (damages-allocation) is usually shaped by two layers:

1. Fault allocation / recovery gate based on Vermont’s “not greater than” threshold, and
2. Damage allocation of the pain-and-suffering component according to the plaintiff’s causal negligence inputs (as reflected in the tool’s allocation approach).

What you need to know

The key Vermont rule is in 12 V.S.A. § 1036. It tells you when contributory negligence bars recovery (it often does not), and that affects how you should model damages in DocketMath.

The contributory negligence threshold in Vermont

Under 12 V.S.A. § 1036, contributory negligence shall not bar recovery in a negligence action seeking damages for death, personal injury, or property damage if the plaintiff’s negligence is not greater than the defendant’s causal total negligence.

In plain terms, the comparison works like this:

• If the plaintiff’s causal negligence is equal to or less than the defendant’s causal total negligence → recovery is not barred
• If the plaintiff’s causal negligence is greater than the defendant’s causal total negligence → recovery is barred (for the covered negligence-based action)

How this affects pain and suffering in DocketMath

People sometimes think pain-and-suffering is “separate” from fault. In a negligence system governed by § 1036, the first question is whether recovery is barred under the contributory-negligence threshold. Only after that gate is passed does it make sense to allocate a pain-and-suffering component.

So, when using DocketMath → damages-allocation, you should expect the workflow to follow a concept like:

• Use your inputs to compute/compare plaintiff causal total negligence versus defendant causal total negligence
• Apply the § 1036 gate:

  • Allowed when plaintiff negligence ≤ defendant causal total negligence
  • Barred when plaintiff negligence > defendant causal total negligence
• If allowed, allocate the pain-and-suffering component according to the tool’s damages-allocation method (typically reducing or proportioning non-economic damages based on the causal-fault inputs you provide)

Step-by-step

Use DocketMath’s damages-allocation tool to model Vermont’s § 1036 contributory negligence logic and allocate pain-and-suffering accordingly.

1) Gather the fault comparison inputs (the “bar/no bar” gate)

You need inputs that allow DocketMath to compare:

• Plaintiff’s causal total negligence
• Defendant’s causal total negligence (including a combined total if there are multiple defendants)

If you’re starting from jury-style percentages, enter:

• Plaintiff causal negligence %
• Defendant causal negligence % (or combined defendant total)

If you have multiple defendants, make sure you’re not entering separate defendant values in a way that prevents the tool from forming the correct total defendant causal negligence figure for the comparison.

2) Enter the pain-and-suffering damages base amount

Add a baseline pain and suffering number that the tool will allocate (pre-allocation). For example:

• A pain-and-suffering estimate you want modeled before reduction/allocation, or
• A total pain-and-suffering amount you want the tool to apportion based on your fault inputs

In other words, DocketMath needs a pain-and-suffering component to treat like a damages category for allocation.

3) Apply Vermont’s recovery threshold logic (12 V.S.A. § 1036)

In DocketMath, ensure your scenario supports the Vermont threshold check:

• Not barred when:
  plaintiff negligence ≤ defendant causal total negligence
• Barred when:
  plaintiff negligence > defendant causal total negligence

4) Allocate pain and suffering as a damages component

After DocketMath determines the recovery gate, confirm the pain-and-suffering amount is being treated as part of the allocation process. In practice, check that:

• Pain and suffering is included as a damages category in your scenario, and
• The final “pain and suffering after allocation” reflects your fault inputs rather than leaving pain-and-suffering unchanged when the plaintiff has causal negligence.

5) Document assumptions for traceability

Because pain-and-suffering modeling depends on how you framed the scenario, keep a brief record of:

• What your pain-and-suffering base amount represents (total vs. per-injury vs. per-period), and
• How you obtained the causal negligence inputs (e.g., verdict form percentages, agreed allocation, or your best litigation estimate)

DocketMath output is only as reliable as the inputs you provide.

Key statutes and citations

• 12 V.S.A. § 1036 — Vermont contributory negligence rule for negligence actions involving death, personal injury, or property damage
  Statutory source: https://legislature.vermont.gov/statutes/section/12/185/1036
  The statute provides that contributory negligence shall not bar recovery if the plaintiff’s negligence was not greater than the defendant’s causal total negligence.

General/default rule note: Your brief indicated “no claim-type-specific sub-rule was found,” so this guide uses the default contributory-negligence gating rule in § 1036 for deciding whether negligence-based recovery proceeds, and then treats pain-and-suffering as a damages component in the allocation workflow.

Common pitfalls

1) Treating contributory negligence as always barring recovery

In Vermont under 12 V.S.A. § 1036, contributory negligence is not automatically a bar. The bar depends on whether plaintiff causal negligence is greater than defendant causal total negligence.

2) Mixing incomparable fault measures

Make sure the plaintiff and defendant negligence inputs are comparable—e.g., both are causal negligence percentages or both are scaled to the same “causal total negligence” basis. If one number is effectively a liability-phase estimate and the other is a damages-phase adjustment, the comparison can become meaningless.

3) Forgetting that pain and suffering must be allocated

If your workflow treats pain and suffering as separate from allocation, you may fail to model how the causal-fault inputs should reduce/proportion the pain-and-suffering component in DocketMath.

4) Overprecision without support

A pain-and-suffering base number to the nearest dollar is not the same as having a supportable basis for that number. Use a defensible estimate and keep track of how you derived it.

5) Not using the correct “total defendant causal negligence”

With more than one defendant, you still need a clear total defendant causal negligence figure so that the “not greater than / greater than” comparison matches § 1036.

Run the numbers

Use DocketMath directly here: /tools/damages-allocation.

Input checklist (Vermont)

• Plaintiff causal negligence % (or causal total negligence figure)
• Defendant causal total negligence % (or combined total across defendants)
• Pain and suffering base amount (pre-allocation)
• Recovery threshold check consistent with 12 V.S.A. § 1036:

  • If plaintiff negligence ≤ defendant causal total negligence → not barred
  • If plaintiff negligence > defendant causal total negligence → barred

Output validation questions

After you run the calculation, confirm:

• If the plaintiff negligence is higher, does the output reflect a bar consistent with 12 V.S.A. § 1036?
• If the plaintiff negligence is equal or lower, does DocketMath allocate pain and suffering rather than eliminating it?
• Does the “pain and suffering after allocation” output move in line with the fault percentages you entered?

Tip: If results conflict with your expected “bar/no bar” outcome, don’t just rerun—re-check whether you swapped plaintiff vs. defendant inputs or failed to form the proper total defendant causal negligence.

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