How to calculate Settlement Allocator in South Dakota

Quick takeaways

Run this scenario in DocketMath using the Settlement Allocator calculator.

• In South Dakota, the default general statute of limitations (SOL) is 3 years for many claim types, governed by SDCL 22-14-1. DocketMath uses this as the jurisdiction-aware baseline when you calculate a Settlement Allocator tied to timing.
• Use DocketMath’s /tools/settlement-allocator to standardize how you map settlement amounts across claim value components using a consistent time-based allocator.
• This guide assumes there is no claim-type-specific SOL sub-rule found for the workflow you’re running—so the allocator uses the general/default 3-year period from SDCL 22-14-1.
• Your output changes most when you change:

  • the event/trigger date (often the accrual start date your workflow uses),
  • the filing/notice date (when the claim is first asserted in your workflow), and
  • the settlement amount and allocation weights you input.

Inputs you need

Before you open DocketMath’s Settlement Allocator in /tools/settlement-allocator, gather inputs in a consistent format. DocketMath’s jurisdiction-aware rules for US-SD use the general/default SOL period of 3 years under SDCL 22-14-1.

Use this intake checklist as your baseline for Settlement Allocator work in South Dakota.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

Core timing inputs (date-driven)

Use your best-documented dates:

• South Dakota jurisdiction flag: US-SD
• Trigger/event date (e.g., date of injury, wrongful act, or contract breach—whatever date your workflow treats as the accrual start)
• Filing date (or your workflow’s “claim asserted” date)
• Settlement calculation date (optional in some workflows; if your setup uses it, it can affect forward-looking weighting)

Money and allocation inputs

Depending on your DocketMath configuration, you’ll likely provide:

• Total settlement amount (e.g., $250,000)
• Coverage or category weights (if the allocator splits settlement across components)
• Any component ceilings/floors (if your allocator setup applies minimum/maximum allocation rules)

Evidence/assumption inputs (to keep allocations explainable)

• Assumption about the applicable SOL period: you’ll set this implicitly by choosing US-SD general/default logic tied to SDCL 22-14-1
• Any “missing date” policy you follow (for example, if you estimate a trigger date, keep the method consistent and document it)

How the calculation works

DocketMath’s Settlement Allocator is designed to translate jurisdiction timing rules into an allocator factor you can apply to settlement amounts.

For South Dakota (US-SD), the relevant backbone for this workflow is:

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

And, per the jurisdiction data noted in your brief: no claim-type-specific SOL sub-rule was found, so the allocator should treat SDCL 22-14-1’s general/default 3-year period as the controlling timing baseline.

Step 1: Determine the elapsed time under the SOL framework

DocketMath computes elapsed time between two dates you supply, typically:

1. Start = trigger/event date
2. End = filing/claim asserted date

Then it compares that elapsed time against the 3-year general SOL window from SDCL 22-14-1.

A simplified way to think about the math:

• Elapsed years = (end date − start date) / 365
• SOL window = 3.0 years

Step 2: Convert timing into an allocator factor

DocketMath then maps elapsed time into a timing allocator factor.

Common patterns include:

• Within SOL window: higher allocation factor
• Near/approaching SOL window: intermediate factor
• Beyond SOL window: lower factor

Which exact mapping you see depends on the allocator’s configuration (for example, linear versus bracketed thresholds). The key jurisdiction-aware point is: the factor flows from the 3-year baseline under SDCL 22-14-1 for US-SD in this workflow.

Step 3: Apply the factor to split the settlement amount

If your workflow allocates settlement across categories/components, DocketMath uses:

• your component weights
• any component allocation rules (e.g., caps/floors)
• the allocator’s timing factor(s)
• the total settlement amount

A typical generic structure is:

1. Compute component “raw values” using weights
2. Multiply component values by the time-based allocator factor(s)
3. Normalize (if needed) so the sum of allocations equals the total settlement amount

Step 4: Produce outputs you can defend in a spreadsheet

The practical output you want is usually:

• Allocated amount per component
• Elapsed time vs. 3-year SOL window
• Timing factor used
• A short rule summary connecting the factor back to SDCL 22-14-1

That last point matters: you’re not only computing numbers—you’re attaching an explanation that ties the allocator back to the US-SD general/default 3-year rule.

Common pitfalls

Here are the most frequent issues when calculating a Settlement Allocator for South Dakota (US-SD) logic.

Use the general/default 3-year period from SDCL 22-14-1, because no claim-type-specific SOL sub-rule was found for this workflow. Switching between “date of injury,” “date of incident,” and “date discovered” can materially change whether the elapsed time falls inside the 3-year window. Enter dates as consistent calendar dates (e.g., YYYY-MM-DD) to avoid off-by-one-day behavior in elapsed time calculations. If the allocator uses bracketed thresholds, a small date shift can produce a non-linear change in output. A Settlement Allocator is a modeling tool. It can support analysis, but it is not the same as a court’s ruling on timeliness or accrual.

Quick diagnostic checklist

Sources and references

• South Dakota Codified Laws (SDCL) § 22-14-1 — general/default statute of limitations period (used here as 3 years).

Start with the primary authority for South Dakota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Next steps

To run the allocator now, follow this workflow:

1. Open /tools/settlement-allocator.
2. Select South Dakota (US-SD) so the tool applies SDCL 22-14-1’s general/default 3-year baseline.
3. Enter your:

   • trigger/event date,
   • filing/claim asserted date,
   • total settlement amount,
   • and any component weights/caps used in your setup.
4. Review the output fields that typically include:

   • elapsed time vs. the 3-year window
   • the timing allocator factor
   • each component’s allocated amount
5. Adjust one variable at a time to test sensitivity:

   • Move the filing date by 30–90 days and verify the allocation moves in the expected direction.
   • If allocations don’t change, re-check date format and whether the allocator uses bracketed thresholds.

As you refine inputs, document your assumptions—especially how you selected the trigger/event date—so the allocation remains reproducible.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado