Choosing the right Damages Allocation tool for Kentucky
6 min read
Published April 15, 2026 • By DocketMath Team
Choose the right tool
Run this scenario in DocketMath using the Damages Allocation calculator.
If you’re allocating damages in a Kentucky matter, the fastest path to consistent results is picking the right DocketMath workflow before you start entering figures. “Damages allocation” isn’t one single calculation—it’s a set of steps that determine (1) which categories of damages you’re splitting, (2) how you label them for later reporting, and (3) which timing rules apply when the question involves the statute of limitations.
For Kentucky (US-KY), your first jurisdiction-aware checkpoint is the general statute of limitations. Under Kentucky law, the general SOL period is 5 years, codified at KRS 500.020. Based on the jurisdiction data available for this content, no claim-type-specific sub-rule was found, so the default rule is the general 5-year period in KRS 500.020 (not a specialized carve-out).
Start with the “jurisdiction-aware” facts you actually need
Use this checklist to confirm you’ve got the minimum inputs to make your allocation usable:
Note: The guidance here follows the available default information for Kentucky. If your situation involves a potentially different limitations rule, you’ll want to verify whether an exception applies before relying on a general SOL approach.
Why the right tool matters in Kentucky (and what changes in the output)
When you choose the DocketMath damages-allocation tool, the behavior of the output is shaped by how you structure inputs tied to time-based allocation. In practice, you’ll see meaningful output differences when you change:
| Input you control | What it affects in DocketMath | Kentucky-specific impact |
|---|---|---|
| The allocation start date | Which damages amounts fall “inside” vs “outside” the SOL window | The window is anchored to KRS 500.020’s 5 years |
| The allocation end/cutoff date | The boundary for time-based separation | Still governed by the general 5-year rule based on the provided data |
| The damages categories you include | Whether the calculator produces line-item allocations vs a combined figure | Category labeling drives reporting clarity as much as the SOL math itself |
| Whether you’re using general SOL vs a specialized rule | Whether the calculator uses the default timing framework | For this content scope, only the general rule is supported by the provided data |
If you accidentally use a workflow that assumes a different timing rule than you actually intend, your “recoverable/allocable” totals can shift substantially—especially where damages span multiple years.
Selecting DocketMath for Kentucky
For your primary CTA, use:
- Primary action: /tools/damages-allocation
This is the best fit when you need to:
- allocate damages across categories and/or time boundaries,
- keep your inputs aligned with Kentucky’s general SOL timing framework (KRS 500.020),
- produce output that you can carry into case strategy workstreams (demand packages, settlement modeling, and internal summaries).
When you open /tools/damages-allocation, plan to enter the date(s) you’ll use for the allocation boundary first, then structure your damages categories so the calculator can report clearly by component.
Next steps
After you’ve selected DocketMath’s damages-allocation tool, follow a workflow designed to reduce rework and keep the allocation “audit-friendly.”
After you run the Damages Allocation calculation, capture the inputs and output in the matter record. You can start directly in DocketMath: Open the calculator.
1) Confirm the SOL rule you’re actually using
Before any calculation, lock in what timing framework applies.
- Kentucky general SOL period: 5 years
- Authority: KRS 500.020
- Rule selection: Use the general/default period unless your analysis identifies a claim-type-specific rule (and for this content scope, none was found in the provided data).
Practical tip: reflect this in your internal notes or your allocation worksheet so the numbers don’t get questioned later.
Gentle caution (not legal advice): If a case involves a cause of action with a shorter or longer limitations period, using only KRS 500.020’s 5-year default could materially misstate recoverability windows. This content is aligned to the general/default period provided for Kentucky.
2) Choose your allocation boundary dates deliberately
Time-based allocation turns on boundaries. Before entering dates into /tools/damages-allocation, decide what each date represents in your recordkeeping.
A practical approach:
- Use the event date (or earliest relevant date) as your “start” point.
- Use the cutoff date that corresponds to your modeling needs (e.g., last claimed year, present date, or a date tied to pleadings).
Small date changes can move whole blocks of damages across the “within SOL” vs “outside SOL” split.
3) Enter damages categories in a way that matches how you’ll report them
The goal isn’t just a number—it’s a defensible allocation structure.
Use this checklist:
A clear set of categories usually produces more actionable output than lumping everything together.
4) Run the calculation and review output changes by input edits
Do at least one “sensitivity pass.” Edit one input at a time—especially dates—to see how the output shifts.
Try this sequence:
- Run with your baseline start date and cutoff date
- Change only the start date (e.g., by a month or a quarter) and compare results
- Change only the cutoff date and compare again
This makes it easier to spot data entry issues and identify where your modeling is most sensitive.
5) Export or reuse outputs in your broader workflow
After /tools/damages-allocation generates the allocation results, plan how you’ll use them:
- include them in internal settlement notes,
- summarize the breakdown in a demand/response worksheet,
- convert the allocation output into exhibits or schedules.
If you need additional workflow steps, start from this tool and expand outward based on your team’s process. For example, you may review other DocketMath tasks related to damages allocation setup and case organization by navigating from /tools/damages-allocation.
6) Document assumptions (without clutter)
Your output will be stronger when assumptions are captured clearly. Keep it short and consistent:
- Kentucky rule used: **general 5-year SOL (KRS 500.020)
- Dates used: start = ___, cutoff = ___
- Categories included: ___
- Exclusions: ___ (if any)