Worked example: Alimony Child Support in Nevada
7 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Alimony Child Support calculator.
This worked example shows how DocketMath can be used to estimate alimony and child support calculations in Nevada using jurisdiction-aware defaults. It’s designed to be practical—showing what you enter and how results change—without providing legal advice.
Assumptions for this example
Because alimony and child support are fact-driven, this example uses a simple, illustrative set of inputs. You can swap in your numbers to mirror a real situation more closely.
Household and income
- County / venue (informational): Washoe County (not used for the math in this example)
- Filing date / calculation date: 2026-04-15
- Payor gross monthly income: $7,500
- Payee gross monthly income: $4,000
- Payor pay frequency: Monthly
- Payee pay frequency: Monthly
Children
- Number of children: 2
- Children’s current status: Under 18 (or otherwise eligible as applicable for support)
Alimony (spousal support) inputs
- Is there a prior support order being modified? Yes (for demonstration)
- Alimony amount method in the calculator: “Estimate” mode (tool determines a modeled output based on the inputs you provide)
Nevada SOL context (timing awareness)
If a person is trying to enforce or collect unpaid support obligations, Nevada’s general statute of limitations for many civil actions can matter in strategy and documentation. In this worked example, we demonstrate how to track timing using the general default period.
- General SOL period: 2 years
- General statute: **NRS § 11.190(3)(d)
Note: This content uses the general/default SOL period. No claim-type-specific sub-rule was found in the provided materials, so the example treats 2 years under NRS § 11.190(3)(d) as the default reference point rather than a claim-specific rule.
Nevada SOL reference point used in this example (general/default)
- Start point (for documentation checks): the date unpaid amounts accrued (modeled input)
- Lookback window (for quick audits): 2 years
To operationalize that, this example includes:
- Unpaid amounts date to check (modeled): 2024-12-01
- Current date: 2026-04-15
- Time elapsed: ~1 year 4.5 months (within 2 years)
This helps you see how the tool’s timing awareness can affect whether you flag older amounts for review.
DocketMath inputs checklist
Use the following in DocketMath → alimony-child-support:
Example run
Below is a step-by-step “what happens next” flow for a DocketMath run in US-NV.
Run the Alimony Child Support calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Income modeling
DocketMath uses your entered monthly gross incomes to produce a baseline support ability picture. With:
- Payor: $7,500/month
- Payee: $4,000/month
…the calculator will generate modeled obligations that reflect the income gap, while also incorporating the children count (2).
Step 2: Child support estimate (based on your inputs)
Your number of children (2) is a key driver. If you change only this variable and rerun, you should expect the child-support component to shift materially.
Step 3: Alimony estimate (spousal support component)
Alimony varies dramatically depending on case-specific factors (duration of marriage, need/ability, and other considerations). In this tool-based example, DocketMath’s “estimate” mode produces a modeled alimony component from the information you supply.
Step 4: Nevada timing awareness using the general SOL default
Because the example includes a modeled “unpaid amounts date,” DocketMath can tag whether the date falls within the general 2-year window.
- Modeled accrual: 2024-12-01
- Calculation date: 2026-04-15
- Window: 2 years per NRS § 11.190(3)(d) (general/default)
Result in this example: Within 2 years, so the tool would flag those amounts as potentially within the general enforcement window for the default SOL check.
Warning: A statute of limitations analysis can require more than a default period—facts about accrual, enforcement history, and the specific procedural posture can alter outcomes. This worked example uses NRS § 11.190(3)(d) as a general reference point per the provided materials, not as a guarantee for any specific claim.
Example output format (what to look for)
After you run the calculator, focus on these output sections:
| Output category | What it represents | What changes it |
|---|---|---|
| Child support estimate | Monthly amount attributed to the children | Number of children, income gap |
| Alimony estimate | Monthly amount attributed to spousal support | Alimony estimate settings, income inputs |
| Total estimated monthly support | Combined modeled amount | Changes to either child support or alimony |
| SOL timing flag | Whether a modeled accrual date is within the 2-year default window | Accrual date, calculation date |
Because DocketMath is a calculator workflow, treat the numerical amounts as model outputs based on your inputs—use them to compare scenarios and prepare questions for your case.
Sensitivity check
The fastest way to validate whether your inputs are influencing the results in a reasonable way is to run small variations. Below are three practical sensitivity checks you can do in DocketMath without changing the overall scenario.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Check 1: Change children count (2 → 1 and 2 → 3)
Keep everything else fixed, and rerun:
- Scenario A: 1 child
- Scenario B: 2 children (baseline)
- Scenario C: 3 children
Expected behavior:
Child support should move up or down with the number of children. If your results don’t change meaningfully, double-check that the children count is being applied in the calculator settings.
Checklist:
Check 2: Change income gap (Payee income up or down)
Run two variants:
- Scenario A (lower gap): Payee monthly gross income $4,500
- Scenario B (higher gap): Payee monthly gross income $3,000
Keep:
- Payor monthly gross income: $7,500
- Children count: 2
- Alimony estimate enabled: Yes
Expected behavior:
As payee income increases, the modeled support typically decreases; when payee income decreases, it typically increases. This is the kind of input sensitivity you want to confirm.
Check 3: Timing window test using NRS § 11.190(3)(d) default (2 years)
Now keep income/children constant, and vary the modeled accrual date:
- Accrual date 1 (within window): 2024-12-01
- Accrual date 2 (near boundary): 2024-04-15
- Accrual date 3 (outside window): 2023-03-01
With:
- Calculation date: 2026-04-15
- General SOL default: 2 years under **NRS § 11.190(3)(d)
Expected behavior:
- Within ~2 years → SOL timing flag should indicate “within”
- Beyond 2 years → flag should indicate “outside”
Pitfall: Many people test SOL concepts using the filing date rather than the accrual date for unpaid amounts. In this worked example, the model uses an accrual date input specifically to demonstrate how the 2-year window changes.
Quick “what to log” table
Use this to document how outputs behave across runs:
| Run | Payor income | Payee income | Children | Modeled accrual date | SOL default flag | Key output to record |
|---|---|---|---|---|---|---|
| Baseline | 7,500 | 4,000 | 2 | 2024-12-01 | Within 2 years (default) | Total estimated monthly support |
| Child count test | 7,500 | 4,000 | 1 | 2024-12-01 | Within 2 years (default) | Child-support portion |
| Child count test | 7,500 | 4,000 | 3 | 2024-12-01 | Within 2 years (default) | Child-support portion |
| Income gap test | 7,500 | 4,500 | 2 | 2024-12-01 | Within 2 years (default) | Total estimated monthly support |
| Timing boundary test | 7,500 | 4,000 | 2 | 2023-03-01 | Outside 2 years (default) | SOL timing flag only |