Step-by-step

Run this scenario in DocketMath using the Treble Damages calculator.

This guide explains how to run Treble Damages in DocketMath for Oklahoma (US-OK) using jurisdiction-aware rules. It’s focused on using the calculator accurately (workflow and arithmetic)—not legal advice. If your situation has claim-specific deadlines or requirements, you should confirm those separately.

1) Start the treble-damages calculator

1. Open DocketMath’s Treble Damages tool: /tools/treble-damages
2. Confirm the jurisdiction is set to Oklahoma (US-OK) (or select it if prompted).

2) Enter the monetary base for trebling

Treble damages are driven by a base amount that the calculator multiplies by 3.

In DocketMath, provide:

• Base damages (single amount): the dollar figure you want multiplied to reach the treble total.

What to expect in the output:

• Treble damages total (typically base × 3)
• Any additional breakdown fields the tool exposes based on its input design (for example, if the tool distinguishes “actual damages” from a trebling/multiplier input).

How outputs change

• If you enter $10,000 as the base, the treble damages output should be $30,000.
• If you instead enter a different base component (for example, a narrowed damages figure you intend to treble), the treble total updates immediately—there’s no assumption that the base is always one particular number you’ve seen elsewhere.

Practical check: after entering your base, confirm the output reflects the 3× trebling concept before relying on timing-related messages.

3) Use jurisdiction-aware timing inputs (Oklahoma SOL context)

DocketMath’s jurisdiction-aware mode may use SOL/timing-related inputs to generate workflow flags or warnings tied to the jurisdiction configuration.

For Oklahoma, the jurisdiction data you provided specifies a general default statute of limitations (SOL) period of 1 year, keyed to Oklahoma’s general limitations statute:

• General SOL Period: 1 year
• General Statute: 22 O.S. § 152
• Dataset citation/source: https://www.findlaw.com/state/oklahoma-law/oklahoma-criminal-statute-of-limitations-laws.html

Clear rule for this calculator run

No claim-type-specific sub-rule was found in the dataset you provided. That means this workflow uses the 1-year general/default SOL under 22 O.S. § 152 as the default timing assumption, rather than a specialized SOL for a specific claim type.

Practical steps in the tool

If the calculator asks for timing-related fields (for example, event date and filing date):

• Enter the dates that you intend the workflow to analyze.
• Use the 1-year general/default SOL as the baseline interpretation for any SOL/timing outputs tied to the general limitations rule.

4) Confirm how DocketMath uses the SOL input

Depending on the tool configuration, DocketMath may:

• Show a consistency check (e.g., whether the entered dates appear to align with the default 1-year SOL), or
• Produce an internal timing-validity style indicator summarized in the output.

In this guide’s workflow framing, treat SOL-related output as an analysis flag for your entered dates under the general/default 1-year assumption—not as a guarantee about whether a specific claim is legally timely.

Gentle reminder: calculators help standardize inputs, but they can’t replace legal judgment—especially where deadlines vary by claim type or other case-specific facts.

5) Review the output summary before exporting or copying

Before saving, exporting, or pasting results:

1. Verify the base amount: make sure the base damages number matches the figure you intend to treble.
2. Confirm the trebling logic: check that the output reflects 3× trebling.
3. Check timing messages (if present): confirm any SOL/timing note aligns with the dates you entered and the general/default 1-year assumption.

Quick verification checklist

Common pitfalls

Below are common mistakes when running a treble-damages-style calculation with jurisdiction-aware timing inputs in DocketMath.

1) Trebling the wrong “base” number

A frequent error is trebling an amount that is already trebled or otherwise not the intended base.

Common ways this happens:

• Feeding a number that already reflects 3× into the base field
• Using a settlement amount (or another total) where the tool expects the underlying damages base
• Including amounts you didn’t intend to include in the trebling base

Quick test:

• If you input $20,000 and the output isn’t $60,000, you likely entered the wrong value into the base field or selected a mismatched calculation mode.

2) Treating SOL/timing output as definitive legal timeliness

Your Oklahoma timing dataset uses:

• 1-year general/default SOL
• 22 O.S. § 152
• No claim-type-specific sub-rule found

That’s useful for consistent workflow checks, but it can be wrong if the actual case requires a different limitations rule. Read timing output as a calculator flag tied to the general/default workflow, not a final legal determination.

3) Entering dates in the wrong order or format

Even correct math can be paired with misleading timing flags if dates are entered incorrectly.

Examples:

• Event/trigger date entered after filing date
• Using approximate dates when the tool expects specific dates
• Mixing date formats (e.g., MM/DD/YYYY vs. DD/MM/YYYY) if the tool is sensitive to formatting

Checklist:

4) Assuming the provided statute automatically answers every claim-type question

The included reference, 22 O.S. § 152, is being used as the general/default SOL for this workflow. It’s not automatically a claim-type-specific limitations answer.

If you’re modeling a specific cause of action with its own limitations rules, confirm whether DocketMath’s general/default assumption is appropriate for that claim.

Try it

Run this quick “sanity check” to confirm your US-OK DocketMath workflow is operating as expected.

1. Open /tools/treble-damages
2. Set jurisdiction to **Oklahoma (US-OK)
3. Enter a simple base number:

   • Base damages: $1,500
4. If prompted, enter timing dates that are clearly within the general/default 1-year window:

   • Event date: January 1, 2025
   • Filing date: October 1, 2025

Then check outputs:

• Treble damages total should be $4,500 (because $1,500 × 3 = $4,500)
• Any SOL/timing note should reference a 1-year general/default assumption tied to 22 O.S. § 152, consistent with the jurisdiction data provided.

If results look inconsistent:

• Re-check the base damages field
• Re-check the jurisdiction selection (US-OK)
• Re-check date ordering and formatting

Related reading

• Browse the blog

Step-by-step

• Select Oklahoma in the Treble Damages tool.
• Enter the trigger dates and any caps or rates.
• Run the calculation and save the output.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Common pitfalls

• 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.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Try it

Open the Treble Damages calculator and follow the steps above: Run the calculator.

Capture the source for each input so another team member can verify the same result quickly.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Related reading

• Treble Damages Calculator Guide for Alabama
• Treble Damages Calculator Guide for Arizona
• Treble Damages Calculator Guide for Colorado