How to run Alimony Child Support in DocketMath for Kentucky
Step-by-step
This guide walks you through running Alimony (maintenance) and Child Support in DocketMath for Kentucky, using jurisdiction-aware rules (jurisdiction code US-KY). DocketMath’s alimony-child-support calculator is built to model outcomes based on the inputs you provide—so you can see how the numbers change as you adjust assumptions.
Note: This is modeling guidance, not legal advice. Kentucky support obligations depend on the specific facts of your case, and courts may apply additional considerations beyond what any calculator can capture.
1) Open the Kentucky alimony/child-support calculator
- Go to the primary tool page: /tools/alimony-child-support
- Confirm the tool is set to Kentucky (US-KY).
- Choose the run mode the UI provides (for example: child support only, maintenance only, or both, if available).
If you don’t see a “both” option, run a combined scenario (if the calculator supports it) or run separate scenarios and compare results.
2) Enter income inputs (and keep them consistent)
DocketMath typically needs income figures to estimate support amounts. Use the exact labels from the form:
- Gross and/or net income (use what each field specifies)
- Payor vs. recipient direction (make sure you select the correct payer/receiver for each section)
- Any additional income stream fields the calculator requests
- Frequency and time period (weekly/biweekly/monthly/annual—whatever the UI asks for)
Consistency matters:
- If a field asks for monthly, enter monthly everywhere you can.
- If a field asks for annual, enter annual everywhere you can.
- Don’t mix gross and net across fields unless the form clearly separates them and you understand the difference for each input.
3) Add child-related inputs
For Kentucky child support modeling, you’ll generally enter inputs like:
- Number of children (if requested)
- Any child-related adjustments the calculator prompts for
- A support start date / effective period (if supported by the tool)
Kentucky’s child support statute authorizes courts to order child support in amounts the court determines to be just and appropriate under the circumstances, and it provides broad authority regarding payments from either or both parents:
- Ky. Rev. Stat. § 403.212 (child) (source: https://apps.legislature.ky.gov/law/statutes/statute.aspx?id=50811)
Because this is a modeled estimate, treat the results as an approximation of how numbers may change—not as a guaranteed court outcome.
4) Add maintenance (alimony) inputs
For Kentucky maintenance (alimony) modeling, enter what the calculator requests, such as:
- Spousal income figures for the payor and recipient (as labeled)
- Marriage duration (if prompted)
- Any maintenance-related modifiers the UI offers
Small changes in one spouse’s income can materially change maintenance estimates. If you’re exploring ranges, run multiple scenarios (for example, “baseline,” “higher income,” “lower income”) so you can see the sensitivity.
Kentucky’s maintenance authority is:
- Ky. Rev. Stat. § 403.200 (maintenance) (source: https://apps.legislature.ky.gov/law/statutes/statute.aspx?id=50811)
5) Choose the “period” logic (default vs. claim-specific rules)
Kentucky support calculations can depend on case facts and timing. However, your run should match what the tool actually supports.
Per your note:
- No claim-type-specific sub-rule was found.
- The general/default period is what you should treat as your baseline.
So, in DocketMath:
- Start with the default period behavior unless the UI explicitly offers claim-type-specific selection.
- If the calculator provides multiple period options, use the one that matches your situation and document which selection you used.
6) Run the calculation and review outputs
After you submit inputs, review results by component:
- Maintenance estimate (if maintenance is enabled)
- Child support estimate (if child support is enabled)
- Any breakdowns shown in the results (for example: monthly totals, component splits, or period-by-period outputs)
A practical workflow:
- Start with your best available numbers.
- Save results if the platform allows it.
- Adjust one variable at a time (such as recipient income or number of children) so you understand what caused the change.
7) Document assumptions before you share results
Before exporting, screenshotting, or sharing outputs, write down (or capture) the key assumptions:
- The income amounts you entered and whether they are gross or net
- The timeframe/frequency used (monthly vs. annual)
- Which toggles/checks were selected (maintenance on/off; child support on/off; any extra adjustments)
- The “period” logic/option used (especially since you’re using the general/default period baseline)
This makes comparisons between runs much easier to interpret.
Common pitfalls
Most errors in support modeling come from input mismatch, not from the math.
Pitfall checklist
- Mixing gross income in one field and net income in another
- Entering annual income into a field that expects monthly (or vice versa)
- Flipping payor vs. recipient roles
- Updating only one of the sections (e.g., changing maintenance inputs but forgetting to update child support inputs)
- Assuming a claim-type-specific rule is being applied when only the general/default period is available in your setup
- Using income data that doesn’t match the timeframe you’re modeling (for example, entering pay data from a different effective period)
Warning (gentle): Kentucky statutes authorize courts to order support in amounts the court finds “just and appropriate” under the circumstances. If your inputs don’t match the facts (income timing, which parent pays, number of children, and effective period), the modeled output may not align with what a court could order. (See Ky. Rev. Stat. § 403.212 and Ky. Rev. Stat. § 403.200.)
A quick diagnostic table
| Symptom in DocketMath results | Likely cause | What to check |
|---|---|---|
| Output seems too high | Income entered as gross vs. net or frequency mismatch | Verify “per month” vs “per year” labels; re-enter consistently |
| Output seems too low | Wrong payer/recipient selection or missing income stream | Confirm direction and whether the UI asked for multiple incomes |
| Maintenance changes but child support doesn’t (or vice versa) | You changed only one component | Ensure both sections reflect the same assumptions where appropriate |
| Results look identical after changes | The input isn’t connected to the calculation or wasn’t applied | Look for enablement toggles/switches and confirm field relevance |
Try it
Ready to run a Kentucky scenario in DocketMath?
- Open the calculator: /tools/alimony-child-support
- Set jurisdiction to Kentucky (US-KY).
- Enter:
- Payor and recipient income (as labeled)
- Child count (if prompted)
- Maintenance inputs (if prompted)
- Run your baseline scenario.
- Do two quick sensitivity checks:
- Change payor income by ±10% and re-run
- Change recipient income by ±10% and re-run
Interpretation tip: whichever adjustment creates the bigger movement in the estimate is likely the most influential assumption in your modeled scenario.
For statute context while you test:
- Child support authority: Ky. Rev. Stat. § 403.212
- Maintenance authority: Ky. Rev. Stat. § 403.200
These provisions reflect the “just and appropriate under the circumstances” concept, so treat the calculator outputs as modeled estimates alongside your case facts.
Related reading
- How Alimony Child Support rules vary in New York — What varies by jurisdiction
- How to calculate Alimony Child Support in Philippines — Full how-to guide with jurisdiction-specific rules
- Worked example: Alimony Child Support in Philippines — Worked example with real statute citations
Run the numbers for your matter against the verified rule for this jurisdiction.
Run the calculation