How to run Alimony Child Support in DocketMath for Michigan

Step-by-step

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

This guide explains how to run alimony and/or child support calculations in DocketMath for Michigan (US-MI) using jurisdiction-aware rules. You’ll enter the core inputs, choose the right calculator mode, and interpret outputs consistently.

1) Open the correct Michigan calculator

1. Go to the tool: /tools/alimony-child-support
2. Confirm the jurisdiction is set to Michigan (US-MI).
3. Select the calculator mode that matches what you’re trying to model:

   • Alimony
   • Child support
   • Both (if DocketMath offers a combined workflow in the tool interface)

If the interface asks for jurisdiction or court-related toggles, choose Michigan so the tool applies Michigan-specific defaults.

2) Enter the alimony inputs (if you’re modeling alimony)

Typical alimony modeling inputs in calculators like DocketMath include items such as:

• Income information (often broken out by spouse)
• Any adjustments supported by the calculator’s logic
• Payment frequency (e.g., monthly)

How outputs change:

• Increasing the payor’s net income generally increases potential alimony range.
• Increasing the recipient’s income generally reduces potential alimony range.
• If DocketMath uses adjustment factors (for example, dependents or expense proxies), adding those inputs can change the final number more than small rounding differences.

Practical tip: Enter values in the units the tool requests (for example, monthly vs. annual). If you’re unsure, check for unit labels directly on each input field.

3) Enter the child support inputs (if you’re modeling child support)

For child support modeling, DocketMath typically requires:

• Number of children
• Parent incomes (often combined or listed per parent)
• Parenting-time assumptions (if the tool supports them)

How outputs change:

• More children usually increases the total support output.
• Higher income for the payor generally increases support.
• Parenting-time inputs can change the monthly total materially, depending on how DocketMath applies Michigan’s approach within the tool logic.

4) Confirm Michigan timing logic for enforcement questions

Michigan includes a general enforcement-related statute of limitations (SOL) period that may come up in support enforcement contexts.

DocketMath applies the general/default SOL period you provided:

• General SOL period: 6 years
• General statute: **MCL § 767.24(1)
• Source (jurisdiction info): https://www.michigan.gov

Important clarity: Your jurisdiction data notes that no claim-type-specific sub-rule was found. So this guide uses the general/default 6-year period clearly, rather than implying a different timeline for a specific type of support-related claim.

If the DocketMath tool includes an “enforcement timeframe” or “lookback” feature, use:

• 6 years based on MCL § 767.24(1) (general/default)

5) Run the calculation and review the output panel

After entering inputs, run the calculation. Then review:

• Monthly alimony (if selected)
• Monthly child support (if selected)
• Any combined total (if your mode includes both)

Also check how the tool displays:

• Frequency (monthly is the common default)
• Ranges vs. single estimates (if shown)
• Rounding rules

Practical tip: Change one variable at a time (for example, parenting-time hours, payor income, or number of children). That makes it easier to see which inputs drive the largest changes.

6) Use DocketMath’s “what-if” loop for scenario comparison

Family-law numbers often depend on facts you may be clarifying or negotiating. Use DocketMath iteratively:

• Scenario A: Current income figures
• Scenario B: Updated income estimate (e.g., after a job change)
• Scenario C: Different parenting-time split (if adjustable)

Scenario testing checklist:

• Change only one input per run where possible
• Keep units consistent (monthly vs. annual)
• Record the output changes between scenarios (especially the monthly amounts)

7) Export or save your work (if available)

If DocketMath provides saving, exporting, or generating a shareable summary:

• Save the run that matches the facts you want to model
• Ensure the output reflects Michigan (US-MI) so you don’t lose jurisdiction context

That helps you compare runs later without re-entering everything.

Common pitfalls

These are the most frequent mistakes people make when running alimony and child support scenarios in Michigan using DocketMath.

1. Using the wrong jurisdiction

   • If you accidentally run a non-Michigan setting, the tool may not apply Michigan logic.

2. Mixing yearly and monthly income

   • Enter income in the exact unit the calculator expects. A “$60,000” field can mean very different results depending on whether it’s annual or monthly.

3. Forgetting the number of children

   • An incorrect child count can substantially change child support outputs.

4. Entering parenting-time assumptions inconsistently

   • If parenting-time inputs are required for the tool, changing them between scenarios (without realizing it) can make comparisons misleading.

5. Assuming a different SOL for every support scenario

   • Your Michigan jurisdiction data specifies a general/default SOL period of 6 years under MCL § 767.24(1).
   • Since the provided data did not identify any claim-type-specific sub-rules, this guide uses the general 6-year period rather than inventing a different timeline.

1. Expecting alimony and child support results to move the same way

   • Alimony modeling and child support modeling are driven by different inputs. If you only adjust one income number, one category may move more than the other.

Try it

Ready to run a Michigan scenario in DocketMath?

1. Open the tool at: /tools/alimony-child-support
2. Ensure US-MI is selected.
3. Start with a baseline run:

   • Enter current income values
   • Enter the number of children
   • Add parenting-time inputs if the calculator asks for them
4. Run the calculation.
5. Do one change and re-run:

   • Example: adjust parenting-time or update income for the second scenario
6. Compare the output numbers side-by-side (monthly amounts and any totals displayed).

If you want to review timing expectations for enforcement-related questions, use:

• 6-year general/default SOL under **MCL § 767.24(1)

For a broader set of calculators and resources, you can browse:

• /tools

Quick input sanity checklist

Related reading

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