Worked example: Alimony Child Support in Wisconsin

Example inputs

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

This worked example shows how you can run alimony + child support calculations in Wisconsin (US-WI) using DocketMath with jurisdiction-aware rules. The goal is to make the workflow concrete: pick inputs, run the tool, then sanity-check the results.

Scenario setup (example facts)

To illustrate the calculation flow, assume:

• Spouse A (recipient): requesting support
• Spouse B (payor): paying support
• Combined gross monthly income: $10,000
• Income split used in the example:

  • Spouse A gross monthly income: $4,000
  • Spouse B gross monthly income: $6,000
• Number of children: 2
• Child-related monthly expenses included by the tool (example values):

  • Child care: $400/month
  • Health insurance premiums: $150/month (allocated for children)
• Parenting time inputs (example):

  • Spouse B overnights per month: 10
• Alimony assumptions (example):

  • Requested duration: 36 months (3 years)
  • Alimony monthly amount input basis: in this example, DocketMath calculates the relevant monthly alimony figure from the variables you enter (including the duration you choose)

DocketMath inputs you would enter

Open the calculator here: /tools/alimony-child-support

In DocketMath, use these categories in the /tools/alimony-child-support tool:

• Jurisdiction

  • **Wisconsin (US-WI)
• Income

  • Spouse A gross monthly income
  • Spouse B gross monthly income
• Children

  • Number of children
  • Child care expense (monthly)
  • Health insurance expense (monthly, if applicable)
• Parenting time

  • Overnights per month (or the parenting-time input format the tool asks for)
• Alimony

  • Duration months (example: 36)
• Other / toggles

  • Any toggles the tool requires (for example, whether health insurance is provided or whether child care applies)

Quick checklist (before running)

Use this checklist to avoid common “garbage in, garbage out” issues:

Example run

Below is an example run using the scenario inputs above.

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: Select the jurisdiction-aware rules

In DocketMath, choose:

• **Jurisdiction: Wisconsin (US-WI)

Even when the calculation is formula-driven, jurisdiction settings help ensure the tool applies the correct Wisconsin-specific framework where applicable.

Step 2: Enter values and run

Enter the following values:

• Spouse A gross monthly income: $4,000
• Spouse B gross monthly income: $6,000
• Children: 2
• Child care: $400
• Health insurance premiums (children): $150
• Overnights per month for Spouse B: 10
• Alimony duration: 36 months

Then click calculate in DocketMath (within /tools/alimony-child-support).

Step 3: Interpret outputs

DocketMath typically returns items in two buckets:

1. Child support (monthly)
2. Alimony (monthly, sometimes with a duration-based framing)

For this worked example, the tool will produce outputs like:

• Child support (monthly): $X
• Alimony (monthly): $Y
• Total support (monthly): $X + $Y
• (Optionally) Estimated total over duration, if the tool multiplies by the selected alimony duration

Because DocketMath performs the computation, treat $X and $Y as the tool-computed results for your exact inputs.

How to read the result logically:

• If you change parenting time or child-related expenses, the child support line item is usually the first one to move.
• If you change alimony-related variables (especially duration and any alimony assumptions the tool uses), the alimony line item is the one most likely to shift next.
• Total monthly support is the sum of child support and alimony, so even “small” input changes can noticeably affect the combined total.

Worked-example takeaway

After your first run, you should have:

• A monthly child support number
• A monthly alimony number (and possibly any duration-based totals shown by the tool)
• A combined monthly total

Next, use the sensitivity check to see which inputs are the biggest “levers” in your scenario.

Sensitivity check

A sensitivity check answers: “If I change one input slightly, which output moves the most?” This is especially useful because in Wisconsin scenarios, outcomes can be driven by different factors depending on your inputs—income, child-related expenses, parenting time, and alimony duration/assumptions.

Sensitivity test A: Parenting time (overnights)

Change only one input:

• Overnights per month for Spouse B: 10 → 12 (add 2 overnights)

Expected directional effect (typical modeling intuition):

• Child support: likely decreases (more parenting time often reduces the paying parent’s share of certain day-to-day support needs), though the exact magnitude depends on how the tool applies parenting-time logic.
• Alimony: may be unchanged in many workflows unless the tool ties alimony to parenting-time inputs. If the tool uses only the alimony duration and income-based assumptions, you may see alimony stay the same.

What to record after re-running:

• New **child support (monthly)
• New **total support (monthly)

Checklist:

Sensitivity test B: Child care expense

Change only one input:

• Child care: $400 → $550

Expected directional effect:

• Child support: likely increases, because child care is a direct child-related cost input.
• Alimony: often not directly tied to child care in many simplified workflows; even if it changes indirectly in some setups, child support is usually the most responsive line item.

Checklist:

Sensitivity test C: Alimony duration assumption

Change only one input:

• Alimony duration months: 36 → 48

Expected directional effect:

• Monthly alimony may remain the same while the total over time increases, depending on how DocketMath structures duration.
• If the calculator re-derives the monthly figure based on duration assumptions, you may see the monthly alimony change too.

Checklist:

Wisconsin-specific timing note (statute citation context)

This worked example also touches Wisconsin timing language that can matter in the background of some disputes. Wisconsin has a general statute of limitations of 6 years:

• Wis. Stat. § 939.74(1)
  Source: https://codes.findlaw.com/wi/crimes-ch-938-to-951/wi-st-939-74/

Important clarity: No claim-type-specific sub-rule was found for the purposes of this brief. So treat this as the general/default limitation period rather than a promise about how every support-related dispute would be classified.

Takeaway from the sensitivity check

After you run A, B, and C:

• The biggest swing usually comes from your high-impact lever (often parenting time and child-related costs for child support, and duration assumptions for alimony totals).
• Income assumptions can also have broad impact across multiple outputs because they affect both buckets.
• Alimony duration may change totals even if monthly amounts stay the same—depending on the tool’s structure.

Related reading

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