How to run Alimony Child Support in DocketMath for Nevada

Step-by-step

Run this scenario in DocketMath using the Alimony Child Support calculator.

This guide shows you how to run Alimony and Child Support in DocketMath for Nevada (US-NV) using jurisdiction-aware rules. DocketMath helps you structure the math and workflow; it does not replace legal advice. If you’re unsure about facts (income, dates, custody details), verify them before relying on results.

1) Open the correct calculator in DocketMath

• Go to the calculator here: /tools/alimony-child-support
• Select Nevada (US-NV) as your jurisdiction (if the interface prompts you)

2) Enter party and case details (the “who/when” layer)

Even when you’re focused on the numbers, DocketMath typically needs case framing so it can apply the right logic.

Add:

• Filing or relevant date(s) (use whatever dates the calculator asks for)
• Party names (optional for the math, but helpful for organizing outputs)
• Whether you’re modeling alimony, child support, or both (based on the calculator’s options)

3) Provide income inputs (the “engine”)

DocketMath will usually compute support based on entered financial inputs. Enter values carefully and consistently.

Use the calculator’s fields for:

• Gross monthly income for each parent/spouse (or the equivalent income type the tool requests)
• Any income adjustments the tool supports (if present)

How outputs change:

• Higher gross income for the paying party typically increases the calculated obligation.
• Adding or removing income items (bonuses, additional earnings, or deductions the tool supports) can shift the payment amount depending on how the tool models those items.

4) Enter child-related inputs (the “obligation” layer)

If you’re calculating child support, the tool commonly needs inputs such as:

• Number of children
• Custody / parenting time allocation (for example, a time split or schedule inputs the calculator supports)

How outputs change:

• A larger parenting-time share for the recipient parent often reduces the paying parent’s obligation in typical support models, while a smaller share can increase it—depending on the Nevada logic implemented in DocketMath.

5) Enter alimony inputs (the “spousal support” layer)

For alimony modeling, DocketMath typically prompts for inputs like:

• Spousal income comparison (often derived from the same income entries, or entered through separate fields)
• Duration or other alimony-related parameters the calculator supports

How outputs change:

• Changes in the income gap tend to move the modeled alimony amount.
• If you adjust assumptions about length/duration (where supported by the calculator), the resulting timeline and total payments can change even if monthly figures appear similar.

6) Set the Nevada “time-related” rule (use the general default SOL)

Nevada’s general statute of limitations (SOL) rule for certain civil actions is a default period of 2 years, found in:

• NRS § 11.190(3)(d) — General SOL Period: 2 years
  Source: https://law.justia.com/codes/nevada/chapter-11/statute-11-190/

Important clarification for this workflow: No claim-type-specific sub-rule was found in the provided research beyond the general/default period. That means you should treat 2 years as the calculator’s general/default SOL period here—not as a tailored rule for a specific claim type.

Practical workflow in DocketMath:

• If DocketMath asks you to select an SOL period or time window, choose the 2-year general/default option for Nevada tied to NRS § 11.190(3)(d).
• If the calculator uses a date-to-date window, use the relevant dates for your scenario and ensure the overall window aligns with 2 years, unless you have a reason (based on your own research) to apply something else.

7) Review the output breakdown (don’t stop at the total)

After you run the calculation:

• Check line-item outputs (monthly alimony, monthly child support, combined totals, and any totals over time)
• Verify how the tool treated key assumptions—especially parenting time and time-window/SOL inputs

What to verify:

• Does the tool treat your inputs as monthly or annual?
• Are incomes entered as gross (before taxes) or net, depending on the tool’s field definitions?
• Did your SOL/time window selection match the intended 2-year general/default assumption?

8) Export or save results for edits

Use DocketMath’s save/export features (if available) to:

• Run scenario comparisons (change parenting time, income, or duration inputs)
• Maintain an audit trail of assumptions

Quick sanity checks:

• Reduce the paying party income slightly and confirm the obligation shifts in the expected direction.
• Increase parenting time for the recipient and confirm the child support output moves accordingly.

Common pitfalls

Below are issues that commonly distort alimony/child support calculations in DocketMath workflows for Nevada.

• Mixing annual and monthly income

  • If you enter annual income where the tool expects monthly (or vice versa), outputs can be off by a factor of 12.
• Entering parenting time in the wrong format

  • For example, using “days per week” where the calculator expects a “percentage split,” or leaving parenting-time fields blank and relying on defaults.
• Forgetting to align “time-related” assumptions with the SOL rule

  • This guide uses the general/default SOL period of 2 years under NRS § 11.190(3)(d).
  • The DocketMath workflow you choose should reflect that assumption; otherwise, time-based outputs may not match your intended period.
• Assuming the 2-year SOL applies to every situation

  • The 2-year figure is a default based on NRS § 11.190(3)(d), not a claim-type-specific determination.
• Omitting secondary income items the tool can accept

  • If the tool has fields for bonuses/other income categories you intend to include, leaving them at 0 may understate the obligation.
• Not reviewing output assumptions

  • Many calculators show how they interpreted your inputs—if you skip that, you may miss a unit mismatch (gross vs. net) or a parenting-time conversion.

Try it

Use DocketMath to run a first-pass scenario and confirm results change logically as you adjust inputs.

Quick practice checklist:

What you should expect during scenario testing:

• Increase paying party income → child support/alimony outputs generally increase.
• Increase recipient parenting time (if modeled that way in the tool) → child support generally decreases for the paying party.
• Extend the time window (if the calculator computes totals over time) → totals over time generally increase, even if monthly amounts stay the same.

Related reading

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