Offer of Judgment Analyzer Guide for Kentucky

What this calculator does

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

DocketMath’s Offer of Judgment Analyzer (Kentucky) helps you estimate the potential financial impact of a Kentucky offer of judgment under Ky. R. Civ. P. 68. In plain terms, it’s designed to answer:

• If I make (or receive) an offer, how might the cost-shifting rules affect the case if the offer is accepted or not beaten at trial?

This guide focuses on the mechanics you typically see in litigation involving Ky. R. Civ. P. 68 offers. It’s not legal advice; think of it as a practical calculator workflow and scenario explainer so you can understand how the numbers often map to the rule.

At a high level, Kentucky’s Rule 68 allows a party to serve an offer “at any time more than thirty (30) days before the trial.” That timing trigger comes directly from Ky. R. Civ. P. 68:

“At any time more than thirty (30) days before the trial, a party may serve upon any other party an offer to allow judgment to be taken…”
(see Ky. R. Civ. P. 68 via Justia: https://law.justia.com/codes/kentucky/2013/chapter-68/68-010/)

The calculator (access it here) is the /tools/offer-of-judgment-analyzer workflow you’ll use to explore outcomes. Start with:

• /tools/offer-of-judgment-analyzer

Key rule components referenced in Kentucky practice

• Timing: Must be served more than 30 days before trial (Ky. R. Civ. P. 68).
• Subsections that govern mechanics: the rule’s related parts—Ky. R. Civ. P. 68.03 and Ky. R. Civ. P. 68.04—are where courts address how offers work and the consequences for costs and potentially other judgment-linked components (depending on how the judgment is framed).

When to use it

Use DocketMath’s Offer of Judgment Analyzer when you’re dealing with the practical decision points that usually surround a Rule 68 offer. Common triggers include:

• You’re considering making an offer and want to gauge whether the target number creates meaningful leverage.
• You received a Rule 68 offer and you want to understand how “beating” (or not beating) the offer might affect costs.
• You’re mid-case and you’re updating an estimate of the likely verdict range (e.g., after depositions, discovery, or expert reports).
• You have partial information but want to explore multiple outcomes (best case / expected case / worst case) using the calculator’s input scenarios.

Practical timing check (before you even run numbers)

Because Ky. R. Civ. P. 68 requires service more than 30 days before trial, you should verify:

• Offer service date
• Trial date (or the scheduled trial date that matters for the filing/serving timeline)

Then compare:

• If offer date ≤ trial date minus 30 days, you may be outside the rule’s core timing requirement.

Even if your goal is budgeting—not litigation strategy—the 30-day requirement is often the difference between a workable offer and one that becomes more vulnerable.

Step-by-step example

Below is a realistic walkthrough using the calculator’s logic. Since the exact financial effect depends on how the judgment compares to the offer and how Ky. R. Civ. P. 68.03 / 68.04 apply in your case posture, this example models the comparison-based payoff: “Did the result beat the offer?”

Step 1: Gather your inputs

You’ll typically need these kinds of values (the calculator will guide the exact fields you enter):

• Offer amount (the dollar figure stated in the offer)
• Your expected/estimated trial judgment amount (or the “actual” judgment if you’re post-verdict modeling)
• Relevant timing (offer served date and trial date) so you can sanity-check the >30 days before trial requirement under Ky. R. Civ. P. 68
• Any known cost components you want included in your model (if the tool asks for them)

Step 2: Confirm timing passes the Ky. R. Civ. P. 68 threshold

Ky. R. Civ. P. 68 says an offer may be served “more than thirty (30) days before the trial.” (Ky. R. Civ. P. 68; Justia link above)

Example:

• Offer served: March 1, 2026
• Trial date: May 15, 2026
• Days between: roughly 75 days
• Result: timing condition is met (based on the scheduled dates you input)

Step 3: Model a likely outcome vs. the offer

Assume:

• Offer amount: $50,000
• Predicted judgment: $62,000 (plaintiff-side prediction)
• Comparison: judgment is higher than the offer

Now run the calculator and observe what it reports:

• Whether the comparison triggers the cost-shifting consequence you’re modeling
• The estimated dollar impact based on your entered costs and judgment terms

Step 4: Repeat with alternative judgment values

A strong calculator workflow includes “what if” runs. Keep everything the same, but change only the judgment estimate.

Step 5: Interpret the output conservatively

DocketMath’s analyzer is meant to help you compare outcomes numerically. Treat outputs as planning estimates:

• If the judgment estimate changes by even 10–20%, the “beat the offer” status could change.
• If costs figures are incomplete, the dollar impact could be materially different.

Common scenarios

Offer-of-judgment fights in Kentucky typically land in a few recurring patterns. Here are scenarios where the calculator tends to be most useful.

1) You’re the offeror with a strong damages case

If you believe the trier of fact is likely to award at least the offer amount, you can model:

• A judgment that beats your offer
• The cost-shifting effect if the offer is not accepted

Focus input discipline:

• Use a range for judgment outcomes
• Don’t assume “likely” equals “certain”—run at least 3 estimates

2) You’re the offeree trying to decide whether to reject

If you received an offer, the calculator helps you understand:

• How close your expected judgment is to the offer amount
• The effect of being slightly above vs. slightly below the offer

Checklist:

• Are you realistically within single-digit percentage variance?
• If so, small forecast errors can flip the “beat” outcome.

3) Multi-claim cases (one offer vs. multiple issues)

If the case has multiple claims, parties sometimes craft an offer tied to a specific “effect” or component.

DocketMath can still help you, but you must be careful that:

• Offer amount corresponds to the same judgment basis you’re forecasting
• The modeled “expected judgment” is aligned to what the final judgment actually reflects

4) Timing-sensitive decisions near trial

Because Ky. R. Civ. P. 68 requires service more than 30 days before trial, timing can be a decisive factor.

Use the calculator workflow to:

• Verify whether the timeline you’re considering clears the 30-day threshold
• Model outcomes only after confirming the procedural feasibility

Tips for accuracy

To get outputs you can trust for comparison purposes, tighten the following areas before you run the analyzer.

Input hygiene checklist

Use multiple runs, not one

At minimum, run:

This approach shows whether the “beat the offer” outcome is stable or fragile.

Tie handling

If your case could land near the offer amount, create one extra run:

Then compare that output with your “beat” and “miss” cases.

Because cost-shifting standards in Rule 68 frameworks often turn on “more than,” “less than,” or “at least,” ties can behave differently than wins or losses.

Reference the rule language on timing

Before relying on any numbers, anchor to the core requirement:

• Ky. R. Civ. P. 68 allows service “at any time more than thirty (30) days before the trial.”

Related

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for California