Worked example: Alimony Child Support in Minnesota

Example inputs

This worked example shows how DocketMath can calculate a combined view of alimony and child support in Minnesota using jurisdiction-aware rules and a straightforward workflow. It’s an illustration of how the calculator behaves—not legal advice, and not a substitute for Minnesota family-law guidance or court review.

Scenario (Minnesota)

• Jurisdiction: Minnesota (US-MN)
• Parties’ circumstances:

  • Mother has primary parenting time (school-year schedule).
  • Father pays support (monthly).
• Income (used as inputs to the tool):

  • Mother gross monthly income: $4,000
  • Father gross monthly income: $6,000
• Children:

  • Number of children: 2
  • Ages: 8 and 13 (used for any age-dependent elements in the model)
• Alimony assumptions (used as inputs to the tool):

  • Monthly alimony order amount: $750 (example figure)
  • Duration: 24 months (example figure)
• Retroactive or enforcement timing (used for any SOL/period logic in the tool):

  • “Lookback” start: the calculator’s default period will be used for this example.

Statute-of-limitations context used by DocketMath

DocketMath applies a general/default limitations period for the jurisdiction shown. For Minnesota, the general/default period is:

• General SOL period: 3 years
• General statute: Minnesota Statutes § 628.26
• Source (general criminal-court-records page): https://minnesotacourtrecords.us/criminal-court-records/gross-misdemeanor/

Important note (based on the brief): The brief does not identify a claim-type-specific sub-rule, so no special shortened/extended limitations window is applied beyond the general/default SOL period.

What you typically enter in the DocketMath tool

When using /tools/alimony-child-support, you generally provide:

• incomes for both parents,
• number/ages of children,
• parenting-time or custody inputs (if prompted by the calculator interface),
• the alimony amount/duration (for this scenario),
• any timing inputs that affect the calculator’s period logic (if your run includes them).

Checkbox-style checklist (to confirm inputs match your scenario):

Example run

Below is an example run consistent with the inputs above. You can follow along in DocketMath using:

• Primary CTA: /tools/alimony-child-support

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-by-step run (what DocketMath would do)

1. Minnesota rules enabled (US-MN): the calculator turns on jurisdiction-aware logic for child support and applies Minnesota-specific limitations timing logic using the general/default SOL period.
2. Compute the child support component: based on the tool’s formula mechanics using:

   • combined income factors,
   • child count (2),
   • ages (8 and 13),
   • any parenting-time inputs you enter (if applicable).
3. Add the alimony component (if included):

   • in this example, alimony is treated as an input monthly amount ($750/month),
   • the total monthly support view includes both child support and alimony.
4. Apply the limitations period logic (general/default):

   • DocketMath uses 3 years under Minnesota Statutes § 628.26 as the default window for any timing/period-related computation in this tool.
   • Because no claim-type-specific override is identified in the brief, it continues to use the general/default period.

Example numeric outputs (illustrative)

Because DocketMath’s exact numbers depend on the calculator’s internal model and how parenting-time inputs are collected in the interface, treat the following figures as illustrative example outputs (to show the structure you’ll see), not as a legal determination.

How to interpret the results

• The combined monthly amount changes in two main ways:

  1. Child support changes when incomes, children, or parenting-time inputs change.
  2. Alimony changes when the alimony monthly amount or duration changes.
• The 3-year limitations window affects any portion of the tool’s output that relates to timing horizons (for example, lookback-style reasoning). It does not automatically mean “support is owed for life”—it’s a general/default timing period used by the tool’s limitations logic.

Pitfall to avoid: Don’t assume the 3-year general/default SOL will match every enforcement or claim-type scenario. This worked example only applies the general/default rule because the brief did not identify a claim-type-specific sub-rule.

Sensitivity check

Change one input at a time to see how outputs react. This is often the quickest way to identify which variables matter most in a particular run of /tools/alimony-child-support.

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.

A. Change father’s income by +$500

• Father gross monthly income: $6,000 → $6,500
• Mother remains: $4,000
• Children and parenting time unchanged
• Alimony unchanged at $750/month

Expected directional effect:

• The child support component typically increases because the payer’s capacity rises.
• The combined monthly amount increases accordingly (often by more than $0, and sometimes by more than the income change depending on the calculator’s mechanics).

B. Change number of children: 2 → 1

• Keep incomes and parenting time the same
• Children: 2 → 1

Expected directional effect:

• Child support should decrease because fewer children reduces the baseline obligations in the model.
• Alimony stays $750/month in this scenario, so the combined amount won’t drop dollar-for-dollar with child support alone.

C. Change alimony amount: $750 → $1,000

• Alimony monthly amount: $750 → $1,000
• Duration stays 24 months
• Child support inputs unchanged

Expected directional effect:

• The combined monthly amount increases by about +$250/month in the alimony line item (plus/minus any interactions the tool uses for formatting or period-related outputs).
• The limitations timing logic should remain tied to the general/default 3-year window under Minn. Stat. § 628.26, since the brief indicates no claim-type-specific override for this setup.

D. Change timing assumptions to test SOL-window behavior (if available)

If the tool allows a lookback start date (or an “effective date” input), adjust it while keeping other variables constant.

What to expect given the briefing rule:

• The calculator should continue using the general/default 3-year SOL period.
• There should be no switch to a different shorter/longer claim-type period, because the brief explicitly states no claim-type-specific sub-rule was found.

Checklist for sensitivity testing:

• monthly child support,
• monthly alimony,
• combined monthly amount,
• any displayed timing/period line items (SOL window)

Related reading

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