How to run Alimony Child Support in DocketMath for South Dakota

Step-by-step

This guide walks you through running Alimony + Child Support using DocketMath for South Dakota (US-SD). You’ll enter jurisdiction-aware inputs, run the calculation, and interpret the outputs—without relying on guesswork.

1) Open the correct DocketMath tool

• Go to /tools/alimony-child-support
• Confirm the jurisdiction is set to **South Dakota (US-SD)

If you don’t see jurisdiction controls, look for a jurisdiction selector near the top of the calculator. DocketMath uses jurisdiction-aware logic so the math and time assumptions are aligned with SD rules.

2) Confirm how the “general” time rule applies (SOL context)

South Dakota’s general statute of limitations (SOL) period is 3 years, governed by SDCL 22-14-1.

• Use this as the default when you’re modeling timing concepts that depend on an SOL window.
• No claim-type-specific sub-rule was found for this topic in your jurisdiction data. That means 3 years should be treated as the general/default period, not a claim-specific override.

In DocketMath, this typically affects fields related to:

• when a claim is considered timely (if your workflow includes timing),
• how you interpret “lookback” periods,
• or how you document the time window for calculation inputs.

If the calculator view includes timing options, select the general 3-year SOL rather than trying to apply a different period without a specific SD citation tied to the claim type.

3) Enter child support inputs

In the alimony-child-support calculator, inputs are usually grouped into categories. Start with child support.

Common inputs you should expect to enter (wording may vary by screen):

• Number of children (or child count)
• Child age(s) (if requested)
• Parent income figures (often gross income)
• Any allowed deductions the tool models

As you add values, watch the output area for:

• the estimated child support amount,
• whether totals update automatically (often “per month”),
• and any intermediate line items (income allocation, adjustments).

How outputs change (practical intuition):

• Increasing the noncustodial parent’s income typically increases estimated child support.
• Adding additional children generally increases total support, and the incremental amount depends on the tool’s formula and the children’s ages.

4) Enter alimony inputs (spousal support)

Next, fill in alimony inputs. DocketMath typically requires items such as:

• the parties’ incomes (if not already captured in the child support section),
• duration of marriage,
• and any scenario factors the tool requires (the factor list depends on the calculator design).

If DocketMath asks for marriage length, be precise:

• enter a date-based duration (e.g., years and months) if the tool supports it,
• avoid rounding unless the tool instructs you to.

How outputs change (practical intuition):

• Longer marriage length and larger income disparity often increase the alimony estimate in these types of models.
• If DocketMath includes category/toggle options (e.g., different alimony scenario types), choose the option that best matches what you’re modeling in your workflow.

5) Review combined results in the summary panel

After entering both sets of facts, DocketMath should show a combined summary.

Look for:

• separate line items for child support and alimony,
• an overall monthly total (if included),
• and any “calculation notes” or “rule logic” assumptions.

A practical sanity-check:

• Adjust inputs and confirm the results move in a reasonable direction.
• Change child-related inputs and confirm they mostly affect the child support portion.
• Change marriage duration and confirm it mainly affects the alimony portion.

6) Use the timing/SOL note in your documentation workflow

Even if the main output is support amounts, timing assumptions can matter in your process.

Given the jurisdiction data you’re using here:

• Default SOL: 3 years
• Statute: SDCL 22-14-1

If DocketMath includes a “timing” or “lookback window” field, select the general 3-year SOL window and keep it consistent across runs.

7) Run scenarios and compare outputs

DocketMath is most useful when you iterate.

Try small edits and observe what changes:

• Change income by a small increment (e.g., ±$500/month) and watch the child support and/or alimony line items.
• Change marriage duration by a few months and watch the alimony output.
• Adjust child count (if your scenario includes it) and watch the child support output.

A simple comparison table can help you see which inputs drive results:

Common pitfalls

Avoid these issues—most are data-entry or assumption problems that distort the output.

• Assuming a claim-type-specific SOL rule without a citation

  • Your jurisdiction data says no claim-type-specific sub-rule was found.
  • Default to 3 years under SDCL 22-14-1 as the general/default period.

• Mixing annual and monthly income

  • If a field expects monthly income and you enter annual values (or vice versa), results can swing dramatically.
  • Follow the unit labels exactly as shown in DocketMath.

• Forgetting to update both parties’ income fields

  • Some calculators require both parties’ incomes even if one category seems “primary.”
  • If the alimony section is involved and you miss one party’s income, the spousal support estimate can be skewed.

• Rounding marriage duration too aggressively

  • If the tool supports granular durations, “7 years” vs “7 years 9 months” may affect the alimony output.
  • Enter the most precise duration your tool accepts.

• Expecting child-related edits to change alimony

  • In many designs, changing child inputs primarily affects child support, not alimony.
  • If alimony changes after you modify child count, double-check you edited the correct field(s) in the correct section.

Try it

You can run the calculation directly here:

• Primary CTA: /tools/alimony-child-support

When you run your first scenario, perform these three checks:

• Does child support respond to child-related inputs?
• Does alimony respond to marriage duration and income disparity?
• Are timing assumptions using 3 years (SDCL 22-14-1) only as a general/default SOL period (not a claim-specific override)?

Related reading

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