Spreadsheet checks before running Alimony Child Support in Kentucky

5 min read

Published April 15, 2026 • By DocketMath Team

What the checker catches

Run this scenario in DocketMath using the Alimony Child Support calculator.

DocketMath’s Alimony Child Support spreadsheet checker helps you validate the key numbers and dates before you run calculations in Kentucky (US-KY). The goal isn’t to predict outcomes—it’s to reduce avoidable spreadsheet errors that can cascade into incorrect support projections.

Below are the most common issues the checker is designed to catch, with Kentucky-specific timing logic tied to the general statute of limitations (SOL) period in KRS 500.020.

1) Date logic that breaks retroactive timing

A spreadsheet can look correct while still producing misleading results if the date inputs are inconsistent. The checker flags problems such as:

  • Start date after end date (reversed date ranges)
  • Missing date fields needed to compute elapsed time
  • Mismatched “effective” dates across sheet tabs (for example, when one tab was updated but another wasn’t)

Kentucky timing rule the checker uses (general/default)

Kentucky’s general SOL period is 5 years under KRS 500.020.

Note: No claim-type-specific sub-rule was found in the provided jurisdiction data. The checker therefore treats 5 years as the general/default limitation period rather than applying a specialized time rule.

2) Retroactive window cutoffs (5-year default)

Support calculations sometimes include amounts tied to prior periods. The checker applies a 5-year general/default SOL lens so you can spot when your spreadsheet is inadvertently counting more than a reasonable limitation window.

Example issue:

  • Your sheet totals support for 3 years
  • But the start date of the counted period is more than 5 years before the relevant event date
  • The checker can alert you that the totals may be outside the general 5-year period under KRS 500.020

3) Consistency checks across income/expense fields

Even with correct dates, spreadsheets often fail due to inconsistent input formats, such as:

  • Income entered as annual in one tab and monthly in another
  • Self-employment income inputs using conflicting assumptions
  • Rounding differences that create different totals depending on which reference cell is used

The checker verifies that:

  • Units match (monthly vs annual)
  • Totals roll up correctly
  • Dependent cell references stay consistent so formulas aren’t effectively computing from different assumptions

4) Worksheet integrity (formula and reference sanity)

Calculator tabs can silently drift over time. The checker looks for typical integrity problems, including:

  • Broken cell references (for example, if a column was moved)
  • Overwritten formulas (inputs accidentally replacing calculations)
  • Hard-coded numbers where linked values are expected (which can cause totals not to update when inputs change)

5) Kentucky jurisdiction awareness (US-KY)

Because the checker is running in Kentucky (US-KY) mode, it aligns the limitation/timing logic to KRS 500.020 (general 5-year period) using the jurisdiction code. This helps reduce the risk of mixing “any-state” assumptions with Kentucky settings.

Common pitfall to avoid: running a spreadsheet with a default SOL assumption intended for a different state, then changing only the displayed state name. The checker is designed to tie the limitation logic to US-KY rather than the label alone.

When to run it

Run the checker at two practical points: before you finalize data entry and immediately before you export or submit results.

Run the checker before importing a spreadsheet into the Alimony Child Support workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Run it early (during setup)

Do this right after you:

  • Enter the relevant dates
  • Fill in income inputs
  • Set the number of children and any other scenario controls
  • Confirm the sheet is configured for **Kentucky (US-KY)

Running early is most effective because changes are still easy, and the checker can help you correct structure—not just symptoms.

Run it again right before you rely on outputs

Re-run after you:

  • Adjust dates
  • Update income figures
  • Change assumptions that affect monthly vs annual conversions
  • Modify cells that feed other tabs (for example, anything tied to totals)

Think of it as a “pre-flight checklist.” In practice, it helps prevent treating an incorrect spreadsheet result as meaningful information.

Quick order checklist

Try the checker

You can test this workflow directly in DocketMath’s Alimony Child Support tool:

  1. Open the calculator: /tools/alimony-child-support
  2. Paste or enter your spreadsheet inputs into the corresponding fields.
  3. Use the checker step to review alerts and validation results.
  4. Fix any flagged issues (especially date logic and unit consistency), then re-run until the checker output looks clean.
  5. When you’re satisfied, run the calculation and compare outputs before/after your corrections.

What to expect when you change inputs

Use these cause-and-effect checks to build confidence:

If you change…The checker impact you should see
The relevant start/end datesAlerts related to date ordering or limitation-window alignment (general 5 years under KRS 500.020)
Income entered as annual instead of monthlyUnit mismatch warnings or inconsistencies in rollups/totals
A referenced input/dependent cellFormula/reference integrity flags or total discrepancies
An effective date that shifts retroactive totalsAlerts that the counted window may exceed the 5-year general/default period

Gentle reminder: This tool is for validation and spreadsheet integrity checks. It does not replace a full legal review of your facts. For final filing or legal strategy in Kentucky, consider consulting a qualified professional.

If you want the fastest path to a trustworthy sheet, start with conservative/rough inputs to confirm the logic, then tighten the numbers.

Related reading