Inputs you need for Alimony Child Support in Kentucky
4 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 to estimate alimony (spousal support) and child support in Kentucky (US-KY), the calculator will need inputs that drive the outcome. In practice, the biggest changes to the results usually come from income numbers, each child’s details, and the support start/adjustment timing—especially if you’re comparing scenarios.
Because your question involves both alimony and child support, plan to gather information for both streams, even if you run child support first and alimony second.
Use this checklist to collect everything before you click Run it:
Note (not legal advice): This is about inputs and how to use DocketMath—not legal advice. Support outcomes depend heavily on the facts you enter and the assumptions the tool uses.
A key timing note: Kentucky’s general statute-of-limitations backdrop
Kentucky’s general statute-of-limitations rule is 5 years, found at KRS 500.020. The “general SOL period” referenced here is the default baseline, and no claim-type-specific sub-rule was identified in the information provided. So treat 5 years under KRS 500.020 as the general planning baseline—not a guarantee that every situation follows the same timeline.
Where to find each input
To run DocketMath accurately, you’ll usually pull the following from documents and records you already have. Match your source to the input below:
| Input DocketMath asks for | Common place to find it | Practical tip |
|---|---|---|
| Gross monthly income | Pay stubs (last 2–4 months), employer letters | Use consistent averaging if income fluctuates |
| Bonuses/commissions/overtime | Year-to-date pay summaries, offer letters, employer statements | If irregular, enter a “typical” monthly average |
| Self-employment income | Tax returns, profit & loss summaries, bank deposits | Keep your numbers consistent across months and assumptions |
| Child ages/birthdates | Birth certificates, family records | Enter current age accurately to avoid bracket mismatches |
| Primary physical care / schedule | Parenting plan, custody order, calendar of time | If shared time is supported, use a realistic average schedule |
| Health insurance premiums | Payroll deductions or insurer billing | Confirm the monthly premium cost as of today |
| Childcare expenses | Receipts, childcare provider invoices | Use recurring monthly totals rather than occasional expenses |
| Marriage length | Marriage certificate date | Calculate the time span based on what you’re testing (don’t mix dates across runs) |
| Timing (start date) | Draft orders, filing dates, prior agreements | Pick one start date per scenario so comparisons stay meaningful |
If you’re doing a what-if comparison (for example, lower income vs. higher income, or shared care vs. primary care), collect at least two sets of income figures so you can rerun quickly without re-checking everything.
Pitfall to watch: Small monthly income differences can meaningfully change estimates, particularly when both alimony and child support are in the picture.
Run it
Once you have the checklist completed, open the calculator and enter the inputs in a consistent format.
Primary CTA: /tools/alimony-child-support
When you run scenarios, focus on a few “levers” that commonly change the estimate:
- **Income for each parent (gross monthly)
- Higher payor income generally increases child support estimates.
- Recipient income can change alimony-related estimates depending on how the tool models the scenario.
- Child count and ages
- Adding a child or moving between age brackets can change the child support amount.
- Shared care / physical care structure
- More overnights/time with the payor can affect how the calculator models child support.
- **Timing (start date)
- Changing the start date may affect how the tool handles calculations, comparisons, or related assumptions.
Suggested workflow (fast and repeatable)
- Step 1: Run a baseline using your most reliable numbers (recent pay stubs + current child ages).
- Step 2: Run a conservative scenario
- If income varies, use lower/average payor income that reflects likely outcomes.
- Step 3: Run a best-case scenario
- Use higher/steadier income if that better reflects expected future earnings.
- Step 4: If the calculator prompts alimony-specific items
- Adjust only one factor per run (for example, change health limitations only if you can support that assumption with your facts).
Timing context (Kentucky baseline)
If your broader goal includes how far back certain obligations might be considered in enforcement-related conversations, keep in mind Kentucky’s general 5-year SOL framework under KRS 500.020. Because no claim-type-specific sub-rule was identified here, don’t assume every situation will follow the same timeline—use this as a general planning reminder tied to the dates you have.