How to calculate attorney fee in Oklahoma

Quick takeaways

• In Oklahoma, a contingency attorney fee is capped by statute at 50% of the net amount of the judgment or compromise. (See 5 O.S. § 7 — primary source in the “Sources and references” section.)
• In DocketMath, your key task is to calculate or enter the net amount (i.e., the “judgment or compromise” after the deductions you model), then apply the 50% ceiling from 5 O.S. § 7.
• If your calculated contingency fee would exceed 50% of net, DocketMath should treat the result as noncompliant with the statutory maximum under 5 O.S. § 7. You can still use the numbers to understand exposure and negotiation posture—just don’t treat the uncapped result as legally allowable.

Inputs you need

To calculate an Oklahoma contingency attorney fee in DocketMath, collect the inputs that determine the fee “ceiling” under 5 O.S. § 7.

• Gross judgment or compromise amount
  The headline award/settlement figure (before you model deductions).

• Net amount
  The “net amount of such judgment or compromise” used as the statutory base. If you don’t know it, compute it in your workflow from the deductions you model.

• Contingency fee contract rate (percentage) (optional, if you want to test compliance)
  The percentage promised in the fee agreement that you want to compare against the statutory maximum.

• Whether you are modeling a contingency fee based on the “judgment or compromise”
  Since 5 O.S. § 7 is tied to the contingency fee base described in the statute, keep your modeling consistent with that concept. (If your matter involves other fee components, model those separately or make sure your “contingency” portion uses the same net base.)

Practical way to organize your numbers

How the calculation works

This section describes the mechanics to implement in DocketMath for US-OK (Oklahoma) using 5 O.S. § 7.

Step 1: Compute the statutory maximum from the “net amount”

Under 5 O.S. § 7, the contingency fee shall not exceed 50% of the net amount of such judgment or compromise.

So the statutory maximum fee is:

• Max contingency fee = 0.50 × Net amount

Step 2: Compute the contingency fee under the contract (if testing)

If you have a contract contingency rate that you want to test:

• Contract fee = (Contract rate) × Net amount

Then compare:

• If Contract fee ≤ Max contingency fee, the contract rate is within the statutory ceiling.
• If Contract fee > Max contingency fee, the statutory maximum would limit the contingency fee to the ceiling.

Step 3: Apply the ceiling in the tool output

In DocketMath, your cap-enforced result should reflect the statutory maximum:

• Allowed (cap-enforced) contingency fee = min(Contract fee, Max contingency fee)
• If no contract rate is provided, DocketMath can still output the statutory maximum based on your net amount.

Step 4: Use input changes to understand the impact

Because the ceiling is a straight multiplier of net:

• Increase net amount → Max fee increases proportionally
• Increase contract rate → Contract fee increases proportionally, but the result cannot exceed 50% of net

Simple example workflow (illustrative)

1. Enter net amount (or enter gross + deductions so DocketMath can reach net via your workflow).
2. DocketMath computes: Max fee = 0.50 × net.
3. If you enter a contract rate, DocketMath also computes the contract fee and flags whether it exceeds the statutory maximum.

Reminder: This article explains the calculation mechanics and tool workflow. It is not legal advice.

Common pitfalls

1. Using gross instead of net

   • 5 O.S. § 7 ties the cap to the “net amount of such judgment or compromise.”
   • If you apply 50% to a gross figure while calling it a “net-based statutory cap,” the output can be materially wrong.

2. Assuming a tiered percentage cap

   • The verified packet for this brief reflects a single flat 50% ceiling tied to the net base.
   • Avoid importing tier logic from other jurisdictions or contexts unless you have Oklahoma-specific authority for that structure.

3. Forgetting to enforce the ceiling

   • Even if a contract rate is higher, the statute limits the contingency fee to 50% of net.
   • In DocketMath, ensure the output you treat as “allowable” is cap-enforced.

4. Mixing fee types or bases

   • 5 O.S. § 7 applies to the contingency fee described by the statute (i.e., based on the “judgment or compromise” net base).
   • If you also have hourly fees or other separate charges, keep those modeling choices consistent so you don’t accidentally compare the wrong number to the cap.

Sources and references

• 5 O.S. § 7 (Oklahoma contingency fee limitation — 50% of the net amount of the judgment or compromise)
  https://www.oklegislature.gov/OK_Statutes/CompleteTitles/os5.pdf
• TODO (if needed): If you plan to model fee reasonableness beyond the statutory cap, confirm which additional Oklahoma authorities you intend to rely on. (The verified packet for this brief centers on 5 O.S. § 7.)

Next steps

1. Open the calculator:

   • Calculate in DocketMath → /tools/attorney-fee

2. Enter your numbers:

   • Provide the net amount that corresponds to the “net amount of such judgment or compromise.”
   • Optionally enter your contract contingency rate to compare the contract fee against the statutory maximum.

3. Review results:

   • Confirm DocketMath computes the statutory maximum as 0.50 × net.
   • If a contract fee is provided, confirm whether it exceeds the cap and whether the output shows a cap-enforced “allowed” amount.

4. Document your net definition:

   • DocketMath can only use what you enter. Make sure your modeled deductions match how you define “net” for the cap calculation.

Related reading

• Attorney fee calculations in United States (Federal) — Full how-to guide with jurisdiction-specific rules
• Why attorney fee calculations results differ in United States (Federal) — Troubleshooting when results differ
• Attorney fee calculations reference snapshot for United States (Federal) — Rule summary with authoritative citations