Pre/Post-Offer Damages Split Guide for Oklahoma

7 min read

Published March 22, 2026 • Updated April 8, 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 Guide (Oklahoma) helps you divide total damages that accrue over time into two buckets based on the timing of an offer:

  • Pre-offer damages: amounts that accrued on or before the offer date
  • Post-offer damages: amounts that accrued after the offer date

The goal is to create a clear line between what happened up to the offer and what happened after, which is especially useful when damages continue to grow over time (for example, time-based losses, repeated payments, or scheduled accruals).

This guide uses Oklahoma’s general/default statute of limitations (SOL) period for the timing context described in the jurisdiction data: 1 year, under 22 O.S. § 152. The provided jurisdiction data did not identify any claim-type-specific sub-rule, so this guide clearly uses the general/default rule rather than attempting to invent a specialized SOL for a particular damages category.

Note: This post focuses on how to split time-based damages using DocketMath’s calculator approach. It does not replace case-specific legal analysis, and limitations/timing rules can vary depending on the procedural posture and the claims at issue.

Primary CTA: /tools/pre-post-offer-damages

Quick reference: the two buckets

BucketTime anchorWhat it represents
Pre-offerAccrual dates ≤ offer dateSum of damages earned/available up to the offer
Post-offerAccrual dates > offer dateSum of damages earned after the offer

Why the split matters

A pre/post-offer damages split can affect:

  • how you present damages to the court (or in settlement discussions),
  • settlement value negotiations (often anchored to what was knowable/arguable at the offer time),
  • and any downstream calculations that depend on when amounts accrued.

When to use it

Use this guide and calculator when all of the following are true:

  • Your damages accrue over time (not a single lump sum that fully exists at filing).
  • You have an offer date that creates a logical pivot point.
  • You need to present or compute how much of the total damages belongs before that pivot and how much belongs after.

Typical Oklahoma-driven timing setups

  • Staged accrual: monthly amounts, continuing accrual-like components, or schedules that increase each month
  • Multiple accrual events: recurring costs/payments where each occurrence can be attributed to a pre- or post-offer period
  • Offer comparisons: where counsel wants to show how damages changed after the offer

SOL context for Oklahoma (general/default rule)

If your workflow includes a “lookback” period tied to statutes of limitation, the default timing anchor described in the provided jurisdiction data is:

  • 1 year SOL under 22 O.S. § 152 (general rule)
  • The jurisdiction data did not identify a claim-type-specific SOL sub-rule. Therefore, this guide treats 22 O.S. § 152’s general/default period as the baseline and does not attempt a specialized exception.

Source (general overview): https://www.findlaw.com/state/oklahoma-law/oklahoma-criminal-statute-of-limitations-laws.html

Pitfall: Don’t assume the 1-year SOL automatically controls every damages component in every procedural posture. This guide uses the general/default SOL period from the provided data, but the actual limitations regime can still depend on the type of action and claims involved.

Step-by-step example

Below is a concrete walkthrough showing how to split damages using DocketMath. The calculator workflow typically boils down to: (1) your accrual timeline, (2) the offer date, and (3) how damages accrue (daily/monthly/event-based).

Hypothetical facts (for illustration)

  • Start date of damages accrual: March 1, 2025
  • End date for damages computation: June 30, 2025
  • Offer date: April 15, 2025
  • Accrual rate: $500 per month, pro-rated by day for partial months

Your goal is to:

  1. Calculate total damages from 3/1/2025 through 6/30/2025
  2. Split them into:
    • Pre-offer: 3/1/2025 through 4/15/2025
    • Post-offer: 4/16/2025 through 6/30/2025

Step 1: Identify the boundaries

  • Pre-offer period: 3/1/2025–4/15/2025
  • Post-offer period: 4/16/2025–6/30/2025

Using one day after the offer date as the start of post-offer prevents double counting when you use a day-based accrual model.

Step 2: Convert the accrual method into pro-ration logic

Because the example uses “$500 per month,” you need a consistent pro-ration approach for partial months. DocketMath’s split conceptually treats time proportionally (days within sub-periods).

For illustration (not legal advice), assume:

  • prorate by (days in sub-period) / (days in month)
  • use the same rule consistently for both pre and post

Step 3: Compute sub-period damages

Pre-offer ($500/month pro-rated):

  • March 1–31: full month = $500
  • April 1–15: 15 days in April
    • $500 × (15/30) = $250

Pre-offer subtotal: $500 + $250 = $750

Post-offer:

  • April 16–30: 15 days in April
    • $500 × (15/30) = $250
  • May 1–31: full month = $500
  • June 1–30: full month = $500

Post-offer subtotal: $250 + $500 + $500 = $1,250

Total damages (window): $750 + $1,250 = $2,000

Step 4: Enter into DocketMath (calculator mindset)

In DocketMath, you’re providing the calculator enough structure to apply the same split rule across your accrual timeline, typically including:

  • the accrual window (start and end dates),
  • the offer date (pivot),
  • and the accrual model (monthly rate with pro-ration, daily rate, or an event schedule).

Output you should expect to reconcile:

  • Pre-offer damages = $750
  • Post-offer damages = $1,250
  • (often) a combined total = $2,000

Note: If your damages are event-based (e.g., “$X occurs each time condition Y happens”), you’ll generally input the event schedule rather than a monthly rate. The pre/post split still works by comparing each event date to the offer date.

Step 5: Reconcile totals (best practice)

After running the calculation:

  • confirm pre + post = total for the same measurement window
  • if the numbers don’t reconcile, the most common causes are:
    • an off-by-one-day offer boundary,
    • a missing accrual day,
    • or inconsistent pro-ration/inclusivity rules

Common scenarios

These are realistic setups you’ll commonly see when splitting damages into pre/post buckets in Oklahoma-related workflows.

1) Monthly payment losses with a clear offer date

Pattern: $A per month; offer lands on a calendar date.
Split: pro-rate the partial month containing the offer.

Checklist:

2) Daily accrual (interest-like or continuing costs)

Pattern: $B per day from a start to an end date.
Split: multiply the daily rate by the number of days in each sub-period (pre vs. post).

Checklist:

3) One-time damages with “continuation”

Pattern: a core lump sum exists, but additional amounts accrue after an event.
Split:

  • Put the portion that was already incurred by the offer date into pre-offer
  • Put the portion that accrues after the offer date into post-offer

Checklist:

4) Multiple offers (and you want the pivot rule consistent)

Pattern: there are multiple offers (e.g., an initial offer and a revised offer).
Split options:

  • use the first offer as the split pivot, or
  • use the last offer as the pivot,

depending on what you are trying to show.

Checklist:

Warning: Don’t mix pivot dates inside the same calculation. If you split some components at one offer date and others at another, your totals may not reconcile cleanly.

5) SOL-driven cutoffs integrated into damages windows

Pattern: you may limit the computation window based on SOL lookback.
Using the provided Oklahoma general/default SOL:

  • default lookback period: 1 year under 22 O.S. § 152

Checklist:

Tips for accuracy

These practical steps help reduce common errors when splitting pre/post damages with DocketMath.

1) Treat the offer date boundary consistently

Related reading