Worked example: Alimony Child Support in Nebraska

Example inputs

This worked example shows how DocketMath can be used to model alimony and child support in Nebraska using jurisdiction-aware defaults. It’s a practical walkthrough of what to enter and how the output changes—not legal advice.

Here is a simple illustration for Nebraska. These values are for demonstration only and should be replaced with your actual inputs.

• Principal or amount: $100,000
• Rate or cap: 10%
• Start date: 2025-01-15
• End/as-of date: 2025-09-30

Scenario overview (Nebraska, US-NE)

Assume a Nebraska case with:

• One child (age 8)
• The paying parent pays support monthly
• The case includes both child support and spousal support (alimony)

DocketMath inputs you would use

Open the calculator here: /tools/alimony-child-support.

Then enter values like the following (example numbers are chosen for clarity):

Jurisdiction/time reference used in this example

Nebraska includes a general statute of limitations (SOL) period. For this walkthrough, we use the general/default SOL period because no claim-type-specific sub-rule was found.

• General SOL period: 0.5 years
• General statute cited in this worked example: Neb. Rev. Stat. § 13-919
• Source: https://law.justia.com/codes/nebraska/chapter-13/statute-13-919/

Clear note: This example uses Nebraska’s general SOL period of 0.5 years under Neb. Rev. Stat. § 13-919 because a claim-type-specific sub-rule was not identified for this scenario. If your matter involves a specific claim type with a different limitations rule, the effective time horizon in a tool output may not match your real case.

What to do before running

Before you click Calculate, confirm:

• Your income inputs are monthly (or match the calculator’s expected cadence)
• Child age and child count are correct
• Any optional fields (insurance, childcare) reflect your best available figures
• Alimony type/duration match what you want the tool to model (e.g., monthly payments and 4-year totals)

Example run

Using the example inputs above, run the DocketMath: alimony-child-support calculator for US-NE.

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.

Example output (illustrative)

Because tool outputs depend on the specific formula implementation and the entered numbers, your exact dollar results may differ. A typical structure you can expect to see includes:

• Child support (monthly): a computed amount based on income and child data
• Alimony/spousal support (monthly): a computed amount based on income disparity and duration inputs
• Total support (monthly): child support + alimony
• Total support (over the selected duration): total monthly × duration
• Potentially: adjustments for insurance/childcare and any credits/offsets if the tool includes them

Here’s an illustrative “shape” of results to help you interpret what you see after the run:

How jurisdiction-aware rules show up in this walkthrough

In addition to the payment math, DocketMath uses jurisdiction-aware parameters relevant to Nebraska—including the general/default SOL period reference used for this walkthrough:

• If the tool incorporates time-window logic (for example, how long an amount is assumed to be relevant for certain modeling), it will anchor to the general/default Nebraska SOL period:

  • 0.5 years under Neb. Rev. Stat. § 13-919

Because this is a worked example focused on tool usage, treat the SOL piece as a model parameter—not a substitute for claim-specific legal analysis.

Interpreting the numbers safely (without legal advice)

When you review the output:

• If child support is large relative to alimony, it usually indicates that the income difference and child-related factors are driving most of the total in this model.
• If alimony is large or highly sensitive to your duration setting, it suggests the calculator is using duration to frame/scaling the alimony output.

If something looks extreme:

• Recheck the child age (small age changes can matter in age-based structures)
• Confirm whether your income entries are gross monthly
• Check insurance/childcare fields—mis-entries can shift totals materially

Sensitivity check

A worked example is more useful when you test “what if” scenarios. Here are three sensitivity checks you can run in DocketMath to see how outputs respond.

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.

Sensitivity check A: Increase the paying parent income by 10%

Change only:

• Paying parent gross monthly income from $5,500 → $6,050 (+$550)

Expected direction:

• Child support generally increases because the paying parent’s income is higher.
• Alimony often increases as well if the tool ties spousal support to income disparity and the parties’ relative ability to pay.

Quick checklist:

• ✅ Keep child count and child age unchanged
• ✅ Keep duration unchanged (4 years)
• ✅ Keep insurance/childcare unchanged

Sensitivity check B: Remove the child inputs (single child → none)

If your calculator allows a “no child” scenario or you run a separate scenario:

• Child count: 1 → 0
• Keep incomes unchanged

Expected direction:

• Child support should drop to $0 (or be omitted).
• Total support should now reflect only alimony (if alimony is still modeled in the tool).

Purpose:

• This isolates how much of your total payment comes from child support vs. alimony.

Sensitivity check C: Change the alimony duration (4 years → 2 years)

Change only:

• Alimony duration: 4 years → 2 years

Expected direction:

• Your monthly alimony line item may remain similar (depending on how the tool models duration).
• Your total over duration will likely decrease (roughly in proportion to time):

  • Example: total over 4 years ≈ 2 × total over 2 years

What to look for:

• If DocketMath reports both monthly and “total over duration,” confirm which line item is being scaled by your duration input.

How to record your results (so you can compare runs)

Create a mini comparison table:

Checkboxes to help ensure clean comparisons:

Where the SOL reference fits in this sensitivity check

Because this walkthrough uses Nebraska’s general/default SOL period (0.5 years) under Neb. Rev. Stat. § 13-919, most of what you see in sensitivity tests should track your payment inputs (income, child data, duration). If the calculator includes time-window logic, you may notice differences in any fields that mention time relevance—but the SOL should not “override” the basic drivers like income disparity and child inputs.

Related reading

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