Common Alimony Child Support mistakes in Nevada

The top mistakes

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

If you’re calculating alimony and/or child support in Nevada with DocketMath’s Alimony/Child Support calculator (US-NV), a few common input and workflow mistakes can swing results dramatically. Below are the most frequent issues we see when users enter income, timing, or rely on incomplete information.

1) Using the wrong “default” time window for limitations

Some users assume there’s a special statute of limitations (SOL) rule for every category of family-law money. Nevada does have a general SOL framework, and for general purposes the default is 2 years.

Nevada’s general SOL is set out in NRS § 11.190(3)(d), which provides a 2-year limitations period under the general rule described in that statute.

• Common error: Treating 2 years as “claim-type specific” without checking whether the general rule applies to your situation.
• Practical impact: You may spend time gathering documentation that’s outside the likely limitations window—or miss a document needed within the period.

What DocketMath does with this: The calculator is designed for calculation support estimates; it doesn’t replace a limitations analysis. If you’re tracking potential arrears or deadlines, keep the default 2-year SOL in mind: NRS § 11.190(3)(d).

2) Entering income net of the wrong deductions

Income is the backbone of both alimony and child support calculations. A frequent error is entering income that’s reduced by deductions that aren’t treated consistently in support calculations.

• Common error: Using take-home pay (after tax withholding and benefits) as if it were the full “income” figure.
• Practical impact: This can understate or overstate available resources and produce an unrealistic estimate.

How to catch it quickly: Compare your entered number to:

• recent pay stubs (gross pay),
• annual W-2 or tax summaries (where applicable),
• and any consistent documentation you used to compute income.

3) Forgetting to include secondary or irregular income streams

Wage-only entries are common. Yet many households have additional income such as overtime, bonuses, commissions, self-employment income, or other recurring payments.

• Common error: Leaving out income that appears on bank statements or past tax returns but not on the “main” pay stub.
• Practical impact: Estimates may be low—especially if the irregular income has been consistent over time.

4) Mis-specifying the child-related inputs (age, number of children, or custody timing)

Even if the tool is straightforward, small input errors are easy, such as:

• wrong number of children,

• wrong child age bracket inputs (when applicable in the calculator logic),

• incorrect time-sharing/custody arrangement inputs that affect the support estimate.

• Common error: Relying on assumptions like “one child is mostly with me” without entering the actual arrangement used for the estimate.

• Practical impact: Support can change meaningfully with custody/time-sharing inputs.

5) Mixing up what the output represents (alimony vs. child support)

Users often expect one number to “cover everything.” In reality, estimates for:

• child support (driven by child-related factors and the incomes),
• and alimony (driven by marital circumstances and other considerations)

may produce separate line items or different sensitivities to income.

• Common error: Comparing a single combined number to what you believed was owed without confirming which component it represents.
• Practical impact: You may adjust inputs based on the wrong line item.

6) Not running “what changes if…?” scenarios

A single calculation doesn’t tell you where the leverage points are. Without sensitivity checks, it’s easy to lock onto an incorrect assumption.

• Common error: Entering current income once and stopping—without testing how changes (like a raise, reduced hours, or a different time-sharing assumption) affect the output.
• Practical impact: You might plan based on a brittle number.

How to avoid them

You can reduce errors quickly by standardizing your inputs and using the calculator as decision-support—not a final legal determination.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

1) Use a documentation checklist before you enter anything

Before opening DocketMath’s Alimony/Child Support calculator (US-NV), gather the inputs you’ll need:

2) Treat “2 years” as the default limitations window—and be clear why

If your goal is to evaluate how far back certain amounts might be actionable, anchor your review to the general Nevada default:

• Nevada default SOL: 2 years
• Statute: **NRS § 11.190(3)(d)
• Source: https://law.justia.com/codes/nevada/chapter-11/statute-11-190/

Important clarity: This is a general/default period described by NRS § 11.190(3)(d). The content above is not a claim-type-specific rule.

3) Enter income consistently across alimony and child support runs

If the tool asks for a specific income field (like monthly gross wages), use the same approach every time you rerun scenarios. Avoid mixing:

• one run using gross pay,
• another using net pay,
• and a third using a “rounded” annual estimate.

Goal: Make each scenario comparable so differences reflect real assumptions—not inconsistent math.

4) Run at least 3 scenarios to identify the drivers

Instead of a single calculation, try:

1. Baseline (your best estimate of income and time-sharing)
2. Lower-income scenario (e.g., reduced hours or confirmed lower earnings)
3. Higher-income scenario (e.g., include documented bonuses/commissions)

Then compare output sensitivity—this helps you spot which inputs matter most.

5) Separate “component thinking” when you review outputs

When you review results from DocketMath, don’t treat the final number as one interchangeable bucket. Break it down:

• child support line item(s)
• alimony line item(s)
• totals

If your numbers don’t match expectations, check the component first before changing multiple inputs at once.

6) Use the calculator before you talk numbers with anyone

If you’re preparing for negotiations, discussions, or review of draft paperwork, use DocketMath to create a structured estimate you can explain clearly.

Start here: /tools/alimony-child-support
For adjacent help with calculations and inputs, you can also explore: /tools/

Related reading

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