Workers compensation settlement guide for South Dakota

Direct answer

This South Dakota workers’ compensation settlement guide shows you how to use DocketMath (damages-allocation) to organize and allocate settlement amounts in a way that you can reconcile with the procedural limitation concept referenced in SDCL § 20-9-2.

It’s designed to help you structure settlement math and documentation—not to provide legal advice. When you work with SDCL § 20-9-2, use the official statute text as your starting point, including the limitation period concept noted in the verified facts packet.

Primary CTA: /tools/damages-allocation

What you need to know

In practice, most settlement allocation problems come from two places:

1. Using settlement numbers without tying them to the way the file is being documented, and
2. Treating procedural facts as an afterthought rather than a framework you check alongside your math.

Before you enter anything into DocketMath, do a quick alignment pass using these ideas:

• Use SDCL § 20-9-2 as your procedural framework anchor. The verified facts indicate there is a limitation period concept you should track from the statute text.
• Collect the settlement components you intend to allocate. Don’t rely on a single “total” if you can break it into line items that match your documentation.
• Keep your allocation inputs consistent with your settlement characterization. If your settlement packet is framed using SDCL § 15-8-15.1 or SDCL § 15-8-12, reflect that consistently in how you label and group components in DocketMath.
• Use DocketMath to make changes visible. When you adjust inputs, the output should change in a predictable way—this helps you catch mis-keyed amounts or mismatched categories.

If you’re using DocketMath’s damages-allocation calculator, the core value is consistency: it pushes you to list inputs clearly and then shows how output changes when you adjust those inputs.

Step-by-step

Follow this workflow to turn settlement terms into an allocation-ready worksheet in DocketMath (US‑SD).

1) Start with the statutory “frame,” then document your timing facts

Before you enter amounts, open the verified statute source and note the limitation period concept tied to SDCL § 20-9-2.

Practical action:

• Read SDCL § 20-9-2 from the official source: https://sdlegislature.gov/Statutes/20-9-2
• Create a small “procedural facts / limitation period concept” note area in your worksheet, so your math work doesn’t float disconnected from timing facts.

2) Break the settlement into allocable components (don’t rely on one total)

DocketMath is easiest to use when each settlement component is a distinct input line.

Practical action:

• List each settlement amount as its own line item, even if you later sum them.
• For each line item, add a short description tied to your facts (avoid vague labels like “other”).
• Keep descriptions aligned with how you plan to present the settlement documentation.

3) Use DocketMath: open the allocation calculator

Start the DocketMath allocation flow here: /tools/damages-allocation

Practical action:

• Enter the settlement component values you listed.
• If your settlement characterization references SDCL § 15-8-15.1 or SDCL § 15-8-12, mirror that structure consistently in your component grouping and labels so the allocation output corresponds to how your packet is organized.

4) Sanity-check with sensitivity testing

A quick way to detect mistakes is to run small “what if” tests and verify output behavior.

Example sensitivity checks you can do:

• If one category increases, does its allocated share increase?
• If you temporarily set an input category to zero, does the output remove that category?
• If two category values swap, does the allocation shift correspondingly?

If results behave unexpectedly, pause and re-check the inputs and category mapping before moving on.

5) Reconnect the math to the procedural framework in SDCL § 20-9-2

Once allocation output looks consistent, verify it lines up with your procedural frame.

Practical action:

• Confirm your settlement documentation plan aligns with the limitation period concept from SDCL § 20-9-2.
• If there is any dispute related to timeliness or procedural posture, keep those facts surfaced next to your allocation outputs rather than buried elsewhere.

6) Add a reviewer-ready “inputs → outputs” explanation

Even when the numbers are correct, reviewers want to understand how the worksheet was built.

Practical action:

• Create a short page that lists:

  • What each DocketMath input represented (your settlement component labels/values)
  • What the DocketMath outputs represented
  • How your worksheet grouping relates to your statutory framing choices (SDCL § 20-9-2, and whether you used SDCL § 15-8-15.1 / SDCL § 15-8-12 for characterization)

This reduces back-and-forth when more than one person reviews or edits the settlement packet.

Key statutes and citations

Reminder: This guide is for organizing allocation math and documentation structure. It isn’t a substitute for legal advice.

Common pitfalls

Watch for these issues when preparing a South Dakota settlement allocation workflow with DocketMath:

• Using only one “total” without splitting components

  • Allocation inputs become too aggregated to map cleanly to your documentation.
• Mixing category labels that don’t match your framing

  • If you use SDCL § 15-8-15.1 or SDCL § 15-8-12 in how you characterize components, keep the worksheet grouping consistent.
• Skipping the procedural limitation concept from SDCL § 20-9-2

  • Even if the settlement is agreed, you still want your documentation to reflect the procedural/timing framework you’re tracking.
• Not running sensitivity checks

  • If small changes lead to counterintuitive output, likely inputs or category mapping are incorrect.
• No reviewer-ready “inputs → outputs” explanation

  • You’ll spend more time later explaining how you built the worksheet.

Run the numbers

Use DocketMath’s damages-allocation tool to convert your settlement terms into consistent allocation inputs and outputs.

What to do next (practical):

1. Go to /tools/damages-allocation
2. Enter each settlement component as a separate input line
3. Run the allocation
4. Do at least one sensitivity check (change one input and confirm the output shifts logically)
5. Add a short “inputs → outputs” explanation page to your packet
6. Cross-check your procedural note area against the limitation period concept from SDCL § 20-9-2

If your goal is for others to understand and reuse your work, keep input labels and grouping consistent with your settlement documentation.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance