How to run Damages Allocation in DocketMath for Kentucky

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide shows how to run Damages Allocation in DocketMath for Kentucky (US-KY) using jurisdiction-aware setup. It also applies Kentucky’s general statute of limitations (SOL) period of 5 years under KRS 500.020 and clarifies that, based on the information available here, there is no claim-type-specific sub-rule being applied beyond that default SOL.

Before you start, decide what role Damages Allocation will play in your workflow:

• Allocation-focused work: assign totals across parties, periods, or categories based on your case structure.
• Timing-aware work: ensure the analysis aligns with the relevant limitations framework you’re using (in this guide, the general 5-year period).

1) Open the Damages Allocation calculator

1. Go to /tools/damages-allocation.
2. Confirm you’re using Damages Allocation (calculator name: damages-allocation).
3. If DocketMath prompts you to select a jurisdiction, choose:

   • Jurisdiction: **Kentucky (US-KY)

2) Confirm the jurisdiction rule set (SOL framework)

When Kentucky is selected, DocketMath’s jurisdiction-aware rules will use the provided default SOL period:

• General SOL Period: 5 years
• Authority: KRS 500.020

Because no claim-type-specific sub-rule was found for this configuration, DocketMath should treat KRS 500.020 (general default) as the controlling limitation period in this Damages Allocation run.

In the calculator UI, you’ll typically see (or be able to view) a limitations/timing assumption or a “selected rules” summary. Look for wording similar to:

• “General/default SOL: 5 years (KRS 500.020)”
• No additional branching by claim type

3) Enter allocation inputs (what changes the output)

Damages Allocation typically depends on how you structure the “total” you want allocated. Use the inputs that best match your case organization.

Common input patterns include:

• Total damages amount (the number you want allocated across your chosen dimensions)
• Allocation buckets (e.g., time periods, parties, categories, or events)
• Weights/percentages (or another basis figure) for each bucket so the calculator knows how to distribute the total

How outputs change as you type:

• If you adjust weights/percentages, the allocation across buckets updates immediately (while preserving the “shape” of your entered total).
• If you revise totals, each bucket’s allocation scales accordingly.
• If you enter date ranges, the Kentucky SOL framework (general 5-year window) can change which portions are effectively treated as included for the timing-aware part of the result—depending on how the tool applies the window.

4) Set the date range(s) using the 5-year Kentucky default

Damages allocation results often differ based on whether the system “includes” or “excludes” amounts outside the limitations window.

Use this Kentucky default framework:

• SOL window: 5 years (general)
• Statutory reference: KRS 500.020

Practical approach:

1. Identify the earliest date from which damages you’re considering begin.
2. Identify the latest date relevant to your calculation period.
3. Enter a date range consistent with the general/default 5-year SOL you want the calculator to apply.

If your overall period spans more than 5 years, your outputs may reflect that by allocating only the portion within the 5-year window (or otherwise adjusting the effective included period), depending on the calculator’s timing logic.

5) Review the computed allocations

After you run the calculator:

• Check the bucket-by-bucket allocations
• Look for any indicators that amounts are affected by the SOL window
• Confirm whether the tool indicates a reconciliation back to:

  • your input total damages, or
  • a SOL-adjusted total (if timing causes truncation/adjustment)

A quick sanity check:

• Compare sum of allocations across buckets
  vs.
• Input total damages (or the tool’s SOL-adjusted total, if it reports one)

6) Export or document your run

To keep your work reproducible:

• Record the jurisdiction setting (US-KY)
• Record the limitations assumption (5 years under KRS 500.020, general/default)
• Save the allocation output table

If DocketMath provides export/copy options, save a screenshot or exported report. Also capture the key inputs (especially total, dates, and bucket weights/percentages).

Common pitfalls

These issues commonly lead to confusion or results that don’t match expectations when running Damages Allocation for Kentucky:

• Assuming claim-type-specific limitations are being applied

  • In this guide’s setup, only the general/default SOL is applied: 5 years under KRS 500.020.
  • If your claim type would involve a different limitations rule, you’ll need to make sure your workflow accounts for that—because the configuration here is explicitly anchored to the general/default period.

• Date range mismatch

  • If the date range doesn’t match the damages period you intend, the tool may allocate in a way that effectively shifts which amounts fall inside the 5-year SOL window.

• Confusing weights with percentages

  • Decide whether numbers like “30” and “3” represent:

    • raw weights (relative basis), or
    • actual percentages.
  • Mixing formats can skew allocations significantly.

• Forgetting to reconcile totals

  • Always verify whether bucket totals sum to your expected overall amount (or to the calculator’s SOL-adjusted total, if the tool truncates/adjusts for timing).

Try it

Run a quick Kentucky test in DocketMath to see how the allocation outputs respond to changes in inputs. Use small, easy numbers so you can verify math quickly.

Open the Damages Allocation calculator and follow the steps above: Run the calculator.

Suggested test checklist (2-minute run)

• allocations per bucket

  • whether the tool indicates any SOL-related truncation/adjustment
  • whether totals reconcile

What to watch as you change inputs

• Adjust date range → allocations should shift if the SOL window excludes part of the broader period.
• Adjust weights/percentages → the distribution across buckets should rebalance immediately.
• Change total damages → bucket amounts should scale while preserving relative allocation proportions.

If the behavior doesn’t match the expectations above, re-check:

• whether the jurisdiction is correctly set to US-KY
• whether the calculator is using the **general 5-year SOL (KRS 500.020)
• whether your bucket inputs are in the correct format for weights vs. percentages

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