How to run Alimony Child Support in DocketMath for North Dakota

Step-by-step

This guide walks you through running Alimony + Child Support in DocketMath for North Dakota (US-ND) using the built-in, jurisdiction-aware calculator: alimony-child-support. It’s written to help you understand what to enter and what changes in the results—without providing legal advice.

1) Open the correct tool

1. Go to the primary calculator page: **/tools/alimony-child-support
2. Confirm you’re using North Dakota (US-ND) jurisdiction controls. If the tool lets you choose a state, select US-ND (the tool should default appropriately, but it’s worth double-checking).

2) Identify the “support timeline” inputs

Before entering numbers, decide what period you want the estimate to cover (for example, “current proposed monthly support” vs. “support through the year X”). DocketMath typically uses these inputs to model monthly payment outputs.

Common fields you’ll see include:

• Parent roles (who pays / who receives)
• Number of children
• Dates relevant to support (if the form includes them)
• Whether support is continuing until a child is no longer eligible

If your case has multiple kids with different birthdays or eligibility dates, you’ll usually get the cleanest results by running:

• one pass with the “current” eligible set, then
• a second pass for future eligibility changes (if the tool supports it).

3) Enter child support variables (inputs that affect monthly child support)

In DocketMath, the child support portion is generally the part that moves most with family and income inputs. Enter each item carefully and use whole numbers where the interface requests them.

Typical inputs include:

• Gross monthly income for each parent
• Any shared custody flag (if present)
• Health insurance / childcare expenses (if the calculator includes them)
• Number of overnight days or custody schedule details (only if prompted)

How outputs change as you adjust inputs

• If the paying parent’s gross monthly income increases, the child support estimate generally increases.
• If the receiving parent’s income increases, results may change because the calculation framework considers both parties’ resources.
• Adding or removing allowable work-related childcare expenses typically increases or decreases the child support portion.
• Shared custody settings can materially change the final monthly amount depending on how the tool allocates parenting time.

4) Enter alimony variables (inputs that affect monthly alimony)

North Dakota alimony calculations are sensitive to the facts you provide—especially the length of marriage and the income/cash-flow profile of each spouse. In DocketMath, look for fields tied to:

• Length of marriage
• Each spouse’s gross monthly income
• Whether you’re modeling spousal support (the tool name suggests it covers both alimony and child support, but the calculator will still ask you to confirm the alimony portion)
• Potential adjustments (for example, health insurance costs or other categories—only if the tool includes them)

How outputs change as you adjust inputs

• A longer marriage duration can increase the weight of alimony compared to a shorter marriage.
• If the paying spouse’s income is reduced (or the receiving spouse’s income is higher), alimony estimates may decrease.
• Changes to documented monthly expenses that the tool treats as relevant may shift alimony and overall combined support.

5) Confirm special flags that affect results

North Dakota cases often turn on practical details. DocketMath may include toggles such as:

• Shared parenting time
• Additional dependents
• Any extraordinary childcare/medical inputs
• Whether either party has health insurance available and associated costs

Checklist for this step:

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

When you run the calculator, DocketMath should show:

• Child support estimate (monthly)
• Alimony estimate (monthly)
• Combined monthly total
• Possibly supporting figures such as inputs used in the calculation

Use the breakdown to do quick reasonableness checks:

• If child support changes but alimony does not when you tweak childcare costs, that’s a sign the childcare inputs are being applied only to the child portion.
• If alimony changes when you adjust marriage length, that’s consistent with alimony being sensitive to relationship duration.

7) Run scenarios to understand “what moves the number”

A single result rarely tells the full story. Try at least two scenarios:

• Scenario A (baseline): your best estimate of monthly income and current custody schedule
• Scenario B (sensitivity): adjust one high-impact variable (commonly the paying parent’s income, custody time, or childcare/insurance costs)

If you see large shifts from small input changes, it may indicate you’re near a threshold the calculator uses. Capturing those ranges can help you understand uncertainty.

8) Export and capture your work

If DocketMath supports exporting or saving results, do it before changing inputs again. Keeping a record helps you later:

• compare baseline vs. alternative custody schedule,
• update income for a new job month, or
• model a future child eligibility change.

Common pitfalls

These are the mistakes that most often distort alimony/child support estimates in DocketMath runs for North Dakota:

1. Using mismatched income periods

   • Example: entering one parent’s income as “current monthly” while entering the other as “annual average / yearly divided monthly.”
   • Fix: keep income definitions consistent across both parents for the same months you’re modeling.

2. Forgetting to reflect custody time accurately

   • If the tool asks for shared parenting time inputs, approximate numbers can still be useful—but accuracy matters.
   • Fix: use the best known schedule; run a second scenario if the schedule is in flux.

3. Leaving childcare/health insurance fields blank

   • Many calculators treat these categories as additive where appropriate.
   • Fix: enter documented monthly amounts; if you’re unsure, run one scenario with $0 and one with a conservative estimate.

4. Assuming “more income always means more support”

   • For combined estimates, results can shift in non-intuitive ways because both parties’ financial profiles may be considered.
   • Fix: change one variable at a time and observe which output lines move.

5. Overreliance on the combined total

   • The combined number is useful, but the breakdown is what tells you why it changed.
   • Fix: always review child support vs. alimony components separately.

6. Skipping multiple child eligibility runs

   • If children reach eligibility at different times, a single “current” run may not model future transitions.
   • Fix: run separate scenarios when eligibility dates differ.

Try it

Ready to run your first North Dakota estimate in DocketMath?

1. Open the calculator here: **/tools/alimony-child-support
2. Select US-ND jurisdiction if prompted.
3. Enter:

   • number of children,
   • parenting time (if applicable),
   • each parent’s gross monthly income,
   • any childcare/health insurance amounts the tool requests,
   • marriage length and other alimony-related fields.
4. Click Calculate, then review:

   • child support output line,
   • alimony output line,
   • combined monthly total.

For quick iteration, use this sequence:

• Run baseline
• Change only one variable (income, parenting time, or childcare)
• Run again
• Compare the breakdown totals

Related reading

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