Inputs you need for Alimony Child Support in Illinois
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Alimony Child Support calculator.
If you’re preparing for an Illinois alimony and/or child support calculation using DocketMath (jurisdiction US-IL), the biggest risk isn’t “getting the math wrong”—it’s missing inputs that drive the result. Illinois support outcomes typically depend on each parent’s finances, the children’s situation, and (for alimony/maintenance scenarios beyond simple guideline math) the court’s specific factual findings.
Below is a practical input checklist designed to match what DocketMath: alimony-child-support generally needs for jurisdiction-aware computations.
Reminder (not legal advice): This is a budgeting/scenario tool checklist, not a guarantee of how a court will decide. Use it to organize facts and document sources.
- DocketMath can help you organize numbers consistently, but it can’t replace the legal framing your attorney would use.
Warning: DocketMath’s output can only be as accurate as the numbers you enter. If you don’t have documentation for a variable (like childcare costs or health insurance premiums), you can still run a scenario—but label it clearly as an estimate in your notes and consider rerunning when you can confirm the figure.
Illinois timing context (general limitation period)
If you’re thinking about enforcement or related timing, Illinois has a general 5-year limitation period under 720 ILCS 5/3-6. This is the general/default period—the jurisdiction data provided did not identify any claim-type-specific sub-rule. DocketMath’s calculations don’t enforce deadlines, but your case timeline affects what issues matter right now.
Source: https://ilga.gov/ftp/Public%20Acts/101/101-0130.htm?utm_source=openai
Where to find each input
Use the same places you’d typically rely on during case preparation—pay systems, tax records, and household expense documentation—to gather what you’ll enter into DocketMath: alimony-child-support.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
1) Income and pay frequency
For both parents:
- Pay stubs (employer portal, payroll email, or HR portal)
- Year-to-date figures on the most recent stub
- Tax return forms (often W-2s and/or 1099s)
- Latest tax return summaries (including relevant schedules)
- If self-employed: profit-and-loss statements, business accounting records, and quarterly estimated tax documentation
Tip: DocketMath works best when income inputs match the cadence you select (annual vs. monthly vs. weekly). If one parent is hourly and the other is salaried, normalize the figures so you’re comparing like with like across scenarios.
2) Health insurance and childcare costs
- Health insurance premiums
- Employer benefits pages or payroll deduction lines
- If the court order amount isn’t clear, use the current premium you pay (or would pay) and note it as your scenario assumption
- Childcare costs
- Invoices and payment confirmations from daycare/after-school providers
- Convert weekly payments to a monthly total when needed
3) Children’s schedule and parenting time
- Parenting calendar or proposed schedule
- Any existing order documents (especially for modification scenarios)
- Travel or holiday patterns that repeat annually
Keep it concrete. For example:
- “3 overnights per week”
- “Every other weekend plus 1 weekday” Vague descriptions are harder to translate into calculator inputs.
4) Marital duration and alimony facts
- Marriage date and separation date (use the actual dates)
- Documentation supporting financial need and ability to pay, such as:
- monthly budgets
- debt obligations
- education-related expenses (if documented and relevant)
5) Documentation discipline (so you can rerun scenarios)
Create one folder (digital or physical) with:
- PDFs of pay stubs
- tax return pages or summaries
- childcare invoices/receipts
- insurance premium statements
- a one-page parenting schedule summary
Pitfall: Entering expenses from memory often causes rework later. Updating childcare and insurance numbers can materially change your output.
Run it
After you assemble your inputs, run DocketMath: alimony-child-support in Illinois (US-IL) here: /tools/alimony-child-support.
Use a practical run sequence:
Enter baseline income
- Input both parents’ income using the cadence DocketMath requests.
- If income fluctuates (commissions/bonuses), decide on an approach for consistency:
- use the most recent month, or
- annualize recent figures, or
- use last tax year for a baseline
- The key is consistency across scenarios.
Add child-related costs and schedule
- Enter number/ages of children
- Add childcare and health insurance premiums
- Input the parenting time schedule you want to model
**Add alimony variables (if included)
- Enter marriage duration and any other structured alimony inputs DocketMath requests
- Run at least two scenarios when you’re unsure about income verification, such as:
- “recent YTD annualized” vs.
- “last tax year verified”
Compare outputs and adjust inputs methodically
- Change one major variable at a time so you can interpret what drove the difference.
- For example:
- Adjust childcare by a known amount (e.g., +$200/month) and note how the estimate responds.
- Correct one parent’s income from an estimate to a tax-verified number and observe the shift.
Save your scenario notes Record assumptions like:
- “insurance premium as currently paid”
- “childcare invoice monthly average”
- “income annualized from YTD” This makes later review faster and more accurate.
Note: DocketMath is for running numbers—not a substitute for a court’s final findings. Treat outputs as scenario estimates you can support with documentation.
