Why Alimony Child Support results differ in Utah

The top 5 reasons results differ

When you run DocketMath’s alimony-child-support calculator for Utah (US-UT), you can see noticeably different outcomes even when you think you’re entering the “same” facts. Utah’s inputs and jurisdiction-aware rules create multiple points where small changes matter.

Below are the top 5 reasons results differ—each one maps to a specific input or Utah rule behavior you can verify in your numbers. (This is informational math-and-process guidance, not legal advice.)

1. Parenting-time and schedules change the child-support share

   • Even with identical income inputs, different parenting-time arrangements can shift how much the child-support obligation is attributed to each parent.
   • Result: the calculator output changes because the child-support portion is sensitive to time allocation assumptions.

2. Income definition differences (gross vs. adjusted) drive the biggest swings

   • DocketMath relies on the income numbers you enter.
   • If one run uses higher “gross-style” income and another run uses “adjusted” income (after deductions you chose), you’ll get different results.
   • Result: both child support and alimony estimates move because they’re downstream of the income inputs.

3. Alimony duration and eligibility assumptions

   • Alimony results can differ when the scenario changes assumptions about duration, purpose, and when support begins relative to the case facts.
   • Result: the calculator may suggest different alimony ranges depending on the alimony-related inputs you provide.

4. Rounding and sequencing effects

   • Many calculators apply percentages, then apply constraints/caps, then round to display-friendly numbers.
   • Result: two very similar input sets (especially with decimals or annual-to-monthly conversions) can produce outputs that look “inconsistent” even though the underlying math is consistent.

5. Time-bar confusion for “how much can be requested,” even if the monthly math is the same

   • A common diagnostic error is assuming every past period can be claimed or credited automatically just because you calculated an amount for that month.
   • Utah uses a general/default statute of limitations of 4 years under Utah Code § 76-1-302.
   • Important: The Utah Courts guidance you’re using indicates no claim-type-specific sub-rule was found for this discussion—so treat 4 years as the default baseline for timing analysis.
   • Note: DocketMath’s calculator output focuses on support amounts. It doesn’t decide recoverability for every prior month. But people often compare runs without applying the timing baseline, which makes results feel contradictory.

Utah’s general SOL period is sourced here:

• Utah Courts: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html
• Statute: Utah Code § 76-1-302 (general rule)

How to isolate the variable

To pinpoint why your results differ, use a single-variable workflow in DocketMath. Change one lever at a time instead of adjusting multiple fields between runs.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Checklist: run these in order

Quick diagnostic table

For time-related confusion, use the default 4-year SOL baseline:

• Baseline: 4 years under Utah Code § 76-1-302
• General/default: apply when no claim-type-specific rule overrides it (as indicated by the Utah Courts guidance)

If you’re comparing past-period questions (recovery/credit vs. ongoing support), compare your scenario to the 4-year baseline before concluding there’s a “math error.”

Next steps

1. Re-run DocketMath with locked inputs

   • Keep everything constant except one variable (parenting-time first, then income, then alimony settings).
2. Compare outputs side-by-side

   • Identify the first line item that changes: child support vs. alimony.
3. Cross-check the timeframe

   • Use the 4-year default SOL baseline for timing expectations: Utah Code § 76-1-302 (Utah Courts guidance).
4. Use the tool directly

   • Start with DocketMath’s calculator: **alimony child support

If you want a practical troubleshooting order:

• Treat income format as the most likely cause of “same facts, different numbers.”
• Treat parenting-time as the most likely cause of child support changing even when income doesn’t.
• Treat timing assumptions as the most likely cause of confusion about earlier months and what people think “should be included.”

Related reading

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