How to run Wrongful Death Damages in DocketMath for Oklahoma
6 min read
Published November 6, 2025 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page includes a legal claim or source that failed the current primary-source review.
Step-by-step
This guide explains how to run Wrongful Death Damages in DocketMath for Oklahoma (US-OK), using jurisdiction-aware rules—specifically the general statute of limitations (SOL) default that applies when no claim-type-specific sub-rule is provided.
Note: This article explains how to use DocketMath and apply the Oklahoma SOL rule shown for 22 O.S. §152. It does not provide legal advice. SOL and accrual rules can be fact-specific.
1) Open the correct DocketMath calculator
Start at the primary call-to-action:
- Wrongful Death Damages calculator: /tools/wrongful-death-damages
This is where you’ll enter the facts that drive the output: dates and the damages inputs the calculator requests.
2) Confirm jurisdiction is set to Oklahoma (US-OK)
In DocketMath, confirm jurisdiction = US-OK (Oklahoma). If the calculator prompts for jurisdiction, select Oklahoma before entering dates.
Why this matters: DocketMath can apply Oklahoma-specific logic, including the SOL window you’ll see in results or validation messages.
3) Enter the SOL-critical dates
For Oklahoma, the general SOL period provided for this setup is:
- General SOL Period: 1 year
- General Statute: 22 O.S. §152
What to enter (common in calculators):
- Date of death / date of the event (the anchor date)
- Any additional date fields the calculator uses (for example, a filing date or another accrual-related date)
If DocketMath provides a field for “date filed” or “evaluation date/current date,” use the date you’re evaluating for timeliness (i.e., the date the SOL comparison should be measured against).
How DocketMath typically decides SOL:
- It compares (evaluation date) − (anchor date) against 1 year (the general/default window).
4) Apply the “general/default” SOL rule clearly
DocketMath’s jurisdiction-aware rules for Oklahoma rely on the general SOL period above because no claim-type-specific sub-rule was found in the jurisdiction data provided.
So, in practice, treat the SOL step as:
- Use the general/default 1-year SOL from 22 O.S. §152
- Do not automatically apply a different “wrongful death” SOL just because the label says “wrongful death,” unless DocketMath surfaces a specific override (not provided in the jurisdiction data you provided)
Warning: If you believe a different accrual theory should apply in your case, make sure your DocketMath inputs reflect that same theory. DocketMath’s SOL screening will follow the rule set it has for this jurisdiction configuration.
5) Input damages-related fields
Next, fill out the damages inputs the calculator asks for. Depending on the calculator’s structure, these commonly include fields such as:
- Economic losses (e.g., lost earnings)
- Non-economic losses (e.g., loss of society/companionship, if included)
- Other assumptions (e.g., time horizon, dependency assumptions, discounting parameters)
As you enter values, watch for:
- Inline validation (e.g., missing/invalid dates or numeric fields)
- Live recalculation (totals and breakdowns updating as inputs change)
6) Review outputs with SOL awareness
After you click Calculate, review outputs with the Oklahoma SOL rule in mind. You should typically see:
- Total damages estimate (sum of enabled/entered categories)
- Breakdown by category
- A SOL status indicator or warning banner based on the Oklahoma 1-year general/default rule
If DocketMath flags a SOL concern, treat it as a screening indicator for docket workflow, not a definitive legal holding. The results will reflect the timing inputs you used and the rule configuration shown for 22 O.S. §152.
7) Capture results and iterate
To use the calculator effectively, iterate with controlled changes:
- Adjust only one date at a time (e.g., evaluation/filing date)
- Re-run and compare:
- Totals (damages amounts)
- Eligibility/SOL status (whether the SOL window is met)
- Record which scenario changes drive differences
A practical scenario structure:
- Scenario A: actual filing/evaluation date
- Scenario B: alternative evaluation date (if you’re testing timing assumptions)
- Scenario C: alternative damages inputs (if estimates depend on earnings, time horizon, or assumptions)
Common pitfalls
Use this checklist to avoid the most frequent errors when running Oklahoma wrongful death damages in DocketMath.
- missing a required input
- using a stale rate or rule
- ignoring calendar or holiday adjustments
- skipping documentation of assumptions
Capture the source for each input so another team member can verify the same result quickly.
SOL and date handling pitfalls
Damages input pitfalls
Interpretation pitfalls
Try it
Here’s a quick “run it now” workflow you can follow in under 5 minutes.
Open the Wrongful Death Damages calculator and follow the steps above: Run the calculator.
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
Quick workflow
- Go to ** /tools/wrongful-death-damages
- Set **jurisdiction = Oklahoma (US-OK)
- Enter:
- Date of death / event anchor date
- Your evaluation or filing date (the date DocketMath should use for the SOL comparison)
- Enter damages inputs (economic/non-economic fields requested)
- Click Calculate
- Review:
- Damages total and category breakdown
- SOL status based on the 1-year general/default rule under 22 O.S. §152
What to look for in the results
Use this mini matrix to guide your next step based on what changes after rerunning:
| What you change | What should change in DocketMath | What to watch |
|---|---|---|
| Evaluation/filing date | SOL status and any SOL messaging | Confirm it crosses the 1-year boundary if you expect SOL status to flip |
| Anchor date (date of death) | SOL status and timing calculations | Confirm the event date is the correct “start” date for the comparison |
| Earnings/non-economic inputs | Damages total and breakdown | Confirm units (annual vs. lump sum) and the calculator’s time horizon fields |
| Category toggles (if available) | Total may drop/rise | Verify you enabled the categories intended for the scenario |
Pitfall: If only the damages total changes but SOL status stays the same, that’s often expected—your changes didn’t affect the SOL-critical timing inputs.
