How to run Settlement Allocator in DocketMath for South Dakota
5 min read
Published January 5, 2026 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
Step-by-step
Run this scenario in DocketMath using the Settlement Allocator calculator.
You can run Settlement Allocator in DocketMath for South Dakota (US-SD) by selecting the US-SD jurisdiction so the tool applies South Dakota’s jurisdiction-aware default statute of limitations rules, then entering your dates and settlement amount so the allocator can distribute value across time buckets.
Gentle note: This guide is for using the tool and understanding inputs/outputs—not for legal advice.
1) Open the tool
- Go to /tools/settlement-allocator
- Set **Jurisdiction: South Dakota (US-SD)
If you don’t see “South Dakota” in the jurisdiction dropdown, use the jurisdiction picker to explicitly set it to US-SD. The allocator’s timing rules depend on the selected jurisdiction.
2) Confirm the limitation period used (South Dakota default)
Settlement Allocator uses the statute of limitations window to allocate settlement value across potential claim timeframes.
For South Dakota, this workflow should use the general/default period, because no claim-type-specific sub-rule was found. That means the tool should rely on the general limitations period:
- 3 years under SDCL 22-14-1
What to expect in the output: the allocation timeline should be anchored to a three-year lookback (subject to the specific dates you enter in the tool).
Note: Because only a general/default rule was found, the allocator should apply SDCL 22-14-1’s 3-year period rather than attempting to apply different limitation periods to different claim types.
3) Enter the core dates that drive allocation
Settlement Allocator’s outputs typically change most when you update these date inputs:
- Incident/trigger date (date the underlying conduct occurred)
- Filing date (if the tool uses it for the allocation timeline)
- Settlement allocation “as of” date (if your workflow uses it)
- (Often) payment date or another effective date the calculator requests for timing purposes
Use the exact dates you’re working with. Small date changes can shift how much of the exposure falls inside vs. outside the limitations window.
How outputs typically change when dates change
- Move the incident/trigger date closer to the “as of” (or other anchor) date → more settlement value tends to fall inside the 3-year period.
- Move the incident/trigger date further back → more settlement value tends to fall outside the 3-year window, which can reduce (or reclassify) the allocable time-based exposure depending on how the tool structures its allocation model.
4) Provide the settlement amount and allocation method inputs
Next, enter:
- Total settlement amount (the dollar figure you’re allocating)
- Any allocation approach options the tool offers (for example, whether it allocates by time proportion or another internal factor)
If DocketMath asks for component breakdowns (such as damages buckets), fill them in consistently:
- Ensure the sum of components matches the total settlement amount—unless the tool explicitly allows component totals to differ from the overall settlement total.
- If the tool supports weighting, use weights that match your litigation strategy or internal case model, and keep your assumptions documented for auditability.
5) Run the calculation
- Click Calculate (or the tool’s equivalent button).
- Review the results, especially:
- The allocation timeline showing inside limitations vs. outside limitations
- The allocated amounts for each time bucket
- Any displayed rate/percentage assumptions used in the calculation
Because South Dakota’s default limitations period here is 3 years under SDCL 22-14-1, the calculator should present allocations consistent with a three-year framework, adjusted to your entered dates.
6) Export or save your results for your workflow
If the tool supports exports/downloads:
- Save the output (for example, PDF/spreadsheet export).
- Record the key inputs you used:
- The date values entered
- The jurisdiction rule applied (US-SD / SDCL 22-14-1 / 3 years)
This makes it easier to reconcile the allocation with settlement paperwork, internal memos, or client reporting later—especially if you rerun the calculator after settlement terms or dates change.
Common pitfalls
A few common issues can cause your South Dakota (US-SD) run in DocketMath to produce results that don’t match expectations. Check these before you rely on the numbers.
- If you run under the wrong jurisdiction, the limitations timeline won’t correspond to SDCL 22-14-1 (3 years).
- For this workflow, no claim-type-specific sub-rule was found, so the allocator should apply the general/default 3-year period under SDCL 22-14-1.
- Many allocation models treat the incident/trigger date as a critical anchor. Reversing dates can shift what portion is classified inside the limitations window.
- Entering a best guess (e.g., “around April 2023”) can materially affect allocation bucket boundaries. Re-run with precise dates when possible.
- If the tool expects components to reconcile to the total settlement amount, mismatches can distort bucket allocations.
- If you update dates or the settlement amount, export again so your saved document reflects the latest calculation run.
Warning: If your allocation seems “too high” or “too low” relative to your internal assumptions, the fastest diagnostic is to re-check the 3-year window anchored to SDCL 22-14-1, and verify the incident/trigger date you entered.
Try it
Follow this quick checklist to run a South Dakota allocation using DocketMath and the jurisdiction-aware default:
- Open: /tools/settlement-allocator
- Set **Jurisdiction: South Dakota (US-SD)
- Confirm the tool is applying:
- 3-year general limitations period from SDCL 22-14-1
- Enter:
- the incident/trigger date
- the filing date (if required by the tool)
- the settlement “as of” date (if required)
- the total settlement amount
- Click Calculate
- Review:
- the computed inside/outside limitations timeline
- the allocated dollar amounts by time bucket
Quick checklist before you save:
When you’re done, export the output and keep a copy of the input dates used—especially if you plan to run iterations after settlement terms or date assumptions change.
