Abstract background illustration for How to run Alimony Child Support in DocketMath for Nevada

How to run Alimony Child Support in DocketMath for Nevada

6 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Step-by-step

Below is a practical workflow for running Alimony + Child Support in DocketMath using Nevada jurisdiction-aware rules (jurisdiction code US-NV). This guide focuses on setup and calculation mechanics—not legal advice.

Note: Nevada uses separate authorities for child support and alimony. Your DocketMath inputs should reflect that distinction so the calculator can apply the correct rules.

1) Start the correct DocketMath calculator

  1. Open DocketMath → Alimony Child Support using the primary CTA: /tools/alimony-child-support
  2. Confirm you’re using Nevada (US-NV) rules within the calculator settings (or jurisdiction selector if shown).

2) Enter child support data (Nevada guideline framework)

Nevada directs courts to set child support using guideline rules administered under NRS 425.620 and codified in N.A.C. Chapter 425. The legal backbone is:

  • NRS § 125B.070 — court determines child support pursuant to the adopted guidelines
  • N.A.C. § 425.140 et seq. — Nevada’s child support guideline rules

In DocketMath, you’ll typically provide inputs that drive the guideline math, such as:

  • Parties’ incomes (gross or as defined by the tool)
  • Number of children
  • Parenting time / allocation (if the tool supports it)
  • Any guideline-adjustment items the calculator exposes

How outputs change:

  • Increasing the non-custodial/obligor income (as defined in the tool) generally increases the guideline child support amount.
  • Increasing time-share or parenting-time credits (if available in the tool) often shifts the presumptive obligation.
  • Adding children changes the guideline baseline because the amount is calculated per the child-support formula framework.

3) Enter alimony data (Nevada alimony framework)

For alimony, Nevada’s statutory authority is:

  • NRS § 125.150 (alimony)

In DocketMath, alimony inputs commonly include:

  • The parties’ incomes and/or earning capacities
  • Marriage length and relevant alimony parameters supported by the calculator
  • Other factors the tool models (for example, duration-related inputs)

How outputs change:

  • Alimony in many calculation models responds strongly to income disparity and marital-duration inputs.
  • Changing the assumed income used for alimony calculations can materially shift the alimony output even when child support stays constant.

4) Run the combined calculation (or sequential results)

Once you’ve populated both the child support and alimony sections:

  1. Click Calculate.
  2. Review results in the output panel(s). Many tools provide:
    • A child support figure (often under guideline assumptions)
    • An alimony figure (based on the alimony model used in the tool)
    • A combined monthly estimate (if the calculator aggregates totals)

Tip: Even if results display together, the calculator usually treats child support and alimony as separate calculation tracks internally.

Pitfall: Don’t assume the calculator “adds” results correctly if you left required fields blank. Missing parenting-time or income fields can cause the tool to fall back to a default assumption set.

5) Verify the period and default behavior (Nevada “default period” note)

Nevada orders are typically described in monthly terms, but tool behavior depends on the calculator’s structure. Where DocketMath uses a general default for calculation periods, apply it deliberately.

Clear default statement for Nevada period handling:
No claim-type-specific sub-rule was found in the provided jurisdiction notes; therefore, the general/default period behavior should be treated as the calculator’s standard timeframe for the combined outputs (unless the tool explicitly offers overrides).

6) Adjust inputs and observe deltas

Use DocketMath as an iteration engine:

  • Change only one variable at a time (e.g., parenting-time credit, or one party’s income).
  • Re-run calculations.
  • Compare outcomes side-by-side.

Here’s a quick “delta map” you can use while testing:

  • +1 child → baseline guideline amount typically increases (formula-driven)
  • Higher obligor income → child support likely increases
  • More parenting time for obligor (if modeled) → child support may decrease
  • Longer marriage duration (if used in alimony model) → alimony may increase or change duration category
  • Reduced income disparity (alimony inputs) → alimony may decrease

Common pitfalls

Below are the most frequent issues people hit when running Nevada alimony + child support in calculation tools like DocketMath.

  • Mixing income definitions between alimony and child support
    • Child support and alimony can use different income concepts in practice. In the tool, ensure you’re using the same “meaning” of income for each section the calculator expects.
  • Leaving parenting-time fields empty
    • If DocketMath supports parenting time or allocation for child support, leaving it blank often triggers a default that may not reflect the case facts.
  • Assuming Nevada guideline law is optional
    • Nevada law requires child support to be determined pursuant to guideline rules adopted for the program framework (see NRS § 125B.070 and the guideline codification under N.A.C. Chapter 425). In other words, a “no-guidelines” approach generally won’t align with the statutory structure.
  • Confusing alimony with child support
    • Nevada treats alimony under NRS § 125.150 and child support under NRS § 125B.070 / N.A.C. Chapter 425. Even if outputs are displayed together, the underlying calculations are conceptually separate.
  • Relying on a tool default period without checking
    • Because no claim-type-specific sub-rule was found in the provided jurisdiction notes, the general/default period should be treated as standard unless the calculator lets you specify otherwise. If a tool offers multiple timing modes (monthly vs. weekly), pick the one that matches your order-writing workflow.
  • Not documenting input versions
    • Revisions matter. Save screenshots or record the input set used for the results you plan to reference.

Warning: Calculation tools can produce outputs that look precise but rest on assumptions (especially around income and parenting time). Treat outputs as an estimation or a decision-support calculation, not a substitute for an order entered by a Nevada court.

Try it

If you want to validate your Nevada workflow in DocketMath, run a quick “sanity check” scenario:

  1. Enter Nevada (US-NV) as the jurisdiction.
  2. Add realistic baseline values for:
    • Child support: both parties’ incomes (as defined by the tool), number of children, and parenting-time inputs (if available).
    • Alimony: marriage duration (if the tool requests it), and the income inputs the alimony model uses.
  3. Click Calculate.
  4. Record:
    • Child support output
    • Alimony output
    • Combined total (if shown)

Then do two controlled experiments:

  • Experiment A (child support sensitivity):
    • Increase the obligor income by a small increment (e.g., +$500/month, or the tool’s smallest step if it offers increments).
    • Recalculate and observe how the child support component changes.
  • Experiment B (alimony sensitivity):
    • Change only the alimony-relevant input (e.g., reduce income disparity or adjust duration if the tool supports it).
    • Recalculate and observe how the alimony component changes while child support stays stable.

When your outputs respond in the expected direction, you’ve confirmed the calculator is using the intended sections and inputs.

You can start right here: /tools/alimony-child-support

Related reading