Why Alimony Child Support results differ in Delaware
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
If you’re seeing different alimony and child support outcomes in Delaware (US-DE) from DocketMath, it’s usually not “math mistakes”—it’s jurisdiction-aware rules interacting with your inputs. Also, Delaware has a general default statute of limitations (SOL) concept in certain enforcement contexts, which can change what older obligations appear in the results.
Important SOL note (Delaware): No claim-type-specific sub-rule was found. So the 2-year period below is treated as the general/default period.
Here are the top 5 drivers that most commonly change results:
The debt-enforcement timeline (SOL) changes what gets considered
- Delaware’s general SOL is 2 years, described in Title 11, §205(b)(3).
- If your payment history spans dates farther back than the relevant window, the “catch-up” picture can shrink—changing net totals and the totals you see reflected in the calculator output.
Different treatment of income components
- DocketMath’s Delaware-aware logic can treat categories differently (for example, more stable wage income vs. other income types).
- Even small changes in how you enter or categorize income (or whether certain periodic items are included) can move both support and alimony outputs.
Parent/household details alter multipliers
- The number of children (and sometimes how residential time is entered) changes calculation inputs that feed the formulas.
- So even if incomes are unchanged, “household facts” that differ between runs can cause meaningful output differences.
Deductions and credits shift computed available income
- Any input affecting “net” income available for support (like certain deductions/credits you enter) can shift results.
- Because formulas often apply multipliers after income adjustments, effects can be non-linear—meaning a seemingly modest change can create a larger change in the final totals.
Time sensitivity: results vary by “as-of” dates and the analysis window
- DocketMath behavior can depend on the time window you’re analyzing (including how far back the model considers).
- Delaware’s 2-year general SOL concept under Title 11, §205(b)(3) can make date-related differences more impactful than expected, especially when comparing scenarios with different timelines.
Pitfall: If you compare two runs but change more than one field (or leave date fields inconsistent), the resulting difference may be driven by the SOL/date-window effect rather than the income or household change you’re trying to test.
For hands-on testing, start at the Alimony/Child Support calculator.
How to isolate the variable
To identify why Delaware results differ, isolate changes using a controlled comparison. Use DocketMath to run a baseline and then change one variable at a time.
- Freeze the jurisdiction and tool settings so both runs use the same rule set.
- Compare one input at a time (dates, rates, amounts) and re-run after each change.
- Review the breakdown to see which segment or assumption drives the difference.
Step-by-step isolation checklist
- Ensure the “as-of”/timeline inputs match between runs.
- Use your most complete dataset: income, children, deductions/credits, and any relevant timing facts.
- Income (wages vs. other income)
- Deductions/credits
- Child-related inputs (number of children; any entered custody/residential assumptions)
- Timeline dates (only after income/child factors are stable)
- Track how each run changes:
- estimated child support
- estimated alimony
- any combined totals you’re comparing
Delaware-specific sanity check (SOL window)
Because Delaware’s general default SOL is 2 years under Title 11, §205(b)(3) (and no claim-type-specific sub-rule was found), verify whether your scenarios include obligations older than the default window. If they do, differences between runs may show up as:
- outputs appearing to “drop” or stop accumulating
- reduced catch-up totals
- larger-than-expected swings when the time window changes
| What you change | What to look for in output | Likely driver |
|---|---|---|
| As-of date | Support totals may “drop” or stop accumulating | SOL/date-window effect (default 2 years) |
| Income amount | Both child support and alimony can move | Income component treatment |
| Deductions/credits | Lower/high available income | Net-income adjustment |
| Child-related inputs | Child support changes first; alimony may follow | Multipliers and household factors |
| Residential/time inputs | Child support recalibrates | Assumption-driven formula inputs |
Gentle disclaimer: DocketMath estimates are meant to help you understand how inputs affect results; they don’t replace legal advice or review of the actual decree and procedural posture of your case.
Next steps
- Run 2–4 controlled DocketMath scenarios
- Keep everything identical except one field per run.
- Document the exact input differences
- Save an input summary (even a screenshot) so you can map each delta to a specific change.
- Re-check date alignment against Delaware’s default 2-year SOL concept
- Reference: Title 11, §205(b)(3) (Delaware general SOL 2 years).
- Focus on the biggest delta first
- Start with the input change that produces the largest output shift (often income categorization, deductions/credits, or timeline alignment).
