Common Alimony Child Support mistakes in Kentucky
6 min read
Published April 15, 2026 • By DocketMath Team
The top mistakes
Families often approach DocketMath’s alimony-child-support calculator with good intentions, but a few recurring Kentucky errors can meaningfully change the output numbers. This section highlights common pitfalls you can catch before you file, negotiate, or finalize paperwork.
Pitfall: Small input errors (especially dates, income numbers, or time-sharing assumptions) can swing the results range—even if your overall story is correct.
1) Using the wrong “type” of support or mixing categories
A common workflow error is blending alimony-style income adjustments with child support inputs, or treating child-related amounts as if they were part of spousal support.
Kentucky filings often distinguish:
- alimony (support tied to the marital relationship), and
- child support (support tied to the children).
In DocketMath, keep your inputs aligned to the alimony-child-support tool so the output matches the obligation category you intend to address. If you’re modeling both issues, make sure each number is entered in the field that matches that category rather than “averaging” them together.
2) Entering inconsistent income (gross vs. net, or using outdated pay)
Kentucky calculations are very sensitive to income figures. The biggest data-quality errors usually come from:
- using a monthly net number where the tool expects monthly gross (or vice versa),
- entering a number from an old pay period (for example, last year’s income instead of current earnings),
- not reflecting income changes such as overtime, bonuses, or job changes.
Before you type anything, check your sources (pay stubs, employer statements, and year-to-date earnings are common starting points). Also, use the same time basis consistently (weekly → monthly, or annual → monthly) so the calculator doesn’t effectively double-convert your numbers.
3) Ignoring time-sharing / parenting-time assumptions
Child support outcomes depend heavily on the amount of time each parent has with the child(ren). A frequent error is assuming:
- “50/50” when the schedule is actually uneven, or
- steady time-sharing when the schedule differs across seasons (alternate weekends, holidays, and summer weeks).
If your parenting time changes throughout the year, input the most typical arrangement for the period you’re modeling. That prevents results that look precise but aren’t aligned with your real schedule.
4) Using the wrong number of children
If multiple children are involved, child support modeling often changes as the number of children changes. Errors include:
- entering 1 child when the scenario involves 2 or 3, or
- entering the wrong child status (for example, including a child who may not be treated as covered under your intended modeling scope).
Even if you “know” the case involves multiple kids, verify that the child count field matches your scenario.
5) Misunderstanding Kentucky’s general statute of limitations (SOL) when organizing records
People often focus only on what they can file now, but they also need to track how far back they may be able to act—especially when gathering payment history.
Kentucky’s general statute of limitations is 5 years, under KRS 500.020. Use this as the default framework for time-based limitations unless a specific claim-type rule applies.
Key point (general/default):
- Kentucky general SOL period: 5 years (default), based on KRS 500.020
- State this clearly: the general/default period is the only limitation described here; no claim-type-specific sub-rule was identified for this overview.
Note: This is a general/default SOL overview. If you’re dealing with a specialized claim category, the applicable limitation period may differ from the 5-year default.
6) Relying on outputs without verifying input units and periods
This is a “calculator hygiene” issue. Watch for mismatches such as:
- annual income entered as monthly,
- child-related inputs entered as yearly when the tool expects totals for the relevant calculation period,
- parenting-time figures entered in days when the tool expects weeks (or vice versa).
A practical quality-control approach is to do a quick sanity check using DocketMath’s scenario workflow:
- Change only one variable (like income) and confirm the output moves in the direction you expect.
How to avoid them
Use a repeatable workflow to reduce avoidable edits and produce numbers that reflect your situation accurately. For convenience, you can start here: alimony-child-support tool.
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.
Step-by-step checklist before you run DocketMath
How outputs change when inputs change (directional guidance)
Use these as directional sanity checks while you iterate in DocketMath. (The exact dollar impact depends on the calculator’s modeling rules and your specific inputs.)
| Input you change | What you should usually see |
|---|---|
| Higher income for the paying parent | Likely increases support obligations (directionally) |
| Fewer days/overnights for the child with the other parent | Often increases support in favor of the parent with less time |
| More parenting time than you assumed | Often reduces support relative to a lower-time scenario |
| Updating the child count | Output often changes more than you expect—recheck this first |
Warning: These are directional expectations for sanity checks, not guarantees. Always verify the result after updating inputs in the correct fields.
Use iteration as quality control
DocketMath is built for scenario planning. Instead of one-shot data entry:
- Run a baseline scenario.
- Modify one input (e.g., switch from “prior year” to “current” income).
- Confirm the output changes logically.
- Repeat for key variables (parenting time and child count are common culprits).
This process catches unit errors and category mixing faster than reviewing a finished PDF/printout.
Record-keeping for the 5-year general window
If you’re organizing payment history or need a default “how far back” rule, Kentucky’s general SOL is 5 years under KRS 500.020. Even when you’re not filing immediately, consistent records help you:
- compare prior periods against current income,
- document schedule stability or changes,
- avoid last-minute scrambling when deadlines or enforcement questions arise.
Gentle reminder: this article is for practical guidance and not legal advice. If your case involves complex timing or a specialized claim, consider confirming the applicable limitations rules with a qualified attorney.