Inputs you need for Alimony Child Support in United States Federal
4 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
If you’re using DocketMath to estimate alimony and child support under United States Federal (US-FED) parameters, start by gathering the exact inputs the calculator expects. Even though many support rules are state-law driven in practice, this workflow is still useful for organizing data, running scenarios, and documenting assumptions.
Use this checklist to collect what you’ll need before you click DocketMath: /tools/alimony-child-support:
Note: DocketMath’s calculator requires inputs that drive the math. Missing or inconsistent income fields (especially for self-employment and benefits) typically cause the largest swings in results.
What you’re trying to optimize
Decide what you want from the run:
Where to find each input
To avoid “guessing,” pull each input from documents and records you can cite. Here’s a practical mapping:
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
Income inputs
- Pay stub(s): gross wages, regular pay, overtime patterns
- IRS tax documents (e.g., Forms 1040 and schedules): self-employment income averages and household tax context for the relevant year
- Employer year-to-date statements: a cleaner baseline than a single check when overtime/bonuses fluctuate
- Benefits award letters / benefit statements (e.g., unemployment, disability, Social Security benefits if applicable)
Checklist guidance:
Child information
- Birth certificates / vital records: for current ages
- Custody or parenting plan: to represent the custodial schedule used in the tool
- Insurance policy premium statements: monthly cost attributable to children
- Childcare receipts or provider invoices: recurring monthly amounts
Alimony-specific information
- Marriage duration records: dates of marriage and separation (or the tool’s expected time category)
- Any existing orders or settlement documents: if you’re testing compliance or forecasting modifications
Warning (not legal advice): “Net income” is not universal across all calculators. If DocketMath prompts both gross and net, use the form the tool requests and keep your definition consistent across runs (especially when comparing scenarios).
Run it
Once your inputs are ready, run the calculator in a disciplined way so you can interpret outputs and adjust only one variable at a time.
- Open DocketMath: ** /tools/alimony-child-support
- Enter inputs using the checklist above.
- Choose the scenario mode (if the tool supports it):
- Single estimate (one set of numbers)
- Scenario comparison (e.g., shared parenting vs. primary residence)
- Review outputs in three passes:
Pass 1: Sanity-check the model
Before trusting the final numbers, verify:
Pass 2: Identify the biggest drivers
Use quick changes to see what moves the results most:
- Increase/decrease payor income by 5% or 10% and observe the effect.
- Swap the custodial schedule input (if available) to see how shared parenting changes child support.
- Add/remove child-related insurance and watch the delta.
Pass 3: Document assumptions for repeatability
For each run, record:
Quick scenario table (example workflow)
Use this format to keep your runs organized:
| Scenario | Payor monthly income | Custody schedule | Child insurance | Childcare | Alimony mode |
|---|---|---|---|---|---|
| Baseline | $5,000 | Primary residence | $250 | $300 | Category-based |
| Higher income | $5,500 | Primary residence | $250 | $300 | Category-based |
| Shared parenting | $5,000 | Shared parenting | $250 | $300 | Category-based |
| No childcare | $5,000 | Shared parenting | $250 | $0 | Category-based |
When your outputs differ, don’t change everything at once—alter one input per run, then re-check your results.
Pitfall: If you annualize income in one run and enter “monthly” in another, results can look wildly inconsistent even when you meant the same earnings. Keep units consistent across every scenario.