Why Alimony Child Support results differ in Nevada
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
If you run DocketMath’s alimony-child-support calculator for the same general case facts but you see different numbers in Nevada (US‑NV), the mismatch usually comes from how inputs, court-style assumptions, or timing are handled.
Here are the top 5 reasons Nevada alimony/child support results differ:
**Different income definitions (gross vs. “available” income)
- Nevada calculations are highly sensitive to which income components are included (for example: wages only vs. wages plus other recurring income).
- If one run includes bonus/commission or a different averaging approach, and the other does not, the underlying “ability to pay” side shifts—so monthly totals can change even when your “story” sounds identical.
**How many children are included (and what ages are assumed)
- Child support depends on household composition.
- Changing the number of children you model (or selecting different age-related options, if your workflow includes them) can move the child support line items without changing alimony.
Alimony duration or modification assumptions
- Some scenarios are set up as time-limited, while others are treated as longer-running assumptions.
- If one set of inputs assumes a fixed term (or uses an assumed end date), and another run leaves it open-ended, monthly totals and totals-by-horizon can diverge sharply.
Overlapping or competing deductions/credits
- Real forms and practical workflows can include or exclude costs like health insurance, childcare, or other deductions/credits.
- When one run includes an expense category and another omits it, the “net” affordability can change, which changes the output.
**When you’re “anchoring” the numbers (timing + enforcement/recoverability window)
- Nevada has a general statute of limitations reference that can affect what disputes are practically reachable in a claim context.
- Specifically, Nevada references a 2-year general period under NRS § 11.190(3)(d).
- Even if the calculator is focused on monthly obligations, differences in what time span is being discussed (or what periods are treated as contestable) can make two “correct-looking” runs feel inconsistent.
- Important: The 2-year period above is a general/default reference. No claim-type-specific sub-rule was found beyond that default reference in the information provided.
Warning (gentle): A statute-of-limitations “anchor” affects what may be recoverable or disputable in a claim context. The calculator can still be useful for monthly planning, but different measurement windows can make two outputs seem mismatched.
How to isolate the variable
Use DocketMath like a diagnostic tool: change one input at a time, keep everything else fixed, and compare results line-by-line.
- Freeze the jurisdiction and tool settings so both runs use the same rule set.
- Compare one input at a time (dates, rates, amounts) and re-run after each change.
- Review the breakdown to see which segment or assumption drives the difference.
A practical isolation checklist (do this in order)
- Run #1: use the income set you believe is complete.
Run #2: toggle only one component (for example, include/exclude bonus or commission).
Compare changes in alimony and child support separately—this tells you which part of the model is moving.
Run #1: lock the exact number of children you’re modeling.
Run #2: change only that one variable (or the relevant age-related selection).
If the child support portion moves while alimony stays stable, your driver is likely children/age configuration.
Run #1: keep alimony duration/term exactly as selected.
Run #2: change only the duration assumption.
If results jump here, the mismatch is likely structural (term assumptions), not income-driven.
Run #1: include health insurance/childcare/any selected expense categories.
Run #2: remove only one expense category at a time.
If only one line item materially changes, you’ve found a high-probability cause.
Run #1 and Run #2 should use the same effective date, start date, and any “measurement window” selection used in your workflow (if applicable).
Nevada’s 2-year general period reference comes from NRS § 11.190(3)(d) and is treated here as a general/default reference.
Keep that reference in mind when comparing outputs that might be discussing different relevant time spans.
If you want to jump back into the same tool flow, use this entry point: /tools/alimony-child-support.
Next steps
To reconcile differences efficiently in Nevada (US‑NV), do these three steps:
Document the exact input set used
- Record: payer income, recipient income, number of children, included expense categories, and the alimony duration/term selections.
Run a two-column comparison
- Create a quick comparison:
- “Run A” inputs → “Run A” outputs
- “Run B” inputs → “Run B” outputs
- The goal is to spot the first line item that changes after you adjust one input category.
**Use NRS § 11.190(3)(d) as a timing sanity check (general/default context)
- Nevada’s information here points to a 2-year general period under NRS § 11.190(3)(d) as a general/default reference.
- If your two runs appear to be measuring different relevant time spans, the difference may be explainable without reworking every financial input.
Pitfall: Chasing “math differences” without confirming income-definition differences or expense-inclusion differences often turns into wasted cycles.
When ready, rerun with the corrected variable using DocketMath’s alimony-child-support calculator at /tools/alimony-child-support, and keep inputs consistent across runs.