Common Alimony Child Support mistakes in North Dakota
6 min read
Published April 15, 2026 • By DocketMath Team
The top mistakes
Run this scenario in DocketMath using the Alimony Child Support calculator.
North Dakota alimony and child support orders often turn on details like dates, income math, guideline inputs, and how changes are documented over time. DocketMath can help you run consistent scenarios in US-ND, but certain mistakes show up again and again in real cases.
Below are the most common pitfalls—along with how they typically distort the outcome. (This is general information, not legal advice.)
1) Using the wrong income base (or skipping key income)
A frequent error is building support calculations on incomplete or inconsistent income—especially when pay varies, includes overtime, bonuses, commissions, or non-wage benefits.
What goes wrong
- Omitting recurring bonuses or commissions
- Using take-home pay when the calculator expects gross (or using a different “average” than your evidence supports)
- Ignoring self-employment considerations or business-related adjustments
How it impacts results in DocketMath
- Small changes to income can shift both child support and alimony inputs.
- The output may look “clean,” but it can be wrong if the income you enter doesn’t match the income base the court expects in practice.
Pitfall: Switching between “last paycheck” and “annualized” income midstream can create two different income baselines—then the results differ, even though the math is stable.
2) Treating child support and alimony as interchangeable
Another common error is assuming that reducing one automatically reduces the other. In North Dakota, these are separate obligations with different purposes and often different input logic.
What goes wrong
- Estimating alimony using a child support number that later changes
- Assuming a temporary child support amount will stay the same without a modification review when facts change
How it impacts results in DocketMath
- You might run a blended scenario that seems internally consistent at first.
- But once child support assumptions update (income, parenting time, or healthcare inputs), alimony may no longer align with the revised child support reality.
3) Not reflecting parenting time accurately (custody/overnights)
Parenting time directly affects the child support computation. A mismatch between the real schedule and what’s entered into DocketMath can skew the monthly amount.
What goes wrong
- Entering “50/50” when the actual schedule is closer to a different number of overnights (or vice versa)
- Using an outdated schedule instead of the current one
- Forgetting holidays and extended-time patterns
How it impacts results in DocketMath
- Even with steady income, parenting time changes can move the child support output meaningfully.
4) Failing to account for special expenses or medical-related costs
Support calculations often depend on whether certain costs are treated as included or handled separately—commonly healthcare and certain extraordinary or “special” expenses.
What goes wrong
- Including the same expense twice (once through an income/adjustment concept and again as a separate expense)
- Leaving out recurring medical premiums or predictable out-of-pocket costs
- Assuming everything paid during a similar period is “already covered,” without matching how the calculator expects inputs
How it impacts results in DocketMath
- A scenario can produce a monthly figure that’s consistent with entered fields but still doesn’t reflect the real-world monthly obligation.
5) Forgetting the calculations are time-sensitive
Support math isn’t “set and forget.” Pay changes, insurance costs change, and schedules evolve.
What goes wrong
- Using old income (for example, 2023) for a 2025 estimate without updating inputs
- Not updating retirement/disability/wage-related changes
- Ignoring step changes like job transitions or a new compensation structure
How it impacts results in DocketMath
- Your estimate can be anchored to outdated figures, which makes it harder to justify the numbers later with updated evidence.
6) Relying on one scenario without checking alternatives
Many people run one set of inputs and stop. Courts and negotiations usually require evidence, comparisons, and reasonableness across likely fact patterns.
What goes wrong
- Running only a single “best case” or “worst case”
- Not testing how sensitive the result is to income averaging, overtime, or parenting time
How it impacts results in DocketMath
- DocketMath can compare scenarios (for example, different income averages).
- Without that comparison, you may miss the input range that’s more stable—or more defensible.
7) Copying order language without matching it to calculator inputs
A practical administrative error: the order uses one definition (for example, “monthly income”), but the calculator may require a different structure (for example, gross vs. net, or a specific expense layout). Parenting schedule descriptions can also differ.
What goes wrong
- Misreading what the order includes or excludes
- Translating order terms into calculator fields incorrectly
- Entering a schedule that doesn’t match the order’s parenting-time definition
How it impacts results in DocketMath
- The output will only align with the order if your inputs match the order’s definitions closely enough.
How to avoid them
You can reduce errors quickly by tightening your input process and verifying how each input changes outputs. DocketMath works best when the entries are consistent and traceable.
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.
Step 1: Build an input checklist before running the calculator
Use this checklist each time you run /tools/alimony-child-support.
Step 2: Run 2–3 scenarios to expose sensitive inputs
Instead of one “final” number, compare:
In DocketMath, this helps you see whether the output is stable or fragile. If a relatively small income adjustment flips the outcome, that’s a sign you should focus on documenting that specific input.
Step 3: Validate parenting time with a simple schedule count
Before entering parenting time, do a quick audit:
Then enter the same structure into DocketMath to avoid the common “looks right, but isn’t” problem.
Step 4: Separate income inputs from expense inputs
A clean workflow helps prevent duplication errors.
If you’re unsure how a cost should be treated, compare two scenarios—one that includes it and one that does not.
Step 5: Keep a one-page explanation of your inputs
If you need to show your work later (in negotiations or case planning), a short input memo can help.
Include:
- Your income figures and the time periods they came from
- The parenting schedule definition you used
- A list of expenses added, with notes on whether each is recurring
This is a practical documentation step—not legal advice.
Step 6: Use the tool directly so inputs match outputs
Start with DocketMath here: /tools/alimony-child-support. As you enter values, watch how the output changes when you adjust:
- income amount or averaging approach
- parenting-time entry
- expense inputs
That feedback loop is the fastest way to catch a wrong assumption early.
Warning: If the number you’re relying on is based on last year’s income or an outdated schedule, your plan can be wrong even if the math in the calculator is working correctly. Update the inputs, then rerun DocketMath.