The top mistakes

Damages allocation errors in West Virginia often come from treating “damages” as one undifferentiated number. In practice, allocation issues can change what’s recoverable, how damages are presented, and whether a claim is timely. Using DocketMath’s damages-allocation calculator can help you organize inputs—but the biggest wins usually come from avoiding predictable mistakes.

Below are the most common damage-allocation mistakes we see for West Virginia (US‑WV) matters.

1) Missing the timeliness assumption (SOL vs. allocation)

A frequent error is to assume allocation affects the statute of limitations (SOL). In reality, SOL generally governs whether a claim can be brought at all—not how you later split damages within a pleading or calculation.

For West Virginia, the general/default SOL period is 1 year, under W. Va. Code § 61-11-9. This article uses that general rule as the baseline because no claim-type-specific sub-rule was found in the provided data. (That does not mean other categories never exist—just that this content is anchored to the general/default period you provided.)

What goes wrong in practice

• You allocate damages carefully, but the demand/filing happens outside the 1-year window for the general rule.
• Your damages work product looks “right,” yet the underlying claim is vulnerable on timing.

2) Using the wrong units or inconsistent time bases

Allocation inputs frequently mix:

• totals vs. line items,
• per-day amounts vs. lump sums,
• different date ranges (e.g., damages “from March 1 to April 1” in one field, “from March 1 to March 31” in another).

Typical symptom

• Your spreadsheet adds up cleanly, but the sum doesn’t match what DocketMath expects because the underlying time base differs.

Impact on output

• Change the start/end date in one component and the calculator’s allocation totals can swing materially—especially when one category is time-dependent.

3) Double-counting overlapping damage categories

Even when the categories seem distinct, they may be the same economic harm described two ways.

Common overlap patterns:

• “Loss of income” and “wage/earnings” included separately without confirming they’re not the same pool.
• “Repair costs” plus “diminution in value” without distinguishing whether both are being asked for on the same asset and for the same timeframe.

Impact on output

• DocketMath totals can become inflated because two separate input streams actually represent the same underlying loss.

4) Not defining allocation methodology before entering numbers

If the method isn’t fixed up front, users tend to “eyeball” percentages after seeing calculator output. That leads to inconsistent allocations across drafts.

Examples of methodology drift:

• Early draft allocates 60/40 between two causes, later draft changes to 55/45 without documenting why.
• Category A is allocated by percentage one time, but by exact amounts another time.

Impact on output

• Your final allocations can become non-auditable: anyone reviewing your inputs can’t tell which rule drove each split.

5) Treating negative or zero values as harmless

Zero and negative entries often signal a data problem:

• negative amounts appear due to refunds or offsets, but the model may not be designed to net them the way you intend,
• a zero value might reflect “missing data,” not “no damages.”

What to check

• If a field is zero, confirm it’s intentional.
• If a field is negative, confirm the calculator logic matches your approach to offsets.

How to avoid them

A reliable damages allocation workflow is part math, part documentation. Here’s a practical checklist designed for use with DocketMath. (This is general information, not legal advice.)

Step 1: Lock your timeliness baseline (West Virginia)

Use the general/default SOL period as your initial filter:

• West Virginia general SOL: 1 year
• Statute: W. Va. Code § 61-11-9 (general period referenced for this article)

Because no claim-type-specific sub-rule was found in the provided jurisdiction data, treat this as the default starting point for timing checks in your workflow.

Actionable workflow

• Create a simple “timeline box” in your working notes:

  • event date (e.g., accrual trigger date you’re using),
  • filing/demand date,
  • compute “days elapsed” and compare to 1 year.

Even if DocketMath doesn’t compute SOL, this prevents you from doing a full allocation on a case that’s already time-barred under the general rule.

Step 2: Standardize your time windows and units

Before entering numbers into DocketMath:

• Confirm whether each damages component is per day, per month, or lump sum.
• Ensure the same start date and end date are used across time-based components.

Quick validation

• Add a note: “All time-based components cover YYYY‑MM‑DD through YYYY‑MM‑DD.”
• If any component uses a different window, label it and enter it separately.

Step 3: Use a “no-overlap” list for categories

Create a short internal mapping like:

• Category: Income loss

  • Source: pay stubs / invoices / statements
  • Overlap risk: “Do not include the same period as wage/earnings if separately entered.”

• Category: Repair costs

  • Source: invoices
  • Overlap risk: “Do not include costs already embedded in replacement value.”

This is less about legal theory and more about data integrity: it stops double-counting before it reaches DocketMath.

Step 4: Choose an allocation method and keep it stable

Pick one approach and apply it consistently during calculation:

• Method A (percentage split): Allocate a single harm bucket across parties/components.
• Method B (direct totals): Enter each component as its own amount with minimal percentage logic.
• Method C (hybrid): Percentage split only when the underlying totals are documented and not overlapping.

Then, document the method in one sentence near your inputs. That reduces accidental drift between drafts.

Step 5: Sanity-check the outputs against your “sum story”

After running /tools/damages-allocation, compare:

• the calculator’s category totals vs. your source totals,
• the grand total vs. the sum of intended components.

If DocketMath returns an amount you can’t reconcile, treat it as a sign to revisit:

• time windows,
• units,
• overlap,
• zeros/negatives.

DocketMath workflow checklist (copy/paste)

• I’m using the West Virginia default SOL = 1 year for timing triage under W. Va. Code § 61-11-9
• All time-based inputs use the same start/end dates (or are clearly separated)
• Units are consistent (daily, monthly, or lump sum)
• Categories are checked for overlap (no duplicate economic harm)
• I committed to an allocation method before entering inputs
• Zero and negative values are intentional and match my intended netting/offset logic
• I can reconcile the calculator total to my source “sum story”

Related reading

• Browse the blog