How to run Alimony Child Support in DocketMath for Wisconsin

Step-by-step

This walkthrough shows how to run Alimony + Child Support in DocketMath for Wisconsin (US-WI). The key is to use Wisconsin’s jurisdiction-aware rules—especially Wisconsin’s statutory framework for child support under Wis. Stat. § 767.511 and maintenance (alimony) under Wis. Stat. § 767.56.

Start at the tool entry point here: /tools/alimony-child-support.

1) Select Wisconsin jurisdiction (US-WI)

In the DocketMath tool, confirm the jurisdiction is set to US-WI (Wisconsin). This matters because DocketMath applies Wisconsin-specific calculations and default assumptions tied to:

• Child support: Wis. Stat. § 767.511, using the percentage standard established by the department under Wis. Admin. Code DCF 150
• Maintenance (alimony): Wis. Stat. § 767.56 (maintenance framework)

If the tool offers a jurisdiction selector, choose Wisconsin before entering any numbers. Otherwise, the tool may use the wrong guideline structure and produce results that don’t match Wisconsin’s approach.

2) Enter the child-related inputs used by the calculator

In the tool’s child support portion, enter the inputs DocketMath asks for (often including):

• Number of children
• Income figures for each parent (as prompted)
• Any additional factors the calculator supports via the UI (for example, healthcare or parenting-time adjustments, if those fields exist in the tool)

Wisconsin baseline rule to keep in mind: Under Wis. Stat. § 767.511, the court shall determine child support payments using the percentage standard set out in Wis. Admin. Code DCF 150, unless applying the standard would be unfair to the child or either party.

In practical terms for DocketMath, that means your child support output is primarily guideline-driven using the DCF 150 percentage approach—unless the tool includes an explicit way to address “unfairness”/deviation.

Note (default vs. special periods): The Wisconsin tool implementation described here does not identify a claim-type-specific sub-rule. So, if the tool asks about timing/coverage and doesn’t clearly offer a different branch, treat it as the general/default period logic.

3) Enter maintenance (alimony) inputs under Wisconsin’s framework

Next, fill in the maintenance (alimony) inputs in DocketMath. Wisconsin maintenance law under Wis. Stat. § 767.56 is broader than child support’s percentage model, so the tool may request more fact inputs than it does for child support.

Common categories you may see in the tool include:

• Income/earning capacity for each party
• Information that affects duration or relevant maintenance factors (depending on what the calculator requests)
• Additional fields the UI uses to reflect Wisconsin maintenance considerations

Because maintenance can be less “mechanical” than child support, expect that the alimony portion may respond differently to changes in the same income fields.

4) Confirm the calculator’s “default period” behavior

Some calculators include special cases for different order types (temporary vs. final, modification vs. initial, etc.). For this Wisconsin implementation, no claim-type-specific sub-rule was found.

So if DocketMath asks about timing/coverage (or if it uses an internal default), use the general/default period unless the tool explicitly provides a distinct Wisconsin option for your scenario.

5) Review outputs separately: child support vs. maintenance

After running the calculation, review the output in separate sections:

• Child support output: should align with Wis. Stat. § 767.511 and the DCF 150 percentage standard
• Maintenance output: should reflect Wis. Stat. § 767.56 considerations as implemented by DocketMath

If the tool provides monthly amounts, totals, or line-by-line breakdowns, capture them—those numbers make it easier to compare different scenarios in the next step.

6) Run “what-if” iterations to see what changes

A practical way to validate the tool’s behavior is to change one input at a time and observe how outputs move.

Try controlled iterations such as:

• Change one parent’s income (for example, increase by $2,000/month) and rerun

  • Check how child support changes (expect closer alignment to guideline mechanics)
  • Check how maintenance changes (expect it may respond more variably)
• Adjust child-related inputs (like the number of children) if the tool supports it

  • Observe whether the child support component updates consistently with the guideline structure
  • Note whether maintenance changes are driven by income changes or additional fields you modified

Use the tool’s recalculation controls so you can compare scenarios fairly.

7) Export or capture results for recordkeeping

If DocketMath offers a way to download, export, or share results, use it. Even if you’re only exploring estimates, keeping a snapshot of:

• The inputs used
• The output numbers
• The scenario label (if provided)

reduces confusion if you rerun with updated income, different child counts, or different timing facts.

Common pitfalls

• Using the wrong jurisdiction

  • If US-WI isn’t selected, child support and maintenance logic may not match Wisconsin rules.

• Forgetting Wisconsin child support is based on the DCF 150 percentage standard

  • Under Wis. Stat. § 767.511, the court uses the percentage standard from Wis. Admin. Code DCF 150 (unless application would be unfair).

• Assuming a deviation happens automatically

  • The statute directs use of the percentage standard unless it would be unfair to the child or either party. If DocketMath doesn’t provide an explicit deviation/unfairness input pathway, the estimate may not reflect that concept.

• Assuming claim-type-specific timing rules are built in

  • For this Wisconsin implementation, no claim-type-specific sub-rule was found. If your case requires a different timing posture, verify whether the tool provides a distinct option; otherwise, the tool uses the general/default period logic.

• Mixing up which inputs affect child support vs. maintenance

  • Even when income drives both, the way inputs feed outputs can differ. Child support tends to track guideline drivers more directly, while maintenance may depend on additional factors.

• Not iterating

  • Running only one scenario makes it harder to tell whether the output matches your expectations. Try at least 2–3 scenarios that change one input at a time.

Try it

To run a Wisconsin estimate in DocketMath, go here: /tools/alimony-child-support.

Before you hit calculate, use this quick checklist:

• Jurisdiction is set to Wisconsin (US-WI)
• You entered child count and the income inputs the calculator requests
• You entered the maintenance-related inputs tied to Wisconsin’s Wis. Stat. § 767.56 logic as implemented in the tool
• You didn’t rely on “special claim-type” behavior—if the tool doesn’t show a separate option, assume the general/default period
• You reviewed outputs separately for:

  • Child support (Wis. Stat. § 767.511 + DCF 150)
  • Maintenance (alimony) (Wis. Stat. § 767.56)

After the first run, do at least one controlled change:

• Adjust one parent’s income (e.g., +$2,000/month)
• Keep everything else the same
• Compare how the child support line changes versus the maintenance line

This helps you see whether the results track Wisconsin’s guideline-driven child support approach and the tool’s maintenance framework.

Related reading

• How Alimony Child Support rules vary in New York — What varies by jurisdiction
• How to calculate Alimony Child Support in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Alimony Child Support in Philippines — Worked example with real statute citations