Spreadsheet checks before running Damages Allocation in West Virginia

What the checker catches

Run this scenario in DocketMath using the Damages Allocation calculator.

Running a West Virginia damages allocation spreadsheet without validating basic assumptions can create avoidable downstream errors—especially when the model’s outputs depend on dates. DocketMath’s Damages Allocation calculator is designed to work from structured inputs, and the spreadsheet checker step helps you catch problems before you lock in allocation results.

Because this workflow is jurisdiction-aware for West Virginia (US-WV), the checker uses the general/default statute of limitations (SOL) period as the baseline: 1 year under W. Va. Code § 61-11-9. No claim-type-specific sub-rule was found in the provided materials, so the checker applies the default general rule rather than attempting to change the SOL period based on claim label.

Common spreadsheet issues the checker is designed to surface for US-WV include:

• Missing or inconsistent date fields

  • Example: one sheet uses “Service Date,” another uses “Filing Date,” and a formula references the wrong column.
  • Likely outcome: the spreadsheet may compute a misleading “timeliness” flag and allocate damages against the wrong eligibility window.

• Date format mismatches

  • Example: mixing MM/DD/YYYY with YYYY-MM-DD.
  • Likely outcome: dates may be treated as text, causing date arithmetic to return blanks, incorrect day counts, or inconsistent comparisons.

• Off-by-one logic caused by time-of-day

  • Example: your spreadsheet stores timestamps, but your logic assumes dates only.
  • Likely outcome: something that looks “within 1 year” can cross the boundary after subtraction or rounding rules are applied.

• SOL eligibility conflicts

  • Example: one part of the spreadsheet uses a 2-year horizon, while another uses a 1-year horizon.
  • Likely outcome: the model may produce allocations that are internally inconsistent and misaligned with the calculator’s jurisdiction-aware rules.

• **Allocation weights that don’t sum correctly (or don’t balance)

  • Even if dates are correct, damages allocation often depends on weighting.
  • The checker verifies things like:

    • totals are consistent (commonly 100%, or 1.00, depending on your sheet conventions)
    • no negative weights
    • no blank weights where values are expected
    • row/category alignment across tabs

Pitfall to avoid: A spreadsheet can “look right” while still being wrong if dates are stored as text or if date comparisons don’t behave as intended. The checker’s job is to catch these issues early, before the Damages Allocation output looks confidently numeric.

To make the jurisdiction logic explicit, the West Virginia SOL baseline used here is:

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

Gentle note: This content is focused on spreadsheet quality control and calculator consistency—not legal advice. If you’re dealing with exceptions or specialized legal theories, you’ll still want to evaluate those separately.

When to run it

For the best signal-to-effort ratio, run the spreadsheet checker:

1. right before you run Damages Allocation in DocketMath, and
2. again after you update inputs.

Use this quick timing checklist:

• Confirm all date fields exist, parse correctly, and map to the columns the calculator expects.

• Ensure the jurisdiction context is set to US-WV.

• Re-run if you changed any “trigger” date (for example: incident/event date, notice date, discovery date, filing date).

• Data movement is where date formats and blank cells often sneak in.

• If you add categories (damage buckets) or modify weight formulas, re-check totals and row alignment.

Here’s how common input changes affect outputs in a typical Damages Allocation workflow:

Gentle disclaimer: This workflow supports spreadsheet accuracy and consistency, not legal advice. The SOL “default general rule” approach described here is the checker’s baseline; it’s not a substitute for analyzing whether any special circumstances apply.

Try the checker

Start with DocketMath’s Damages Allocation flow:

• Primary CTA: /tools/damages-allocation

A practical test drive:

1. Open Damages Allocation in DocketMath.
2. Upload or enter your spreadsheet data for West Virginia (US-WV).
3. Execute the spreadsheet checker step.
4. Review any flagged items.
5. Fix the spreadsheet inputs (especially date parsing and weight totals), then run the checker again.
6. Only after the checker passes should you proceed to finalize Damages Allocation results.

What you should expect when the checker passes cleanly:

• A 1-year default general SOL baseline for West Virginia under W. Va. Code § 61-11-9
• consistent date arithmetic behavior
• coherent allocation weights that match the calculator’s assumptions

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