How to calculate Alimony Child Support in Delaware

Quick takeaways

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

• Delaware support calculations follow court-established rules that depend on what you’re calculating (child support vs. alimony). DocketMath helps you structure inputs and compare scenarios, but it’s not a substitute for a judge’s final order.
• Delaware’s provided jurisdiction data points to a general/default 2-year statute of limitations (SOL) for many claims: 11 Del. C. § 205(b)(3). No claim-type-specific sub-rule was identified in the provided data, so treat this as the default/general reference, not a specialized timing rule for every support-related issue.
• If you change inputs like income, custody/parenting time, child count/ages, or timing assumptions, your outputs should change in transparent, testable ways—this is the practical advantage of using DocketMath.
• Before relying on any calculation, make sure the facts you enter match how Delaware orders are typically framed:

  • income definitions (gross vs. net, and consistency across both parties),
  • child-related inputs (as applicable), and
  • time framing (start date, term, and any retroactivity assumptions).

Inputs you need

To calculate alimony and/or child support in Delaware with DocketMath, gather your inputs first. The goal is to enter the same underlying facts across repeated scenarios so you can see how each change affects the output.

Use this intake checklist as your baseline for Alimony Child Support work in Delaware.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

Core financial inputs

• Payor and recipient identification
• Gross monthly income for each party (use the most recent stable amount you have)
• Additional income sources (e.g., overtime, bonuses, second job, commissions)

  • Enter them consistently for both sides where applicable.
• Deductions that affect “available income” (only if the selected DocketMath calculator flow asks for them)
• Health insurance costs for children and/or the parties (if included in your DocketMath version)

Support-relevant relationship inputs

Depending on whether you’re calculating child support, alimony, or both, you’ll typically need:

• Number of children covered
• Custody / parenting-time split (the input that drives the child-support portion)
• Childs’ ages (if the rules distinguish age brackets)
• Which support type(s) you’re modeling (child support vs. alimony)

Timing inputs

Support isn’t only “how much”—it’s also from when.

• Effective date (the scenario start date you’re treating as the beginning of the obligation)
• Duration / term (if your DocketMath flow supports it)
• Modification triggers (if you’re modeling scenarios that change later)

Delaware jurisdiction context (time limit reference)

When you’re doing a “how to calculate” walkthrough, it helps to know that Delaware has a general 2-year time limit for many claims under:

• 11 Del. C. § 205(b)(3) — General SOL Period: 2 years
  Source: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai

How the calculation works

DocketMath turns your inputs into a structured output using Delaware-aware, calculator-style steps. Because alimony and child support often follow different approaches, the workflow is typically modular—you may calculate them separately or together depending on what your tool version supports.

1. Normalize income for each party
   DocketMath uses the income numbers you enter to build the inputs used in the calculation.

2. Apply the child-support component (if selected)
   If you include child support, DocketMath uses your:

   • number of children,
   • child ages (if relevant),
   • and custody/parenting-time split.

3. Apply the alimony component (if selected)
   If you include alimony, DocketMath uses the alimony-specific inputs included in that calculator flow.

4. Combine results into a monthly figure
   If you run both components, the tool can show how they fit together into a combined monthly amount (depending on the tool’s design and what you selected).

What changes the output the most (practical levers)

Use this checklist to anticipate directionally how changes may affect results:

• Gross monthly income changes

  • Payor income increases → support scenarios often move upward.
  • Recipient income increases → support scenarios may move downward (depending on tool treatment).

• **Parenting-time / custody split changes (child support)

  • Shifting the time/care share toward the payor or recipient can increase/decrease the child-support component.

• **Number / age of children changes (child support)

  • More children or different age brackets can increase baseline child-support calculations.

• Timing changes

  • If your scenario includes retroactivity or effective-date differences, total amounts over time may change even when the monthly logic is consistent.

Scenario testing in DocketMath (how to use it effectively)

A good workflow is to run a baseline first, then adjust one variable at a time:

1. Run your baseline scenario using your best available facts.
2. Update one variable at a time (examples):

   • income for one party,
   • parenting-time split,
   • number/ages of children,
   • effective date.
3. Record how the monthly output changes.
4. Repeat until you understand which facts are “sensitive.”

Common pitfalls

Delaware support calculations can be sensitive to details that look small in a spreadsheet but matter in actual orders. Here are the most common issues to watch for when using DocketMath.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

1) Confusing SOL timing with support calculation

• 11 Del. C. § 205(b)(3) references a general 2-year SOL period for many claims (per the provided jurisdiction data).
• That does not tell you the monthly support amount.

2) Mixing gross and net income

Support calculations typically require consistent definitions. If you enter:

• one party’s gross income, and
• the other party’s take-home net, you’ll skew comparisons.

Fix:

• Use the same basis for both parties.
• If your case documents show different categories (gross pay, adjusted income, deductions), align your entries to what your DocketMath calculator expects.

3) Inconsistent parenting-time/custody formatting

Parenting-time splits may be entered as:

• percentages,
• days per month,
• or another format depending on the calculator.

Fix:

• Use one consistent representation and double-check it matches the DocketMath field expectations.

4) Forgetting child ages or the number of children

Child count and age can significantly affect the child-support component.

Fix:

• Confirm how many children are covered by the scenario/order you’re modeling.
• Ensure child ages align to the effective date you enter.

5) Assuming one method fits both alimony and child support

Alimony and child support are not interchangeable.

Fix:

• Select the correct calculator mode(s) in DocketMath.
• If the tool provides component-level output, review child support and alimony separately.

6) Skipping scenario documentation

Support discussions often rely on “what numbers were used” and “when.”

Fix:

• Save your baseline scenario.
• Note dates and list the exact input changes for each sensitivity run.

Sources and references

• Delaware Code, Title 11, 11 Del. C. § 205(b)(3) (General SOL Period: 2 years)
  Source: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai

Start with the primary authority for Delaware and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Next steps

1. Open DocketMath: Alimony Child Support (Delaware):
   /tools/alimony-child-support
2. Use Inputs you need to assemble your income, parenting-time/custody split, children count/ages, and timing details.
3. Run a baseline scenario.
4. Run at least 2 sensitivity scenarios, changing one factor at a time:

   • income for one party,
   • parenting-time/custody split (if applicable),
   • child count/ages,
   • effective date or duration assumptions (if the calculator supports it).
5. Compare results and document the input change so you can explain what drove the output difference.

Also, if you want jurisdiction-aware workflow guidance across DocketMath calculators, you can review related tooling here:

• /tools

Related reading

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