Inputs you need for Alimony Child Support in Connecticut
6 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 using DocketMath → Alimony Child Support for Connecticut (US-CT), you’ll get the cleanest, most defensible numbers when you assemble your inputs first. This section is a practical checklist of what you typically need to run the alimony + child support calculator in Connecticut.
Note: This article is informational and doesn’t provide legal advice. It helps you organize inputs so you can run DocketMath accurately.
Financial inputs (income, deductions, and parenting-related expenses)
- ☐ **Payor’s gross income (and income source)
- Examples: wages, bonuses, self-employment income, rental income
- ☐ Payor’s verified deductions
- Examples: certain payroll deductions, documented business expenses (as applicable to your situation)
- ☐ **Payee’s gross income (and income source)
- ☐ Payee’s verified deductions
- ☐ Any additional income streams
- Examples: interest/dividends, unemployment benefits, retirement distributions
- ☐ Health insurance costs for the child
- Include monthly premiums and who pays them (parent vs. other)
- ☐ Childcare costs
- Provide monthly amount and the basis for the expense
- ☐ Work-related transportation or extraordinary expenses (if you’re including them)
- If you don’t have documented numbers, you may need to omit them rather than estimate.
Parenting / schedule inputs (time-sharing)
- ☐ How many overnights each parent has
- ☐ Total child time split per year
- If you track it by custody order or calendar, use the most recent version.
- ☐ Number of children covered
- ☐ Any relevant special needs costs you intend to reflect in the worksheet
- Examples: required therapies, special schooling, or documented care expenses.
Case timing / verification inputs (if available)
- ☐ **Date your situation began (or the month you want the calculation to start)
- DocketMath works best when you align inputs to a specific timeframe.
- ☐ Documentation status
- Example: “Pay stubs for last 8 weeks available,” “tax returns available for the last year,” etc.
Statute awareness (useful for expectations—not a calculator input)
Connecticut has a general statute of limitations period of 3 years for certain financial claims under Conn. Gen. Stat. § 52-577a. The general/default period is 3 years. Based on the jurisdiction data provided, no claim-type-specific sub-rule was found, so treat this as the default general period for expectation-setting rather than a personalized timeline.
Source: Conn. Gen. Stat. § 52-577a (3-year general limitations period), https://law.justia.com/codes/connecticut/title-52/chapter-926/section-52-577a/?utm_source=openai
Where to find each input
To avoid last-minute guesswork, collect inputs from the same places you’d use to support them later: records, statements, and orders. Below is a “where-to-find” guide you can follow quickly.
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.
Income
- W-2s / pay stubs → recent wage income and typical monthly earnings
- Last filed tax return → baseline for self-employment, business income, and adjustments
- Bank statements / 1099s → non-wage income patterns (if applicable)
- Benefit statements (e.g., unemployment or disability, if relevant) → for income that isn’t wages
Deductions and required costs
- Employer benefit statements → health insurance premiums
- Invoices / receipts → childcare, medical-related premiums, or recurring special expenses
- Custody order / parenting plan → the “how many overnights” input that drives the schedule component
Parenting time
- Court order or written agreement → official time-sharing schedule
- Calendar records (if you’ve been tracking changes informally) → confirm the pattern for the timeframe you’ll input
Timing and documentation
- Agreements or filings → the date range you’re modeling
- Pay periods and invoice dates → align monthly figures to the same month logic across both parents
Run it
Once your inputs are assembled, you’re ready to run DocketMath. Start at: /tools/alimony-child-support.
Enter the inputs in DocketMath and run the Alimony Child Support calculation to generate a clean breakdown: Run the calculator.
Step-by-step workflow
- Open the DocketMath calculator:
- /tools/alimony-child-support
- Enter both parents’ income inputs first
- This is usually the biggest driver of output amounts.
- Add child-related expenses (as applicable)
- Health insurance and childcare costs often influence the final numbers more than minor adjustments elsewhere.
- Enter parenting time (overnights / schedule split)
- Changing the time split can alter how expenses and responsibilities are allocated in the worksheet logic.
- Confirm the number of children
- Make sure you’re not accidentally mixing “children in household” with “children covered by the order.”
- Review outputs and run a quick comparison
- If you’re between two plausible income figures (e.g., commission-heavy months), run the calculator twice with different documented numbers and compare results.
How outputs typically change when you adjust inputs
Use this quick “cause → effect” map to sanity-check what you see:
| Input you change | Output impact to watch |
|---|---|
| Higher payor gross income | Usually increases support outcomes tied to the payor’s ability to pay |
| Higher payee income | May reduce or shift support amounts |
| More childcare cost included | May increase the portion attributable to childcare needs |
| Higher health insurance premium | May increase support related to ongoing health coverage costs |
| Parenting time shifts (more overnights for one parent) | Can change how the calculator allocates parenting-time-related expense responsibility |
Warning: If you input estimates instead of documented monthly figures, you may get outputs that look precise but won’t match what you can actually support with evidence. For calculators, consistency of documentation generally matters more than “exactness.”
Limitations and timing expectation (Connecticut)
Separate from what DocketMath calculates, Connecticut’s general 3-year statute of limitations may affect how far back certain financial matters may be actionable, depending on the claim context. Your jurisdiction data provided the default general period only, so use this as an expectation-setting rule rather than a personalized legal timeline.
Source: Conn. Gen. Stat. § 52-577a, https://law.justia.com/codes/connecticut/title-52/chapter-926/section-52-577a/?utm_source=openai
