Why Damages Allocation results differ in Kentucky

The top 5 reasons results differ

Damages Allocation outputs in Kentucky can look inconsistent even when you feed the “same” story into DocketMath. In practice, differences usually come from how the tool applies jurisdiction-aware rules—especially the statute of limitations (SOL)—and how your case facts map to those rules.

Below are the top 5 reasons Kentucky allocation results differ, using the general/default SOL period in Kentucky:

1) Different “clock start” dates

Even a small change to the event date used to start the SOL clock can flip whether a component is considered time-barred.

Common inputs that move the clock:

• Date of injury / loss
• Date of discovery (if you entered one)
• Date of alleged breach or occurrence

2) Different “allocation windows” caused by SOL cutoff

DocketMath’s damages allocation can treat portions outside the 5-year window differently. When that boundary shifts, the allocation can change materially because the tool may exclude or reweight damages that fall beyond KRS 500.020 (5 years).

3) Mixed-duration damages (like continuing harm)

If your damages span multiple years, the output is sensitive to:

• the start year
• the end year
• how you entered interim damages frequency (one-time vs recurring)

A case that runs “just over” 5 years may allocate fewer dollars to covered periods than one that finishes “just under” 5 years.

4) Missing or inconsistent time granularity

If you provide annual, monthly, or lump-sum values inconsistently, the tool must convert them into an allocation timeline. That conversion can cause drift at the boundaries (especially around the SOL cutoff).

5) Claim-type mapping not recognized (defaulting to KRS 500.020)

Per your jurisdiction note, no claim-type-specific sub-rule was found. That means:

• DocketMath applies the general/default 5-year period from KRS 500.020
• if your fact pattern would ordinarily trigger a different limitation category, the tool may not have that specialized rule available

How to isolate the variable

To pinpoint why two runs differ, isolate inputs one at a time—especially anything tied to timing.

Start with a “before vs after” checklist:

A practical isolation workflow:

1. Run once with everything locked (all dates and amounts identical).
2. Change only the SOL start date by a single day (e.g., +1 day).
3. Observe whether the allocation changes only for boundary-year damages.
4. Repeat for:

   • damages start date
   • damages end date
   • damage frequency/granularity

If the output swings sharply after changing one date, that date is likely the control variable creating the inconsistency. If it barely moves, the differences may come from how the timeline is segmented into periods.

For quick access to the tool workflow, start here: /tools/damages-allocation.

Next steps

Use DocketMath to produce a “defensibility check” style output rather than chasing multiple narratives. You’re aiming to confirm whether the differences are:

• timing-driven (SOL cutoff and timeline segmentation), or
• input-driven (granularity, dates, or inconsistent damage spans).

Concrete next steps:

• Capture the exact dates used in each run (SOL start, damages start, damages end).
• Ensure all runs use the same reference date for “as of” calculations.
• Keep your damages entries consistent (same unit basis and same date range).
• Run a controlled set of scenarios:

  • Scenario A: baseline dates
  • Scenario B: +1 day on SOL start
  • Scenario C: +1 day on damages start
  • Scenario D: -1 day on damages end

Then compare where the allocation changes. If changes cluster right at the 5-year boundary, the result differences are almost certainly SOL/timeline segmentation artifacts under KRS 500.020.

Finally, if you believe a claim-type-specific limitation period applies, verify whether your setup includes the necessary claim categorization—because your current rule set is using the general/default 5-year period.

Gentle disclaimer: This is an analytical workflow explanation, not legal advice. SOL issues can be fact-specific.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules