Spreadsheet checks before running Alimony Child Support in Utah

What the checker catches

Running an alimony/child support spreadsheet in Utah is usually less about arithmetic and more about whether the numbers will hold up when they’re copied into filings, exhibits, and settlement communications. DocketMath’s alimony-child-support checker is built to catch spreadsheet issues and jurisdiction-aware timing problems before you finalize figures—especially problems that can quietly undermine your request.

Below are the most common types of issues the checker flags for Utah (US-UT) workflows.

1) Deadline risk: statute of limitations (SOL) mismatches

Utah generally applies a 4-year statute of limitations period under Utah Code § 76-1-302 (this is the general/default SOL framework). Utah’s courts also summarize the general SOL period as 4 years.

Important framing for your spreadsheet: the 4-year period is the general/default period. This brief does not identify a claim-type-specific sub-rule. In other words, don’t assume a different limitations window automatically applies for every alimony/child support theory—unless you confirm it for your exact claim type and legal theory.

A checker can’t replace legal advice, but it can highlight when your spreadsheet reaches back farther than the general 4-year window.

2) Date alignment problems

Alimony and child support calculations depend heavily on dates and the boundaries of each payment period. The checker commonly catches:

• Reversed dates (end date earlier than start date)
• Inconsistent period lengths (for example, mixing monthly and weekly assumptions)
• Rows where an amount is entered but the related effective date (or period boundary date) is blank

When dates are off—even by a month or two—your “per period” calculations can still look plausible, but your arrears and totals may be wrong.

3) Amount math consistency

Even small spreadsheet slips can change outcomes. The checker often flags:

• Negative values in fields tied to arrears or paid-to-date
• Totals that don’t match the sum of the line items
• Rounding inconsistencies (e.g., rounding in one column but not another)
• Mixed income period logic (e.g., one row uses annual income while another uses monthly income without consistent conversion)

These issues matter because viewers typically verify “sanity” by scanning totals, balances, and reconciliation logic.

4) Output interpretability flags

A spreadsheet that produces a number without clear labels can create risk in court filings. The checker helps ensure your outputs are interpretable by:

• Encouraging consistent labeling of key outputs (e.g., “calculated support for period,” “arrears,” “running balance”)
• Checking that cross-column logic is consistent (so the number you cite matches what your timeline says it should be)

Quick “at a glance” checklist

Before you finalize anything, confirm:

When to run it

Run DocketMath’s checker before you lock in numbers for filing, negotiation, or declarations—because timing errors can force bigger rewrites than pure math mistakes.

Run the checker before importing a spreadsheet into the Alimony Child Support workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Run it at these decision points

1. Before you build the spreadsheet timeline
   Confirm your row structure and date boundaries first. Catching timeline logic early prevents garbage-in/garbage-out results later.

2. After you enter dates and first-pass amounts
   This is the best moment to review “SOL window” and “date alignment” checks. It’s usually much cheaper to fix a date than to recalculate an entire timeline.

3. After you import or update income/expense inputs
   Income changes can ripple through every period’s calculated amount. Validate totals immediately after updates.

4. Right before export or copying into a filing packet
   Use the checker as a final quality control step for sign errors, rounding issues, and missing required fields that may not be obvious by eye.

SOL timing: use the general 4-year window as a guardrail

Utah’s general SOL framework, summarized as 4 years, is tied to Utah Code § 76-1-302. For spreadsheet checking purposes, treat the 4-year general period as a practical guardrail.

How that translates into spreadsheet behavior:

• If your timeline reaches back more than 4 years, the checker should flag it for review.
• If you later confirm a different limitations rule applies to your specific situation, you can adjust the spreadsheet—but don’t skip review just because a number “looks right.”

Try the checker

You can run DocketMath’s alimony-child-support checker here:

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

When you use the tool, pay attention to inputs that strongly affect outputs:

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

What to input (and why it matters)

• Start date and end date
  These determine the time period covered and whether the timeline exceeds the general 4-year SOL guardrail under Utah Code § 76-1-302.
• Payment frequency / period structure
  Ensures the checker doesn’t mix monthly and yearly assumptions incorrectly.
• Income and adjustment figures (as applicable)
  Changes calculated figures across every period in your timeline.
• Any paid amounts / prior payments
  Drives arrears and running balance computations.

What to review in the results

Treat the checker output like a debugging dashboard:

• Did it warn about dates outside the general 4-year window?
• Are date ranges consistent row-to-row?
• Do computed totals match the sums you expect?
• Are there any negative or blank-amount rows that could distort the running balance?

Example workflow (spreadsheet-first mindset)

• Step 1: Enter a tight date range (e.g., the last 36–48 months) so the general 4-year window is easy to verify.
• Step 2: Confirm totals and running balances.
• Step 3: Expand backward only after you’ve reviewed whether a different limitations framework might apply to your specific situation.

This reduces the chance of a late-stage timeline or SOL correction that forces a major rewrite.

Related reading

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