How to run Damages Allocation in DocketMath for West Virginia

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide explains how to run Damages Allocation in DocketMath for West Virginia (US-WV). The goal is to apply jurisdiction-aware rules so your allocation math aligns with West Virginia’s general statute of limitations (SOL) framework.

Before you start, note the key limitation used in this workflow:

• West Virginia default SOL period used here: 1 year
• General statute: W. Va. Code § 61-11-9
• What we did not find: No claim-type-specific SOL sub-rule was identified for this calculator workflow, so the general/default period is used.

1) Open the calculator

1. Go to the calculator: /tools/damages-allocation
2. Select Jurisdiction: West Virginia (US-WV) if the UI requires it.
3. Confirm the calculator type is damages-allocation.

2) Enter the inputs (what each one changes)

Use these inputs to drive the allocation output. Because DocketMath’s UI may label fields slightly differently, match the concepts below to what you see on screen:

• Damages amount (often the total claim figure)

  • Effect: Sets the pool that DocketMath allocates across time buckets and/or damage components (depending on the calculator model).
• Allocation basis / categories (if available)

  • Effect: Controls how DocketMath splits amounts (for example, by time periods or damage components).
• Key dates

  • Effect: Controls whether an amount falls within or outside the SOL window.
• SOL rule application

  • Effect: In West Virginia mode, the default SOL period is applied as 1 year under W. Va. Code § 61-11-9.

If the calculator asks for a date of accrual and/or a case-relevant date (such as filing date or demand date), provide the best-supported dates you have available in your workflow. Small date shifts can change whether certain buckets are treated as potentially time-barred.

3) Verify the SOL assumption shown by DocketMath

After you enter dates, check the calculator’s jurisdiction/SOL summary panel (often near results).

You should see that the tool is using:

• General/default SOL period: 1 year
• Statute: W. Va. Code § 61-11-9
• Source reference: https://codes.findlaw.com/wv/chapter-61-crimes-and-their-punishment/wv-code-sect-61-11-9/

Because no claim-type-specific SOL sub-rule was located for this workflow, DocketMath should apply the general period consistently.

4) Run the allocation

Click Calculate (or the equivalent button).

DocketMath will produce outputs such as:

• Allocated amount within the SOL window
• Allocated amount outside the SOL window
• A breakdown by bucket/category (depending on the calculator design)
• Potentially percentages showing how much is attributable to each segment

5) Review outputs and sanity-check date sensitivity

Treat the results like a model output that depends heavily on the dates you entered.

Do a quick validation:

• If your result shows a large “outside SOL” portion, confirm the accrual date and the relevant date you selected are correct.
• If everything appears “within SOL,” verify you didn’t accidentally enter today’s date (or another unintended date) as the accrual date.

Practical approach: rerun once with a small date adjustment (for example, move the accrual date by ~30 days). If the allocation doesn’t change when you expect it to, re-check the date fields.

6) Export or capture the results for your record

If DocketMath offers export options (PDF/CSV/copy table), save the output snapshot:

• Preserves the **jurisdiction setting (US-WV)
• Preserves the **SOL rule used (W. Va. Code § 61-11-9, 1-year general/default)
• Preserves the exact date inputs used

This is especially helpful when you later iterate on dates or run alternative scenarios.

Common pitfalls

Running Damages Allocation successfully in West Virginia often comes down to a few predictable issues:

• Using the wrong jurisdiction code

  • If you switch away from US-WV, the SOL logic may change even if your numbers stay the same.
• Confusing accrual date vs. filing/relevant date

  • With a 1-year period, even a one-month (or more) mix-up can shift the outcome across the boundary.
• Assuming a claim-type-specific SOL rule exists in this workflow

  • For this West Virginia Damages Allocation workflow, no claim-type-specific sub-rule was found, so the tool uses the general/default period under W. Va. Code § 61-11-9.
• Entering approximate dates without checking sensitivity

  • If you only know dates approximately (e.g., “around May 2023”), consider testing a narrow range of dates to see whether the allocation flips.
• Over-interpreting “outside SOL” inside the output

  • The calculator’s labels reflect its timing math. The real-world legal significance can depend on additional facts and procedural posture—use the output as a quantitative aid, not a final legal conclusion.

Pitfall to watch: A large “outside SOL” bucket can be the expected mathematical result if your accrual date is more than 1 year before the relevant date you selected. In that situation, the first fix is usually correcting dates or aligning your bucket logic—not changing the statute.

Try it

Use this quick checklist to run your first West Virginia scenario in DocketMath:

• Open /tools/damages-allocation
• Confirm Jurisdiction = US-WV
• Enter:

  • Damages amount
  • All key dates the tool requests (especially accrual and the comparison/relevant date)
• Verify the SOL summary shows:

  • 1-year general/default SOL period
  • W. Va. Code § 61-11-9
• Click Calculate
• Review:

  • Allocated amount within SOL window
  • Allocated amount outside SOL window
  • Any breakdown by time buckets/categories
• Run one quick sensitivity check:

  • Adjust the accrual date by ~15–30 days
  • Confirm whether the allocation changes in a way that matches your expectations for your fact pattern

If the result feels “too extreme,” pause and audit the date fields first—especially in a 1-year workflow where boundary effects are common.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules