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

Quick takeaways

• Oklahoma’s pre/post-offer damages split is anchored in Okla. Stat. tit. 12, § 1101.1, which sets the framework for offers of judgment made after a petition is filed and before trial, and the cost/interest consequences if the offer is not accepted and the verdict awards less than the offer.
• In the cited materials, the timing rule appears to be a general/default rule (no claim-type-specific sub-rule was found). That means the split boundary you model is based on the statutory “after petition / before trial” concept rather than a special rule for particular damages categories.
• Using DocketMath, you typically compute two buckets:

  • Pre-offer damages: the portion of the eventual damages attributable to the time before the offer’s effective boundary
  • Post-offer damages: the portion attributable to the time after that boundary
• Your final split is only as good as your time/allocation assumptions (for example, linear accrual vs. event-based accrual). Treat your allocation method as an input, not a “given.”
• Note: This article explains a calculation workflow and the Oklahoma rule conceptually, not legal advice.

Inputs you need

To calculate a pre/post-offer damages split for US-OK (Oklahoma) in DocketMath, collect the inputs below. If you don’t have a fully developed damages timeline yet, you can still run a first-pass split and refine it as you gather supporting records.

Offer and timing inputs (Oklahoma offer-of-judgment framework)

• Offer serving/effective boundary date

  • Use the offer’s serving date (or the date your workflow treats as the boundary) as the “pre vs. post” cutoff.
• Statutory timing anchor (how to think about the boundary)

  • Okla. Stat. tit. 12, § 1101.1 frames offers as being made “after a petition has been filed and prior to trial.”
  • Practically, for a split calculation, that means you should align your model’s boundary with the offer’s relevant date (not the petition filing date or the trial start date).
• Total damages figure (the number you’ll split)

  • The final amount you’re splitting (often based on the verdict or another final damages determination amount you’re modeling).

Source for statutory anchor: Okla. Stat. tit. 12, § 1101.1 (via OSCN)
https://www.oscn.net/applications/oscn/DeliverDocument.asp?CiteID=438873

Damages timeline inputs

You need a way to allocate total damages across time. Choose an approach that matches how the damages actually accrue.

Pick one approach (or use a hybrid where different components behave differently):

• Linear accrual (often used for lost earnings-type damages)

  • Start date of accrual
  • End/through date of accrual
  • Offer boundary date (from above) to determine how much time falls pre vs. post
• Event-based allocation (often used where damages hinge on discrete treatment events, incidents, or episodes)

  • Date(s) of damage-triggering events
  • Dollar amounts (or proxies) linked to each event
  • Which events fall before vs. after the offer boundary
• Custom schedule (best when you already have a month-by-month or bill-by-bill structure)

  • A schedule of dated amounts (e.g., medical expenses by month)
  • A rule for summing all amounts before the boundary vs. on/after the boundary

Optional inputs (helpful for accuracy and auditability)

• Rounding rules (e.g., round dollars at the end to 2 decimals)
• Damages components included in “total damages”

  • Make sure your “total” matches the exact set of components you intend to split (so pre + post corresponds to the same definition of damages throughout).
• Treatment of boundary day

  • Decide whether the offer date itself is treated as pre-offer or post-offer within your workflow (then apply it consistently).

How the calculation works

DocketMath turns your allocation method and dates into two outputs:

• Pre-offer damages = damages attributable to the period before the boundary date
• Post-offer damages = damages attributable to the period after the boundary date

Oklahoma’s statute supplies the procedural timing concept for offers—after petition and before trial—which you translate into the practical “before vs. after” boundary in your calculation model.

1) Oklahoma’s governing rule (timing anchor)

Under Okla. Stat. tit. 12, § 1101.1, after a petition is filed and before trial, a party may serve an offer of judgment for a sum certain. If the offer is not accepted and the verdict awards damages less than the offer, the statute describes cost/interest consequences.

