How to run Alimony Child Support in DocketMath for Utah

Step-by-step

Below is a jurisdiction-aware walkthrough for running Alimony + Child Support in DocketMath for Utah (US-UT) using the alimony-child-support calculator. This guide focuses on how to set inputs and interpret outputs—not legal advice.

1) Open the correct DocketMath calculator

1. Go to the primary calculator page: **/tools/alimony-child-support
2. Confirm the jurisdiction setting shows Utah (US-UT) (or select it if your version prompts you).

2) Enter the party and support scenario basics

In DocketMath, you’ll typically be asked for facts that affect both:

• Child support calculations, and
• Spousal support/alimony calculations.

Fill in what the form requests, such as:

• Filing context / case type (if prompted)
• Parenting time or custody-related inputs (often used for child support)
• Whether the request is “current support” or involves arrears (if the UI offers that distinction)

If you see a case timing or date field, enter accurate dates—those drive how long support claims have been active and can affect any timing/limitations references the tool displays.

3) Provide income inputs (the calculations depend heavily on them)

Support formulas in practice are income-sensitive. In DocketMath:

• Enter gross income values for each parent/spouse (as requested).
• If the tool separates monthly vs annual income, use the format it asks for.
• Include any income categories the calculator expects, but only enter categories that match the fields shown in the UI.

How outputs change

• Higher income for the supporting party generally increases the child support figure.
• If the recipient’s income is higher, the net support need can decrease.
• For alimony, income differences and duration factors (if included) can meaningfully affect the result.

4) Add parenting time / custody details (child support inputs)

Child support outcomes are often driven by time allocation. Enter:

• Overnights/days per parent (or the parenting-time method the calculator uses)
• Any split custody breakdown if the calculator asks for it

How outputs change

• More parenting time for the non-primary parent often reduces the child support obligation (because cost allocation changes).
• If the tool provides a “combined parenting-time percentage,” make sure it matches the schedule you’re trying to model.

5) Add alimony-related inputs (spousal support factors)

Depending on what the DocketMath UI asks for, alimony may require inputs such as:

• Duration/relationship-length factors (e.g., years married, relationship length, or a “support duration” reference)
• Employment status changes or health/disability inputs (only if the calculator includes those fields)
• Whether you’re estimating ongoing support or considering a modification-style scenario (if the UI supports it)

How outputs change

• Larger income disparity can increase the suggested alimony amount.
• If the tool uses duration/relationship-length variables, longer duration factors can influence the output more than small income changes.

6) Confirm the “statute limitation” reference in the results section

Because Utah’s general/default limitation period is 4 years under Utah Code § 76-1-302, the tool may include a timing reference or limitations note in its output panel.

**Utah workflow instruction (keep this consistent)

• Treat 4 years as the default reference point unless a more specific rule clearly applies.
• In this guide, that general/default approach is used because no claim-type-specific sub-rule was found for this workflow. Use the general reference unless you confirm a different controlling rule for the specific claim type.

7) Review output components and switch scenarios if the tool allows it

After running the calculator, review each output section. Common result categories include:

• Child support estimate (often a monthly figure)
• Alimony/spousal support estimate (monthly figure or range)
• Total combined monthly support (if shown)
• Any notes about timing/limitations references

If the UI supports scenario testing:

1. Adjust one variable at a time (for example, change parenting-time percentage by 10–20%).
2. Re-run the calculation.
3. Note how much each output line changes.

Use scenario testing to understand drivers of the results—not to “game” numbers.

8) Export or capture results for your next step

If DocketMath offers a download, share, or copy function:

• Capture the inputs you used and the outputs you generated.
• Save at least one baseline run and one alternate run (for example, “current schedule” vs “proposed schedule”).

This helps you compare changes later without re-entering everything.

Common pitfalls

Support calculations are sensitive. These are the issues that most commonly lead to confusing or incorrect outputs in tools like DocketMath:

• Using the wrong time basis for income

  • Example: entering annual income into a field that expects monthly.
• Mixing parenting-time inputs

  • Example: if the calculator asks for “days per parent,” entering “hours” will skew the time factor.
• Leaving alimony fields blank when the calculator expects values

  • Some UIs treat blanks as zero or “unknown,” which can materially change results.
• Inconsistent scenario dates

  • If the tool uses an “as of” or “effective date,” mismatched dates can affect any timing/limitations references the tool shows.
• Assuming Utah’s 4-year period is claim-type specific

  • Utah Code § 76-1-302 is used here as the general/default statute of limitations framework for this workflow. In this guide, the period is 4 years by default because no claim-type-specific sub-rule was identified.
• Assuming arrears treatment is automatic

  • If your situation involves arrears, check whether the tool estimates “current” amounts, models “past-due” components separately, or only produces forward-looking estimates.

Quick checklist before you submit or use the output

Try it

1. Open DocketMath’s calculator here: **/tools/alimony-child-support
2. Set Utah (US-UT) as the jurisdiction.
3. Enter your baseline scenario:

   • Income for both parties
   • Parenting time/custody schedule
   • Any alimony-related inputs the calculator requests
4. Run the calculation and review:

   • The child support estimate
   • The alimony estimate
   • The combined monthly output (if shown)
5. Run one alternate scenario by changing one input set:

   • For example, update parenting time, then re-run
6. Compare results and note which section changed most.

If the results panel includes a statute-limitation reference, it should align with the default general period of 4 years under Utah Code § 76-1-302. Because no claim-type-specific sub-rule was found for this workflow, treat that reference as the general default.

Related reading

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