Spreadsheet checks before running Alimony Child Support in West Virginia

5 min read

Published April 15, 2026 • By DocketMath Team

What the checker catches

Before you calculate alimony (spousal support) and child support using DocketMath for West Virginia (US-WV), it helps to run a spreadsheet-style “sanity check.” The alimony-child-support calculator is jurisdiction-aware, but the accuracy of any calculation still depends on the inputs you feed into your spreadsheet and how your sheet translates dates and time windows.

This West Virginia-focused checker mainly catches issues that lead to subtle timing and math errors:

  • Stale or missing dates
    • Examples: leaving an intake/trigger date blank, pasting an incorrect filing date in place of the worksheet’s “start” date, or mixing date formats (e.g., 2026/4/1 vs 01-04-26).
  • Support calculation windows that don’t make sense
    • If your worksheet implies support starts earlier than your earliest legally relevant date input, totals can drift while still looking “reasonable.”
  • Time periods that conflict with West Virginia’s general statute of limitations baseline
    • West Virginia has a general/default 1-year timing baseline under W. Va. Code § 61-11-9 (cited below).
    • Important: No claim-type-specific sub-rule was found for this content. So your spreadsheet should treat 1 year as the general baseline check, unless you’ve verified that a different, claim-specific rule applies to your exact scenario and you have the support for that assumption.
  • Inconsistent “months” math
    • Common worksheet issues include:
      • dividing annual amounts by 12 while your time range covers 11 months (or any mismatch)
      • rounding each month first, then summing, instead of summing first (then rounding)
  • Negative or reversed timelines
    • If end_date < start_date, your month-count function may return a negative value or zero—either can silently break downstream totals.

Note: The West Virginia 1-year period referenced here is the general/default statute of limitations baseline under W. Va. Code § 61-11-9. This content does not identify claim-type-specific variations for different kinds of support-related claims. Use 1 year as the baseline check unless you’ve verified a different timing rule for your specific situation.

Quick checklist (spreadsheet-level)

Use these checks before you run or trust results from the DocketMath calculator:

Statute timing baseline used by the checker

(Reminder: this is the general/default baseline. This checker does not assume a different claim-specific period.)

When to run it

Run the spreadsheet checks in two moments: before you calculate and after you update inputs. This is where you prevent “credible-looking” outputs from being wrong due to timing or date handling.

Run the checker before importing a spreadsheet into the Alimony Child Support workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Best time: right before you click “calculate”

Do the checks after you’ve entered:

  • support-related dates your worksheet uses (start/end or effective dates)
  • income/expense inputs you’ll map into DocketMath
  • any toggles or assumptions that affect the time window

Then run the checker to confirm:

  • your date ranges produce a valid, non-negative month count
  • your limitation/timing logic consistently uses 1 year as the baseline (per W. Va. Code § 61-11-9)
  • your worksheet’s implied timeline matches what you intend to model

Also run it after any of these updates

Re-run immediately if you change:

Why timing checks matter in West Virginia worksheets

Because the general statute of limitations baseline is 1 year under W. Va. Code § 61-11-9, worksheets can become inconsistent quickly. For example, a sheet might:

  • model a broad period but apply a narrower “collectable” window, or
  • apply different timing windows to alimony vs. child support while using the same assumption logic on the surface

Even if your spreadsheet is only modeling scenarios (not making real-world filing decisions), the goal is the same: keep the internal timeline and your limitation baseline aligned so the numbers you see reflect the inputs you meant to use.

Try the checker

Want a fast way to apply these US-WV (US-WV) spreadsheet checks alongside DocketMath? Use the alimony-child-support tool here:

Alimony / Child Support calculator (West Virginia)

A practical flow:

  1. Open DocketMath
    • Start with the alimony-child-support calculator for US-WV.
  2. Enter dates first
    • Fill in your start/end or effective dates using a consistent format.
  3. Validate timing logic in your spreadsheet
    • Confirm your date range produces sensible month counts.
    • Ensure any “1-year” baseline logic in your spreadsheet matches W. Va. Code § 61-11-9 (general/default period).
  4. Then enter income/other inputs
    • Once date integrity is confirmed, other inputs are less likely to hide timing mistakes.
  5. Compare outputs after each change
    • If adjusting a single date causes a large swing, treat it as a red flag—commonly a month-count or lookback/timing filter issue.

Example: how outputs change with timing integrity

Small timeline errors can create big differences. Common spreadsheet issues include:

Spreadsheet issueWhat the checker flagsTypical output impact
End date earlier than start dateNegative/reversed timelineTotal becomes 0 or distorted due to month-count failure
Off-by-one month countMonth-count mismatchAnnual-to-month conversion error → totals drift (often around several percentage points depending on range)

Pitfall: Month-difference formulas can behave differently at boundaries (e.g., first-of-month vs mid-month). If you don’t test boundary dates, your spreadsheet can be “mathematically consistent” while still being off for the date rules you intended to model.

If you want the fastest path: run the calculator once, validate your spreadsheet’s timing inputs with the checker logic, then refine assumptions only after the date window and month math look correct.

Related reading