How to run Offer Of Judgment Analyzer in DocketMath for West Virginia

Step-by-step

Below is a practical walkthrough for running Offer Of Judgment Analyzer in DocketMath for West Virginia (US-WV), using jurisdiction-aware rules based on West Virginia Rule 68.

1) Open the tool

1. Go to the primary call-to-action: /tools/offer-of-judgment-analyzer
2. Select West Virginia (US-WV) as the jurisdiction.

2) Enter the core Rule 68 “offer math” inputs

DocketMath’s analyzer is designed around Rule 68 mechanics. In the tool, you’ll typically see fields for things like:

• Offered amount (the dollar amount in the offer)
• Judgment amount (the judgment you want to compare against the offer, or the amount you expect the case will end at)
• Offer date
• Trial start date (the date that starts the “before trial begins” timing measurement)
• Costs inputs (whether and how the tool models costs impact, depending on the interface)

Because timing is central to Rule 68, use real court dates when possible (not estimates), and be consistent with what the tool labels as the trial start date.

Quick checklist for entries:

• Offer amount (money or the effect specified in the offer)
• Judgment amount (the amount used in the comparison step)
• Offer date
• Trial start date (trial begins)
• Costs inputs (if requested)

3) Confirm the timing rule applies (West Virginia Rule 68 default)

West Virginia Rule 68 allows an offer “at any time more than 10 days before the trial begins”. The jurisdiction text also references a “within 10 days” concept in the surrounding framework, but the timing rule you’re working with for the offer timing analysis is the default “more than 10 days before trial begins” period.

In other words, unless the tool indicates otherwise, DocketMath should apply the general period that starts counting more than 10 days before trial begins.

Practical timing action:

• Compute whether your offer date is strictly earlier than the cutoff.
• A simple way to think about it:

  • If trial begins on June 20, then “more than 10 days before” means the offer must be made before June 9.
  • Why: June 10 is exactly 10 days before June 20, and the rule says more than 10 days (so exactly 10 days is not enough).

If the tool shows a timing validity warning, treat it as meaningful—timing is part of Rule 68’s structure, not just a clerical detail.

4) Choose the scenario you want to analyze

Most Offer Of Judgment Analyzer experiences let you run the math either:

• Prospectively (e.g., “If we offer $X, what happens if judgment ends up at $Y?”), or
• Retrospectively (e.g., “Given the final judgment, did our offer look favorable?”)

In DocketMath, this usually comes down to which numbers you enter for offer amount and judgment amount, and how the tool frames the comparison.

Practical tip: If you’re unsure which mode you’re effectively running, start with a scenario that uses your best-known dates and the most defensible judgment amount, then adjust one number at a time (see Step 6).

5) Run the calculation and interpret the outputs

After you click Calculate, review outputs in three layers:

1. Timing validity

   • Does the tool consider the offer “at any time more than 10 days before the trial begins”?
2. Outcome comparison

   • How does the judgment amount compare to the offered amount in the way Rule 68-style mechanics require?
3. Modeled cost impact

   • If the tool estimates consequences tied to costs, read that estimate alongside the comparison and timing results.

If the tool indicates timing is not satisfied, it’s usually best to fix the offer date first. Otherwise, the cost impact and threshold comparisons may reflect a mismatch with Rule 68’s intended timing structure.

6) Iterate: adjust one variable at a time

Use the analyzer as a decision simulator. A clean workflow:

• Change only the offered amount
• Re-run
• Keep trial start date and judgment amount fixed
• Compare the result threshold behavior and any modeled cost impact changes

Then, if needed, try changing offer date next (but only after you’ve already verified you understand the timing cutoff logic).

7) Save or record the scenario (if available)

If DocketMath supports saving/exporting:

• Save the scenario with clear identifiers like:
  “WV Rule 68 — Offer $50k, Trial June 20”
• Record the inputs you used (offer amount/date, trial start date, judgment amount)

For collaboration (litigation teams), capturing the exact inputs is often just as important as capturing the output.

Common pitfalls

West Virginia Rule 68 has a few recurring “gotchas” that commonly show up when running an analyzer. These are the issues most likely to create results that don’t align with how the rule would operate.

1) Timing mistakes (especially the “exactly 10 days” problem)

Watch for:

• Offer date = exactly 10 days before trial start (likely fails the default timing test)
• Confusing the trial start date with another date (pretrial milestones are often not the “trial begins” date the rule uses)

2) Confusing “trial begins” with other court dates

Pitfall: Using a pretrial hearing or motion deadline date instead of the actual date your scheduling order identifies as when trial begins.

Fix: Ensure the date you enter matches the tool’s label and corresponds to the day the trial begins.

3) Using estimates that later change

Pitfall: Estimating trial start dates and then updating them later. Even a small shift can flip the “more than 10 days” validity result.

Fix: If your trial date changes, re-run the scenario.

4) Entering the wrong “effect” or comparison amount

Rule 68 covers offers for money or property or to the effect specified. If your tool supports only monetary amounts, you’ll still want to use the closest supported proxy consistently.

Pitfall checklist:

• You entered the intended offer amount/effect
• You entered the correct judgment amount used for the comparison step
• You didn’t accidentally compare against an earlier partial figure rather than the relevant judgment outcome for the analyzer

5) Costs inputs inconsistent with your scenario

If DocketMath asks for costs assumptions, costs modeling can materially change results.

Pitfall: Changing offer amount while also changing costs assumptions without realizing it.

Fix: When sensitivity-testing, change one variable at a time—usually start with offer amount, then later adjust costs inputs only if you must.

Quick timing rule reference (West Virginia default)

Based on the provided jurisdiction text, the relevant default timing language is:

• “At any time more than 10 days before the trial begins”
• plus an additional “within 10 days” concept elsewhere in the rule’s framework

For the purposes of this guide, DocketMath applies the default “more than 10 days before trial begins” timing period unless the tool indicates an alternate path.

Try it

Here’s a quick “run it now” workflow you can complete in under 3 minutes.

1) Set up your baseline scenario

1. Open: /tools/offer-of-judgment-analyzer

2. Set jurisdiction: West Virginia (US-WV)

3. Enter:

   • Offer amount: $50,000
   • Judgment amount: $45,000 (use the amount you expect or the final judgment amount you want to analyze)
   • Offer date: pick a date that is strictly more than 10 days before the trial begins
   • Trial start date: enter the trial beginning date your schedule controls

4. Click Calculate

2) Interpret the result

• If timing is valid:

  • Focus on the offer vs. judgment comparison and any modeled cost impact estimate.
• If timing is not satisfied:

  • Go straight back to the offer date and adjust it until it clears the “more than 10 days” threshold.

3) Run a sensitivity test

Keep everything the same, then change only the offer:

• Offer amount: $60,000
• Click Calculate again

Compare outputs—especially any “threshold” behavior and cost impact changes—so you can see how sensitive the outcome is to the offered amount.

Gentle reminder: DocketMath output is a structured calculation of Rule 68-style mechanics based on the inputs you provide. It’s not a substitute for case-specific legal review.

Related reading

• How to calculate Offer Of Judgment Analyzer in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Offer Of Judgment Analyzer in Philippines — Worked example with real statute citations
• [Inputs you need for Offer Of Judgment Analyzer in Philippines](/blog/inputs-offer-of-jud