How to run Damages Allocation in DocketMath for West Virginia

Step-by-step

You can run Damages Allocation in DocketMath for West Virginia (US-WV) using jurisdiction-aware rules tied to West Virginia’s tort reform framework. This walk-through assumes you’re using the Damages Allocation calculator in DocketMath.

1) Open the correct tool and choose the West Virginia jurisdiction

1. Go to the primary CTA: /tools/damages-allocation
2. Select jurisdiction: West Virginia (US-WV).
3. Confirm you’re in the Damages Allocation calculator (not another calculator that only estimates damages or only allocates fault).

What changes in DocketMath: jurisdiction selection drives the applicability of West Virginia’s several-liability rule and its modified comparative fault structure (including the 51% bar, described below).

2) Gather the inputs DocketMath needs

DocketMath’s Damages Allocation flow generally requires, at minimum, the following categories of information:

• Total damages (the fact-finder’s damages total before allocation)
• Fault allocation percentages for each responsible party (including the plaintiff if the model includes plaintiff fault)
• Your fault bar / threshold behavior (i.e., what happens when plaintiff fault triggers the statutory bar)
• Any optional modeling choices your workflow uses (for example, how to handle parties with 0% fault)

If your interface asks for specific fields (party names, roles, or separate plaintiff vs. defendant fault fields), map them to how your case is recorded.

3) Enter fault percentages in a way that matches your record

West Virginia’s tort reform (S.B. 421 era) replaced joint and several liability with pure several liability and codified modified comparative fault with a 51% bar.

• Pure several liability means each defendant is generally responsible separately for their percentage share, rather than being jointly responsible for the entire amount.
• Modified comparative fault with a 51% bar means the plaintiff’s recovery is reduced based on the plaintiff’s own percentage fault, and recovery is barred when plaintiff fault reaches the statutory threshold (modeled as: if plaintiff fault is 51% or more, recovery becomes $0 for the plaintiff’s side, depending on how you represent “recovery” in the tool).

In DocketMath:

• Enter fault values as percentages (e.g., 20 not 0.20) unless the tool explicitly instructs otherwise.
• Check whether DocketMath expects faults to sum to 100%. If it enforces total-to-100, adjust for rounding so the sum matches what the tool expects.

4) Use W. Va. Code § 55-7-13a et seq. to guide interpretation of results

West Virginia’s framework is codified at:

• W. Va. Code § 55-7-13a et seq. (2015 tort reform; S.B. 421) including:

  • the shift to several liability
  • modified comparative fault with a 51% bar

How the statute affects outputs in DocketMath:

• If a defendant has 30% fault, DocketMath will generally allocate that defendant’s share as 30% of the damages (several-liability style), rather than allowing “full amount from one defendant.”
• If the plaintiff’s fault is 51% or more, DocketMath’s “recovery” outputs should reflect the statutory bar—often resulting in $0 recoverable for the plaintiff’s side, depending on how the tool models plaintiff recovery.

Gentle disclaimer: DocketMath is an input-driven calculator. It reflects your numbers and West Virginia’s general/default allocation framework, but it does not replace legal advice or the underlying record (e.g., verdict forms, findings of fact).

5) Review allocation outputs party-by-party

After you calculate, you should be able to answer:

• What is each party’s allocated share of damages?
• Does plaintiff fault trigger the 51% bar?
• How sensitive are outputs to small changes (for example, moving plaintiff fault from 50% to 51%)?

Practical workflow:

• Change one fault percentage at a time and re-run.
• Observe the exact point where comparative fault turns the plaintiff’s recovery to zero at the 51% bar.

6) Export or capture your results for reporting

Many users need a clean record of assumptions:

• Total damages entered
• The fault percentages used for each party
• The resulting allocations and whether the plaintiff bar outcome occurred

Capture outputs in a way you can review with your team, but avoid treating calculator outputs as factual findings.

Common pitfalls

West Virginia tort-reform modeling tends to break in predictable places. Watch for these:

• Using the wrong liability framework (joint vs. several)

  • West Virginia’s tort reform is built around pure several liability, where exposure is based on each party’s percentage share.
• Crossing the 51% bar without noticing

  • If plaintiff fault reaches 51% or more, recovery is barred under the modified comparative fault framework described for the S.B. 421 reforms codified in W. Va. Code § 55-7-13a et seq.
• Entering decimals instead of percentages

  • Example: entering 0.3 instead of 30 can produce nonsensical allocations.
• Fault totals drifting due to rounding

  • If the tool expects totals to sum to 100%, rounding errors can matter. Ensure your inputs align with the tool’s requirements.
• Assuming claim-type-specific rules are included

  • For this write-up, no claim-type-specific sub-rule was found in the cited framework. If your case involves a specialized statutory cause of action, you may need rule coverage beyond the default model.
• Treating DocketMath results as fact-finding

  • DocketMath allocates based on the inputs you provide. It doesn’t replace jury findings, interrogatory answers, or trial findings.

Try it

To validate your setup quickly, run one controlled scenario and then modify one variable at a time.

Quick “sanity check” exercise

1. Enter:

   • Total damages: pick a round number (e.g., 100,000)
   • Defendant fault: split into two or three defendants (example: 20% / 30% / 50%)
   • Plaintiff fault: start at 50%
2. Calculate and confirm:

   • Plaintiff recovery is not barred at 50% (since the bar is 51%).
3. Now change only the plaintiff fault to 51% and re-calculate.
4. Confirm:

   • Plaintiff recovery becomes barred under the modified comparative fault framework described in W. Va. Code § 55-7-13a et seq.

What you should learn from the output

• Pure several liability should map defendant responsibility to their percentage shares.
• Comparative fault should show the threshold effect at the 51% bar.
• Outputs should remain consistent when you reorganize party labels, as long as the percentages don’t change.

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