Why Alimony Child Support results differ in Virginia
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Alimony Child Support calculator.
If you run DocketMath’s alimony-child-support calculator for Virginia (US-VA) and see different results than expected, it’s usually not the arithmetic—it’s the inputs and jurisdiction-aware rules. Below are the top 5 causes that reliably change outcomes in Virginia.
The “support type” you’re calculating
- Virginia treats alimony and child support differently, including how each is computed and modified.
- If you accidentally choose a scenario that’s child support only, alimony only, or both, the totals can change materially—even when incomes are the same.
- Use the matching mode for what you’re trying to model from the start.
Parenting time / custody assumptions
- Child support in Virginia is sensitive to time share (how parenting time is allocated) and which parent is treated as the primary physical custodian (captured by the tool’s inputs).
- That means you can keep income the same and still see a different monthly support number if you adjust time share.
Income classification and how “effective income” is modeled
- DocketMath requires income inputs that align with how Virginia support calculations treat different compensation types.
- Small differences in how income is entered can shift results, for example:
- W-2 wages vs. self-employment patterns
- Handling of overtime/bonus
- Whether items like retirement contributions (or other components) are included in the chosen income entry method
Health insurance and childcare inputs
- Virginia child support calculations commonly incorporate work-related childcare and may include medical/health insurance costs, depending on how you input them.
- Even “small” monthly premiums or childcare totals can noticeably affect the output.
Alimony duration and eligibility-related inputs
- Alimony in Virginia depends on multiple scenario inputs, including items like marriage duration fields that the calculator uses to determine the structure of alimony.
- When those eligibility/duration inputs change, amount and duration can change even if both parties’ incomes stay constant.
Common pitfall: Updating only one value (like income) while leaving parenting-time or expense assumptions from a different scenario. The tool is often “correct”—your inputs just don’t describe the same underlying facts.
How to isolate the variable
Use a diagnostic, one-change-at-a-time approach. The goal is to find which input category is driving the difference in DocketMath (US-VA).
- Freeze the jurisdiction and tool settings so both runs use the same rule set.
- Compare one input at a time (dates, rates, amounts) and re-run after each change.
- Review the breakdown to see which segment or assumption drives the difference.
Step 1: Freeze everything except one category
Create three runs:
- Run A (baseline): Use your best-available facts for custody/time share, expenses, and incomes.
- Run B (single change): Modify only one category (for example, parenting time).
- Run C (verification): Return everything back to baseline, then change only the next category.
Step 2: Track what moves
Compare the outputs across the runs. A practical checklist:
Step 3: Match the output change to the likely input
Look at which component shifts:
- If child support changes but alimony stays the same → suspect parenting time or child-related expenses/income.
- If alimony changes but child support stays the same → suspect alimony-specific scenario inputs or income modeling.
- If both change → suspect shared drivers such as income classification or expense inputs that affect multiple parts.
Step 4: Confirm you didn’t switch calculator mode
Make sure the run aligns with what you intended:
Even when you think you “entered the same numbers,” a different mode can change the computation path.
Next steps
Use these steps to tighten your inputs and reduce “mysterious” differences:
**Re-enter inputs in a consistent order (baseline facts first)
- Start with custody/time share (it shapes child support).
- Then enter each parent’s monthly income.
- Finally add childcare and health insurance costs.
Run a 3-pass sensitivity test
- Pass 1: parenting time
- Pass 2: income (one parent at a time)
- Pass 3: childcare + health insurance
Compare run-by-run deltas Write down:
- Baseline total
- Total after each single change
The biggest delta usually points to the input category most inconsistent with your expected scenario.
**Document your assumptions (briefly) For example:
- “Time share entered as X/X”
- “Childcare entered as $Y/month”
- “Health insurance premium entered as $Z/month”
That documentation makes it much faster to correct mismatched assumptions.
Gentle reminder: DocketMath is a modeling tool—it can help you understand how inputs affect outcomes, but it can’t replace legal review of the specific facts in your case.
If you want to start with the tool directly, use: /tools/alimony-child-support.