Why Alimony Child Support results differ in South Carolina

The top 5 reasons results differ

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

If you’re seeing different alimony/child support-style outcomes across calculators or spreadsheets while you’re in South Carolina (US-SC), the differences usually come from inputs and how a tool applies jurisdiction-aware timing rules—not “randomness.” DocketMath’s alimony-child-support tool is designed to apply South Carolina context, but small changes in case facts (or how you enter them) can move the numbers.

Here are the top 5 reasons you’ll get different results:

1. **Different treatment of time windows (SOL vs. ongoing obligations)

   • Some tools reference a dispute/claim timing window (for example, when obligations are being challenged or back-calculated).
   • For this brief, South Carolina’s general/default statute of limitations baseline is 3 years under GS 15-1.
   • Important: No “claim-type-specific” sub-rule was identified for this brief. So treat the 3-year period under GS 15-1 as the general reference point, not a guaranteed rule for every specific claim type.

2. **Unequal input values (income, bonuses, overtime, and benefits)

   • Even if two people think they have the same income, different calculators may treat earnings differently, such as:

     • overtime as regular income vs. excluded
     • annual bonuses as recurring vs. averaged
     • employer-provided benefits as countable income vs. ignored
   • DocketMath’s outputs will track the categories you enter and the format you use (for example, monthly vs. annual amounts).

3. Varying assumptions about time allocation for children

   • Child-related results can shift when parenting time is expressed differently, such as:

     • number of overnights
     • how custody/parenting time is entered (e.g., days per month vs. days per year)
   • Two scenarios that are “equally fair” in plain English can still produce different outputs if the tool needs a specific input structure.

4. Inconsistent handling of health insurance and childcare costs

   • Some models include these as add-ons; others assume they are already reflected elsewhere.
   • Small input changes can create big deltas—e.g., entering $0 vs. a real monthly amount for childcare, or deciding whether health insurance includes the child.

5. Different formatting of the timeline for support changes

   • If you compare results “before vs. after” a job change, custody change, or other event, you may be testing different effective periods.
   • DocketMath is sensitive to how you structure timeline-related inputs (such as effective dates and the sequence of periods), so “same facts” entered with different timeline structure can produce different outcomes.

For South Carolina timing context in this brief: the general statute of limitations period is 3 years under GS 15-1.

How to isolate the variable

Use a controlled approach so you can tell which change is driving the discrepancy.

1. Start with one baseline run in DocketMath

   • Open the alimony-child-support tool: /tools/alimony-child-support
   • Enter your best-known facts.
   • Capture exactly what you input (especially: income categories, parenting time format, childcare, health insurance, and timeline/effective dates).

2. Change only one variable per run Use this checklist style so you don’t accidentally mix causes:

3. Watch how the output changes When you adjust one variable, note the pattern:

   • If results move smoothly, it’s often income-driven
   • If results “jump,” it may be threshold or period-handling
   • If results only change after a date, it’s often timeline/effective-date structure

4. Lock the SOL/timing baseline explicitly for South Carolina

   • For this brief’s jurisdiction data, use GS 15-1 (3-year general/default period) as the reference.
   • Do not assume a special shorter/longer period for a specific claim type unless you have confirmed the exact statute for that claim type. Per this brief, no claim-type-specific sub-rule was found, so GS 15-1 is the stated baseline.

Gentle reminder: This is about modeling and comparing outputs, not guaranteeing legal results or enforceability.

Next steps

To make your comparison more reliable:

• Standardize units: ensure all amounts are consistently entered (e.g., monthly vs. annual) before re-running /tools/alimony-child-support.
• Normalize parenting time format: use one representation and keep it consistent across runs.
• Document the delta: after each single-variable change, record which input produced the largest outcome shift.
• Match assumptions when comparing tools: if another calculator treats bonuses or benefits differently, align those assumptions first.

If you want a practical starting point for a jurisdiction-aware baseline run, use:

• /tools/alimony-child-support

Related reading

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