Worked example: Damages Allocation in West Virginia

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

Below is a worked example of how DocketMath can allocate damages timing using West Virginia jurisdiction-aware rules. This example focuses on selecting a statute of limitations (SOL) window as part of a damages-allocation workflow.

Note (not legal advice): This is a practical modeling example. SOL rules and their application can depend on claim facts, accrual nuances, and procedural details.

What rule we’re using in West Virginia

West Virginia’s general SOL period for certain claims is 1 year, governed by:

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

Important clarity for this example: No claim-type-specific sub-rule was found for this worked example. That means we apply the general/default period of 1 year described above, rather than narrowing to a specialty SOL.

Example scenario (numbers you can change)

Assume a business files suit after discovering damage from a contractual dispute tied to a 2024 event. The timeline below feeds the damages-allocation calculator.

Use these inputs:

Accrual model (for allocation math)

To keep this concrete, assume a monthly accrual weight that decreases over time:

• Mar 2024: 15%
• Apr 2024: 15%
• May 2024: 12%
• Jun 2024: 10%
• Jul 2024: 9%
• Aug 2024: 9%
• Sep 2024: 8%
• Oct 2024: 7%
• Nov 2024: 7%
• Dec 2024: 4%
• Jan 2025: 3%

These percentages sum to 100% across the modeled period.

If you prefer a different accrual pattern (e.g., flat, back-loaded, or step-changes), DocketMath will shift the allocation totals into different months while keeping the same SOL window logic.

Where this fits in the tool

This example corresponds to the damages-allocation calculator you can access here:
/tools/damages-allocation

Example run

Here’s how the DocketMath → damages-allocation workflow can look with the inputs above.

Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Compute the SOL cutoff date (1-year window)

Using the general/default 1-year period under W. Va. Code § 61-11-9, compute the earliest date that would be within the limitations window relative to the filing date.

• Filing date: 2025-04-20
• SOL period: 1 year
• SOL cutoff (earliest covered date): 2024-04-20

In a monthly allocation, a common approach is to treat months as “covered” if their month range overlaps the covered period (not if every day in the month is guaranteed to be covered). This matters when the cutoff lands mid-month.

So, for a monthly model, we apply:

• Months fully before 2024-04-20: excluded
• Months starting on/after 2024-04-20 (or overlapping): included

Step 2: Allocate damages into eligible vs. excluded months

With monthly granularity, compare each month in the accrual model to the cutoff date 2024-04-20.

• Excluded: Mar 2024 (15%)
• Included: Apr 2024 through Jan 2025 (85%)

Now apply the same weights to the total claimed damages ($120,000).

Eligible (within SOL) amount

• 85% × $120,000 = $102,000

Excluded (outside SOL window under the general default) amount

• 15% × $120,000 = $18,000

Step 3: Monthly breakdown (what DocketMath would output)

Below is a month-by-month allocation for the eligible period only. (You can also track excluded amounts separately for reporting.)

Under the SOL logic applied here, the recoverable/time-covered allocation equals $102,000 (Apr 2024–Jan 2025), and the portion tied to Mar 2024 equals $18,000.

Pitfall to watch: Monthly bucketing can create boundary effects when the cutoff date lands mid-month (like 2024-04-20). If your evidence ties accrual to specific days, switching DocketMath to a daily allocation (when available) may change the included/excluded split.

Step 4: How the output is used (without legal advice)

DocketMath’s output is best treated as a modeling tool for damages segmentation. Common practical uses include:

• building a litigation-ready spreadsheet showing eligible vs. time-barred portions (as modeled)
• supporting settlement valuation ranges by translating timing into dollars
• structuring discovery efforts around when damages accrued

Sensitivity check

Small input changes can materially shift what falls inside the SOL window. Below are three quick “what-if” scenarios using the same W. Va. Code § 61-11-9 general 1-year period.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity 1: Filing date delayed by 30 days

Change filing date from 2025-04-20 to 2025-05-20.

• New cutoff: 2024-05-20
• Now exclude Mar 2024 (15%) + Apr 2024 (15%) = 30%
• Eligible portion becomes 70%
• Eligible damages = 70% × $120,000 = $84,000

Impact: Eligible allocation drops from $102,000 → $84,000 in this modeling approach.

Sensitivity 2: Event date moved earlier by 20 days

Change event date from 2024-03-10 to 2024-02-19, keeping filing date 2025-04-20.

If your accrual model shifts so that more of the total weight moves into the period before the cutoff (for example, earlier months like February/March), the eligible allocation will typically decrease.

Actionable tip: Re-run the calculator using the month (or day) weight schedule you expect from your evidence (invoices, deliverables, payment records, repair logs), so the timing model matches reality.

Sensitivity 3: Switch allocation granularity from monthly to daily

Monthly weights assume the pattern you provided (or an even distribution within each month bucket, depending on how you set the weights). If damages actually accelerate sharply right after 2024-04-20, a daily method can be more precise than monthly bucketing.

Expected effect: The eligible/excluded boundary around 2024-04-20 becomes more exact, and the totals may move.

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