Pre/Post-Offer Damages Split Guide for Ohio

What this calculator does

Run this scenario in DocketMath using the Pre Post Offer Damages calculator.

DocketMath’s Pre/Post-Offer Damages Split Guide for Ohio helps you break a damages amount into two time-based buckets:

• Pre-offer period damages: damages “as of” the time of an offer (commonly used in analysis tied to offer-related cost-shifting frameworks).
• Post-offer period damages: damages accruing after the offer date.

Because your goal is usually to determine which portion of damages falls before vs. after the offer, the tool centers on the date split, and then applies a chosen daily accrual approach (for example, simple interest-style accrual or a per-day earnings/expense model you provide).

Ohio timing rule used in this guide (general/default)

Ohio Rev. Code § 2901.13 provides the general limitations period for many civil actions. This guide uses it as the default period when a claim-specific sub-rule isn’t provided.

• General SOL period (default): 0.5 years
• Statute: Ohio Rev. Code § 2901.13
• Source: https://codes.ohio.gov/assets/laws/revised-code/authenticated/29/2901.13/7-16-2015/2901.13-7-16-2015.pdf
• Important: No claim-type-specific sub-rule was found in the provided jurisdiction data. This guide treats § 2901.13’s general/default period as the governing one for the timing split unless you have a different, claim-specific limitations rule.

When to use it

Use this guide (and DocketMath’s /tools/pre-post-offer-damages) when you need a clean pre/offer vs. post/offer damages allocation in Ohio and you want the calculation to reflect a defined default time horizon.

Common use cases

• Offer-related cost or damages analysis where you compare amounts before and after a particular offer date.
• Case budgeting where you estimate how much exposure grows after an offer date under a daily accrual assumption.
• Settlement documentation that requires consistent, date-based math you can show in an exhibit or spreadsheet.

Practical triggers checklist

Step-by-step example

Below is a worked example showing how you can use the DocketMath approach and how changing inputs changes the output. You can run the same logic in DocketMath’s calculator via this link: /tools/pre-post-offer-damages.

Example inputs (for illustration)

• Offer date: 2026-01-15
• Start date (accrual measurement begins): 2025-12-15
• End of accrual measurement date (what you’re calculating through): 2026-03-15
• Daily accrual amount: $120/day
• Default limitations timing anchor used for horizon-checking: 0.5 years under Ohio Rev. Code § 2901.13

Important: The calculator primarily does math split by date. It won’t “decide” what is legally recoverable for your claim. Use the limitation horizon check separately.

Step 1: Define the date range you’re splitting

You’re splitting damages accrual into two buckets:

1. Pre-offer bucket: from the start of your measurement period up to but not including the offer date (typical convention).
2. Post-offer bucket: from the offer date through the end of your measurement period (inclusive or exclusive depending on your convention—be consistent).

For this example:

• Start date: 2025-12-15
• Offer date: 2026-01-15
• End date: 2026-03-15

Step 2: Count days pre-offer and post-offer

Use one “day-count convention” and document it. A common approach is:

• Pre excludes the offer date
• Post includes the offer date

Under that convention:

• Pre-offer days: 2025-12-15 through 2026-01-14
• Post-offer days: 2026-01-15 through 2026-03-15

Now compute counts (and keep your convention consistent across exhibits):

• Pre-offer: 31 days (Dec 15–Dec 31 = 17 days; Jan 1–Jan 14 = 14 days; total = 31)
• Post-offer: 61 days (Jan 15–Jan 31 = 17; Feb = 29 days in 2026; Mar 1–Mar 15 = 15; total = 61)

If your spreadsheet counts differently, you’ll see a 1-day difference. That’s why the convention matters.

Step 3: Apply the daily accrual rate

Daily accrual = $120/day

• Pre-offer damages = Pre days × $120

  • 31 × $120 = $3,720

• Post-offer damages = Post days × $120

  • 61 × $120 = $7,320

• Total damages = $3,720 + $7,320 = $11,040

Step 4: Horizon check against the default § 2901.13 period (0.5 years)

This is a modeling check—not an automatic legal determination.

• Ohio Rev. Code § 2901.13 is used here as the general/default limitations anchor (0.5 years based on the jurisdiction data).
• If your measurement window spans more than ~6 months, you may choose to narrow the dates in your model to align with the portion you are treating as within the default limitations horizon.

Step 5: Translate inputs into DocketMath outputs

The calculator will return, in substance:

• Pre-offer damages
• Post-offer damages
• Total damages
• Often, day counts feeding those numbers (depending on the tool’s interface)

If you change the daily accrual amount (for example, $120/day → $150/day), both buckets rise proportionally; the split still depends primarily on your day counts.

Common scenarios

The value of a pre/post split is highest when you handle edge cases consistently. Here are common Ohio-focused scenarios you might model with DocketMath.

Scenario 1: Same offer date, different end dates

• Offer date stays fixed.
• End date moves (you measure accrual longer/shorter).

Effect: post-offer damages changes; pre-offer damages stays the same.

Example:

• Offer date: 2026-01-15
• End date A: 2026-02-15 → fewer post days
• End date B: 2026-03-15 → more post days

Result:

• Pre-offer = same
• Post-offer = larger in B
• Total = larger in B

Scenario 2: Daily accrual rate changes over time

If your damages aren’t linear, don’t force a single daily rate across the entire timeline. A practical workaround is to run multiple calculations for different phases and sum results.

Typical approach:

• Run Calculation #1 for Phase 1 (start → rate-change date)
• Run Calculation #2 for Phase 2 (rate-change date → end)
• Add pre/post outputs across the phases

Scenario 3: Offer date equals the start date

• Start date = offer date

Effect: pre-offer days become 0; post-offer becomes the entire measured period.

This is useful for modeling situations where the offer is treated as the pivot from which accrual is calculated.

Scenario 4: Measurement window exceeds the default limitations horizon

Because this guide uses § 2901.13 as the default (0.5 years), you may choose to align your measurement window accordingly.

Effect (modeling):

• Full window: outputs reflect accrual across the whole span.
• Narrowed to ~0.5 years: outputs reflect only the portion within that default horizon.

Since the provided data does not include claim-specific sub-rules, this guide can’t determine what portions are legally recoverable—it only helps you structure the math consistently.

Scenario 5: Inclusive/exclusive offer date conventions

Even when dates seem clear, different day-count conventions can shift totals by one day.

To prevent drift:

• Choose one convention (for example, post includes offer date)
• Apply it in the calculator
• Mirror it in your exhibit language and any spreadsheet summary

Tips for accuracy

Accuracy here is mostly about disciplined inputs and consistent conventions.

1) Use consistent date formats and avoid time-zone surprises

• Enter dates as calendar dates (YYYY-MM-DD).
• If you’re using a spreadsheet, confirm it’s using whole days rather than timestamps.

2) Document your day-count convention

Pick one and use it everywhere, such as:

• Pre excludes offer date
• Post includes offer date

Then note it in your work

Related reading

• Pre/Post-Offer Damages Split Guide for Alabama
• Pre/Post-Offer Damages Split Guide for Arizona
• Pre/Post-Offer Damages Split Guide for Colorado