How to calculate Offer Of Judgment Analyzer in West Virginia

Quick takeaways

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

• West Virginia’s offer-of-judgment consequence is governed by W. Va. Code § 56-4-3, which hinges on whether the party who does not accept an offer ultimately gets a verdict more favorable than the offer.
• DocketMath’s Offer Of Judgment Analyzer (US-WV) models that decision pressure by comparing the offer amount you enter to the verdict amount (or other modeled outcome) you provide.
• In the material reviewed for this workflow, no claim-type-specific sub-rule was found for West Virginia—so this calculator applies the general/default rule reflected in § 56-4-3, rather than special timing adjustments by cause of action.
• If the rejecting party fails to obtain a verdict more favorable than the offer, the rejecting party can be liable for costs of the action incurred by the offeror, consistent with § 56-4-3.

Inputs you need

Before you run the Offer Of Judgment Analyzer in DocketMath (jurisdiction US-WV), gather the numbers your case needs to compare.

Use this intake checklist as your baseline for Offer Of Judgment Analyzer work in West Virginia.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

Core inputs

• Offer amount (WV)
  The dollar value of the offer of judgment you’re analyzing.

• Direction of comparison
  The “more favorable” concept is evaluated relative to the side the offer benefits. In practice, you’ll need to select the scenario that matches your intent, such as:

  • “I’m modeling the situation where my side made the offer and the other side rejected,” or
  • “I’m modeling the reverse (the other side made the offer and my side rejected).”

• Verdict amount (modeled outcome)
  The money figure you want DocketMath to compare to the offer amount (for example, a jury verdict total, based on the convention your workflow uses consistently—pre- or post-adjustment, as long as you’re consistent).

Timing inputs (to align with “when” the offer is made)

W. Va. Code § 56-4-3 discusses an offer of judgment “made by either party and not accepted.” For practical use in this tool, you typically need:

• Offer date (or at least the stage/date range)
• Verdict date (optional in some runs, but helpful for consistency)

Costs inputs (if you want more than a trigger/no-trigger answer)

Because § 56-4-3 addresses liability for “costs… incurred,” you may want to estimate the financial impact. If DocketMath supports it in your run mode, gather:

• Estimated recoverable costs incurred by the offeror (if you have a figure)
• Whether you want a costs-inclusive view or a comparison-only view

A practical workflow is:

1. run comparison-only to understand the threshold, then
2. re-run with cost figures if you want an estimate of cost exposure.

How the calculation works

DocketMath’s Offer Of Judgment Analyzer (US-WV) models the statutory trigger in W. Va. Code § 56-4-3: whether the party who rejects the offer gets a verdict more favorable than the offer.

DocketMath applies the West Virginia rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.

1) The decision rule being modeled (West Virginia)

Under W. Va. Code § 56-4-3, the key consequence is:

• If an offer of judgment is made and not accepted,
• then the party who does not accept may be liable for costs of the action incurred by the offeror if that rejecting party fails to obtain a verdict more favorable than the offer.

The jurisdiction data provided highlights the statute’s opening language:

“In any civil action where there is any offer of judgment made by either party and not accepted by the other party, the party who does not accept the offer shall, in the event that party fails to obtain a verdict more favorable than the offer, be liable for the costs of the action incurred by the par…”
**(W. Va. Code § 56-4-3)

2) Default vs. claim-type-specific logic (West Virginia)

Per the jurisdiction note for this workflow: no claim-type-specific sub-rule was found. That means you should not build special timing logic into your DocketMath run based on cause of action.

So the practical takeaway is:

• Treat West Virginia’s offer-of-judgment consequence here as primarily driven by:

  • offer amount
  • verdict outcome relative to the offer
  • costs incurred by the offeror, if you input them

3) The “threshold” comparison: how outputs change

At a high level, the calculator performs a threshold comparison:

• Step A: Determine whether the modeled verdict is more favorable than the offer for the relevant side (based on the comparison direction you select).
• Step B:

  • If the verdict is more favorable, the statutory cost consequence is typically treated as not triggered in the model.
  • If the verdict is not more favorable, the tool projects that the cost consequence is triggered (subject to your cost inputs).
• Step C: If costs are provided, the calculator can estimate financial impact aligned to the statute’s “costs incurred by the offeror” concept.

Because “more favorable” depends on which side’s perspective matters, selecting the correct direction of comparison is one of the biggest drivers of accurate outputs.

4) Output categories you should expect

When you run the calculator, your output generally falls into practical buckets:

• Comparison result: “Verdict beats offer” vs. “Verdict does not beat offer”
• Cost consequence (if costs are provided):

  • If the verdict fails to beat the offer, the tool models a costs consequence consistent with § 56-4-3
• Sensitivity / what-if testing: how changing offer or verdict flips the trigger

This threshold behavior is where DocketMath is especially useful: you can quickly test multiple offer values to see where the outcome changes.

5) Example: how the threshold flips

Illustration (simplified):

• Offer amount: $50,000
• Verdict amount: $45,000

If your “more favorable” direction is set so that the side benefited by the offer is the one compared against the offer, then:

• $45,000 does not beat $50,000 → the “fails to beat offer” condition is met → the cost consequence is the model’s expected outcome.

Change the verdict to $60,000:

• $60,000 beats $50,000 → the cost trigger is not met in the model.

In real use, you’ll want to use your actual conventions for what number you label as the verdict amount (and how offsets/adjustments are handled).

Common pitfalls

Avoid these common issues when using an offer-of-judgment analyzer:

• Mixing up which side you’re modeling

  • If you enter the same numbers but reverse the “rejecting party” perspective, you can invert the “more favorable” logic.

• Comparing net vs. gross numbers inconsistently

  • If your “verdict amount” is entered after offsets, fee shifts, or post-trial adjustments, your comparison may not match your offer amount convention. Keep the same approach across runs.

• Forgetting the threshold nature of the calculation

  • This is a “beats/no beats” test. Changing the offer (or verdict) by even a small amount—like $5,000—can flip the outcome.

• Over-relying on the model without cost inputs

  • W. Va. Code § 56-4-3 focuses on costs incurred. If costs are left blank, the tool may still show the trigger based on the threshold comparison, but it can’t compute numeric cost exposure.

• Assuming claim-type timing or special rules apply

  • The jurisdiction note for this workflow states no claim-type-specific sub-rule was found here. Don’t assume separate offer timing regimes by claim type unless you have a specific statutory basis beyond this workflow.

Sources and references

• W. Va. Code § 56-4-3 (Offer of judgment; costs consequence)
  http://www.legis.state.wv.us/wvcode/ChapterEntire.cfm?chap=56&art=4&section=3
  (Key concept used in this workflow: if the party who rejects the offer fails to obtain a verdict more favorable than the offer, that rejecting party may be liable for costs of the action incurred by the offeror.)

Next steps

1. Open DocketMath’s Offer Of Judgment Analyzer: /tools/offer-of-judgment-analyzer
2. Enter:

   • **Offer amount (WV)
   • **Verdict amount (modeled outcome)
   • Direction of comparison (so “more favorable” aligns with the rejecting party scenario)
3. Choose a run mode:

   • Comparison-only first to understand the threshold, then
   • Cost-included if you want numeric estimates using your entered “costs incurred” figures.
4. Run at least 3 scenarios:

   • Verdict just below the offer
   • Verdict at the offer (use your conventions to see how the tool treats equality)
   • Verdict above the offer

If you’re preparing for settlement discussions, threshold testing often makes leverage points clearer than a single pass.

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado