Inputs you need for Alimony Child Support in Utah
6 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
If you’re using DocketMath to estimate alimony and child support inputs in Utah (US-UT), you’ll get the most accurate results when you gather specific financial and household details up front. That’s because these calculations are driven by concrete numbers—especially each parent’s income, employment situation, and the children’s living arrangement.
You may also see deadlines referenced in your research. Utah has a general statute of limitations (SOL) of 4 years under Utah Code § 76-1-302. Utah courts describe this as the general/default SOL period, and the Utah Courts website provides a general framework for thinking about SOL timing and limitations. Since this article is about inputs you need for a calculator, not about whether a particular claim is time-barred, you typically don’t need an SOL date to run the numbers.
Note: This is a general/default 4-year SOL period based on Utah Code § 76-1-302. No claim-type-specific sub-rule was found, so treat 4 years as the baseline SOL concept described by Utah’s general SOL framework.
Alimony inputs (typical categories)
In the alimony-child-support workflow, DocketMath will ask for fields that generally fall into categories like:
- Payor and recipient identity
- The roles you select (payer vs. payee) and the case context fields the tool requests.
- Income details
- Employment income (commonly salary/wages)
- Self-employment income (if applicable)
- Other sources that the input screen supports (such as commissions, bonuses, rental, or similar items).
- Work and earning capacity indicators
- Any inputs tied to how much the payor is working, changes in hours, reduced income facts, or earning-capacity assumptions (depending on what DocketMath requests in the form).
- Time framing / assumptions
- Whether the model is using current income assumptions versus another period (follow the fields provided by the tool).
Child support inputs (typical categories)
For child support, the biggest drivers are usually:
- Number of children
- Parenting time / custody split
- Overnights or the percent/number of days each parent has (enter what DocketMath asks for so the tool can allocate parenting time within its method).
- Each parent’s income
- Again, the exact fields depend on the DocketMath form, but you’ll generally provide current income figures for each parent.
- **Child-related costs (if supported by the tool)
- Some calculators allow inputs for certain shared or child-specific expenses (like childcare or medical coverage). Only enter amounts if the DocketMath alimony-child-support inputs provide a place for them—and keep your numbers consistent with your documentation.
Timing / documentation inputs (optional but helpful)
Even if DocketMath doesn’t require them, having the underlying documents can reduce guesswork and help you choose reasonable numbers:
- Recent pay stubs (often last 30–90 days)
- Last tax return (useful for grounding annual income assumptions)
- Childcare cost documentation
- Medical insurance premium statements and other relevant coverage documents
- A parenting calendar or schedule summary (for overnights/holiday time)
Gentle reminder: This is for organizing inputs, not for legal advice. If you have a complex income situation, unusual custody structure, or questions about legal timelines, consider reviewing your situation with a qualified attorney.
Where to find each input
To streamline your process, try to source each input from the same kinds of documents you’d use in a real support calculation packet.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
Income sources (payor and recipient)
- **Pay stubs (most recent)
- Useful for: wages, regular hours, and context for gross-to-net assumptions.
- Employer/HR documentation
- Useful for: base pay, commission structure, benefits that may affect income modeling.
- Tax documents
- Useful for: annual baseline income, especially for salaried or self-employed situations.
- Bank statements
- Useful for: variable income patterns (bonuses, irregular deposits), if you need to support estimates.
Parenting-time / custody split
- Parenting calendar
- Best for: overnights, weekday/weekend splits, and holiday approximations.
- **Existing custody order (if one exists)
- Useful for: the baseline schedule you’re trying to model or approximate.
Child-related costs
- Receipts and invoices
- Useful for: childcare costs and other recurring child expenses.
- Insurance statements
- Useful for: premiums tied to medical/dental coverage, if the tool supports them.
Utah SOL baseline (if you’re tracking deadlines)
Utah Courts explains the general SOL framework and provides the reference point for the general/default period:
- Authority: Utah Code § 76-1-302
- Utah Courts summary page: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html
Warning: The SOL is not the same thing as a support calculation. DocketMath helps you model support numbers, while SOL concepts relate to timing for legal action. Don’t mix them when you’re deciding what numbers to enter.
Run it
Start with the DocketMath alimony-child-support calculator and enter your collected inputs. Use this primary CTA to get there quickly: **/tools/alimony-child-support
Enter the inputs in DocketMath and run the Alimony Child Support calculation to generate a clean breakdown: Run the calculator.
Step-by-step input workflow (practical checklist)
As you go through the DocketMath screens, use this checklist:
How outputs change when inputs change
Even when the legal framework stays the same, your results can move significantly based on inputs:
- Income changes
- Higher payor income generally increases support expectations.
- Lower recipient income can also affect the modeled balance (depending on the tool’s method).
- Parenting-time adjustments
- More parenting time for one parent often shifts allocation and can change the amount indicated by the tool.
- Child count changes
- Adding or removing children in the assumption set typically changes the baseline support calculation.
- Documented vs. estimated inputs
- If you enter estimated values instead of pay-stub- or tax-backed figures, expect larger swings. Keep the modeled period aligned with the documentation you used.
Utah SOL reminder (default baseline only)
If you’re tracking timelines for next steps, remember the general baseline referenced by Utah’s general SOL framework:
- General SOL period: 4 years
- Authority: Utah Code § 76-1-302
- Utah Courts reference: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html
Pitfall: Don’t assume “4 years” automatically applies to every situation involving support. This article references the general/default SOL concept based on the provided Utah authority. For situation-specific deadlines, you’d need claim-type-specific analysis.
