Spreadsheet checks before running Alimony Child Support in Virginia
5 min read
Published April 15, 2026 • By DocketMath Team
What the checker catches
DocketMath’s alimony-child-support tool is most useful when you run a quick “sanity pass” on the numbers before you rely on the spreadsheet results. In Virginia (US-VA), alimony and child support calculations can hinge on a few discrete inputs—so small spreadsheet errors can create outsized output swings.
Here’s what the checker is designed to catch before you run the calculation:
- Missing or blank required fields
- Example: annual income left blank for one party, or the child birthdate/dates not entered in the expected format.
- Inconsistent time periods
- Example: you enter monthly income for one parent and annual income for the other. Even if the values are correct “on paper,” the unit mismatch can distort the output.
- Wrong direction of amounts
- Example: entering “net income” where the sheet expects “gross” (or the reverse), or swapping the two parties’ roles.
- Zero/negative values that break logic
- Example: a $0 income entry for a party when the worksheet expects current income, or a negative “health insurance” credit.
- Child-related date mistakes
- Example: child dates entered in a format that’s interpreted incorrectly (day/month vs. month/day), which can affect which children count for support.
- Overlapping or duplicate entries
- Example: entering the same child twice, or including expenses that were already rolled into another field.
- Numerical outliers
- Example: entering $12,000 as a monthly amount when the intent was $12,000 annually (or vice versa). The checker can flag amounts that are far outside typical patterns so you can re-check units.
- Formatting errors that silently convert values
- Example: commas and currency symbols typed into numeric cells (e.g., “1,200.00”) that get stored as text—this can cause downstream calculations to behave unexpectedly.
Pitfall: A spreadsheet can “run” and still be wrong. The goal of a checker is to catch input inconsistencies that won’t necessarily trigger an obvious error—just incorrect outputs.
To make the checker practical and actionable, use this workflow mindset:
- Validate inputs (units, presence, and consistency).
- Run the calculator.
- Review the output components (income used, children counted, and major deductions/credits).
If your numbers pass those checks, you’ll have far more confidence that the tool is reflecting your situation rather than a formatting mismatch.
When to run it
Run DocketMath’s spreadsheet checks any time you change an input that could materially affect alimony or child support outcomes.
Use this decision checklist:
- Examples: new pay stubs, changed overtime, commission shifts, bonuses, or a job change.
- Examples: adding/removing a child, correcting a birthdate, or updating which children are included.
- Examples: health insurance amounts, childcare-related figures, or other worksheet-supported categories.
- Examples: converting from monthly to annual (or vice versa).
- Copy/paste is a common source of text-formatted numbers or swapped columns.
- Instead of guessing, re-check the inputs for units, blanks, duplicates, and date interpretation.
A simple rule of thumb: if you’re doing a “what if” scenario—like estimating support under $X/month income—run the checker again for that scenario. Spreadsheet logic is deterministic; your output is only as trustworthy as the inputs you just changed.
If you’re starting from scratch, consider this sequence:
- Enter all required fields.
- Run the checker.
- Fix every flagged issue.
- Only then run DocketMath alimony-child-support.
Gentle reminder: This is a tooling check to reduce spreadsheet errors. It isn’t legal advice, and it won’t replace a review by a qualified professional if your situation is complex.
Try the checker
Start with the tool here: Alimony & Child Support (Virginia) — DocketMath.
Once you open the calculator, you’ll typically see an input area (income, children, and relevant supporting expenses). The “spreadsheet checks” step is about verifying your inputs before you rely on the computed result.
Here are the specific input categories to double-check while you run the checker:
1) Income fields and units
- Confirm each income value uses the same frequency (monthly vs. annual).
- Watch for accidental text entries (e.g.,
$3,200typed with symbols). - Ensure you didn’t invert the two parties’ amounts.
2) Child count and date precision
- Verify each child is included once.
- Re-check birthdates using the calculator’s expected format.
- Confirm any “included/active” status (if the tool uses it) matches the scenario date you’re modeling.
3) Expense and credit categories
- Validate health insurance and any related expense inputs.
- Ensure amounts reflect the same time period as the tool expects (monthly figures should remain monthly).
4) Scenario alignment
- If you’re modeling a temporary vs. longer-term situation, make sure the tool inputs match the time horizon you’re representing.
- If your income changed recently, decide whether you’re modeling current income or prior income consistently across all fields.
When the checker finishes, use the output review pass:
- Check components: confirm the calculator used the income numbers you intended.
- Look for abrupt changes: if changing one input causes a disproportionate swing, that often signals a unit mismatch or duplicated entry.
- Re-run after fixes: don’t assume the first correction corrected the downstream logic—rerun the checker after each major edit.
If you want a clean starting point, begin with one scenario at a time: enter baseline facts, run checks, then adjust a single variable (like income) and re-check.
