How to run Alimony Child Support in DocketMath for Utah

Step-by-step

This guide walks you through running Alimony + Child Support in DocketMath for Utah (US-UT) using jurisdiction-aware rules grounded in Utah’s statutory framework. We’ll focus on what to enter, what the calculator expects, and how the outputs typically change based on your inputs.

1) Start the correct tool

• Open DocketMath’s Alimony Child Support calculator:

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

You should now be on the calculator page where you’ll provide case details and income-related inputs.

2) Confirm the jurisdiction is set to Utah (US-UT)

Before entering numbers, confirm jurisdiction = US-UT.

• In DocketMath, the jurisdiction setting drives which statutory rules and default assumptions are applied.
• For Utah, DocketMath uses:

  • Child support framework under Utah Code § 78B-12-301 et seq.
  • Alimony (spousal support) reference under Utah Code § 30-3-5(8)

3) Enter child support inputs (Utah Code § 78B-12-301 et seq.)

Utah’s child support model uses a base combined child support table tied to the parents’ combined adjusted gross income.

A key statutory anchor is:

• Utah Code § 78B-12-301: “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.”
  (See: https://le.utah.gov/xcode/Title78B/Chapter12/78B-12-S301.html)

What to enter in DocketMath (typical fields you’ll see):

• Number of children (used to select the applicable table level)
• Parents’ income inputs, often shown as “income,” “adjusted gross income,” or similar terms
• Adjustments / shared placement inputs (if your interface includes them)

How outputs change as you enter data:

• If combined adjusted gross income increases, the base child support amount generally increases because DocketMath ties the base award to the § 78B-12-301 table.
• If the number of children changes, the tool generally moves you to a different schedule level, which can change the base child support amount even if income stays the same.

4) Enter alimony inputs (Utah Code § 30-3-5(8))

Next, provide the inputs needed for alimony/spousal support. The tool may ask for:

• Parties’ incomes and/or income-related inputs used to compute support capacity
• Marital circumstances indicators (depending on the tool’s design)
• Any additional amounts relevant to the alimony component

For Utah, the reference point is:

• Utah Code § 30-3-5(8) (alimony/spousal support)

Because tool field names vary, your practical goal is to ensure:

• The income assumptions you enter for alimony are consistent with how you entered income for child support in the same run.
• Any duration/amount fields are entered in the format the calculator expects.

5) Use the default period explicitly (Utah general/default logic)

You may see a “period” selection or assumption in the calculator. For Utah, this workflow follows the default/general period logic described in your brief.

No claim-type-specific sub-rule was found beyond the general/default period. Treat the calculator’s period setting as the general/default period, unless the tool provides an explicit Utah-specific option tied to a distinct rule basis.

In practice:

• If DocketMath shows a dropdown for support duration (or similar), keep default unless the tool explicitly tells you otherwise via its Utah-specific options.
• Record which period you selected so you can compare scenarios later.

6) Run the calculation and review line items

Once inputs are complete, run the calculator and review the output sections. A typical DocketMath results view for this tool may separate:

• Child support component
• Alimony (spousal support) component
• Combined total (if displayed)

Use the results to create at least one baseline scenario:

• Baseline: your current inputs with jurisdiction set to US-UT.

Then run a second scenario to test sensitivity:

• Example approach: change one income figure (or modify the shared placement input if applicable) and compare how the child support line changes.

7) Iterate with controlled changes (so you learn what drives the numbers)

To get the most value from the calculator, change one variable at a time.

Try this sequence:

• Variation A: adjust combined income input(s)
• Variation B: adjust number of children
• Variation C: adjust shared placement/time-sharing if your interface supports it
• Variation D: adjust alimony-related inputs

What you should look for:

• Child support should generally move most predictably with combined adjusted gross income, because Utah’s base award uses the § 78B-12-301 table.
• Alimony should generally respond to the alimony-specific inputs related to § 30-3-5(8).

Quick input/output map

Common pitfalls

Most mistakes come from inconsistent assumptions or mis-entered income details.

Pitfall checklist

• Wrong jurisdiction selected (make sure you use US-UT)
• Child support inputs don’t reflect “combined adjusted gross income” the tool expects (Utah base table logic under § 78B-12-301)
• Number of children mismatch with the case record
• Changing too many inputs at once (you lose the ability to tell what changed the output)
• Forgetting the period setting (don’t treat it as claim-type-specific when the workflow should be default/general unless the tool explicitly offers a distinct basis)

Data consistency issues that commonly distort results

• Updating income for alimony but not updating the related income used for child support (or vice versa)
• Entering annual totals in a field that expects monthly values (and skipping conversion)
• Using a placeholder like “0” for one party’s income and then interpreting comparisons from that flawed baseline

Try it

Here’s a practical way to run DocketMath for Utah and quickly test your understanding.

1. Open the calculator:

   • /tools/alimony-child-support
2. Set jurisdiction = US-UT.
3. Enter:

   • Child inputs (including combined adjusted gross income components the tool expects)
   • Alimony inputs tied to the tool’s Utah alimony workflow
4. Keep the default/general period unless the tool explicitly offers a Utah-specific alternate tied to a distinct rule basis.
5. Run the baseline calculation.
6. Run two quick “what if” scenarios:

   • Scenario 1: Increase combined adjusted gross income moderately and observe how the child support line moves (Utah Code § 78B-12-301 table-driven).
   • Scenario 2: Change only one alimony-related input and observe whether the alimony line changes while the child support line stays stable (as separated by the tool).

If you want the cleanest learning loop:

• One change per run.

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