How to run Alimony Child Support in DocketMath for West Virginia

Step-by-step

Below is a practical workflow for running Alimony + Child Support in DocketMath for West Virginia (US-WV). This guide focuses on tool setup and jurisdiction-aware rules, not legal strategy.

• Select West Virginia in the Alimony Child Support tool.
• Enter the trigger dates and any caps or rates.
• Run the calculation and save the output.

1) Start in the Alimony/Child Support calculator

1. Open DocketMath here: **/tools/alimony-child-support
2. Confirm the jurisdiction selection shows West Virginia (US-WV).
   If DocketMath prompts you to pick a jurisdiction, choose US-WV so the calculator applies the correct West Virginia defaults.

2) Enter each income figure (and keep pay periods consistent)

DocketMath typically needs inputs for:

• Your income
• Other party’s income
• Any additional recurring income the tool accepts

Consistency matters: if you enter weekly figures, make sure the tool is set to interpret them as weekly (or convert them to the calculator’s expected period). Changing only one party’s frequency can significantly shift outputs.

3) Add the child-related inputs (so the calculator can model obligations)

Enter the children-related items that the calculator requests, such as:

• Number of children
• Parenting-time / custody split (if included in the tool fields)
• Child-related expenses (if the tool includes toggles/categories)

If DocketMath offers options for parenting time, use the option that matches the records you’re working from (for example, the same basis you’d reference in filings).

4) Add alimony inputs (so the alimony portion is calculated using WV context)

Most alimony/maintenance calculators request inputs that help model the alimony portion. Common categories include:

• Request type or alimony indicator (if the form includes it)
• Duration-related factors (if the tool uses them)
• Any income/expense inputs required by the calculator’s formulas

Even if you’re unsure about entitlement, entering the best available facts can help you:

• produce a realistic estimate, and
• identify which inputs drive the result.

5) Run the calculation and review each output component

After you click Calculate, review:

• Child support estimate
• Alimony estimate (if enabled)
• Combined monthly total
• Any breakdown components shown (for example, base components and adjustments)

Then sanity-check the result:

• Does the monthly figure change when you update only one input?
• Does it move in the expected direction (for example, lower income → lower calculated amount)?

6) Use the timeline and “staleness” concept for West Virginia defaults

DocketMath may ask questions tied to enforcement timing, arrears, or recency. When those questions appear, use the West Virginia limitation period information provided in the jurisdiction data.

For West Virginia, the provided jurisdiction data indicates:

• General SOL Period: 1 years
• General 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/

Important clarity (per your jurisdiction data):
No claim-type-specific sub-rule was found. The 1-year period is the general/default period referenced by the jurisdiction data above, and this guide treats it as the baseline.

7) Save or export results if the tool provides it

If DocketMath includes features to:

• Save scenarios
• Export to PDF/CSV
• Share a link

…use them after you finalize inputs. This is especially helpful if you want to compare scenarios (for example, current income vs. projected income).

Common pitfalls

Many users get misleading results not because the calculator is wrong, but because inputs are inconsistent or incomplete. Watch for these West Virginia–relevant workflow issues when using DocketMath:

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Input and interpretation pitfalls

• Mixing pay periods (weekly vs. monthly vs. annual) without aligning with the calculator’s expected format.
• Forgetting to update dependent values after editing income (if the tool doesn’t auto-recalculate all assumptions).
• Using an incorrect parenting-time basis when the tool offers multiple options (for example, a 50/50 option vs. a “days per month” style entry).
• Entering estimates for income categories without noting variability, then comparing outputs that reflect different levels of uncertainty.

Timing/presumption pitfalls

• Overlooking the 1-year general/default period tied to the jurisdiction data for W. Va. Code § 61-11-9.
  Since your dataset does not identify claim-type-specific sub-rules, treat 1 year as the baseline and avoid assuming longer lookback time without the appropriate rule for the specific claim type.

Scenario comparison pitfalls

• Changing multiple inputs at once (income + parenting time + alimony indicator). You lose the ability to see which factor caused the change.
• Comparing “before and after” without keeping units identical, such as updating income but leaving frequency unchanged.

SOL-related pitfalls to keep distinct

Your West Virginia jurisdiction data points to W. Va. Code § 61-11-9 and a general/default 1-year SOL period. Don’t combine this with:

• enforcement timelines, or
• arrears rules, or
• other time limits
  unless DocketMath’s workflow explicitly ties them together using the same statute and mechanism.

Try it

Want to validate your setup quickly? Run a short “input sensitivity” test in DocketMath for US-WV:

1. Enter your best estimates for:

   • both parties’ incomes,
   • number of children,
   • parenting-time inputs (if applicable),
   • and alimony settings.
2. Click Calculate and record:

   • the child support estimate,
   • the alimony estimate,
   • the combined monthly total.
3. Change only one input:

   • Adjust one party’s income by a small amount (for example, one step in the tool).
4. Recalculate and confirm:

   • the combined total moves up or down,
   • and the direction matches your expectation.

If the result barely changes despite a meaningful input change, re-check:

• that the edited field is connected to the formula, and
• that the tool’s units match what you entered.

To keep your West Virginia assumptions clear during scenario runs, you can also keep a note of the baseline limitation reference used for jurisdiction-aware timing logic:

• General SOL Period: 1 year
• W. Va. Code § 61-11-9 (as provided in your jurisdiction data)
• No claim-type-specific sub-rule found in your dataset, so treat this as the general/default baseline

When you’re ready to generate a shareable estimate, revisit:

• **/tools/alimony-child-support

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado