Inputs you need for Damages Allocation in Oklahoma

5 min read

Published April 15, 2026 • By DocketMath Team

Inputs you will need

Damages allocation in Oklahoma depends on two things: (1) what “damages” categories you’re allocating and (2) whether your claims were filed within the applicable statute of limitations (SOL). DocketMath’s damages-allocation calculator helps you keep the allocation math consistent, while the jurisdiction-aware step helps you avoid building around a time-barred claim.

Before you run the calculator, gather these inputs:

  • ☐ **Claim date (or accrual date)
    • The date the claim accrued (or the best-documented date for accrual under your case facts).
  • Filing date
    • The date the lawsuit (or the relevant pleading) was filed in Oklahoma.
  • Damages categories to allocate
    • Examples you might allocate (tailor to your pleadings/evidence):
      • Economic damages
      • Non-economic damages
      • Future damages (if applicable)
      • Attorney’s fees (only if your case treats them as part of damages to be allocated)
  • Dollar amounts per damages category
    • The amounts you want DocketMath to allocate across responsible parties or theories (according to your allocation workflow).
  • Allocation basis
    • The rule you want DocketMath to use to distribute amounts (for example, by percentage weights, by time on task, or by another method you’re modeling).
  • Number of parties/allocations
    • How many allocation buckets you’re splitting totals into.
  • Any caps or exclusions reflected in your damages model
    • If your model already accounts for a cap, exclusion, or setoff, capture the final “included” amounts so DocketMath stays aligned with your theory.

Important SOL note (Oklahoma): This guidance uses the general/default SOL period from the dataset provided. No claim-type-specific sub-rule was found, so DocketMath won’t select a different SOL period based on a specific claim type—it will use the general framework instead.

Oklahoma SOL baseline you’ll use in DocketMath (general/default)

(Gentle reminder: this is a planning tool, not legal advice. If your situation turns on a specific claim type or accrual nuance, you should verify the SOL rule that applies.)

Where to find each input

Use your case file and litigation workflow to pull these inputs:

  • Claim date / accrual date
    • Look to:
      • Pleadings stating when the wrongful conduct occurred and when damages began.
      • Demand letters (often specify the “date of loss”).
      • Time-stamped communications showing when harm was known or should have been discovered (if your model uses a discovery-style date).
  • Filing date
    • Pull from the case caption docket entry.
    • If you track milestones in a case management system, export the filed date directly.
  • Damages categories and dollar amounts
    • Pull from:
      • Your complaint or amended complaint damages schedule
      • Expert reports (if you’re allocating expert-supported components)
      • Accounting spreadsheets used in discovery
  • Allocation basis and weights
    • Use whatever methodology your workflow already relies on, such as:
      • Deposition testimony breakdown
      • Event timelines
      • Percentage responsibility estimates (common for settlement or scenario allocation)
  • Party list / allocation buckets
    • Use the parties you’re allocating at the time you run the model:
      • Plaintiff(s) / defendant(s)
      • Any additional parties later added (only include those buckets if you’re allocating for the current version of the case)

If you maintain a “single source of truth” spreadsheet, you can often paste numbers into DocketMath with minimal reformatting. Consistency matters more than false precision—incorrect inputs can produce incorrect allocations.

Run it

Open DocketMath’s calculator here: /tools/damages-allocation.

Then follow this workflow:

  1. Enter the filing date and claim date (accrual date).
  2. Confirm you’re using the general/default SOL rule
    • DocketMath applies the 1-year general period from the provided dataset:
      • 22 O.S. §152
    • Because the jurisdiction data did not provide claim-type-specific SOL sub-rules, the calculator treats the SOL input as the default framework rather than selecting a different period for a specific claim type.
  3. Enter damages categories and amounts
    • Add economic/non-economic/future components (or your other categories).
  4. Set the allocation basis
    • Provide the allocation method or weights so each party/bucket receives its modeled share.
  5. Review the output
    • DocketMath should provide:
      • A total damages figure based on your categories
      • Allocation splits by party/bucket per your allocation basis
      • A SOL status check using the 1-year general period from 22 O.S. §152

Quick checklist before you hit “Calculate”

How outputs change when inputs change

  • Filing date moves later
    • SOL status can flip (timely → outside SOL, or vice versa) using the 1-year general rule.
  • Claim/accrual date moves earlier
    • SOL status can change as the “elapsed time” between accrual and filing changes under the 1-year general framework.
  • You add or remove a damages category
    • Total damages and the denominator used for allocation splits change, so party/bucket shares can shift.
  • You change allocation weights
    • Category totals may remain the same, but each party/bucket share changes.
  • You revise economic vs. non-economic amounts
    • Category totals and the allocated outcomes update accordingly.

Warning: Don’t mix “modeling” dates (e.g., trial timelines) with “actual” docket dates. If the SOL check is failing under the general 1-year rule from 22 O.S. §152, DocketMath will reflect that—even if your damages math is correct.

Related reading