Worked example: Alimony Child Support in South Dakota

Example inputs

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

This worked example shows how DocketMath applies a jurisdiction-aware workflow for alimony and child support in South Dakota (US‑SD), using the jurisdiction data you provided: a general 3-year statute of limitations (SOL).

Parties and facts (example scenario)

We’ll use a simple monthly-income scenario to keep the math readable:

• Payor (obligor) monthly gross income: $6,000
• Recipient (obligee) monthly gross income: $3,500
• Children: 2
• Custody / parenting arrangement assumption for illustration: 50/50 time (used only to illustrate input structure)
• Requested monthly alimony (entered as a hypothesis): $400
• Requested effective child support basis: calculated by the tool from the income inputs and child count

Timing assumptions (how to think about the “how long can you sue” piece)

Your brief asks to use South Dakota statute citations from the jurisdiction data provided. Here is what the jurisdiction data says:

• General SOL period: 3 years
• General statute: SDCL 22-14-1

Important limitation: The brief notes: “No claim-type-specific sub-rule was found.”
That means this example uses the general/default 3-year SOL from SDCL 22-14-1 rather than switching to a special limitation period for a particular type of claim. In other words, the SOL “guardrail” stays the general 3-year window for this worked example.

Jurisdiction inputs used by DocketMath (US‑SD)

DocketMath treats “jurisdiction-aware” rules as guardrails for what timing/parameter logic it applies in the workflow. For this scenario, the jurisdiction inputs are:

• South Dakota SOL (general/default): 3 years
• Statute: SDCL 22-14-1

Example run

Below is a single pass through DocketMath using the example inputs above. The goal is to show what you enter and how outputs tend to change when you adjust the inputs.

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.

1) Run the alimony + child support calculator

Open the tool here (primary CTA):

• /tools/alimony-child-support

Then enter:

• Payor monthly gross income: $6,000
• Recipient monthly gross income: $3,500
• Number of children: 2
• Parenting-time assumption: 50/50 (for illustration)
• Alimony hypothesis input: $400

2) What DocketMath outputs (illustrative structure)

DocketMath typically presents results in categories so you can separate “alimony” from “child support” and also see combined totals. For this example, you can think of outputs in this structure:

Because the brief only provides the general SOL rule (not a source for a specific formula to “recreate” the support amount), the amount outputs should be treated as the tool’s computed results from the calculator logic, not something we manually derive here.

3) Timing piece: how the 3-year SOL shows up as a workflow constraint

In a jurisdiction-aware workflow, the SOL generally acts as a procedural/timing context—it doesn’t necessarily change the monthly support arithmetic itself, but it can affect how and when support-related actions should be brought or enforced.

For this example, DocketMath’s timing guardrail uses the general/default limitation period you provided:

• 3-year SOL
• SDCL 22-14-1

And because the brief explicitly says no claim-type-specific sub-rule was found, DocketMath does not replace the SOL window with a different specialized limitation period for a particular claim type in this example.

Sensitivity check

Support calculations are input-sensitive. This section shows which variables are usually worth stress-testing in South Dakota runs using DocketMath, and what direction of change you should expect.

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 variables to test

Try varying these core inputs:

• Payor income changes (e.g., overtime, bonus, job change)
• Recipient income changes
• Number of children (e.g., 1 vs 2 vs 3+)
• Parenting time assumption (even if you keep it simple)
• Alimony hypothesis (use it for “what if” scenarios)

Three quick “what-if” mini-runs

Below are practical tweaks to the original example scenario. Rerun DocketMath for each change rather than extrapolating.

A) Reduce payor income by $500/month

• Payor gross income: $6,000 → $5,500
• Recipient: $3,500
• Children: 2
• Parenting-time assumption: 50/50
• Alimony hypothesis: $400

Expected direction: Child support generally decreases when the payor’s income base decreases. Alimony remains at $400 only because this example holds the alimony hypothesis constant.

B) Increase recipient income by $300/month

• Payor: $6,000
• Recipient: $3,500 → $3,800
• Children: 2
• Parenting-time assumption: 50/50
• Alimony hypothesis: $400

Expected direction: Child support often decreases when the recipient’s income rises (because overall support capacity shifts). Alimony stays $400 in this illustration for the same “held constant” reason.

C) Change children from 2 to 3

• Payor: $6,000
• Recipient: $3,500
• Children: 2 → 3
• Parenting-time assumption: 50/50
• Alimony hypothesis: $400

Expected direction: Child support generally increases with more children. Again, use DocketMath to see the exact output because the relationship may not be perfectly linear.

SOL timing sensitivity (separate from monthly math)

Now treat timing as a separate dimension from monthly amounts:

• If you’re applying timing constraints using the general rule you provided, the “window” remains:

  • 3 years
  • SDCL 22-14-1
• The brief also notes no claim-type-specific sub-rule was found, so there’s no SOL window swapping in this example.

Pitfall to avoid: Don’t assume a “special” limitation period applies because the case is framed differently. With the information given here, this worked example uses the general 3-year period from SDCL 22-14-1.

Related reading

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