Worked example: Alimony Child Support in Vermont

Example inputs

Run this scenario in DocketMath using the Alimony Child Support calculator.

Below is a worked example for Vermont using DocketMath’s alimony-child-support calculator (jurisdiction code US-VT). This is a practical illustration of how the tool wires together inputs and outputs—not legal advice.

If you want to follow along, open the calculator here: /tools/alimony-child-support.

Scenario snapshot (Vermont, US-VT)

Assume a divorcing couple with the following facts:

• Filing status: Divorce proceedings requiring support calculations
• Children: 2 children
• Residential placement: “Shared” custody arrangement
• Payor: Parent A
• Recipient: Parent B

Financial inputs used in this run

Use these inputs in DocketMath’s Alimony Child Support tool:

• Payor gross monthly income: $6,500
• Recipient gross monthly income: $3,000
• Payor time with children: 40%
• Child support arrears / offsets: $0
• Health insurance costs (monthly, payor-paid portion): $150
• Childcare costs (monthly): $250
• Alimony duration: 6 years
• Requested alimony type logic (tool default): Uses the tool’s jurisdiction-aware model for Vermont based on the inputs above
• Alimony start date: Today’s month (for demonstration)

“Time” input that matters for enforcement timing

For this example, we include a statute-of-limitations reference point used as a general time horizon in the workflow:

• General SOL period used by the tool/workflow: 1 year
• Source provided for this workflow: calendar materials referencing Vermont’s general limitations period

  • https://legislature.vermont.gov/Documents/2020/Docs/CALENDAR/hc200226.pdf

Important: No claim-type-specific sub-rule was found in the provided jurisdiction data. So this 1-year period is treated as the general/default period only, not a substitute for every possible Vermont limitations or enforcement rule that might apply to different remedies or case postures.

Example run

Now run the scenario through DocketMath (alimony-child-support, US-VT).

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: Income and allocation impact (what changes the result first)

With Payor income of $6,500/mo and Recipient income of $3,000/mo, the calculator determines the income gap and then adjusts for:

• **Number of children (2)
• **Time split (40%)
• **Health insurance ($150/mo)
• **Childcare ($250/mo)

Those add-ons tend to increase the child-support component because they are direct costs tied to supporting the children.

Step 2: Child support calculation component (illustrative outputs)

Under the shared arrangement assumption (40% time with children), the calculator produces a monthly child support figure. For this example, assume DocketMath outputs:

• Monthly child support (estimated): $1,425

Step 3: Alimony calculation component (illustrative outputs)

Next, the calculator uses the income difference plus the support context to generate an alimony figure. With a requested duration of 6 years, assume DocketMath outputs:

• Monthly alimony (estimated): $625

Step 4: Total monthly support payment estimate

Finally, DocketMath sums the components into a combined monthly figure:

Step 5: Enforcement/limitations workflow note (general SOL)

Because the jurisdiction data provided includes a general SOL period of 1 year, this example workflow marks 1 year as the default horizon for limitations-related checks:

• General SOL horizon used: 12 months

Sensitivity check

A worked example is most useful when you see how small input changes can move the number. Below are three sensitivity checks you can run in DocketMath to understand the direction and magnitude of change.

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 check A: Change time with children from 40% to 55%

• Change: Payor time with children: 40% → 55%
• Likely effect:

  • Child support typically trends down as the payor has more parenting time.
  • Alimony may also adjust indirectly because total support pressure changes, but it depends on the tool’s combined model logic.

Expected outcome (directional):

• Child support: decreases
• Alimony: may decrease modestly

Practical way to test:

• Keep all other inputs fixed
• Re-run the tool
• Compare the new child support and total payment

Sensitivity check B: Increase childcare from $250 to $450

• Change: Childcare costs: $250/mo → $450/mo
• Likely effect:

  • The child-support component generally moves up because childcare is directly tied to child-related costs.

Expected outcome (directional):

• Child support: increases
• Alimony: may remain similar or change slightly, depending on how the model weighs child-related expenses

Quick checklist to run:

• Confirm you updated the childcare field in DocketMath
• Keep health insurance the same
• Record the delta for child support first, then total

Sensitivity check C: Increase payor income from $6,500 to $7,200**

• Change: Payor gross monthly income: $6,500 → $7,200
• Likely effect:

  • The income gap widens, which typically increases child support and can affect alimony.

Expected outcome (directional):

• Child support: increases
• Alimony: increases

Summary of sensitivity results to capture

When you run these checks, capture the following from each run:

• Monthly child support
• Monthly alimony
• Monthly total
• Any changes to assumptions you didn’t intend to modify (time split, insurance, childcare, or duration)

Worksheet-style table:

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado