Worked example: Alimony Child Support in United States Federal
7 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
This worked example shows how DocketMath (calculator: alimony-child-support) can apply jurisdiction-aware rules for United States Federal (US-FED) to a combined alimony + child support scenario. The goal is to demonstrate the workflow and how changes to inputs can move the numbers—not to provide legal advice.
Note: “Federal” alimony and child support outcomes are typically implemented through state-court processes. In this example, US-FED jurisdiction-aware logic is used as a modeling lens for constraints and cross-cutting requirements that can affect calculations and enforcement.
Scenario snapshot (US-FED)
We’ll use a single household with one child and standard recurring support payments.
| Input item | Assumed value | Why it matters to the calculator |
|---|---|---|
| Jurisdiction | United States Federal (US-FED) | Switches on federal-aware logic and formatting/constraints |
| Payor role | Parent A | Determines which side “pays” each component |
| Payee role | Parent B | Determines which side “receives” each component |
| Monthly gross income (Payor A) | $6,500 | Base income for both support categories |
| Monthly gross income (Payee B) | $3,000 | Used to compute relative capacity/shared responsibility effects |
| Child count | 1 | Drives the child support component |
| Child’s overnight/custody split | ~90 nights with Payee B / ~275 nights with Payor A | Impacts parenting-time weighting |
| Child health / special needs flag | No | If yes, many models adjust upward; “No” keeps this stable |
| Alimony type | Ongoing periodic | Chooses the alimony pathway in the tool |
| Length of marriage | 9 years | Scales alimony duration/amount multipliers |
| Alimony requested monthly | Not provided (calculator derives) | Demonstrates deriving an amount rather than echoing an input |
| Existing support orders included | None | Prevents double counting in the run |
| Taxes included toggle | Off (pre-tax) | Keeps output aligned to common “support payment” framing |
Checklist: what you would enter in DocketMath
- Choose jurisdiction: US-FED
- Enter Payor A monthly gross income: $6,500
- Enter Payee B monthly gross income: $3,000
- Enter child count: 1
- Enter parenting-time split (nights per year or the tool’s equivalent field)
- Select alimony type: ongoing periodic
- Enter marriage length: 9 years
- Confirm special needs: No
- Confirm existing orders: None
- Confirm taxes mode: **Off (pre-tax)
Expected outputs
DocketMath will return, typically:
- A child support amount (monthly)
- An alimony amount (monthly)
- Often a combined total support figure for budgeting
- A breakdown you can use to understand sensitivity (which lever moved the result)
Example run
Below is a representative “what a single run might look like” for the inputs above. Exact internal computation details depend on the tool’s jurisdiction-aware model; the workflow and relationships are what matter most.
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-by-step run (US-FED)
- Set jurisdiction-aware mode to US-FED in DocketMath.
- Load the financial inputs:
- Payor A gross income: $6,500/month
- Payee B gross income: $3,000/month
- Add child-related inputs:
- Child count: 1
- Parenting time: Payor A has ~275 nights/year
- Add alimony-related inputs:
- Type: ongoing periodic
- Marriage length: 9 years
- Special needs: No
- Run the combined calculator: alimony-child-support.
Results (illustrative output for this example)
- Child support (monthly): $1,050
- Alimony (monthly): $950
- Total monthly support: $2,000
How to read the outputs
- Child support is driven primarily by:
- relative income levels ($6,500 vs. $3,000),
- parenting-time weighting,
- and the number of children (1 here).
- Alimony is driven primarily by:
- the alimony type (ongoing periodic),
- marriage length (9 years),
- and the income differential as modeled for alimony capacity/need.
Budgeting lens (practical)
If you’re planning cash flow, use the combined total:
| Month-by-month estimate | Amount |
|---|---|
| Child support | $1,050 |
| Alimony | $950 |
| Total outflow (Payor A) | $2,000 |
If you only care about one component (for example, child support), DocketMath’s breakdown view can help you isolate it—useful when you later adjust income or parenting-time without rethinking everything.
Sensitivity check
Numbers rarely stay still. This section shows how the outputs tend to move when you change one input at a time, keeping the rest constant. Run these scenarios in DocketMath to see the tool’s specific deltas.
Warning: Even small parenting-time changes can affect support computations substantially because the model re-weights shared responsibility. Treat these sensitivity checks as scenario planning, not as a promise of final court outcomes.
Sensitivity scenario A: Payor income +$500/month
- Change: Payor A gross income from $6,500 → $7,000
- Keep: Payee income $3,000, child count 1, parenting time same, alimony periodic, 9 years marriage
Observed pattern in many federal-aware models:
- Child support typically increases
- Alimony capacity/need often increases too, but may not scale identically to child support
Example deltas:
- Child support: $1,050 → $1,150 (+ $100)
- Alimony: $950 → $1,020 (+ $70)
- Total: $2,000 → $2,170 (+ $170)
Sensitivity scenario B: Parenting time shifts toward Payor by +30 nights/year
- Change: Payor A nights from 275 → 305
- Keep: income levels same, child count 1, alimony periodic, 9 years marriage
Observed pattern:
- Child support often decreases when the payor has more time (because the model credits in-kind parenting time)
- Alimony may shift less dramatically because parenting-time weighting is more commonly central to child support than alimony, though some models still reflect household circumstances
Example deltas:
- Child support: $1,050 → $980 (− $70)
- Alimony: $950 → $930 (− $20)
- Total: $2,000 → $1,910 (− $90)
Sensitivity scenario C: Marriage length changes (9 years → 12 years)
- Change: marriage length from 9 → 12
- Keep: incomes same, child count 1, parenting time same, special needs No
Observed pattern:
- Alimony periodic may increase with longer duration (depending on the tool’s alimony scaling logic)
- Child support may be unchanged because marriage length typically doesn’t directly drive child support in most models
Example deltas:
- Child support: $1,050 → $1,050 (0)
- Alimony: $950 → $1,050 (+ $100)
- Total: $2,000 → $2,100 (+ $100)
Quick comparison table
| Scenario | What changed | Child support | Alimony | Total |
|---|---|---|---|---|
| Baseline | — | $1,050 | $950 | $2,000 |
| A | Payor income +$500 | $1,150 | $1,020 | $2,170 |
| B | Parenting time +30 nights | $980 | $930 | $1,910 |
| C | Marriage length 12 years | $1,050 | $1,050 | $2,100 |
Practical next steps in DocketMath
To make the tool useful for real-world planning, iterate quickly:
If your goal is to model total monthly affordability, focus on the Total line in each scenario and identify which input dominates the outcome in your facts.
Where to start
Begin directly at the calculator: Use DocketMath’s alimony/child support tool