How to run Alimony Child Support in DocketMath for North Carolina

Step-by-step

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

This guide shows how to run Alimony + Child Support in DocketMath for North Carolina (US-NC) using jurisdiction-aware rules inside the calculator workflow. I’ll walk through the inputs you’ll enter, what DocketMath does with them, and what you should review before saving or sharing outputs.

1) Start the correct DocketMath tool

1. Open DocketMath’s calculator here: /tools/alimony-child-support
2. Confirm the jurisdiction is set to North Carolina (US-NC).

   • If the interface offers a jurisdiction selector, choose US-NC so the calculator uses the correct NC rule set.

2) Enter case basics used by the calculator

In most DocketMath “Alimony + Child Support” flows, you’ll provide core facts that affect both support types:

• Filing context / scenario setup (for example, whether you’re modeling ongoing support vs. a request in a given stage)
• Number of children and how that maps to the support order you’re modeling
• Income inputs for each parent/party (commonly):

  • gross income,
  • income frequency (weekly/monthly),
  • and any adjustments the tool supports

How to avoid errors here: if DocketMath asks for multiple income fields (for example, base income plus additional regular amounts), enter them consistently. If you enter monthly income, make sure all income fields you enter are also monthly (and same for weekly).

3) Add child-related inputs

For child support, DocketMath generally needs inputs such as:

• Parent obligations tied to the children (e.g., how many children are being supported)
• Health insurance / childcare inputs (if the workflow collects them)
• Shared custody / time split (if included in the workflow)

As you change these inputs, watch for two categories of output changes:

• the child support amount (the tool may display weekly or monthly, depending on its settings),
• income-based adjustments (often shown as intermediate calculation components in the tool’s breakdown)

4) Add alimony inputs (spousal support)

For alimony, enter the inputs the calculator requests. Depending on how DocketMath is configured, this can include:

• Spousal income inputs (and any other spousal financial assumptions the tool requests)
• Marriage duration fields (for example, duration-like fields if the workflow collects them)
• Any alimony modifiers the calculator supports (e.g., if the interface provides a way to reflect disability-related income treatment—only use what you can support with accurate information)

Practical approach: because DocketMath’s inputs can drive different calculation branches, change one group of inputs at a time (income first, then duration, then modifiers) and review how the alimony output updates after each change.

5) Review jurisdiction-aware timing assumptions (North Carolina)

North Carolina includes a general 3-year statute of limitations (SOL) period referenced as “General SOL Period: 3 years” for the jurisdiction context used in this workflow.

Important clarification for tool users: the provided jurisdiction materials do not identify a claim-type-specific sub-rule. That means:

• Use 3 years as the default general SOL period, not as a specialized limitation tailored to every alimony/child support claim type.

Also, the jurisdiction materials reference the SAFE Child Act. For calculator usage, this means the workflow may include child-protection–related framing or optional flags that could affect how certain considerations are incorporated. Only turn on such options if they accurately match what you’re modeling.

6) Generate and validate outputs inside the tool

After you complete the inputs, run the calculation. Then validate outputs using this checklist:

• higher income for a payer generally increases support,
• more parenting time may change child support outcomes,
• alimony outcomes generally move with spousal income and duration-like inputs when provided

7) Use DocketMath results consistently

Once you generate results:

• Save screenshots or export outputs if the interface supports it.
• If you’ll run multiple scenarios (for example, changing a custody time split), note exactly which inputs you changed so you can compare results reliably.
• Prefer small, controlled updates—this makes it easier to identify why outputs shift.

Common pitfalls

Most errors in Alimony + Child Support modeling come from input mismatch and assumption drift. Here are the most common issues when using DocketMath for US-NC:

1. Mixing income units

   • Example: one party’s income entered monthly while the other is weekly.
   • Fix: ensure all income values use the same cadence the calculator expects.

2. Leaving optional child-related items blank

   • If DocketMath prompts for childcare or health insurance, omitting them may produce results that don’t reflect your scenario.
   • Fix: only add these modifiers if you have reasonable support for the values you enter.

3. Enabling safety-related options without matching facts

   • The workflow references North Carolina’s SAFE Child Act. If the tool includes a protective circumstances option, don’t enable it unless it truly applies to the scenario you’re modeling.
   • Fix: confirm what each option/flag represents in the UI.

4. Treating the default SOL as claim-specific

   • The jurisdiction context provided for this workflow states General SOL Period: 3 years and clarifies that no claim-type-specific sub-rule was found.
   • Warning: assuming 3 years automatically applies in every specialized way to every distinct claim type can be misleading. In this workflow, 3 years is the general/default SOL period.

5. Changing multiple variables at once

   • If you adjust custody time, incomes, and childcare in the same run, it’s harder to pinpoint why the output changed.
   • Fix: adjust one variable at a time and re-run.

Try it

Ready to run a North Carolina scenario in DocketMath?

1. Open: /tools/alimony-child-support
2. Set jurisdiction to US-NC
3. Enter:

   • party incomes (consistent time units),
   • number of children,
   • shared time and childcare/health insurance (if applicable),
   • alimony inputs (including duration-like fields if prompted)
4. Click calculate and review:

   • the alimony component
   • the child support component
   • any intermediate factors shown by the tool

To practice without getting stuck:

• Run Scenario A using your best estimates.
• Then run Scenario B changing only one input (for example, the shared custody time split).
• Compare outputs and confirm the direction of change matches your expectations.

If results look unusual, re-check input unit consistency first—most “wrong-looking” outputs trace back to that before anything else.

Related reading

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