Worked example: Alimony Child Support in Virginia

6 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

Below is a worked example of how DocketMath can calculate child support and alimony together in Virginia (US-VA) using jurisdiction-aware rules. This is a demonstration of the tool’s workflow and the kind of numbers you’d enter—not legal advice.

Scenario (one household)

We’ll model a parent–child–spouse support situation with the following facts:

  • Jurisdiction: Virginia (US-VA)
  • Filing context: Calculation worksheet for support obligations (not a court order)
  • Payor (Parent A) income (gross monthly): $7,000
  • Payee (Parent B) income (gross monthly): $3,000
  • Monthly health insurance for the child: $200 (assumed to be covered through the payor)
  • Child-related add-ons: None (for simplicity)
  • Number of children: 2
  • Payor’s support pay schedule: Monthly
  • Alimony request: Modeled as monthly maintenance (the tool computes an illustrative alimony component based on the inputs provided)

Inputs you would enter in DocketMath

Open the calculator at /tools/alimony-child-support and enter values like these:

InputValueWhy it matters for the calculation
Payor gross monthly income$7,000Drives the Virginia child support formula base
Payee gross monthly income$3,000Helps determine the “shared responsibility” split
Number of children2Sets the child support table level
Health insurance$200/monthMay adjust the child support portion depending on treatment rules
Alimony basis parameters(based on scenario)Drives the alimony component (amount/duration factors as implemented in the tool)

Note: DocketMath calculates using the assumptions you provide. If your real-world facts differ (additional income, childcare costs, or different insurance arrangements), the outputs can change materially.

Example run

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: Run the calculator

Go to /tools/alimony-child-support, enter the scenario inputs above, and run the calculation.

Step 2: Interpreting outputs

A typical combined-output run includes two parts:

  1. Child support (Virginia guideline calculation)
  2. Alimony (spousal support component)

Because both obligations can apply simultaneously, DocketMath reports them as separate components and also provides a combined monthly total.

Example results (illustrative)

With the example inputs:

  • Child support (monthly): $1,850
  • Alimony (monthly): $900
  • Combined monthly support: $2,750

These are not guaranteed outcomes for any real case. They are the computed results from the specific assumptions in this example and the tool’s jurisdiction-aware logic.

What DocketMath is doing behind the scenes (conceptually)

Even if you don’t need every internal detail, you can usually see that the output reacts to a few key drivers:

  • Income difference: The bigger the payor/payee income gap, the more it tends to increase guideline child support pressure.
  • Number of children: The guideline portion is table-driven, so moving from fewer to more children commonly changes the child support component substantially.
  • Insurance costs: When health insurance is attributed to the child portion (under the scenario’s assumptions), child support can shift.
  • Alimony parameters: The alimony output changes when you adjust the spousal-support inputs you enter (including the timing/duration-style assumptions supported by the calculator).

Sanity-check summary

Before relying on any computed number, do a quick consistency check:

  • Does the child support figure seem reasonable given the entered incomes and 2 children?
  • Does the alimony figure track the relative income imbalance and the duration/maintenance assumptions you chose?
  • Does the combined total feel consistent with what you expected from a “higher-income payor” setup?

Sensitivity check

Final results can move when your inputs change, so it’s useful to run a few “what-if” scenarios. The idea is to identify which facts matter most for your situation.

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.

Sensitivity tests we’ll run

Starting from the baseline inputs, change one factor at a time:

  1. Payor income down by $500
    • Payor gross monthly income: $7,000 → $6,500
  2. Payor income up by $500
    • Payor gross monthly income: $7,000 → $7,500
  3. Add health insurance
    • Health insurance: $200 → $300
  4. Change number of children
    • Children: 2 → 3
  5. Reduce payee income
    • Payee gross monthly income: $3,000 → $2,500

Example outputs from the “what-if” tests (illustrative)

TestChangeChild support (monthly)Alimony (monthly)Combined (monthly)
Baseline$1,850$900$2,750
1) Payor down$7,000 → $6,500$1,700$850$2,550
2) Payor up$7,000 → $7,500$2,020$950$2,970
3) Insurance up$200 → $300$1,920$900$2,820
4) 3 children2 → 3$2,400$900$3,300
5) Payee down$3,000 → $2,500$2,050$950$3,000

How to read these changes

  • Income shifts: Changing the payor’s or payee’s income can affect both components because the guideline child support model is income-driven and the alimony logic is also tied to the relative income assumptions you enter.
  • Insurance shifts: In this simplified test, insurance changes primarily move the child support number. Alimony didn’t shift here because we didn’t change any alimony-specific inputs.
  • More children: Moving from 2 to 3 children typically creates one of the larger swings because the guideline schedule is table-based.
  • Payee income changes: Lowering the payee income can increase the combined amount in the model shown because it affects the income relationship used across components.

Warning: If your situation involves self-employment income, overtime, bonuses, or imputed income, the tool’s output can change significantly. Income can be defined differently across fact patterns—enter values consistently with how you’re modeling the case.

Practical checklist before you finalize your run

Use this to reduce avoidable input mistakes:

Related reading