Inputs you need for Damages Allocation in Kentucky
4 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Damages Allocation calculator.
Kentucky’s damages allocation work in DocketMath starts with a few concrete inputs—most of which come from your case documents and your damages model. Because this post is focused on inputs (not strategy), treat the list below as a practical checklist for setting up Damages Allocation in Kentucky (US-KY).
A timing note matters for any damages workflow: Kentucky’s general statute of limitations is 5 years under KRS 500.020. In the rules used for this calculator, no claim-type-specific sub-rule was found, so the default period is the general 5-year rule (not a special carve-out). Keep that in mind when you decide what portion of your damages window to include.
Core inputs for damages allocation (DocketMath → “damages-allocation”)
Check the boxes as you gather information:
Note: The limitations framework affects whether the damages time window you choose is within reach. So your “date needed” inputs should align with the period you intend to include in your damages allocation. The default rule used here is 5 years under KRS 500.020.
Limitation timing input (recommended)
DocketMath can use these dates to help you keep your allocation windows consistent with the general 5-year limitation period under KRS 500.020.
Where to find each input
Most inputs come from standard litigation records and your damages spreadsheet. Here’s a “source-to-field” guide you can use while you’re building your model.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
Documents that usually contain the dates
Documents that usually contain the damages amounts
Apportionment factors: what to look for
You generally want factors already stated in your materials (or at least explicitly assumed in your model). Look for:
Pitfall: Try not to guess date boundaries “after the fact.” For example, if your invoices are monthly but you set a damages start mid-month, you can create allocation mismatches that are harder to explain during review.
Run it
Once you’ve collected your inputs, run DocketMath → Damages Allocation using Kentucky rules.
- Open /tools/damages-allocation
- Confirm you’re using US-KY for jurisdiction (this is what makes the calculator apply Kentucky jurisdiction-aware settings).
- Enter the date inputs
- Include the incident/start date and the allocation end date.
- If you have a filing-related date (recommended), enter it to align the included period with KRS 500.020’s general 5-year rule.
- Input your damages category totals
- Enter past and future totals as totals or (if your workflow supports it) as breakdowns by category.
- Enter apportionment factors
- Use the percentages/weights your record supports.
- If you’re comparing different assumptions, run them as separate scenarios so you can compare output differences.
- Review outputs and validate against your input logic
- Check that the allocated totals reconcile to the damages totals you entered.
- Confirm that your included time window matches the default 5-year approach unless you later add claim-type-specific inputs supported by your scenario (none were identified as a special carve-out in the rule set used for this calculator).
How the output typically changes when inputs change
Use this quick “what moves what” mapping:
| Input you change | Likely effect on DocketMath output |
|---|---|
| Allocation end date moves later | Enlarges the included period → may increase allocated totals if damages are time-based |
| Filing-related date moves earlier | Tightens which portions fall within the general 5-year window under KRS 500.020 |
| Apportionment percentages change | Reallocates totals across components/parties while keeping overall totals (often) constant |
| Past vs. future split changes | Shifts amounts between “past” and “future” portions |
| Category totals updated | Directly changes computed allocation totals for each category |
Reminder (gentle disclaimer): This is a workflow helper for setting up and running calculations in DocketMath. It isn’t legal advice. If you believe a specific limitations rule applies beyond the general default period, consider verifying that with qualified counsel and then reflecting it in your inputs.