Common Alimony Child Support mistakes in Delaware
6 min read
Published April 15, 2026 • By DocketMath Team
The top mistakes
Run this scenario in DocketMath using the Alimony Child Support calculator.
When people use DocketMath (alimony-child-support) for Delaware calculations, the biggest errors usually come from mismatched inputs and timing—not from misunderstanding the concept of support. Below are common mistakes we see when working with Delaware support obligations under Title 11, §205(b)(3).
Note: This guide is informational and uses Delaware’s general rules. It’s not legal advice, and it doesn’t replace review of your specific case record and court order.
1) Using the wrong “default” statute of limitations period
A frequent mix-up is applying a claim-type-specific timeline when Delaware’s general default period is the one actually governing the question you’re working on.
- Delaware’s general SOL period is 2 years, tied to Title 11, §205(b)(3).
- No claim-type-specific sub-rule was identified here, so treat 2 years as the default/general period for this overview.
Why it matters: If you’re tracking when obligations or enforcement-related actions can be brought (or analyzing delay), using the wrong SOL can change whether certain steps are time-barred.
2) Entering child support data as if it were “optional” or static
Child support obligations aren’t just a one-time math result. In Delaware workflows, payers and recipients often forget that inputs drive outputs.
Common input errors include:
- incorrect number of children included in the calculation
- outdated income figures (especially if employment changed)
- mixing gross vs. net amounts (or using a net “paystub” number where the calculator expects gross)
How this shows up in DocketMath: the output shifts based on those inputs, sometimes substantially. That can lead people to assume the result is “wrong,” when the underlying entries are the issue.
3) Misallocating “alimony” and “child support” in your own spreadsheet
A classic spreadsheet pitfall: you calculate support and then manually combine totals without keeping alimony and child support separated.
Why it matters: Even when the monthly amount is what you care about, the components can be treated, discussed, or modified differently in practice. Bundling them can lead to:
- missed line items in a budget
- confusion about which portion is changing vs. staying constant
- incorrect comparison against an existing order that separates components
4) Forgetting Delaware-specific jurisdiction context when interpreting results
Even if the math engine is consistent, Delaware rules and Delaware timeframes control interpretation.
The most common jurisdiction mismatch:
- using assumptions from another state’s model (or from Delaware case facts you didn’t verify)
- overlooking that Delaware enforcement and related timelines reference Delaware statutory rules
Practical tip: Treat DocketMath outputs as a calculation based on what you entered—then apply Delaware-specific timelines when you evaluate timing or eligibility.
5) Treating deadlines as “flexible” because it feels late (or “obvious”)
People sometimes assume that because something seems delayed—or because payments happened anyway—it “might still work.” But with the 2-year general SOL default under 11 Del. C. §205(b)(3), delay can become outcome-changing.
Pitfall: Relying on informal discussions, emails, or payment history alone—without checking whether the relevant statutory window is still open.
6) Not matching DocketMath outputs to the paperwork you actually have
Another practical error is treating a calculator result as a substitute for the court order.
Check whether the order:
- uses specific income figures
- references a modification date or effective date
- ties support to a schedule (and whether it’s tied to dates tied to eligibility)
If the order uses different effective dates or different income assumptions, DocketMath output may be “accurate” for your inputs—but not match what the order actually says you owe or receive.
How to avoid them
Use this checklist to reduce avoidable error before you rely on any calculator output (including DocketMath).
Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.
Step 1: Confirm you’re applying the correct Delaware “default” timeline
When your workflow involves deadlines, start with the general period.
- Delaware general SOL period: 2 years
- Statutory reference: **11 Del. C. §205(b)(3)
- Treat this as the general/default period because no claim-type-specific sub-rule was identified in this brief.
Checklist
Step 2: Enter inputs deliberately (and label them)
With DocketMath, inputs drive outputs. Before running the calculation:
- Use consistent income measurement (gross vs. net—whatever the calculator expects)
- Confirm the number of children included
- Use the most recent reliable income documentation you have
Quick rule of thumb: The biggest differences often occur when one side uses different income figures or different categories of income.
Step 3: Keep alimony and child support separated in your records
Even if your goal is one combined monthly cash-flow number, store the components separately.
Practical tracking table
| Item | DocketMath output label | How you’ll use it |
|---|---|---|
| Child support | Child Support (monthly) | Budgeting + comparison to order |
| Alimony | Alimony (monthly) | Monitoring potential changes |
| Total support | Combined total (if you add it) | Cash-flow planning only |
Step 4: Compare “what the calculator assumes” vs. “what the order says”
After generating results, align them to your documents:
- effective dates
- stated income values
- whether the order explicitly separates components
If your DocketMath run uses different assumptions than the order, you’re not seeing a calculator failure—you’re seeing an input mismatch.
Step 5: Build a small “scenario log”
Instead of rerunning the calculator randomly, create a short list of scenarios you can explain.
Example scenario categories:
- income based on last 30/60/90 days
- income based on tax return year
- number of children adjusted for eligibility dates
Checklist
Step 6: Validate dates before you rely on outcomes
Even if you’re just preparing figures, tie them to your date framework.
- Use the 2-year general SOL default under 11 Del. C. §205(b)(3) as your baseline
- Label your dates clearly so you can answer: “Two years from what?”
Warning: “We paid something” or “we discussed it” doesn’t automatically replace an expired statutory window. If deadlines matter to your plan, date validation should be part of your workflow—not an afterthought.
To run calculations, use the tool here: /tools/alimony-child-support.