How to calculate pre/post-offer damages split in Ohio

Quick takeaways

• In Ohio, the pre/post-offer damages split is anchored to Ohio Civ. R. 68 (the offer-of-judgment framework).
• Your post-judgment interest mechanics are governed by Ohio Rev. Code § 1343.03(A), which references Ohio Rev. Code § 5703.47 for the interest calculation method.
• Practically, you’ll use DocketMath’s “pre-post-offer-damages” calculator to:

  1. Split your damages into pre vs post buckets using the dates you provide, and
  2. Apply the Ohio post-judgment interest method where the calculator supports that interest component.

Inputs you need

To calculate a split in DocketMath for US-OH, collect the inputs below before you start.

A. Case timing inputs

• Offer date (the pivot date that separates the “pre” vs “post” allocation window under the Ohio Civ. R. 68 concept)
• Judgment date (the end date for the post period in your allocation window)
• Accrual start date (the first date your damages begin accruing)
• Accrual end date (the last date damages accrue before judgment, if you track damages through a specific end point)

If your damages accrue continuously, these dates define the timeline DocketMath uses to allocate a time-based portion into pre vs post.

B. Damages inputs

• Total damages amount (or separate totals by type, if you track different components)
• Whether any portion is time-based (i.e., it grows/accumulates over time rather than being a one-time fixed amount)

C. Ohio post-judgment interest method inputs

For the interest component, the relevant authorities in your verified packet are:

• Ohio Rev. Code § 1343.03(A), and
• its referenced method in Ohio Rev. Code § 5703.47

Per the verified facts packet, the interest method is described as variable, and the approach is § 1343.03(A) referencing § 5703.47 (described in your packet as federal short-term + 3%).

In other words: if the calculator asks for inputs related to the statutory interest method, ensure they align with the § 1343.03(A) / § 5703.47 framework referenced in your packet.

D. Rule anchor (what the “pre vs post” split is trying to model)

• Ohio Civ. R. 68 is the Ohio procedural rule your calculation should be consistent with for the pre/post separation logic.
• Your goal is to ensure the date boundaries you enter reflect the timeline you want to treat as “before the offer pivot” vs “after the offer pivot.”

How the calculation works

Here’s a practical walkthrough of how DocketMath’s pre-post-offer-damages workflow typically translates your inputs into outputs for Ohio (US-OH), using the verified authorities.

Step 1: Create the allocation timeline from your dates

DocketMath needs a timeline that separates:

• Pre-offer window: from accrual start date up to the offer date
• Post-offer window: from the offer date through the judgment date (or your chosen end boundary)

Because the exact inclusion/exclusion of the offer date can affect results slightly, keep your inputs internally consistent:

• Use one consistent method for “what counts as pre” vs “what counts as post” across your data.
• If your damages begin on a particular day, make sure that day is represented in the correct bucket by the dates you supply.

Step 2: Allocate time-based damages proportionally

If you have a time-based portion of damages, DocketMath can generally split it by the proportion of time in each window:

• Pre-offer damages (time-based)
  = (time in pre window ÷ total time window) × time-based damages

• Post-offer damages (time-based)
  = (time in post window ÷ total time window) × time-based damages

This approach makes the split automatically respond to:

• moving the offer date earlier/later, and
• moving the accrual start/end dates.

Step 3: Treat lump-sum damages carefully (don’t spread unless justified)

If part of your damages is a lump sum (for example, a fixed amount tied to a particular event), you usually should not spread it across time automatically.

Instead, map lump-sum components to the side of the timeline that best matches when they were earned/attributable under your modeling approach. Then enter the appropriately categorized amounts (depending on what DocketMath supports for your input format).

Step 4: Add post-judgment interest using Ohio’s referenced method

After the principal damages split, the calculator’s interest component (when enabled) should follow the Ohio statutory framework identified in your verified packet:

• Ohio Rev. Code § 1343.03(A) provides the post-judgment interest approach and references Ohio Rev. Code § 5703.47 for the method.

The key is separation of concepts:

• The pre/post damages split is an allocation concept across windows tied to Ohio Civ. R. 68 logic.
• Post-judgment interest is an additional statutory calculation tied to § 1343.03(A) and the § 5703.47 method reference.

Step 5: Interpret outputs

DocketMath should provide (at minimum conceptually):

• Pre-offer damages (principal damages attributable to the pre window)
• Post-offer damages (principal damages attributable to the post window)
• Post-judgment interest (computed per the Ohio statutory method reference the calculator uses for US-OH)

If you input segmented totals, the calculator may provide a more granular breakdown—use the same date boundaries so the components align.

Common pitfalls

1. Confusing the pre/post split with interest

   • Pre/post allocation is about distributing principal damages across windows.
   • Post-judgment interest is a separate statutory calculation under Ohio Rev. Code § 1343.03(A) referencing § 5703.47.

2. Using the wrong timeline boundaries

   • If you set accrual start date too late, you understate pre-offer and overstate post-offer.
   • If you set judgment date incorrectly, you misstate the post window.

3. Off-by-one errors around the offer date

   • Because the offer date is the pivot, small date handling differences can shift the proportion of time between buckets for time-based damages.

4. Spreading lump-sum damages across the timeline

   • If a component is truly lump-sum, proportional time allocation can distort the pre/post split.

5. Assuming the calculator requires—or assumes—the availability of Rule 68 offers

   • Your verified facts packet says offer_of_judgment_available: false. Even so, the mechanics described here are about how to structure the calculation and interpret results, not about whether the rule applies to your specific matter.

Sources and references

• Ohio Civ. R. 68
  https://www.supremecourt.ohio.gov/LegalResources/Rules/civil/CivilProcedure.pdf
• Ohio Rev. Code § 1343.03(A)
  https://codes.ohio.gov/ohio-revised-code/section-1343.03
• Ohio Rev. Code § 5703.47
  https://codes.ohio.gov/ohio-revised-code/section-5703.47

Next steps

1. Open DocketMath’s Ohio pre/post calculator:
   /tools/pre-post-offer-damages
2. Enter timeline inputs:

   • accrual start date
   • offer date
   • judgment date
   • (and accrual end date if applicable in your workflow)
3. Enter damages:

   • total amount (and split into time-based vs lump-sum components if you can)
4. Confirm interest mechanics (if the calculator includes an interest section):

   • ensure the configured method aligns with § 1343.03(A) and its reference to § 5703.47.
5. Review results:

   • pre-offer damages
   • post-offer damages
   • post-judgment interest

This is a practical guide for running the calculation and structuring inputs. It is not legal advice.

Related reading

• How to calculate pre/post-offer damages split in California — Full how-to guide with jurisdiction-specific rules
• How to calculate pre/post-offer damages split in Florida — Full how-to guide with jurisdiction-specific rules
• How to calculate pre/post-offer damages split in New York — Full how-to guide with jurisdiction-specific rules