How Alimony Child Support rules vary in Utah
5 min read
Published June 4, 2026 • By DocketMath Team
What varies by jurisdiction
Utah’s rules for child support and alimony (spousal support) come from different statutes, and that separation can change what you pay each month—even when your incomes are the same. In DocketMath’s Alimony Child Support calculator, outcomes vary based on the inputs you enter and the facts you can support.
1) Child support: the table governs the base obligation in most cases
Utah uses a base child support table that starts with the parents’ combined adjusted gross income. The governing framework is Utah Code § 78B-12-301 et seq. The key rule for how the base number starts is:
- “The base combined child support obligation table in Section 78B-12-301 shall be used to determine the base child support award based on the parents' combined adjusted gross income.”
Source: Utah Code § 78B-12-S301 (online text)
https://le.utah.gov/xcode/Title78B/Chapter12/78B-12-S301.html
Why this is “jurisdiction variation”: another state may use a different table, different income definition, or different starting logic. In Utah, your starting point is the table, based on combined adjusted gross income, and then adjustments may apply depending on your circumstances and what the calculator allows you to model.
Note (default vs. special rules): No claim-type-specific sub-rule was found in the provided jurisdiction data. The table-based approach described above should be treated as the general/default starting point for the calculation period referenced by the cited table rule.
2) Alimony: separate statutory authority controls whether spousal support applies
Utah’s alimony framework is not in the same chapter as child support. Your jurisdiction data points to Utah Code § 30-3-5(8) for alimony, meaning:
- Child support math typically begins with the § 78B-12-301 table logic.
- Alimony analysis is governed by § 30-3-5(8) and related alimony rules.
Because the statutes are separate, changes to alimony-related factors can shift your overall monthly cash flow even if the child support base stays the same.
3) Combined effect: DocketMath reflects two buckets with different rule “drivers”
In DocketMath, you typically enter inputs for two components:
- Child support inputs → influence the base child support obligation using Utah’s table-based methodology
- Alimony inputs → influence the alimony component under Utah’s alimony authority
That separation is often where “variation” shows up across cases: two people with similar income numbers may still see different monthly totals because alimony inputs (and the evidence behind them) differ.
You can run the worksheet here: /tools/alimony-child-support
What to verify
Before relying on any estimate, verify your inputs and how Utah’s rule framework maps onto your facts. This is especially important because the calculator may require categories (and possibly optional adjustment settings) that need to be supported by documentation.
Gentle disclaimer: This is a practical guide to understanding the moving parts and the sources cited. It’s not legal advice. For advice about your specific situation, consider consulting a qualified attorney.
Income inputs (affect child support table results)
Utah’s child support base depends on parents’ combined adjusted gross income used to reference the base table in § 78B-12-301, as described in § 78B-12-S301.
Verify:
- You can support the adjusted gross income numbers you enter (e.g., pay stubs, tax filings, statements)
- You’re combining incomes correctly (and using the approach consistent with how “adjusted gross income” is treated in Utah’s child support framework)
- Your entry format matches what DocketMath expects for the timeline (e.g., annual vs. monthly conversion)
Alimony basis under Utah Code § 30-3-5(8)
Because alimony is governed by a different statute than child support, alimony inputs must align with what you’re trying to model under § 30-3-5(8).
Verify:
- The alimony-related inputs in DocketMath reflect the factual factors you intend to model under Utah Code § 30-3-5(8)
- You have a reasonable record for the factual drivers you input (because unsupported assumptions can skew the estimate)
Warning: A change in alimony inputs can change the total monthly estimate, even when the child support portion—starting from the Utah table under § 78B-12-301—doesn’t move.
Default method vs. special situations
Your jurisdiction data specifically highlights the table-based rule for establishing the base child support award. It does not identify a special “claim-type-specific” departure from that table rule.
Verify:
- Whether your case involves circumstances that typically warrant adjustments or deviations beyond the base table
- Whether DocketMath’s optional settings (if any) correspond to adjustment logic you can support with your documents
Quick “input → output” map (to prevent surprises)
Use this map while validating your DocketMath run:
| Input area in DocketMath | Utah authority driving it (from your sources) | Likely output impact |
|---|---|---|
| Combined adjusted gross income | Utah Code § 78B-12-301 (table base; described in § 78B-12-S301) | Changes base child support amount |
| Alimony-related inputs | Utah Code § 30-3-5(8) | Changes alimony component (and total monthly estimate) |
| Any calculator adjustments beyond base | Must be supported by Utah adjustment framework (not provided in the excerpt) | May change child support and/or total |
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
Sources and references
- Utah Code § 78B-12-301 et seq. (child support) and specific table-rule text at § 78B-12-S301: https://le.utah.gov/xcode/Title78B/Chapter12/78B-12-S301.html
- Utah Code § 30-3-5(8) (alimony): TODO — add exact online link if you want the citation mirrored to the official Utah Legislature text page.
