How Settlement Allocator rules vary in South Dakota

What varies by jurisdiction

In South Dakota, the key “Settlement Allocator” inputs that can change across jurisdictions usually come from how the court measures claim timing—most importantly the statute of limitations period. That timing affects allocator logic because many settlement allocation approaches treat claims as more (or less) recoverable depending on whether they appear timely or time-barred, and whether multiple claim components fall under the same limitations window.

For South Dakota, DocketMath’s jurisdiction-aware rules for limitations timing are anchored to:

• S.D. Codified Laws § 15-6-23
  Source: https://sdlegislature.gov/Statutes/15-6-23

South Dakota limitations period (default)

• General rule for the period: S.D. Codified Laws § 15-6-23 is the general/default limitations period used when no claim-type-specific limitations statute applies.
• State-specific finding for this article: No claim-type-specific sub-rule was found for this guide.
  That means this post focuses on the general/default period in § 15-6-23, rather than attempting to split by claim category.

Where South Dakota differs in practice

Even though the statute is the same “within the state,” outcomes can still vary because the allocator is sensitive to the timing inputs you choose:

• Trigger date (when the limitations “clock” starts)
• Filing/settlement date (whether the limitations window has expired)
• How components are grouped (whether multiple claim components share the same default limitations rule and the same trigger logic)

DocketMath helps by keeping these assumptions explicit, so you can see how much the allocator’s output depends on the selected timing inputs instead of hiding them behind vague defaults.

Practical impact on allocator outputs

When limitations timing changes, allocation outputs can shift in at least two common ways:

1. Eligibility / timeliness weighting
   Components that appear untimely may be allocated less—or treated as having reduced probability of recovery.
2. Timing-adjusted valuation
   Some models apply discounting or probability adjustments that depend on how close the claim appears to be to (or past) the limitations expiry.

Because timeliness can swing from “timely” to “barred” around the limitations cutoff, relatively small date differences can produce noticeable changes in the settlement allocation results.

What to verify

Before you run the allocator in DocketMath (see /tools/settlement-allocator), verify the limitations timing assumptions so DocketMath’s South Dakota logic aligns with your case facts under S.D. Codified Laws § 15-6-23.

Gentle reminder: This is practical modeling guidance, not legal advice. If you’re unsure about claim accrual or any exception, consider confirming the timing details with qualified counsel or through reliable case law.

1) Confirm you should use the default (not a claim-type-specific rule)

Use this checklist to avoid accidentally applying the wrong limitations period:

• The claim type you’re allocating does not require a different, claim-type-specific limitations statute in South Dakota (outside the scope of this guide).
• You are comfortable using S.D. Codified Laws § 15-6-23 as the general/default limitations period for the allocator model.

Why it matters: If a claim type has its own statute of limitations and you force the default into the model, the allocator’s timeliness assumptions can skew the results.

Sources: S.D. Codified Laws § 15-6-23
https://sdlegislature.gov/Statutes/15-6-23

2) Identify the limitations “trigger” date you will model

Settlement allocation calculations typically need a start date for the limitations analysis.

When setting up inputs in DocketMath, verify you’re aligned on:

• What date you treat as the accrual/trigger date for the § 15-6-23 timing analysis.
• Whether your facts support any delay mechanism that would affect the trigger date—only include this if you have a solid basis in the record.

Pitfall to avoid: Using the settlement date as the trigger date (instead of the claim accrual/trigger date) can systematically misstate timeliness—often making outcomes look more favorable than they should.

3) Align the “as-of” date for the timeliness comparison

Next, verify what date your workflow uses to evaluate limitations:

• The as-of date for limitation evaluation (often the filing date or a key litigation milestone date).
• Whether your allocation method treats the probability/eligibility of recovery as of settlement.

If DocketMath expects a particular “as-of” input, ensure the same concept is used consistently across all components.

4) Keep component mapping consistent

If you’re allocating across multiple claim components (for example, different damages categories), verify:

• Each component uses the same South Dakota default limitations period under § 15-6-23 (unless you have a documented basis for a different rule).
• Components share the same trigger-date logic—or, if they don’t, you’ve documented why.

5) Run sensitivity checks when dates move

South Dakota limitations timing can flip outcomes near the expiry boundary. To catch misalignment quickly:

• Move the trigger date forward/backward by ~30 days and observe the allocator result.
• Move the as-of/filing date forward/backward by ~30 days and observe the allocator result.
• Record how much the allocation swings so you can identify which assumptions matter most.

This “inputs-to-outputs” check is often the fastest way to confirm the model is wired correctly.

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations

Sources and references

• S.D. Codified Laws § 15-6-23 (general/default limitations rule). https://sdlegislature.gov/Statutes/15-6-23
• TODO: If you identify a claim-type-specific limitations statute applicable to the cause of action you’re modeling, verify it against South Dakota’s limitations statutes before treating § 15-6-23 as the default for allocator timing.