Inputs you need for Damages Allocation in West Virginia
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Damages allocation in West Virginia usually hinges on two practical inputs: (1) what damages categories you’re allocating and (2) what time window (SOL-sensitive date logic) you’re applying to those damages. DocketMath’s damages-allocation calculator helps you turn the information you already have—documents, schedules, and claim/damages data—into a consistent allocation you can adjust as you refine timelines and evidence ranges.
Before you run anything, gather these inputs:
Case details
- West Virginia jurisdiction confirmation (US-WV)
- Your claim/cause reference label (use your internal label; the calculator uses the numbers and dates you provide)
- Allocation analysis date range you want to study (start date + end date)
**Damages category amounts (by type)
- Economic damages total (for example, out-of-pocket expenses, documented medical costs, lost income)
- Non-economic damages total (for example, pain and suffering), if your dataset includes it
- Other categories you track (for example, property damage, future treatment costs, additional medical charges)
- Already-agreed payments or offsets you want to reflect in the allocation inputs (if applicable)
**Attribution drivers (how each category is allocated)
- Who bears which component, using your own labels (for example, Party A vs. Party B, or claimant vs. counterparty)
- Allocation weights or factors (for example, percentages, units, or proportional drivers) that match your workflow
**Evidence timing for damages (the SOL-sensitive piece)
- The earliest relevant date supporting each damages component/category
- The latest relevant date supporting each damages component/category
- The date you’re running the allocation (so the tool can compare your evidence timing to the SOL window you’ve selected/configured)
West Virginia SOL note (use the general/default rule): The general/default statute of limitations (SOL) period is 1 year under W. Va. Code § 61-11-9. This content uses that default period because no claim-type-specific sub-rule was found in the provided jurisdiction data.
Source: https://codes.findlaw.com/wv/chapter-61-crimes-and-their-punishment/wv-code-sect-61-11-9/
Where to find each input
Use DocketMath as the “organizing layer,” but collect the raw inputs from your case materials. A practical mapping:
Case details
- Pull from the caption page, docket entry metadata, or your intake/matter tracking sheet.
- If you’re running multiple scenarios, adopt a clear naming convention (for example, “WVDAM-Scenario-1: 2023-01 to 2023-12 timeline”).
Damages category amounts
- Medical expenses: medical bills, treatment summaries, demand package spreadsheets, itemized medical statements
- Lost income: payroll records, wage statements, expert summaries (if used), damages schedule totals
- Property damage: estimates and repair invoices, receipts, valuation summaries
- Non-economic damages: narrative damages worksheets and valuation memos (keep them consistent with how you plan to weight/allocate)
Already-agreed payments / offsets
- Settlement communications and payment confirmations
- Internal reconciliation spreadsheets (make sure totals match what you want the calculator to net or reconcile)
Attribution drivers
- If you allocate by percentages: use the percentages from your damages model assumptions (often an Excel/Sheets model)
- If you allocate by units or counts: use underlying line items (billing entries, treatment occurrences, time logs)
**Evidence timing (earliest/latest dates by category)
- Review the documents that first and last support each category.
- Record an earliest relevant date and latest relevant date for each category in your allocation inputs.
- Consistency matters: if your “earliest” dates are based on rough estimates, the allocation can appear to shift in ways that don’t reflect the actual evidence trail.
**The SOL default you’ll use (jurisdiction-aware workflow setting)
- For West Virginia, use the 1-year general/default SOL period tied to W. Va. Code § 61-11-9:
- Statute: W. Va. Code § 61-11-9
- Period: 1 year (general/default; no claim-type-specific sub-rule found in provided jurisdiction data)
If you’re using DocketMath, go to the tool here: damages-allocation tool.
Run it
After you collect your inputs, enter them into DocketMath’s damages-allocation calculator. The most important practical lever usually isn’t the total damages—it’s the date logic and category structure you enter.
Use this checklist while running:
Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.
How outputs change when you update inputs
Expect output changes in these common situations:
**Changing the timeline window (start/end dates)
- Moving the start date forward can reduce the portion treated as “in-window” under the default 1-year SOL logic.
- Moving the start date earlier can increase that in-window portion.
Changing category amounts
- Output proportions tied to your allocation attribution drivers will adjust.
- The tool will redistribute category totals according to the drivers you provide—so keep category totals consistent with your damages schedule.
Changing evidence timing
- If a category’s earliest relevant date falls outside the default 1-year comparison window (as used by your workflow), that category may be reduced in the tool’s time-supported portion.
- Keep earliest relevant dates evidence-based; “best guess” dates can materially distort the allocation.
Gentle disclaimer: DocketMath can help you structure and compute allocations, but it doesn’t replace legal judgment about which limitation period governs each component of damages in your specific case.
Statute reference you’ll be embedding in the workflow
- Default SOL period used in this West Virginia damages allocation workflow: 1 year
- Citation: W. Va. Code § 61-11-9