How to run Alimony Child Support in DocketMath for South Carolina

6 min read

Published April 15, 2026 • By DocketMath Team

Step-by-step

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

This guide walks you through running Alimony + Child Support in DocketMath for South Carolina (US-SC) using jurisdiction-aware rules. It focuses on setting up the calculation correctly and interpreting results—not on giving legal advice.

Note: Your jurisdiction data specifies a general/default statute of limitations (SOL) of 3 years under GS 15-1. It also states that no claim-type-specific sub-rule was found, so you should treat the 3-year SOL as the general default, not a special carve-out.

1) Open the correct DocketMath calculator

  1. Go to the primary calculator: /tools/alimony-child-support
  2. Confirm the jurisdiction is set to South Carolina (US-SC).
    • If you see a jurisdiction selector, choose US-SC before entering numbers.

2) Enter the basic case inputs

DocketMath typically needs these categories of information (the exact labels may vary slightly):

  • Parties and payment responsibility
    • Who is the payor (the person who pays)?
    • Who is the payee (the person who receives)?
  • Child details
    • Number of children covered
    • Ages (if prompted)
  • Income inputs
    • Payor income (and how it’s described—gross, net, or adjusted—depending on the tool’s inputs)
    • Payee income
    • Any additional income fields the calculator asks for
  • Support profile
    • Any toggle for calculating child support alone vs. alimony + child support (if available)

If you’re unsure what each field expects, use the tool’s inline help text next to each input. The goal is to match the calculator’s expected format so the output changes are meaningful.

3) Add alimony-related inputs (if the tool supports both)

For the alimony portion, you’ll generally see inputs that influence the result, such as:

  • Alimony type selection (if provided)
  • Duration indicators (sometimes based on marriage length or other factors)
  • Health/earning capacity notes (only if DocketMath provides structured fields for these)
  • Any requested caps, deviations, or assumptions the calculator models

When entering these values:

  • Keep your units consistent (annual vs. monthly).
  • Double-check whether the calculator expects income pre-tax or post-tax.

4) Add child support inputs (and verify counts/ages)

Child support outcomes are very sensitive to the child profile inputs:

  • Confirm the number of children
  • Confirm age fields are accurate (especially if the tool uses age bands)

Then review any “income used” fields:

  • If DocketMath uses an adjusted income approach, make sure you’re entering the correct income field(s) rather than duplicating values across multiple boxes.

5) Review assumptions and jurisdiction-aware behavior

Before you run the calculation:

  • Scan for any jurisdiction-specific assumptions DocketMath applies to US-SC.
  • If DocketMath provides a “model notes” panel, read it—those notes often explain which inputs drive changes in output.

Warning: A common failure mode is entering the right numbers in the wrong format (for example, entering monthly income where the field expects annual income). This can swing results dramatically while still looking “plausible.”

6) Run the calculation and interpret outputs

After you submit:

  • Identify each output section:
    • Child support result
    • Alimony result
    • Total combined amount (if provided)
  • Confirm the time basis (e.g., monthly vs. weekly vs. annual), because that determines how to interpret the totals.

To build confidence, test sensitivity:

  • Change one variable at a time (for example, payor income or number of children) and observe how the corresponding output changes.
  • This is the fastest way to learn which fields DocketMath weighs most heavily.

7) Use this results checklist for accuracy

Before you rely on the number for planning or comparisons, verify:

8) Understand the SOL timing context (general/default)

If you’re using the calculator in the context of deadlines for pursuing or responding to claims, incorporate your provided SOL context:

Important clarity based on your data:

  • Your jurisdiction data references GS 15-1 as the general/default SOL and does not identify a claim-type-specific exception.
  • Because this content is about South Carolina (US-SC) calculations in DocketMath, use this SOL citation strictly as the SOL context from your provided data, and verify state-specific SOL authority for any real deadline.

Common pitfalls

Use this section as a debugging list—if the output looks “off,” check these items first.

  1. Wrong jurisdiction selection

    • If DocketMath is set to another jurisdiction, the result can change even when inputs are identical.
  2. Income frequency mismatch

    • Entering annual income into a field expecting monthly (or vice versa) is one of the fastest ways to get incorrect totals.
  3. Duplicating income

    • Some tools ask for multiple related income components (for example, base income plus adjustments). Entering the same earnings in both can inflate the calculation.
  4. Child count/age errors

    • If the calculator uses age bands, incorrect ages can alter the child support component.
  5. Forgetting to enable alimony inputs

    • If DocketMath provides switches like “include alimony” or “include both,” confirm they match what you intend to calculate.
  6. Assuming results equal legal entitlement

    • DocketMath outputs are best treated as model calculations based on the inputs provided. They’re useful for scenario planning and comparison, but not a substitute for legal determinations.
  7. SOL confusion during planning

    • A calculator result might be internally consistent, but the timing or deadline you attach to it may rely on different rules than you assume.

Quick “symptom → likely cause” guide:

  • Total looks far too high → wrong income frequency; duplicated income; wrong child count
  • Child support doesn’t change when you edit ages → ages may not affect that tool version/model, or fields weren’t updated
  • Alimony result stays blank → alimony toggles not enabled or required alimony fields missing
  • Results change drastically between runs → one variable changed unintentionally or jurisdiction reset

Try it

Use this short plan to validate the workflow:

  1. Open /tools/alimony-child-support
  2. Ensure South Carolina (US-SC) is selected.
  3. Enter a baseline set of inputs:
    • One payor income number
    • One payee income number
    • 2 children with reasonable ages
  4. Run the calculation.
  5. Run two controlled variations (change one factor per run):
    • Variation A: increase payor income by a fixed amount (use the same time basis the tool expects)
    • Variation B: change the number of children (for example, from 2 to 1), keeping ages consistent where possible

Compare output differences:

  • If child support changes with Variation B, the tool is responding to the child profile.
  • If the total changes with Variation A, the tool is responding to income.

Note: When you test, change only one factor per run to avoid misattributing what caused the output change.

Finally, keep the SOL context in mind for planning timelines:

  • Your provided data states a general/default SOL of 3 years under GS 15-1, with no claim-type-specific sub-rule identified—so treat it as general context, not a guaranteed match to every possible claim type or situation.

Related reading