How to interpret Damages Allocation results in West Virginia

What each output means

Run this scenario in DocketMath using the Damages Allocation calculator.

In West Virginia, DocketMath’s Damages Allocation calculator helps you understand how a set of damages amounts may be broken into components based on the assumptions you entered (for example: categories of damages, time allocation, and any allocation logic the tool applies). The outputs should be treated as an organized allocation of totals based on your inputs, not as a final court determination.

Because this is a West Virginia–specific workflow, you’ll often see the tool’s totals paired with timing concepts that matter under West Virginia’s general limitations period. Under your jurisdiction data, no claim-type-specific sub-rule was found, so the calculator should use the general/default period of 1 year unless you change the tool settings or assumptions.

1) Total allocated damages

This is the sum of all allocated line items the tool computes from your inputs. Read it as the aggregate number produced by the allocation model.

2) Component allocations (line items)

Each component allocation represents the tool’s best-fit breakdown into the categories you selected (or that your inputs imply). Depending on how you configure Damages Allocation, component line items can reflect distinctions like:

• Economic vs. non-economic categories
• Separate buckets by time period or damage type (if your setup slices damages across time)

If you see component totals that add up to (or closely match) the total allocated damages, that’s the tool “reconstructing” your overall damages using its allocation approach.

3) “Allocated vs. requested” / reconciliation checks (where provided)

If DocketMath includes a reconciliation (sometimes labeled as an “allocated totals” comparison, or an “allocated vs. requested” check), it typically shows whether the tool’s components sum to:

• the total you entered, and/or
• an internal baseline total the model uses.

Use this output to spot input issues such as:

• a category amount left blank,
• a mismatch between a “total” field and the category fields, or
• rounding effects.

4) Time-related outputs tied to West Virginia limitations logic

For West Virginia, your jurisdiction data points to a general/default statute of limitations period of 1 year, associated with:

• W. Va. Code § 61-11-9 (general/default limitations period: 1 year)
  Source: https://codes.findlaw.com/wv/chapter-61-crimes-and-their-punishment/wv-code-sect-61-11-9/

Important: Because no claim-type-specific sub-rule was found in the provided jurisdiction data, the calculator should not automatically swap in a different limitations period by claim type. In other words, the baseline expectation remains 1 year unless you explicitly adjust the tool’s assumptions/settings.

5) “Start date” / “lookback window” framing (if shown)

If the output includes a “window” (for example, damages treated as within versus outside the limitations period), it is describing the time span used by the model. Interpreting it correctly requires matching it to the dates you entered in DocketMath (e.g., event/accrual/occurrence date fields—whichever you selected as relevant inputs).

What changes the result most

DocketMath’s Damages Allocation results typically move the most when you change the inputs that control allocation math and the inputs that control the timeline.

Below are the biggest “levers” to review for US-WV.

These inputs have the biggest impact on the final number. Adjust them one at a time if you need a sensitivity check.

• date range
• rate changes
• assumption changes

1) Date inputs used for the 1-year lookback

Because the baseline is 1 year under W. Va. Code § 61-11-9, small changes in the date you use as the “start” can shift which components fall inside the model’s limitations window.

Practical checklist:

• Confirm which date field you used as the model’s start/accrual/event date.
• Confirm which damages components (especially if you time-sliced damages) are treated as inside the window.
• If you have an alternative fact pattern for accrual/start, re-run using that alternative date.

2) Category selection and category amounts

If you entered separate buckets—or if the tool inferred buckets from your selections—the component allocations will change immediately when you:

• reassign dollars between categories,
• add/remove categories, or
• adjust the inputs that define category amounts.

3) Allocation weights or distribution assumptions

If Damages Allocation uses weights (for example, proportional splits by duration, frequency, or another factor), those assumptions can strongly affect the breakdown even if the total allocated damages stays the same.

Rule of thumb:

• If the total stays constant but component percentages shift, you likely changed an allocation weight, ratio, or slicing rule, not the overall sum.

4) Output reconciliation mismatches

If the tool indicates that allocations don’t tie back cleanly to an expected total, the most common causes are:

• a missing category amount,
• inconsistent totals (one total field updated but category sums didn’t match),
• rounding differences.

5) Jurisdiction setting confirmation (US-WV)

Make sure DocketMath is actually running in West Virginia (US-WV) mode. If you run a different jurisdiction, the “1 year” baseline linked to W. Va. Code § 61-11-9 may not apply, and the timing-related outputs can become misleading.

Pitfall: A wrong jurisdiction can make timing outputs look precise while being legally inapplicable. Always confirm the jurisdiction code US-WV before using limitations-window results.

Next steps

To interpret Damages Allocation results responsibly in West Virginia (without treating the calculator as legal advice), use this workflow:

1. Read outputs in pairs

• Match the total allocated damages to the component allocations.
• If there’s a time window, match it to the dates you entered.

1. Verify the 1-year limitations baseline in West Virginia DocketMath’s West Virginia workflow should reflect the general/default limitations period of 1 year associated with W. Va. Code § 61-11-9.

• Reconcile the time-window output to the fact-pattern dates used in your inputs.
• Since your jurisdiction data found no claim-type-specific sub-rule, don’t assume the tool will automatically select a different period by claim type.

1. Re-run after changing the two biggest drivers Do targeted stress tests:

• Update the start/accrual date used for the 1-year window.
• Update the category amounts (and any weights) that drive the component split.

1. Document the assumptions you used If you’re using the output for internal notes or case planning, capture:

• the exact date values entered,
• the category structure selected,
• any allocation weights/distribution settings used.

1. Use outputs for issue-spotting Damages Allocation is most useful for:

• understanding how assumption changes affect the breakdown,
• identifying which category or time period swings the totals the most, and
• generating targeted questions for later review.

Start the workflow here: /tools/damages-allocation.

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