Why Damages Allocation results differ in West Virginia

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

In West Virginia, DocketMath’s damages allocation can produce different outputs when you enter the same overall scenario but with small input changes. A key reason is that DocketMath applies jurisdiction-aware limitations logic tied to West Virginia’s general statute of limitations framework.

For this jurisdiction, no claim-type-specific sub-rule was found, so the default/general SOL period is the one that drives the comparison.

West Virginia’s general limitation period used by DocketMath is grounded in W. Va. Code §61-11-9 (general SOL period: 1 year). Source: https://codes.findlaw.com/wv/chapter-61-crimes-and-their-punishment/wv-code-sect-61-11-9/

Here are the top 5 reasons results differ for US-WV:

1. **Different “last date” inputs (trigger date mismatch)

   • If you enter different dates for when damages accrued or when the conduct ended, DocketMath checks whether amounts fall inside vs. outside the 1-year general SOL under W. Va. Code §61-11-9.
   • Even a shift of a few weeks can move a component from “eligible” to “limited/excluded,” changing bucket totals.

2. Ownership/party mapping changes

   • Allocation results depend on which party each damages component is assigned to (for example, who incurred costs versus who received benefits).
   • If you relabel parties or remap ownership between runs, the same numeric amounts can be allocated into different output categories.

3. Damages category granularity

   • If one run breaks damages into more line items (e.g., labor vs. materials vs. incidental expenses) while another blends them, DocketMath may apply timing logic per line item rather than to a single blended total.
   • That can create materially different inclusion/exclusion outcomes under the 1-year window.

4. Overlapping time windows

   • When multiple components cover overlapping periods, the “effective” eligible portion may be computed differently depending on how you enter ranges (single continuous range vs. multiple ranges).
   • Small edits to start/end dates can change which portion is treated as within the general 1-year SOL.

5. Missing or inconsistent date formatting

   • DocketMath is sensitive to date fields. If you submit inconsistent formatting—or accidentally switch a start date and end date—the model can treat different parts of the damages timeline as inside/outside the general 1-year SOL.
   • The result is often a sudden shift in one or more output buckets.

To try the calculator directly, use /tools/damages-allocation (DocketMath).

How to isolate the variable

Use DocketMath to run controlled comparisons. The goal is to identify which input change causes the output bucket differences.

Checklist:

• Ensure every run uses the same SOL baseline: 1 year under W. Va. Code §61-11-9.
• Eligible amount (within 1 year)
• Limited/excluded amount (outside 1 year)
• Any computed totals

Practical tip: If you’re using a URL workflow, you can go to /tools/damages-allocation and iterate quickly. For faster debugging, copy the baseline inputs and change just one field before rerunning.

Next steps

1. Create a short “input audit”

   • Write down every date field you entered (start date, end date, accrual/trigger date).
   • Confirm party labels for each damages line.
2. Re-run with one adjustment per run

   • Try to reduce the issue to a single bucket (for example: “only the eligible within 1-year portion changes”).
3. Align your data with the timeline you actually want modeled

   • If you’re modeling discrete events, enter them as separate line items with corresponding date ranges.
4. Capture your baseline and the two most divergent runs

   • Keep those for quick comparison of which bucket moved and by how much.

If you want to sanity-check why the output changed, relate the difference back to the West Virginia baseline: W. Va. Code §61-11-9 provides the general/default 1-year period, and (because no claim-type-specific sub-rule was found here) most allocation differences come from how your dates and line items map onto that 1-year window.

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