Worked example: Alimony Child Support in Kentucky

Example inputs

Below is a worked example for Kentucky using DocketMath’s alimony-child-support calculator (jurisdiction US-KY). This walkthrough shows how the calculator processes inputs and how the outputs respond when you change a few key numbers.

Scenario (monthly amounts)

Assume the following facts for a Kentucky custody/support worksheet:

• Payor monthly gross income: $5,500
• Payee monthly gross income: $2,500
• Shared parenting time: 35% / 65% (payor/payee)
• Number of children: 2
• Child-related monthly healthcare/childcare costs: $300
• Order requested:

  • Child support calculated using guideline logic
  • Spousal support (alimony) included as a modeled amount in the tool

Inputs you’d enter in DocketMath (conceptually)

The exact fields depend on the tool UI, but the “working inputs” generally map like this:

• Income inputs (payor + payee)
• Parenting time split
• Number of children
• Child-related expense add-ons (if the tool supports them)
• Whether to include alimony as a modeled output
• Any agreed/entered alimony amount variables the tool asks for (if applicable)

Time-window context: default Kentucky civil limits

If you’re modeling how far back support obligations (or related payment disputes) might be relevant, Kentucky’s general statute of limitations is tied to KRS 500.020 and Kentucky’s 5-year general rule.

• General SOL period (default): 5 years
• General statute: KRS 500.020

Because no claim-type-specific sub-rule was found here, you should treat 5 years as the general/default time window rather than a claim-type-specific period.

Example run

Let’s run the scenario through DocketMath (US-KY) for alimony + child support.

Run the Alimony Child Support calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Enter the inputs

Use these values as the working example:

• Payor gross: $5,500/month
• Payee gross: $2,500/month
• Children: 2
• Parenting time split: 35% payor / 65% payee
• Childcare/healthcare costs add-on: $300/month
• Include alimony in the output

Step 2: Review the output categories

A typical results screen for this tool will separate amounts into:

• **Child support (monthly)
• **Alimony (monthly)
• (Often) a total monthly support view

Step 3: Example output (illustrative)

Because DocketMath performs the math based on what you enter, the numbers you see will depend on the tool’s current formula logic and any optional settings you toggle. In a worked example, you’d interpret results like this:

• Child support: computed monthly amount (based on incomes, parenting time, and children-related costs)
• Alimony: modeled monthly amount (based on the tool’s alimony logic and your selection/settings)
• Estimated total: child support + alimony

Step 4: Pair results with the default 5-year context (KRS 500.020)

If you’re using the “5-year general/default window” for planning or review purposes, you can pair the monthly results with the default time frame:

• Default lookback period used in this example: 5 years
• Approximate number of months: 60

A simple planning math check (not a guarantee of what any claim would cover) looks like:

• **60 months × (monthly child support)
• 60 months × (monthly alimony) (if you’re modeling alimony exposure for a hypothetical review window)

This is a calculation helper, not a determination of recoverable amounts. The statutory reference for the general/default period is KRS 500.020, with the general rule stated as 5 years.

Checklist for this window usage:

If you want to see and manage this kind of scenario quickly, you can start with the tool here: /tools/alimony-child-support.

Sensitivity check

Support calculations usually react most to a small set of inputs. Below are practical “what if” changes you can test in DocketMath to understand your range.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Change 1: Parenting time split

Try shifting from 35% payor / 65% payee to 45% / 55% while keeping incomes and expenses constant.

Common expected impact:

• More parenting time for the payor often reduces the payor’s child support obligation under guideline-style logic.
• Alimony (if included by the tool) may not move as much as child support unless the tool ties it to dependency/support factors that change with time.

Quick test checklist:

• child support delta
• total delta

Change 2: Payor income adjustment ($5,500 → $6,000)

Increase the payor’s gross income by $500/month.

Typical effects:

• Child support often increases because the paying party’s income affects the guideline calculation base.
• Alimony modeled output may change depending on how the tool computes spousal support.

Test steps:

Change 3: Child-related expense add-on ($300 → $500)

Raise healthcare/childcare from $300 to $500.

Potential effect:

• Child support can increase if the tool includes these add-ons as part of the monthly computation.

Test steps:

Change 4: Remove alimony (toggle off)

For an “apples-to-apples” comparison, turn off alimony in the tool (if there’s a toggle), and compare:

• total monthly support
• child support alone

This helps you isolate whether your planning outcome is driven more by child support or alimony logic in the tool.

Checklist:

Runbook for managing uncertainty in DocketMath

Use this small test matrix:

For deeper exploration on how to structure scenarios quickly, you can also use DocketMath’s other tools from the same workflow path—start with /tools/alimony-child-support again to ensure your inputs match your intended modeling.

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado