Spreadsheet checks before running Alimony Child Support in Michigan

What the checker catches

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

Running an alimony or child support calculator in Michigan can be misleading if the spreadsheet inputs don’t match what the court expects. Before you run DocketMath (alimony-child-support) for US-MI, use a spreadsheet-checking workflow to catch issues that commonly distort results.

DocketMath is designed to be jurisdiction-aware for Michigan, but the spreadsheet still needs clean, consistent data. A good checker focuses on:

• Missing or mismatched dates

  • Examples: parent’s separation date vs. filing date; child DOB missing from one row.
  • Effect on output: support calculations can shift because arrears periods, age-based rules, or start/end windows won’t align.

• Incorrect “time window” assumptions

  • Michigan uses a general 6-year statute of limitations for enforcement-type claims under MCL § 767.24(1).
  • Important clarity: no claim-type-specific sub-rule was identified in this brief, so treat 6 years as the general/default period when setting your spreadsheet window.
  • Effect on output: if you accidentally include 8–10 years of history in a worksheet, arrears totals may be overstated relative to what the general limitation period allows under MCL § 767.24(1).

• Age and “month-by-month” calculations

  • Child support often changes when a child reaches a certain age (or when specific conditions occur).
  • If your spreadsheet calculates only by year totals, boundary errors can happen around birthdays.
  • Effect on output: monthly figures can drift, especially around the month a child turns an age that triggers a change.

• Non-numerical or inconsistent income formatting

  • Examples: “$4,500” stored as text in one column but numeric in another; annual income entered while the worksheet assumes monthly (or vice versa).
  • Effect on output: totals may concatenate, mis-sum, or produce zeros due to blank parsing.

• Expense lines and deductions that don’t map to the calculator’s inputs

  • DocketMath tools expect specific categories/inputs.
  • A spreadsheet that includes “misc.” deductions without a matching slot can produce results that don’t reflect the structure you intended to model.
  • Effect on output: numbers may look plausible inside the spreadsheet, but won’t align with the calculator’s expected inputs.

• Spouse/household labeling mismatches

  • Michigan worksheets need clarity on which income belongs to which party, and whether the calculator is treating support as owed by Party A vs. Party B.
  • Effect on output: swapped parties can flip signs/direction and invert the conclusion (even if the arithmetic is internally consistent).

Pitfall to avoid: If your spreadsheet includes arrears outside the general 6-year window tied to MCL § 767.24(1), your computed totals may not match the enforceable period a court would consider under the general/default limitation rule.

When to run it

Run the spreadsheet checks before you run DocketMath, and re-run them whenever you change anything that could affect timing, amounts, or rule matching. A simple, practical cadence works:

• Before your first DocketMath run

  • Confirm date fields (formats and meaning), income units (monthly vs. annual), and child DOBs.
  • Set the arrears lookback using the general 6-year period under MCL § 767.24(1) as your default (since this brief does not identify claim-type-specific sub-rules).

• After every spreadsheet edit

  • Adding a child row, updating income, changing the filing date, or adjusting separation date should trigger another check.

• Right before you finalize a “shareable” worksheet

  • If you export results or compare scenarios (e.g., Scenario A vs. Scenario B), re-run the checks so formatting issues don’t silently carry forward.

To keep it actionable, you can treat the spreadsheet-check stage like a short checklist (about 10–20 minutes):

For quick entry, start here: /tools/alimony-child-support.

Try the checker

Here’s a hands-on approach to validate your spreadsheet inputs before you run DocketMath (alimony-child-support) in Michigan:

1. Open your spreadsheet scenario

   • Common scenario variants include: current income, post-change income, or amended filing date.
   • Don’t run DocketMath yet—verify the timeline and inputs first.

2. Verify your timeline logic

   • Use the general limitation framework tied to MCL § 767.24(1):

     • Default window: 6 years
     • Michigan statutory context reference: https://www.michigan.gov
   • If your spreadsheet uses a different lookback, update it to match the general/default 6-year rule for this workflow.

3. Confirm child coverage and month mapping

   • Each child should have:

     • DOB
     • Status aligned to a month-by-month timeline
   • If your spreadsheet changes values on birthdays, ensure your date-to-month mapping doesn’t skip or double-count the birthday month.

4. Normalize income units

   • Convert income into the unit your calculator expects (often monthly figures for time-based calculations).
   • Quick test for unit mismatch:

     • If you double monthly income, does the output roughly double (with everything else held constant)?
     • If the output barely changes—or changes unpredictably—you may have unit mismatch or a text-to-number parsing issue.

5. Run DocketMath

   • Once the checks pass, run your Michigan scenario in DocketMath.
   • Make a comparison that helps you isolate errors:

     • Scenario A vs. Scenario B
   • Output changes should match the type of modification you made:

     • date shift should impact timing/arrears windows,
     • income change should scale amounts,
     • child count changes should adjust calculations according to your month coverage.

6. Document the deltas

   • Maintain a small “change log” in your spreadsheet:

     • date of change
     • what changed (income, dates, number of children)
     • expected direction of effect
   • This helps you detect anomalies caused by spreadsheet formatting rather than genuine calculation logic.

Gentle reminder: Don’t assume a calculator output is “court-ready” if the spreadsheet window and date fields don’t align with the general 6-year limitation rule under MCL § 767.24(1). This checker exists to keep the timeline aligned before numbers become misleading.

If you want to begin right now, use the calculator entry point: /tools/alimony-child-support.

Related reading

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