Common Alimony Child Support mistakes in Illinois

The top mistakes

When people use DocketMath’s alimony-child-support calculator for Illinois (US-IL), the same input and modeling issues tend to recur. These mistakes can meaningfully change the output and can also create misunderstandings during negotiations or court filings.

1) Mixing up alimony vs. child support inputs

A frequent problem is using the right numbers in the wrong “category” (or using inconsistent income definitions across the alimony and child support portions).

Common examples:

• Entering gross income where the tool expects an income figure based on a different standard (e.g., available/net framing), or vice versa.
• Including bonus/commission income in one section but excluding it in the other, creating an inconsistent income basis.

What it does to outputs: because the estimate depends on the income inputs, small percentage differences can swing the result—and the mismatch may not be obvious.

Quick checklist

2) Treating Illinois’s 5-year statute of limitations like a guess (instead of a baseline)

Another recurring error is assuming older matters are automatically “too late” (or automatically still actionable) without anchoring to the general limitations framework.

Illinois has a general 5-year statute of limitations described in 720 ILCS 5/3-6. Based on the provided jurisdiction data, this is the general/default period—no claim-type-specific sub-rule was identified there, so you should treat it as the baseline.

• General SOL period: 5 years
• General statute cited: 720 ILCS 5/3-6
• Source: https://ilga.gov/ftp/Public%20Acts/101/101-0130.htm?utm_source=openai

What it does to outputs: the limitations timing usually doesn’t change the calculator’s math directly, but it can change what remedies or adjustments are realistic when you use the estimate for next steps.

Quick checklist

3) Using incomplete or inconsistent income—especially for self-employed pay

If you’re self-employed or have variable income, it’s easy to misstate monthly totals by:

• averaging too few months,
• excluding income that reflects earning capacity (even if it’s not perfectly steady),
• applying deductions inconsistently (or differently than the tool’s expected input approach).

What it does to outputs: the calculator reacts immediately to your entered income. If the input is incomplete, you can get an estimate that’s consistently too high or too low, and that error can carry through multiple scenarios.

Quick checklist

4) Entering incorrect child-related inputs (parenting time/custody-time structure)

Child support estimates often hinge on factual inputs like parenting-time allocation and the number of children. People sometimes:

• enter the right number of children but use an incorrect custody-time format (or wrong conversion),
• forget to update inputs after a schedule change,
• input the correct amount of time but in the wrong field/format (e.g., days vs. percentage, if the tool requires a specific structure).

What it does to outputs: the result may look plausible even when the underlying parenting-time structure doesn’t match the real schedule you intend.

Quick checklist

5) Planning adjustments without accounting for existing orders and payment history

Even if the estimate is calculated correctly from your inputs, it can mislead if you ignore the difference between:

• your current obligation/order, and
• what the estimate projects under new inputs.

What it does to outputs: you might treat an estimate as a recommended new payment instead of a computed scenario based on the numbers you entered.

Quick checklist

6) Not sanity-checking the estimate before relying on it

Because the tool is deterministic, errors in entry tend to produce outputs that are “confident-looking” but wrong in substance. Common examples:

• leaving an income field effectively blank (or entering $0 by error),
• swapping party income fields,
• skipping required numeric inputs.

What it does to outputs: garbage in, plausible-looking garbage out.

Quick checklist

How to avoid them

Using DocketMath’s alimony-child-support calculator for Illinois is mostly about input discipline, repeatable assumptions, and timing awareness.

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.

1) Use one “single source of truth” for income

Before running scenarios, decide what each income number represents and keep it consistent across every relevant field.

A practical workflow:

• Gather documents (pay stubs, tax returns, business statements).
• Convert them into the tool-required structure (often a monthly figure).
• Reuse the exact same figures across alimony and child support inputs.

Checklist

2) Use the 5-year SOL rule as your timeline baseline

When you’re planning around whether issues could still be raised or addressed, anchor the conversation with Illinois’s general 5-year statute of limitations.

• General rule to anchor: 5 years
• Citation: 720 ILCS 5/3-6
• Jurisdiction link: https://ilga.gov/ftp/Public%20Acts/101/101-0130.htm?utm_source=openai

Operationally

• Identify the relevant key dates tied to the matter you’re evaluating.
• If events are older than about 5 years from the key action date, pause and scrutinize assumptions about what remains timely.

3) Run sensitivity checks (change one variable at a time)

Instead of relying on a single run, adjust inputs one at a time to see what drives the estimate. For example:

• Change parenting-time slightly (whatever increment the tool supports).
• Remove or add a bonus amount you’re unsure will recur.
• Swap between two plausible income averages and compare results.

Checklist

4) Compare “current order” vs. “estimate” in a simple table

Turn the output into an actionable comparison by tracking what changed.

Checklist

5) Use DocketMath to reduce transcription errors

If numbers are being copied from documents, transcription mistakes happen. Using DocketMath’s alimony-child-support flow helps by centralizing inputs and making re-runs easier.

Start here: **/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