Worked example: Alimony Child Support in West Virginia
6 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Below is a jurisdiction-aware worked example for West Virginia showing how DocketMath can support an alimony + child support workflow using the calculator alimony-child-support.
Jurisdiction: West Virginia (US-WV)
Before the numbers, one quick legal-tech reality check: this example is illustrative, not legal advice. Family-law outcomes depend on case-specific facts and how a court applies statutory factors and evidence.
Scenario assumptions (example household)
Use these facts as the “inputs” you’d feed into a calculation tool:
- Obligor (payor): earns $5,000/month gross
- Obligee (recipient): earns $2,000/month gross
- Children: 2 children
- Shared parenting time: 45% / 55% (obligor/recipient)
- Health insurance for children: $250/month (include this as a child-related expense input where applicable)
- Work-related childcare: $300/month
- Other deductions/credits: none added in this simplified example
Time frame input (for arrears/collection planning)
This example also includes a time window input, since your brief references jurisdiction rules about time periods.
West Virginia’s general default limitations period (as provided) is:
- General SOL Period: 1 year
- General Statute: W. Va. Code § 61-11-9
Important clarity note: In your provided materials, no claim-type-specific sub-rule was found, so this worked example treats W. Va. Code § 61-11-9 as the general/default period.
Note: In a real case, limitation periods can turn on the type of obligation, the procedural posture, and when claims accrued. This example uses the general/default period you provided, not a claim-type-specific rule.
Example run
Now let’s run the example as if you’re using DocketMath’s alimony-child-support calculator.
Run the Alimony Child Support calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Enter the household and expense inputs
In DocketMath (alimony-child-support), you’d typically set values like:
- Monthly gross income:
- Obligor: $5,000
- Obligee: $2,000
- Number of children: 2
- Parenting time split: 45% / 55%
- Monthly health insurance for children: $250
- Monthly childcare: $300
- Arrears/limitations planning window: 1 year (general/default)
If you want to run it directly, start here: /tools/alimony-child-support.
Step 2: Interpret the tool’s outputs (what changes)
When you run the calculator, you should expect two distinct outputs:
- Child support component (driven largely by children’s needs + parenting time + income inputs)
- Alimony component (driven by the income imbalance and supporting factors modeled by the calculator)
Because parenting time and expense inputs change the allocation of child-related costs, the tool’s total monthly support is typically sensitive to those fields.
Step 3: Example output (illustrative)
Since this is a worked example, the following figures are illustrative to show how to read the result structure. Your actual tool output may differ based on how the calculator applies inputs.
| Output category | Monthly amount (example) | What it’s based on (high-level) |
|---|---|---|
| Child support | $1,050 | Income inputs + 2 children + parenting time + child-related expenses |
| Alimony | $450 | Income disparity (obligor higher than recipient) + simplified factor assumptions in the model |
| Total monthly support | $1,500 | Sum of the components |
Practical takeaway: use the tool to understand directional effects—which inputs move totals up or down—rather than treating any single number as a promise of a court outcome.
Step 4: Use W. Va. Code § 61-11-9 for a planning window (general/default)
For limitations planning in this illustration, you’re using:
- 1-year general/default period under W. Va. Code § 61-11-9
https://codes.findlaw.com/wv/chapter-61-crimes-and-their-punishment/wv-code-sect-61-11-9/
A concrete workflow approach in plain terms:
- If the question is “How far back could certain claims be pursued under the general/default period?” then a baseline planning window is:
- From 12 months prior to the relevant filing/trigger date (the precise start date can vary with accrual rules)
Because this example is not claim-type-specific (per your note), it’s best treated as a baseline planning window, not a guarantee.
Warning: A limitation period analysis usually depends on claim accrual and the nature of the obligation. Using W. Va. Code § 61-11-9 here is aligned with your “general/default period” approach, not a claim-specific rule.
Sensitivity check
Use this section like a checklist: change one input at a time and observe how DocketMath responds. That’s the fastest way to identify which variables most influence the monthly total.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Quick sensitivity matrix (illustrative directions)
| Change you make | Most likely impact | Why (practical terms) |
|---|---|---|
| Obligor gross income increases by $500/month | Higher alimony + higher child support | Higher ability to pay typically raises modeled amounts |
| Parenting time shifts from 45%/55% to 60%/40% | Child support may decrease | More custody time can shift the cost allocation |
| Childcare expense increases from $300 to $600 | Child support increases | Additional documented childcare often flows into child-related expenses |
| Health insurance for children increases by $150/month | Child support increases | Higher recurring dependent expenses usually raise the child-related component |
| Arrears “planning window” changes (e.g., 1 year → 2 years) | Affects lookback planning, not monthly amount | Monthly support comes from incomes/needs; the SOL window affects how far back you estimate claims |
Run these “single-variable” checks in DocketMath
To replicate effects cleanly, do a baseline run and then short follow-ups:
After each run, record:
- Total monthly support
- Child support component
- Alimony component
Then compare the differences.
Example interpretation (how to read deltas)
If the baseline total is $1,500/month, and a test run changes only one variable:
- If Run B changes total to $1,650, that’s +$150/month, likely driven primarily by income.
- If Run C changes total to $1,400, that’s -$100/month, likely mostly in child support.
- If Run D changes total to $1,720, that’s +$220/month, likely mostly in child support.
This “delta” method is usually more useful than focusing on one output number in isolation.
Limitations window sensitivity (using W. Va. Code § 61-11-9)
Because the general/default SOL period you provided is 1 year, you can also do a planning-level check:
This portion is about how far back questions can reach under the general/default period you’re using—not about how the monthly support formula changes.