Offer of Judgment Analyzer Guide for Oklahoma
8 min read
Published March 22, 2026 • By DocketMath Team
What this calculator does
DocketMath’s Offer of Judgment Analyzer for Oklahoma (US-OK) helps you evaluate what happens when a party makes a written offer of judgment and the other side rejects it. The calculator focuses on the mechanics described in 12 O.S. § 1101, which governs when offers trigger additional cost exposure.
At a high level, this tool analyzes:
- Whether your offer is positioned to affect cost shifting under 12 O.S. § 1101
- How changing the offer amount changes the output
- How to compare the final judgment to the offer (because the relationship matters)
- A practical breakdown of likely cost consequences based on the statute’s structure, including the key exception referenced in 12 O.S. § 1102
Pitfall: Oklahoma’s offer-of-judgment provisions are tied to a written offer and a specific comparison between the offer and the final judgment. If you compare the offer to the wrong number (for example, a partial disposition instead of the final judgment), your analysis can be misleading.
Key statute-driven logic (Oklahoma)
- 12 O.S. § 1101: establishes the offer framework and the effect of rejecting an offer.
- Justia summary text: “Offer of judgment shall be a written offer…”
- This is the foundation your inputs should reflect.
- 12 O.S. § 1102: addresses an exception tied to the comparison between the judgment and the offer.
- Provided summary point: If the judgment is less than the offer, the offeree may be liable for costs.
- 12 O.S. § 1103: further details the operation of the offer mechanism.
Because the statute is doing the heavy lifting, you’ll see the calculator designed around (1) offer amount and (2) final judgment amount.
When to use it
Use DocketMath’s offer-of-judgment analyzer when you need a decision-oriented view of how an offer may play out after a case outcome is known (or when you’re modeling possible outcomes).
This is most useful in scenarios like:
- You’re planning whether an offer amount is strategically worth making (modeling different judgment outcomes).
- You already have a judgment number and want to understand cost exposure directionally.
- You’re comparing multiple settlement options and want a consistent framework for “offer vs. judgment” comparisons.
Check whether your situation matches these typical decision points:
- You have a specific offer amount you want analyzed under 12 O.S. § 1101.
- You have a final judgment amount you can reasonably use as the comparison baseline.
- You can identify whether the judgment is less than or greater than the offer (because 12 O.S. § 1102 references that comparison directly).
Warning: This guide supports operational planning and scenario modeling. It’s not legal advice. Offer-of-judgment issues can involve timing, form, and procedural details that a calculator can’t fully validate from amounts alone.
Step-by-step example
Let’s walk through a concrete Oklahoma example using the workflow the DocketMath tool is built for.
Example inputs
Assume you’re analyzing an offer made under 12 O.S. § 1101 with these numbers:
- Offer amount (written offer): $50,000
- Final judgment amount: $62,500
- Case posture: You want to know how the offer-vs-judgment relationship affects cost exposure logic.
Step 1: Enter the offer amount
- Open the tool via the primary CTA: **/tools/offer-of-judgment-analyzer
- Enter:
- Offer amount = 50000
Step 2: Enter the final judgment amount
- Enter:
- Final judgment amount = 62500
Step 3: Run the analysis and review the comparison result
The calculator will compare the two numbers, because Oklahoma’s statute framework turns on whether the judgment is less than or greater than the offer.
In this scenario:
- Judgment ($62,500) is greater than the offer ($50,000)
Given the provided summary for 12 O.S. § 1102:
- “If the judgment is less than the offer, the offeree may be liable for costs.”
That statement implies the liability for costs discussed in that exception is triggered when the judgment is less than the offer. Here, the judgment is not less—it’s greater—so you should not expect the “judgment less than offer” cost exception to apply in the same way.
Example output interpretation (directional)
DocketMath’s output will typically provide:
- A clear statement of the offer vs. judgment relationship
- A scenario label such as “offer below judgment” vs. “offer above judgment”
- A cost-exposure direction consistent with the statute’s comparison structure
Mini-variant: change the judgment amount
Now imagine the judgment came in at $40,000 instead.
- Offer = $50,000
- Final judgment = $40,000
In that variant, the judgment is less than the offer, which aligns with the summary trigger tied to 12 O.S. § 1102:
- Offeree may be liable for costs when judgment is less than the offer.
That’s how the calculator helps you see that a relatively small change in final exposure can flip the modeled outcome.
Common scenarios
Below are frequent ways people use the offer-of-judgment analyzer in Oklahoma civil cases. Treat these as scenario templates—the numbers you plug in drive the result.
Scenario A: Judgment exceeds the offer
Inputs
- Offer: $75,000
- Judgment: $110,000
What you’re checking
- The statute’s cost-shifting logic often depends on whether the judgment is less than the offer (see 12 O.S. § 1102 summary point).
Likely calculator direction
- “Offer below judgment” outcome view, with reduced emphasis on the “judgment less than offer” exception.
Scenario B: Judgment is below the offer
Inputs
- Offer: $100,000
- Judgment: $68,500
What you’re checking
- This directly matches the 12 O.S. § 1102 comparison concept:
- If the judgment is less than the offer, the offeree may be liable for costs.
Likely calculator direction
- A modeled cost-exposure result that reflects the exception trigger.
Scenario C: Close call where outcomes can swing
Inputs
- Offer: $50,000
- Judgment could plausibly be: $49,900 or $50,100
What you’re checking
- Whether small differences cross the comparison boundary.
Practical takeaway
- Scenario modeling helps you quantify how “near the line” the offer is.
Scenario D: Multiple offers over time (modeling comparison)
Even if you’ve made multiple offers, you generally run the analyzer one offer at a time against the final judgment you plan to use as the comparison baseline.
A simple workflow:
- For Offer 1: compare Offer 1 vs. final judgment
- For Offer 2: compare Offer 2 vs. final judgment
- Repeat
Tip: If you’re analyzing successive offers, keep a record of each offer amount used. Consistency matters because the calculator’s conclusions are only as accurate as the offers and judgment values you feed it.
Tips for accuracy
To get reliable, defensible scenario outputs from DocketMath, focus on inputs that map cleanly to the statute’s operation.
1) Use the correct “offer amount” concept
Because 12 O.S. § 1101 is framed around a written offer, your “offer amount” should match the actual offer figure you intend to analyze—not an estimate or settlement discussion number that never became a written offer.
- Checkbox checklist:
2) Use a final judgment number you can defend
Your “final judgment amount” should be the value you can identify as the judgment the statute is meant to compare against the offer.
3) Model both directions when possible
When you’re evaluating risk, run at least two versions:
- Version 1: judgment set to “below offer” (to test 12 O.S. § 1102’s comparison concept)
- Version 2: judgment set to “above offer” (to see the opposite relationship)
This gives you a quick “sensitivity check” without needing to guess how costs will ultimately be applied.
4) Don’t ignore statute structure (12 O.S. § 1101 → 12 O.S. § 1102 → 12 O.S. § 1103)
A frequent error is treating the analysis as if it’s based on a single sentence. Oklahoma’s offer-of-judgment scheme is structured across sections, so make sure your logic includes:
- 12 O.S. § 1101: the written offer framework
- 12 O.S. § 1102: comparison-related cost consequences (notably the “judgment less than offer” concept)
- 12 O.S. § 1103: additional operational details
Even if the calculator output is primarily driven by numbers, your input discipline should reflect the statute’s multi-part design.
5) Keep a quick audit trail of assumptions
If you’re modeling, document:
- The offer amount used
- The judgment figure used
- Any scenario adjustments you made
This reduces confusion later when you reconcile tool outputs with court records.
