How to run Alimony Child Support in DocketMath for West Virginia

Step-by-step

This guide shows how to run Alimony (spousal support) and Child Support in DocketMath for West Virginia (US-WV) using jurisdiction-aware rules. It’s designed to be practical: you’ll enter inputs, run the calculator, and interpret how the output changes when you adjust key facts.

Before you start, anchor your workflow to West Virginia’s two statutory frameworks:

• Child support is governed by W. Va. Code § 48-13-101 et seq.
• Spousal support (alimony) is governed by W. Va. Code § 48-6-301
• The child-support chapter includes legislative findings explaining why guidelines and supporting tables are standardized—referencing concepts like guideline review and standardized expense tables (W. Va. Code § 48-13-101).

Friendly reminder: This is a tool-walkthrough, not legal advice. If your matter has special facts, confirm the inputs match what your court/attorney paperwork expects.

1) Open the correct tool

1. Go to DocketMath’s calculator page:
   Primary CTA: /tools/alimony-child-support
2. Select the jurisdiction option for West Virginia (US-WV) if the UI prompts you.

2) Enter child-support inputs (W. Va. Code § 48-13-101 et seq.)

Next, enter the child-support inputs that drive the computation under West Virginia’s child-support framework. Collect these facts first so you can run consistent “what-if” scenarios.

Common inputs you may see include:

• Number of children
• Ages of children (if the UI asks)
• Income details for:

  • the parent paying support
  • the parent receiving/crediting support
• Health insurance / childcare inputs (if your workflow includes them)
• Any available fields related to time allocation/custodial arrangement (only use what the tool provides—don’t guess)

3) Enter spousal-support (alimony) inputs (W. Va. Code § 48-6-301)

After child-support inputs, add the facts that affect spousal support.

DocketMath’s spousal-support workflow commonly focuses on fields such as:

• Both parties’ incomes (or income components, depending on how the UI is structured)
• Relevant dates (if the tool asks—e.g., separation/filing/other date fields)
• Duration-related inputs (where your form captures them)
• Special circumstance inputs (only enter what the UI supports)

Use the calculator inputs that correspond to the facts your case uses—avoid mixing rough estimates and finalized numbers in the same run unless you’re intentionally modeling a scenario.

4) Understand the default period / rule applicability

Some calculators include a “period,” “phase,” or “duration” setting. Here’s the key point for West Virginia in this workflow:

• No claim-type-specific sub-rule was found for this West Virginia configuration in the workflow.
• Treat the displayed “default period” (or the tool’s primary period setting) as the governing framework unless the UI explicitly provides a different selection.

In other words: rely on what DocketMath shows for the default/primary rule period, and don’t assume a special sub-rule applies based only on intuition. If the UI does not offer a claim-type selector, the safest approach is to run with the default and document that assumption.

5) Run the calculation and review the output breakdown

Once inputs are complete:

1. Click Calculate (or the tool’s equivalent).
2. Review the output sections in a typical order:

   • Child support result (from the § 48-13-101 et seq. framework)
   • Alimony/spousal support result (from § 48-6-301)
   • Combined monthly obligation (if shown)
   • Assumptions and scenario flags (if DocketMath displays them)

When reviewing results, use the tool’s line items (if provided)—especially entries tied to:

• children count/ages
• insurance/childcare
• income numbers and any deductions/credits the UI applies

A single data-entry mistake (wrong children count, wrong income field, missing insurance value) is often enough to explain unexpected output.

6) Adjust inputs to model realistic changes (what-if testing)

DocketMath is most useful when you test how outputs respond to controlled changes. Try a structured approach where only a few variables change per run.

Example what-if structure:

• Income test: increase/decrease the payor income by a known delta (e.g., +$1,500/month)
• Expense test: adjust health insurance/childcare by a known delta (e.g., +$200/month)
• Keep everything else the same so you can interpret differences.

Scenario checklist (run-to-run consistency)

• Same number of children
• Same ages (unless intentionally testing age impact)
• Same baseline incomes for both parties
• Same insurance/care inputs unless intentionally testing those
• Same default period setting (don’t switch without a reason)

Common pitfalls

West Virginia-specific workflows tend to fail for the same reasons each time. Watch for these:

1. Using the wrong mental model for child vs. spousal support

   • Child support: W. Va. Code § 48-13-101 et seq.
   • Spousal support: W. Va. Code § 48-6-301 If you treat alimony like child support (or vice versa), you may misinterpret why the tool output behaves the way it does.

2. Assuming a special duration/period rule without tool support

   • As noted above: no claim-type-specific sub-rule was found for this workflow.
   • Use the tool’s default period unless the UI explicitly offers an alternate selection.

3. Mixing estimates with final income If you enter estimated overtime/bonus/second-job income, you can cause large swings in both child and spousal outputs. If DocketMath offers “current” vs. “average” income-style fields, align your entries with the numbers you can support.

4. Leaving standardized expense components blank W. Va. Code § 48-13-101 references standardized guideline methodology and expense table concepts. If the tool has fields for insurance/childcare and you leave them empty (even if you have those costs), your results may understate expense-linked components.

5. Not documenting assumptions when you reuse results Before you compare runs, capture:

   • incomes used
   • insurance/childcare values entered
   • number/ages of children
   • the period/default framework setting shown by the tool UI

Common trap: copying a prior run and changing only one input (like payor income) without confirming children/ages/insurance/period fields remained the same.

Try it

Follow this quick practice workflow using DocketMath for West Virginia (US-WV):

1. Open: /tools/alimony-child-support

   • /tools/alimony-child-support
2. Confirm jurisdiction US-WV is selected.
3. Enter:

   • child data: number/ages of children
   • both parties’ income information
   • insurance/childcare fields (if the UI includes them)
4. Enter spousal-support-related facts using the tool fields tied to W. Va. Code § 48-6-301.
5. Click Calculate and review:

   • child support output (from the § 48-13-101 et seq. framework)
   • alimony output (from § 48-6-301)
   • combined totals (if shown)
6. Run two controlled variations:

   • Variation A: change payor income by a known amount (e.g., ±$1,000/month)
   • Variation B: change childcare/insurance by a known amount (e.g., ±$200/month)

To keep results interpretable, use a simple tracking table:

If the expected effect doesn’t happen, pause and verify inputs first (children count/ages, both incomes, insurance/care entries, and the default period selection). The fastest fixes are usually data-entry corrections rather than assuming different statute treatment by the tool.

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