Abstract background illustration for How to calculate Damages Allocation in Oklahoma

How to calculate Damages Allocation in Oklahoma

7 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Quick takeaways

  • In Oklahoma negligence cases, damages allocation is controlled by contributory negligence, not a simple “any fault reduces damages” rule. Under Okla. Stat. tit. 23, § 13, contributory negligence does not automatically bar recovery when the injured person’s negligence is of lesser degree than the defendant’s negligence.
  • DocketMath’s Damages Allocation (US-OK) calculator is built to follow this degree-of-negligence framework: your inputs drive both the eligibility gate (“lesser degree”) and the resulting reduction to the damages award.
  • The key inputs are:
    • the total damages you’re allocating,
    • the negligence degree for the plaintiff and the defendant(s),
    • and whether the plaintiff’s negligence is “of lesser degree” than the defendant’s negligence (the statutory gate).

Warning: This guide explains how to run the allocation math consistent with Okla. Stat. tit. 23, § 13. It’s not legal advice and can’t replace case-specific analysis of liability theories, jury instructions, evidentiary findings, or whether § 13 applies on the facts.

Inputs you need

To use DocketMath’s damages-allocation tool for Oklahoma (US-OK), gather inputs that you can consistently map to “degree” concepts used in § 13. Even if your numbers come from a verdict form, jury answers, or an internal estimate, the main requirement is apples-to-apples comparability between plaintiff and defendant.

Core inputs

  1. Total damages amount

    • Use the total amount you want to allocate.
    • If your damages already come as a single combined number, you can enter the combined total.
    • Common categories (if you are breaking them out):
      • medical expenses
      • lost wages
      • property damage
      • pain and suffering (where applicable)
  2. Plaintiff negligence degree

    • Enter it in a format you can compare to the defendant’s degree.
    • Examples of formats people use in practice:
      • percentage (e.g., 30%)
      • a 1–10 “degree” scale
      • a numeric weight used consistently across parties
  3. Defendant negligence degree (combined)

    • If there are multiple defendants, compute a single combined defendant degree for the comparison required by § 13.
    • Enter the number in the same unit/scale as the plaintiff’s degree.

Eligibility gate (statutory comparison)

  1. Lesser-degree determination (“§ 13 gate”)
    • Oklahoma’s Okla. Stat. tit. 23, § 13 provides that contributory negligence “shall not bar a recovery” when the injured person’s negligence is “of lesser degree” than the negligence of the person causing the damage.
    • In other words:
      • If plaintiff negligence is lesser than defendant negligence → the “not bar” condition applies, and your damages are reduced rather than eliminated by the contributory negligence rule.
      • If plaintiff negligence is not lesser → the statute’s “provided that…” operation becomes critical, and you’ll need to reflect that outcome in the scenario you run (including how you determine/enter the gate).

Practical note: DocketMath can calculate cleanly, but you must provide degrees in a way that matches the comparative meaning required by the statute. Don’t compare a “fault percentage” to a separate “1–10 negligence degree” scale unless you first convert them into a common comparability basis.

How the calculation works

DocketMath applies Oklahoma’s contributory negligence rule from Okla. Stat. tit. 23, § 13 using the relative degrees you enter.

Statutory framework (Oklahoma)

The relevant idea in § 13 is:

  • Contributory negligence shall not bar recovery where the injured person’s negligence is of lesser degree than the defendant’s negligence.

That establishes a comparison gate:

  1. Plaintiff negligence is lesser than defendant negligence
    → recovery is not barred by contributory negligence, and the allocation proceeds as a reduction framework.

  2. Plaintiff negligence is not lesser
    → the “provided that…” language becomes relevant to the legal outcome, so your scenario must represent how the fact pattern and findings treat that comparison.

Default period note (no claim-type-specific sub-rule found)

No claim-type-specific sub-rule was found in the statute text provided for this implementation beyond the general/default negligence allocation concept above. Therefore, this guide uses the general/default rule from Okla. Stat. tit. 23, § 13, unless your case-specific posture or the governing jury instruction indicates a different instruction that should be reflected in your inputs.

Degree-based allocation math (how the numbers map)

Once you pass the “lesser degree” gate (or enter the scenario where it fails), DocketMath uses your degrees to compute an allocation proportionally to the relative negligence you provide.

A common way to interpret the degree inputs is:

  • Plaintiff recovery factor = (Defendant degree) ÷ (Plaintiff degree + Defendant degree)
  • Plaintiff allocated recovery = Total damages × Plaintiff recovery factor
  • The remainder (Total damages − Plaintiff allocated recovery) effectively represents the damages impact tied to plaintiff’s contributory negligence.

If your degrees are already percentages that sum to 100, the factor becomes the defendant percentage directly. If your degrees are on a 1–10 scale (or any other numeric scale), the same ratio approach works as long as you used the same scale for both sides.

Example inputs and outputs (illustrative)

Assume:

  • Total damages = $200,000
  • Plaintiff negligence degree = 30
  • Defendant negligence degree = 70
  1. Comparison: plaintiff (30) is lesser than defendant (70)
    → the “not bar” condition applies in the sense described by § 13.

  2. Recovery factor = 70 ÷ (30 + 70) = 70%

  3. Allocated recovery = $200,000 × 70% = $140,000

  4. Reduction tied to plaintiff negligence = $200,000 − $140,000 = $60,000

Now change the comparison:

  • Plaintiff = 60, Defendant = 40
  • Plaintiff is not lesser than defendant
  • In that scenario, § 13’s “provided that…” operation becomes critical to the legal result, and DocketMath will reflect the gate behavior based on how you set up the “lesser degree” inputs for the scenario.

Common pitfalls

  1. Failing to reflect the “§ 13 gate”

    • If plaintiff negligence is not “of lesser degree”, the statute’s “provided that…” language can materially change outcomes.
    • Ensure your scenario and inputs accurately represent that comparison.
  2. Mixing fault formats

    • Percentages, “degree” scales, and internal weights can be reconciled—but only if you keep them consistent.
    • Example mistake: using defendant 70% from one source and plaintiff 7/10 from another without converting/standardizing.
  3. Using total damages that don’t match what the negligence allocation should cover

    • If your “total damages” includes amounts that belong to unrelated issues (or are already excluded by a prior settlement or ruling), you may overstate the allocation.
  4. Combining defendants incorrectly

    • When there are multiple defendants, you need a consistent method to compute defendant negligence degree (combined) for the required comparison.
  5. Assuming special sub-rules exist

    • This implementation follows the general/default rule described above because no claim-type-specific sub-rule was found in the provided statute text for specialized allocation logic.
    • If your case is governed by a distinct jury instruction or statutory instruction, reflect that in your inputs (or treat the scenario separately).

Reminder: DocketMath is a calculator that applies the rule encoded through your inputs. The quality of the output depends on whether the degrees you enter match the “degree” concepts used by the governing instructions and findings.

Sources and references

Next steps

  1. Open DocketMath’s Oklahoma allocation calculator

  2. Standardize your negligence degrees

    • Convert everything to one comparable format (e.g., both sides as percentages or both sides as a common numeric degree scale), so the “lesser degree” comparison means the same thing for plaintiff and defendant.
  3. Run sensitivity scenarios

    • Scenario A: plaintiff negligence clearly lesser than defendant
    • Scenario B: plaintiff negligence near equal or not lesser
    • This helps you understand how sensitive your allocation is to the § 13 gate.
  4. Keep an input log

    • Record total damages + plaintiff degree + defendant degree (combined) + how you determined the “lesser degree” comparison, so the output is auditable.

Related reading