How to run Alimony Child Support in DocketMath for Virginia
7 min read
Published April 15, 2026 • By DocketMath Team
Step-by-step
Run this scenario in DocketMath using the Alimony Child Support calculator.
This guide walks you through running Alimony + Child Support in DocketMath for Virginia (US-VA) using the alimony-child-support calculator. The workflow below is designed to be practical, jurisdiction-aware, and easy to repeat each time your numbers change.
Note: This article explains how to use DocketMath and interpret its outputs—not how to obtain legal advice. If you’re filing in court, verify details with the applicable Virginia procedures and any governing orders.
1) Open the correct DocketMath tool
- Go to the Alimony + Child Support calculator: /tools/alimony-child-support
- Confirm the jurisdiction is set to Virginia (US-VA). If DocketMath prompts for jurisdiction, select US-VA (Virginia).
2) Identify the “support periods” you want to model
Before entering numbers, decide whether you’re estimating:
- Monthly ongoing support (typical baseline), or
- Support that changes after an event (for example, a child reaching a certain age, or alimony transitioning).
In DocketMath, you’ll generally get the cleanest results if you run:
- One scenario for your “current” period, and
- One scenario for any later period with different assumptions (income, custody/placement, or child details).
3) Enter the parties’ income inputs (the biggest driver)
DocketMath will base support calculations primarily on each parent’s income inputs. Enter:
- Income for Parent A (gross monthly income or the relevant equivalent)
- Income for Parent B
- Any additional income items the calculator requests (if shown in the interface)
If the calculator offers choices such as discretionary vs. adjusted income, choose the option that matches how you’re sourcing your figures.
How outputs change:
- Higher income on one side typically increases that parent’s obligation for child support, and it can also affect alimony modeling (if enabled).
- If you lower either parent’s monthly income in your assumptions, expect a corresponding drop in obligations.
4) Input custody / child placement assumptions
Child support calculations depend on which parent has the child(ren) and how much time they spend with each parent.
Enter the custody/placement information DocketMath requests, such as:
- Number of children
- Parent time share (or the placement schedule, if the tool asks for it)
- Any shared custody inputs (the UI should indicate what to provide)
How outputs change:
- More time with the child(ren) for Parent A (relative to Parent B) can reduce the obligation Parent A owes, and vice versa.
- Adding children increases the total support amount, but the distribution between parents depends on the time/placement inputs.
5) Add child details that the calculator needs
Some calculators require child-specific details. Provide:
- Each child’s age (or age ranges, depending on what DocketMath asks for)
- Any “other children” or special sections if the UI includes them
How outputs change:
- Child support schedules often depend on child age brackets. Modeling a child aged 10 versus one aged 17 can change the output even with identical incomes.
6) Enter alimony inputs (Virginia-specific modeling within the tool)
For Virginia, alimony modeling commonly depends on factors such as:
- Whether alimony is being requested as an estimate of spousal support
- The duration or “type” of alimony assumptions (based on the calculator’s options)
- The incomes and circumstances used to compute the alimony component inside the tool
In DocketMath, populate the alimony section based on what it prompts you for—commonly including:
- Whether to include alimony in the run
- Alimony start timing assumptions (if asked)
- Any “term” or “duration” controls
How outputs change:
- Turning alimony on typically changes the alimony portion of the result.
- Because child support and alimony may appear together in the final summary, the total monthly support line can change even if one component remains similar.
- Different term assumptions can change the payment pattern (for example, a defined term vs. longer duration).
7) Choose the scenario style (single vs. multi-period)
If DocketMath supports multiple scenarios, use it to reflect realistic changes.
✅ Recommended workflow:
- Scenario 1: Current incomes + current custody/placement + current child ages
- Scenario 2: Future period with updated ages or updated income
How outputs change:
- Updating child ages can alter the child support portion.
- Updating income affects both child support and alimony estimates (where the tool includes alimony).
8) Run the calculator and review each output line item
After you click Calculate, review outputs in three layers:
- Child support amount
- Alimony amount (if enabled)
- Total monthly support and any breakdown DocketMath provides
Then confirm:
- Whether the obligation is shown as Parent A owes Parent B (or the reverse).
- Whether amounts are displayed as monthly totals (the UI usually clarifies this).
9) Sanity-check the result using “sensitivity” adjustments (fast checks)
Instead of rerunning dozens of times, adjust one input at a time:
- Change Parent A income by a fixed step (for example, +$500/month if the interface supports incremental changes)
- Keep custody/placement constant and re-run
- Observe changes in:
- child support
- alimony (if enabled)
- total obligation
This helps you confirm the tool is responding to inputs as expected, and that your results are consistent with how you understand the inputs.
Pitfall: A common error is mixing “annual” and “monthly” values. If you enter $120,000/year as $120,000/month, the output can become wildly unrealistic. Confirm unit labels on every income field.
Common pitfalls
Use this checklist to avoid avoidable errors when running Alimony + Child Support in DocketMath for Virginia (US-VA):
Quick “reasonableness” tests
When you get an output, try these basic checks:
- If you increase one parent’s income and the obligation doesn’t move at all, verify:
- you edited the correct parent field
- alimony is enabled (if you expected it to change)
- custody/child inputs didn’t inadvertently reset
- If you add a child and the total support decreases, double-check:
- placement/time-share fields
- child ages and which bracket the tool assigns them to
Warning: Avoid making decisions based purely on a calculator run. Even when the arithmetic is correct, real court outcomes can depend on factors outside the inputs you enter into a tool, and the tool may not capture every situation-specific detail.
Try it
Ready to run a scenario?
- Open /tools/alimony-child-support
- Confirm Virginia (US-VA) is selected
- Enter:
- Parent A income
- Parent B income
- Number of children + child ages
- Placement/custody/time share inputs
- Enable alimony (if you want the combined estimate)
- Click Calculate
- Review:
- Child support line
- Alimony line (if enabled)
- Total monthly support
- Re-run once with a single changed input (like income) to confirm the output responds correctly
If you want, create two scenarios—one for today and one for a later period—then compare the monthly totals DocketMath reports for each.
Related reading
Step-by-step
- Select Virginia in the Alimony Child Support tool.
- Enter the trigger dates and any caps or rates.
- Run the calculation and save the output.
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
Common pitfalls
- missing a required input
- using a stale rate or rule
- ignoring calendar or holiday adjustments
- skipping documentation of assumptions
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.
Try it
Open the Alimony Child Support calculator and follow the steps above: Run the calculator.
Capture the source for each input so another team member can verify the same result quickly.
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
