Step-by-step

Run this scenario in DocketMath using the Treble Damages calculator.

You can run Treble Damages in DocketMath for South Dakota (US-SD) by using the treble-damages calculator and relying on jurisdiction-aware rules that match South Dakota’s general statute of limitations (SOL). This guide focuses on setting up your inputs so DocketMath reflects the general/default 3-year SOL under SDCL 22-14-1.

Note (important): For this workflow, DocketMath will apply the general/default SOL because no claim-type-specific treble-damages SOL sub-rule was found. In other words, the time-based part of the calculation should be treated as starting from SDCL 22-14-1 (3 years), not a shorter or longer, claim-specific period.

1) Open the Treble Damages tool in DocketMath

Start at the primary CTA: /tools/treble-damages.

If you’re navigating from elsewhere in DocketMath, make sure you select the treble-damages calculator before entering any numbers, so you don’t accidentally use a different tool with different assumptions.

2) Confirm the South Dakota SOL basis (jurisdiction-aware rule)

For South Dakota, DocketMath’s treble-damages setup should be grounded in:

• General SOL period: 3 years
• General statute: SDCL 22-14-1

How this affects your inputs/outputs: the SOL-related result (often shown as a timing or compliance indicator) depends on the dates you enter and the 3-year window DocketMath applies under SDCL 22-14-1.

Because this is the general/default rule: you should not assume a different limitations period for a specific claim category unless you separately confirm that a claim-type-specific SOL applies.

3) Gather the minimum facts needed for the calculator

Before running the calculator, assemble the values you’ll enter. Exact field labels can vary by UI version, but treble-damages workflows typically require:

• Base damages amount (the amount before applying trebling)
• Date inputs needed for the SOL/timing calculation (commonly an alleged triggering/event date and a filing/triggering date—use the dates your workflow expects)
• Any parameters the tool asks for (some versions show a multiplier explicitly; others may apply a standard treble factor automatically)

If you don’t have all dates finalized yet, you can often preview the trebling by entering the base damages first, then revisit the SOL-related portion after you confirm the correct dates.

4) Enter the base damages and confirm the treble factor behavior

In the calculator, enter your:

• Base damages (example: $25,000)

DocketMath’s treble-damages output should reflect the trebling step (commonly 3× the base amount in treble-damages workflows). When you run it, look for:

• A trebled damages total (commonly base × 3)
• Any breakdown that shows how the multiplier was applied

How outputs change with this input

5) Add the SOL-related dates for South Dakota

Next, enter the date fields the calculator requests.

While the exact labels may differ (e.g., “event date,” “filing date,” or similar), the goal is the same: provide enough date information for DocketMath to evaluate the claim under the 3-year general SOL in SDCL 22-14-1.

Formatting matters: make sure the date format matches what the tool expects (some tools use month/day/year; others use day/month/year). Swapping month/day can move the calculation across the 3-year boundary.

Jurisdiction-aware impact (South Dakota)

Once DocketMath applies South Dakota’s 3-year general SOL, your date inputs determine whether it treats the matter as:

• Within the SOL window (timely), or
• Outside the SOL window (untimely)

And since this is the general/default rule, the tool may not incorporate special limitations that could apply to certain categories—so treat the result as a starting framework based on SDCL 22-14-1.

6) Review the results and capture the numbers

When you run the calculator:

1. Check the trebled damages total first (this is usually the most straightforward part of the output).
2. Then review any SOL/timing indicator the tool provides.
3. Capture your output (copy values, screenshot the result panel, or export/share if your workflow supports it).

You’ll often end up using two layers of outputs:

• Economic/damages math: the trebled amount driven by your base damages and treble factor
• Timing filter: whether the 3-year SOL under SDCL 22-14-1 is satisfied based on your entered dates

7) Interpret the combination of trebling + SOL results (without overreading)

A key workflow distinction: treble damages and SOL timing are separate concepts.

• Treble damages generally multiplies your base damages by a factor (commonly 3×).
• SOL timing concerns whether the claim is time-barred or timely under the applicable limitations period.

DocketMath helps you structure both pieces, but it doesn’t replace legal analysis. Use the output to organize your calculations and assumptions, and confirm claim-specific details through appropriate, reliable legal resources.

Friendly reminder / disclaimer: This walkthrough is about using the tool and its jurisdiction-aware defaults. It’s not legal advice, and it may not capture every nuance that could affect a real-world claim.

Common pitfalls

Treble damages workflows often fail due to input drift (wrong field, wrong date, wrong understanding of the defaults), not because the multiplier is “mysteriously wrong.” When running DocketMath for South Dakota (US-SD) under SDCL 22-14-1, watch for these issues.

Pitfall checklist

This workflow should use the general 3-year SOL under SDCL 22-14-1 because no claim-type-specific sub-rule was identified for this scenario.

If you enter the wrong date into the date fields, the tool’s “within/outside SOL” outcome can flip.

Some scenarios may rely on statutes other than a general SOL. This page specifically uses the general/default framework: SDCL 22-14-1 (3 years).

Enter the amount that should be multiplied. If you include amounts that shouldn’t be part of the trebled base, the trebled total will be overstated.

Even a small formatting error (swapped month/day) can move your timing calculation across the 3-year threshold.

Why the “general/default SOL” matters

Because this workflow is tied to SDCL 22-14-1 as a general rule, the SOL/timing portion should be treated as a baseline output. If your real case involves a claim type that has a specific limitations rule, that would need to be evaluated separately—DocketMath can only apply the defaults implied by the workflow and jurisdiction setup you selected.

Try it

Want to quickly validate your setup before using the results for anything important? Here’s a low-effort test you can run in DocketMath:

1. Go to /tools/treble-damages.
2. Enter a small, easy base damages number first (example: $10,000).
3. Run the calculator and confirm you see the expected 3× treble damages behavior.
4. Then update only the date inputs and rerun.
5. Observe what changes:

   • If the trebled total stays the same, your edits are likely affecting only the SOL/timing portion.
   • If the trebled total also changes, the tool may be applying conditional logic based on timing—review the result panel carefully.

If you want consistency, keep a “test run” version where base damages stays fixed while you adjust dates. That makes it much easier to identify which inputs drive which output.

Finally, treat the DocketMath output as structured figures for discussion/documentation. For any claim-type-specific limitations questions, verify through qualified legal channels or authoritative references.

Related reading

• Browse the blog

Step-by-step

• Select South Dakota 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

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

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

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