How to calculate Alimony Child Support in West Virginia

Quick takeaways

• West Virginia calculates child support and spousal support under different statutes, so DocketMath runs them as separate calculations: child support under W. Va. Code § 48-13-101 et seq. and spousal support (“alimony”) under W. Va. Code § 48-6-301.
• The DocketMath: alimony-child-support tool is jurisdiction-aware (US-WV), so it applies West Virginia’s structure rather than treating everything as one generic formula.
• For child support, West Virginia uses a guidelines framework tied to an income shares model and standardized expense concepts, designed to reduce deviation. (See W. Va. Code § 48-13-101.)
• For spousal support, the calculation is typically factor-driven under W. Va. Code § 48-6-301, so the “inputs that matter” (like need/ability and length of marriage) often change outcomes more than simple income comparisons.
• Default rule set clarity: the DocketMath workflow uses the general/default period because no claim-type-specific sub-rule was found in the provided jurisdiction data.

Inputs you need

Before you run the DocketMath: alimony-child-support calculator for West Virginia (US-WV), gather the following inputs. This reduces back-and-forth and helps keep scenarios consistent.

A. Income (for each parent/spouse)

Collect:

• Gross monthly income for:

  • Parent A
  • Parent B
• Additional income sources (if you track them), such as:

  • overtime averages (monthly),
  • bonuses/commissions (monthly average),
  • self-employment net (monthly),
  • other recurring income
• The time window you’re using to compute averages (for example, “last 4–8 weeks”)

Why DocketMath cares: West Virginia’s child support guidelines rely on income-based assumptions and an income shares model, anchored in W. Va. Code § 48-13-101 et seq.

B. Parenting time / child placement facts

Collect child-support-relevant placement information, including:

• Number of children in the order
• Your best measurable proxy for time-share / overnights (or the schedule pattern)
• How custodial arrangement is being treated in your scenario (e.g., primary physical custody and time split)

C. Spousal support facts (for alimony)

For spousal support under W. Va. Code § 48-6-301, collect:

• Monthly income for each spouse
• A need/expense proxy (your best structured estimate of monthly needs or support-related expenses)
• Length of marriage
• Any relevant facts that reflect earning capacity or ability to pay (for example, disability status or employment limitations, if applicable in your inputs)

D. Confirm the jurisdiction selection

Make sure the tool is set to:

• Jurisdiction code: US-WV
• Tool: alimony-child-support

DocketMath uses the selected jurisdiction to apply:

• Child support: W. Va. Code § 48-13-101 et seq.
• Spousal support: W. Va. Code § 48-6-301

How the calculation works

DocketMath separates the problem into two tracks—child support and spousal support—because West Virginia addresses them under different statutory frameworks.

1) Child support track (W. Va. Code § 48-13-101 et seq.)

West Virginia’s child support chapter includes a legislative finding that the current child support guidelines should be reviewed and revised to:

• reduce the number of cases requiring deviation,
• take into account custodial parents’ contributions to children,
• apply an income shares model, and
• use standardized expense tables.

That structure is reflected in W. Va. Code § 48-13-101.

What DocketMath does with your inputs (conceptually):

• Uses your income inputs for both parties
• Uses number of children and your entered placement/time-share information
• Applies the guidelines logic designed around income-based assumptions (rather than ad hoc estimates)

Output you should expect: a child support amount computed using the guidelines framework tied to W. Va. Code § 48-13-101 et seq.

2) Spousal support track (W. Va. Code § 48-6-301)

Spousal support is governed by W. Va. Code § 48-6-301. Unlike a strict “single table number” that many people expect from guidelines, spousal support typically involves statutory considerations and case-specific factors.

How to use DocketMath effectively here:

• Enter both spouses’ incomes so the tool can model relative financial positions.
• Provide spousal-support inputs that reflect need and ability to pay (for example, your length of marriage and the need/expense proxy you’re using).
• When you want to understand what drives the number, adjust one category at a time:

  • update length of marriage while holding income constant,
  • then update the expense/need proxy while holding other inputs steady,
  • then compare.

Default period / rule-set note

The jurisdiction data provided did not identify a claim-type-specific sub-rule. Because of that, DocketMath runs the general/default period logic for West Virginia for this workflow.

3) How to read the combined result

After you run the tool, you should interpret the results as two separate line items with different legal sources:

• Child support: W. Va. Code § 48-13-101 et seq. (guideline-driven framework)
• Spousal support (“alimony”): W. Va. Code § 48-6-301 (factor-driven framework)

Practical takeaway: Don’t treat the combined result as one “all-in” number with one meaning. The tool’s separation reflects how West Virginia law structures these obligations.

Common pitfalls

Use this checklist to catch issues before relying on the output.

Input and interpretation issues

• Wrong jurisdiction code: confirm US-WV is selected.
• Inconsistent income windows: don’t mix “monthly net” and “weekly gross” without converting to the same basis.
• Forgetting additional income: overtime, commissions, bonuses, and self-employment can significantly affect guideline calculations.
• Parenting time entered inaccurately: even small time-share differences can change the child support outcome.
• Assuming spousal support math matches child support math: West Virginia treats them under different statutes, so the same arithmetic assumptions often won’t apply.

Documentation and scenario management

• No scenario comparison: run at least 2 versions (for example, updated income vs. original) to see how sensitive results are.
• Stale employment information: if income changed since the pay period you’re averaging, update your inputs.
• Changing multiple variables at once: adjust one variable at a time so you can explain why a result changed.

Sources and references

• West Virginia Code (child support): W. Va. Code § 48-13-101 et seq.
  https://code.wvlegislature.gov/48-13-101/
• West Virginia Code (spousal support): W. Va. Code § 48-6-301
• Legislative finding emphasized in W. Va. Code § 48-13-101: guidelines reviewed/revised to reduce deviation, considering custodial contributions, applying an income shares model, and using standardized expense tables.

Next steps

1. Open the DocketMath tool: https://docketmath.com/tools/alimony-child-support (or use the link above).
2. Enter inputs in the following order:

   • income for both parties,
   • number of children and placement/time-share info,
   • spousal-support inputs (length of marriage and need/ability proxies).
3. Run the calculation and capture:

   • the child support result,
   • the spousal support result.
4. Do a quick sensitivity pass:

   • update income first,
   • then update parenting time,
   • then update spousal-support-relevant facts.
5. If you’re using the numbers for negotiation or review, document your assumptions so every scenario version is consistent.

Related reading

• How Alimony Child Support rules vary in New York — What varies by jurisdiction
• How to calculate Alimony Child Support in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Alimony Child Support in Philippines — Worked example with real statute citations