Pre/Post-Offer Damages Split Guide for Kentucky
7 min read
Published March 22, 2026 • By DocketMath Team
What this calculator does
Run this scenario in DocketMath using the Pre Post Offer Damages calculator.
DocketMath’s Pre/Post-Offer Damages Split (Kentucky) tool helps you separate claimed damages into two buckets:
- Pre-offer damages: amounts that accrued before a qualifying settlement offer date
- Post-offer damages: amounts that accrued on/after that offer date
This split is often necessary because Kentucky’s offer-related rules can change what portions of damages (and related costs/interest) may be recoverable depending on when the offer was made and how the case resolves.
DocketMath uses Kentucky’s timing framework based on the applicable statute of limitations, and then supports a date-based damage accrual split you can apply to your own damages proof (e.g., medical bills, lost wages, property damage, or other time-sensitive figures).
Note: This guide focuses on how to structure a pre/post-offer damages timeline and align it with Kentucky’s limitations periods. It is not legal advice.
When to use it
Use this guide and DocketMath’s calculator when you have any claim where a settlement offer date matters to the damage recovery picture, and you need a defensible split between:
- Before the offer (damages that accrued earlier)
- After the offer (damages that accrued later)
You should consider using the tool if you have:
- A known offer date (or a date you can treat as the offer’s effective date for your internal accounting)
- A timeline of damages that spans time (not a single lump-sum item)
- Damages that continue to accrue after the offer (e.g., ongoing wage loss, continuing treatment costs, accruing interest components where tracked by time)
- A need to apply Kentucky’s limitations rules to ensure you’re not including time-barred amounts in either bucket
Limitations framework Kentucky uses here
Kentucky’s limitations period matters because it defines how far back you may effectively claim damages. The following provisions are commonly referenced in Kentucky timing work:
| Kentucky provision | Limitation period shown in this guide | “Exception” callouts in this guide |
|---|---|---|
| KRS 500.020 | 5 years | Exception P3 |
| KRS 500.050 | 5 years | Exception P2 |
| KRS 500.050 | 1 years | Exception P4 |
| KRS 500.050(2) | 1 years | Exception V3 |
| Ky. Rev. Stat. § 355.2-725 | 5 years | Exception D3 |
DocketMath’s pre/post-offer damages split workflow is built to help you track:
- the offer date
- the start date for claimable damages consistent with the limitations framework you’re using
- how much total damages fall into each bucket
Step-by-step example
Below is a practical walkthrough using a hypothetical Kentucky case. You can mirror the structure with your real dates and your damages timeline.
Scenario
- Settlement offer date: March 1, 2023
- Filing/claim date (for your own limits analysis): March 1, 2026
- Damages accrue monthly from January 1, 2021 through December 31, 2024
- Monthly damages amount (for simplicity): $2,000/month
- Assume the damages are governed by a 5-year limitations period for the relevant type of claim in your analysis (one of the 5-year buckets reflected above)
Warning: You must match the correct limitations provision to the claim type you’re valuing. This walkthrough assumes a 5-year period because the split mechanics are easiest to show. If you’re dealing with a 1-year bucket, your pre-offer window changes substantially.
Step 1: Choose the limitations start date
A 5-year limitations period under KRS 500.020 (5 years, exception P3 callout) or KRS 500.050 (5 years, exception P2 callout) or Ky. Rev. Stat. § 355.2-725 (5 years, exception D3 callout) would commonly be handled as:
- Start of claimable window = Filing/claim date minus 5 years
- If filing date is March 1, 2026, then:
- Claimable start date ≈ March 1, 2021
Because your damages accrue starting January 1, 2021, only the portion from March 1, 2021 onward is potentially within the limitations window in this simplified example.
Step 2: Build a damages timeline that can be split
Your damages accrue monthly:
- Jan 2021 … Dec 2024 (48 months total in the full range)
- But you will likely only count from March 1, 2021 through Dec 31, 2024:
- That’s Mar 2021–Dec 2024 = 46 months
Now split at the offer date:
- Pre-offer: from March 2021 through Feb 2023
- Post-offer: from March 2023 through Dec 2024
Step 3: Count months (or time units) in each bucket
Pre-offer months: Mar 2021–Feb 2023
- Mar–Dec 2021 = 10 months
- Jan–Dec 2022 = 12 months
- Jan–Feb 2023 = 2 months
- Total pre-offer = 24 months
Post-offer months: Mar 2023–Dec 2024
- Mar–Dec 2023 = 10 months
- Jan–Dec 2024 = 12 months
- Total post-offer = 22 months
(Pre + post = 46 months total within limitations window.)
Step 4: Compute bucket totals
Using $2,000/month:
- Pre-offer damages: 24 × $2,000 = $48,000
- Post-offer damages: 22 × $2,000 = $44,000
- Total damages (in window): $92,000
Step 5: Input into DocketMath’s calculator
In practice, DocketMath’s workflow is designed to take your dates and compute the split. You’d typically provide:
- Offer date: 2023-03-01
- Damages accrual start date: 2021-03-01 (adjusted for limitations window)
- Damages accrual end date: 2024-12-31
- Damages rate / schedule: $2,000 per month (or an equivalent time-based schedule)
- Limitations mode: select the relevant 5-year framework you’re applying (from the Kentucky provisions listed in this guide)
Then DocketMath outputs:
- Pre-offer total
- Post-offer total
- Supporting breakdown by time period so you can reconcile against your itemized damages chart
What the output means
When you split damages this way, you can align the pre/post totals with whatever Kentucky offer-related consequence you’re analyzing in your own workflow (e.g., how the offer changes what may be recoverable for portions accruing after the offer).
Common scenarios
Below are recurring patterns in Kentucky cases where a pre/post-offer split is especially useful.
Scenario A: Ongoing economic damages (lost wages or treatment continuing after offer)
Symptoms:
- Your damages are not fully “done” as of the offer date.
- Bills, wage loss, or other accrual continues.
How the split behaves:
- Pre-offer bucket contains months ending before the offer date.
- Post-offer bucket contains months on/after the offer date.
✅ Best practice:
Use a monthly (or weekly) accrual log so the split doesn’t depend on intuition.
Scenario B: One-time costs mixed with time-based components
You may have:
- A lump-sum component (e.g., a fixed property repair invoice)
- A time-based component (e.g., follow-up treatment sessions)
How to handle in a split:
- Lump-sum amounts can be assigned to the month/period the cost is incurred.
- Time-based amounts naturally fall into pre vs post based on accrual.
Checklist for your spreadsheet before you run DocketMath:
Scenario C: Limits-driven “missing months” in the pre-offer bucket
Kentucky limitations can cause older damages to be excluded even if they accrued before the offer.
This guide highlights multiple limitation windows:
- 5-year buckets under KRS 500.020 (exception P3), KRS 500.050 (exception P2), and Ky. Rev. Stat. § 355.2-725 (exception D3)
- 1-year buckets under KRS 500.050 (exception P4) and KRS 500.050(2) (exception V3)
Common result:
- Your pre-offer bucket may be smaller than expected because claimable dates start later than the earliest accrual date you tracked.
✅ Best practice:
Derive the claimable accrual start date from the limitations period you’re using (then split at the offer date).
Pitfall: If you accidentally use the earliest accrual date (e.g., January 1, 2020) even though limitations only allow claims back to (for example) March 1, 2021, your pre-offer total will be overstated and your split will be harder to defend.
Scenario D: Disputes about what “offer date” means for your accounting
Even when everyone agrees an offer was made, parties sometimes disagree
Sources and references
Start with the primary authority for Kentucky and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.