How to run Wrongful Death Damages in DocketMath for Kentucky

How to run Wrongful Death Damages in DocketMath for Kentucky

7 min read

Published January 10, 2026 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Step-by-step

Here’s a practical walkthrough for running Wrongful Death Damages in DocketMath for Kentucky (US-KY) using the platform’s wrongful-death-damages calculator and Kentucky’s jurisdiction-aware timing assumptions.

Note: This guide is for using DocketMath only. It is not legal advice and does not account for case-specific exceptions. Consider having a Kentucky attorney review any wrongful death filing decisions.

1) Open the correct DocketMath calculator

  1. Go to DocketMath → Wrongful Death Damages: /tools/wrongful-death-damages.
  2. Confirm the jurisdiction selector is set to Kentucky (US-KY).

If DocketMath supports jurisdiction presets, choosing US-KY should apply Kentucky defaults (including the limitations period assumption) where available.

2) Enter Kentucky timing inputs (the “when” drives viability)

Kentucky’s general limitations period for many civil claims is 5 years, under KRS 500.020.

In DocketMath, find the timing section (often labeled Limitation period, Date of death, Filing date, or Evaluation date). Enter dates like this:

  • Date of death: Enter the date the wrongful death occurred (often shown as the death date in records).
  • Planned filing date or evaluation date: Enter the date you want to measure against (for example, the date you intend to file, or a date you’re evaluating the matter as of).

What DocketMath should do with that timing

DocketMath will typically determine whether the matter falls within the 5-year window derived from KRS 500.020 as the default/general rule.

Important clarity (Kentucky default used here)

  • No claim-type-specific sub-rule was found in the jurisdiction data you provided for wrongful death.
  • Therefore, this walkthrough uses the 5-year general/default period under KRS 500.020 as the applicable baseline for the calculator run.

3) Add economic damages inputs (loss of support and related components)

Next, move to the economic damages fields the wrongful death calculator expects. Field names can vary by tool version, but you’ll commonly see inputs like:

  • Annual income (or wage history basis)
  • Percent of support contributed (or a dependency/support allocation)
  • Projection inputs (such as years of expected support or work-life assumptions)
  • Pre-death loss items (depending on what the calculator includes)

How these inputs generally affect the output:

  • Higher annual income → typically increases projected economic loss.
  • Higher percent of support → typically increases the share allocated to dependents.
  • Longer projection horizon → typically increases the modeled future support stream.

If DocketMath includes a multiplier/dependency duration option, align it with the time window you intend to model (for example, expected years of support vs. any age-based cutoff the tool uses).

4) Add non-economic damages inputs (if supported by the calculator)

Some wrongful death calculators also allow non-economic components. In DocketMath, look for fields that might include:

  • Non-economic damages estimate
  • Caps/limits (only apply if the tool provides Kentucky-specific cap logic or if your jurisdiction data includes it)

If you’re unsure what value to use, a practical approach is to run two scenarios:

  • a low/conservative non-economic estimate
  • a mid/high non-economic estimate

DocketMath’s outputs should update accordingly, helping you see how much of the total is driven by non-economic assumptions versus economic calculations.

5) Run the calculation and interpret the results

Once all required fields are complete:

  1. Click Calculate.
  2. Review the breakdown.

You should expect results such as:

  • Economic damages total
  • Non-economic damages total (if applicable)
  • Total wrongful death damages estimate

Quick sanity checks (especially near the limitations boundary)

  • If you change dates so the run crosses the 5-year mark tied to KRS 500.020, DocketMath may display a timing warning or alter eligibility-related output.
  • If totals shift drastically when you update only one economic assumption (like annual income), that’s a clue your damages are sensitive to that input—use scenario testing to confirm.

6) Compare scenarios to understand sensitivity

To make the model more reliable for planning, run a small set of scenarios:

  • Scenario A (baseline): your best estimate of date of death + planned filing/evaluation date
  • Scenario B (later filing): shift the filing/evaluation date forward by 6–12 months to see whether the 5-year window under KRS 500.020 still applies
  • Scenario C (income update): swap in the best-supported income figure you have

This helps you answer questions like:

  • “Is timing (the 5-year limits rule under KRS 500.020) more important than income assumptions?”
  • “Which input changes move the total the most?”

7) Save or export your outputs

If DocketMath provides export/download or a shareable results view:

  • Save screenshots or export a report for your internal notes.
  • Record which fields you changed in each scenario so your comparisons remain repeatable.
  • Make sure your recorded notes include:
    • Jurisdiction = US-KY
    • Limitations basis = 5-year general/default period under KRS 500.020
    • The main economic/non-economic totals and any warnings

Common pitfalls

These are the most common issues that cause confusing or incorrect runs when using DocketMath for Kentucky wrongful death damages.

  • Using the wrong limitations period

    • For Kentucky in this walkthrough, start from the 5-year general/default period under KRS 500.020.
    • Don’t swap to another period unless DocketMath explicitly supports a different Kentucky wrongful death-specific timing rule—and your jurisdiction data identifies one. (Your provided data did not identify a claim-type-specific sub-rule.)
  • Overriding the default timing without basis

    • Your jurisdiction data indicates no claim-type-specific sub-rule was found.
    • If you override timing assumptions without that support, your output may no longer reflect the stated baseline tied to KRS 500.020.
  • Mixing up dates

    • Entering the incident date when the calculator expects the date of death is a frequent problem.
    • Confusing the evaluation date with the planned filing date can also move you across the 5-year threshold.
    • When you’re near the boundary, double-check both dates carefully.
  • Inconsistent economic inputs

    • If you provide annual income and also add other overlapping wage-loss fields (depending on what the calculator includes), you could effectively double-count assumptions.
    • Keep your economic inputs consistent across scenarios so the comparison remains meaningful.
  • Relying on a single run

    • If your result depends heavily on one or two assumptions (income, support percentage, or the projection horizon), a single run can be misleading.
    • Use at least one comparison scenario to see what actually drives the total.

Warning: If DocketMath shows a timing/limitations warning related to the 5-year period in KRS 500.020, verify your jurisdiction selection and date entries before treating the damages output as reliable.

Try it

Ready to run a first Kentucky (US-KY) scenario in DocketMath?

  1. Set jurisdiction to Kentucky (US-KY).
  2. Enter:
    • Date of death
    • Planned filing date or evaluation date
  3. Add your economic assumptions (for example, annual income basis, support percentage, and any projection inputs the tool requests).
  4. If non-economic inputs are available, try:
    • one reasonable estimate, and optionally
    • a second run with a low vs. mid/high value to see how sensitive the total is
  5. Click Calculate and review:
    • the damages breakdown
    • any timing output tied to the 5-year general/default period under KRS 500.020

Quick checklist for a clean Kentucky run:

Related reading