Damages Allocation reference snapshot for West Virginia
4 min read
Published April 15, 2026 • By DocketMath Team
Rule or statute summary
In West Virginia, the general/default statute of limitations (SOL) for criminal conduct is 1 year, based on W. Va. Code § 61-11-9 (using the felony/fraud-and-misdemeanor limitations framework reflected in the jurisdiction dataset for this snapshot).
For this damages allocation reference snapshot, DocketMath treats “1 year” as the baseline lookback window when allocating exposure across time—unless your workflow separately identifies a claim type with a different SOL. Your brief notes that no claim-type-specific sub-rule was found, so this snapshot uses only the general/default 1-year SOL.
Practical way to use it in a DocketMath allocation workflow
Use a timeline-based input structure:
- If you have event dates (e.g., dates of alleged conduct, invoices, communications, discrete acts), enter those dates into DocketMath.
- DocketMath then applies a 1-year cutoff: it should exclude events more than 1 year before the starting date you provide (for example, a filing-date anchor or another organizational “time anchor” your team uses for allocation).
- The allocation step then focuses on the events within the allowable 1-year lookback period and ties potential damages to those remaining events (depending on how your calculator configuration maps dollars to dates).
“What changes when I change inputs?”
SOL-driven allocation is timing-driven, so your results usually move when you alter these inputs:
- Starting date (time anchor): This controls the cutoff boundary. Moving it forward shrinks the window; moving it backward expands it.
- Event dates: These determine whether each event is inside or outside the 1-year lookback.
- Dollar mapping to events/time segments: If your model assigns dollar amounts to particular events, then excluding an event date typically excludes (or reduces) the associated dollars.
A common pattern: if your timeline includes many events over multiple months, totals often change gradually until you cross the cutoff boundary for a specific event date—then the included/excluded status for that event can change abruptly.
DocketMath’s West Virginia SOL approach (US-WV)
For this snapshot, the jurisdiction-aware rule is:
- Baseline SOL period: 1 year
- Source: W. Va. Code § 61-11-9 (general/default)
If later you confirm a theory/category that requires a different timing rule, you can rerun the calculator with an updated SOL assumption. But this snapshot is intentionally default-only: the one-year rule described above.
Note: This content is structured for timing-and-allocation workflows. It is not a full claim-by-claim legal determination, and it may not capture start-date nuances or doctrines that parties may argue in litigation.
Citations
- W. Va. Code § 61-11-9 — general statute of limitations; West Virginia default period of 1 year (as reflected in the jurisdiction dataset for this snapshot).
Source: https://codes.findlaw.com/wv/chapter-61-crimes-and-their-punishment/wv-code-sect-61-11-9/
Warning / scope note: SOL timing can depend on how a theory characterizes the alleged conduct and how “when the clock starts” is determined for particular facts. This snapshot uses the general/default 1-year SOL from the dataset and does not provide individualized legal analysis.
Use the calculator
To run this West Virginia damages timing reference in DocketMath, use: /tools/damages-allocation.
Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.
Suggested inputs (and how they affect results)
Before running:
- Jurisdiction: West Virginia (US-WV)
- SOL rule selected: general/default 1-year SOL from W. Va. Code § 61-11-9
- Starting date: the date you choose as the cutoff anchor for allocation (align this with your internal process, such as filing-date or another defined accrual anchor)
- Event dates: dates associated with alleged conduct (and often the date points used to associate dollars)
- Dollar amounts mapping (if applicable): how each event or time segment contributes to total damages
Output behavior to expect
When you adjust inputs, DocketMath allocations typically shift like this:
| Change you make | What DocketMath does | Typical allocation impact |
|---|---|---|
| Move starting date forward | Shortens the lookback window | Fewer included events; lower included totals (often) |
| Move starting date backward | Expands the lookback window | More included events; higher included totals (often) |
| Add older events | Events may fall outside the 1-year window | Those events may be excluded/unallocated depending on configuration |
| Shift event dates across the cutoff | Changes whether an event is inside/outside the window | Totals can move abruptly when an event crosses the boundary |
Quick sanity-check checklist
Use these checks before relying on internal outputs:
Gentle disclaimer: DocketMath structures a timing-and-allocation workflow using the jurisdiction-aware rule from your dataset. It is not a substitute for legal advice or a comprehensive litigation-specific SOL analysis.