For your modeling purpose, the key takeaway is the timing constraint: offers occur in the period after petition filing and before trial. That helps justify using an offer serving/effective date as your split boundary, rather than dates like petition filing or trial commencement.

OSCN source:
https://www.oscn.net/applications/oscn/DeliverDocument.asp?CiteID=438873

2) Choose your allocation model (how DocketMath maps to your data)

Option A: Linear accrual split (time-based)

If damages accrue steadily from Start to End:

1. Total days = End - Start
2. Pre-offer days = Offer boundary - Start
3. Post-offer days = End - Offer boundary
4. Allocate proportionally:

• Pre-offer damages = Total damages × (Pre-offer days / Total days)
• Post-offer damages = Total damages × (Post-offer days / Total days)

Then apply your rounding rules.

Option B: Event-based allocation

If damages are tied to discrete events:

• Sum the dollar amounts (or apportioned values) of events that occur before the boundary → Pre-offer
• Sum the dollar amounts (or apportioned values) of events that occur after the boundary → Post-offer

Option C: Custom schedule

If you have a dated schedule:

• Add up all scheduled amounts with dates before the boundary → Pre-offer
• Add up all scheduled amounts with dates on/after the boundary → Post-offer

3) Reconcile edge cases (where splits can drift)

Common decisions you should make up front:

• Inclusion of the boundary day

  • Example: Is the offer serving date treated as pre-offer or post-offer?
• Partial-day timing

  • If your data includes times (not just dates), DocketMath may require date-based decisions. Use a consistent policy (e.g., treat any time on the offer date as post-offer).
• Gaps/missing records

  • If the timeline is incomplete, you may need assumptions or ranges. At minimum, document the allocation logic you used.

A practical approach: record the policy choices (boundary inclusion, accrual method, rounding) alongside the run so the model is explainable.

4) Sanity checks (confirm your split is internally consistent)

Before accepting the output:

• Sum check: Pre-offer + Post-offer ≈ Total damages (within rounding tolerance)
• Boundary behavior:

  • If offer boundary is before damages start → pre-offer should be 0
  • If offer boundary is after damages end → post-offer should be 0
• Model fit check:

  • Linear accrual should make sense only if damages truly accumulate steadily; otherwise, consider event-based or custom schedules.

Common pitfalls

• Using the wrong boundary date

  • Splitting by petition filed date or trial start instead of the offer serving/effective date your split model uses.
• Assuming claim-type-specific timing rules exist

  • In the cited materials provided, no claim-type-specific sub-rule was found. The statute is a general offer framework for after petition and before trial. If you add special allocation rules for specific claims, ensure you have supporting authority (and don’t assume).
• Applying linear accrual to lumpy damages

  • Medical treatment, episodic losses, or event-triggered costs may not accrue proportionally over time.
• Mixing inconsistent definitions of “total damages”

  • If your “total damages” includes items you don’t plan to split (or excludes items you think you included), your pre/post math won’t match the intended damages concept.
• Rounding too early

  • Rounding intermediate calculations can cause the sum check to fail by a few dollars. If needed, round only at the end.

Sources and references

• Okla. Stat. tit. 12, § 1101.1 (offer of judgment; after petition and prior to trial; consequences if verdict awards less than the offer)
  https://www.oscn.net/applications/oscn/DeliverDocument.asp?CiteID=438873

• TODO: Confirm whether Oklahoma courts or other guidance address how to operationalize pre/post splits for specific damages components beyond the statutory framework. (Use this guide for the general conceptual split workflow only unless additional authority is identified.)

Next steps

1. Open DocketMath for this workflow at: /tools/pre-post-offer-damages
2. Pick your allocation method (linear, event-based, or custom schedule) based on how the damages actually accrue.
3. Collect the key dates:

   • damages start date
   • offer serving/effective boundary date (your pre/post cutoff)
   • damages end/through date (or event dates)
4. Run the split and capture:

   • **Pre-offer