How to interpret Damages Allocation results in South Dakota
6 min read
Published April 15, 2026 • By DocketMath Team
What each output means
Run this scenario in DocketMath using the Damages Allocation calculator.
If you ran the Damages Allocation calculator in DocketMath for South Dakota (US-SD), the outputs are meant to translate your damages numbers into an allocation result tied to South Dakota’s time-based general statute of limitations (SOL) logic. This is a math-and-assumptions interpretation to help you plan your next steps—not legal advice.
Because the run is jurisdiction-specific, DocketMath applies South Dakota’s general SOL period to the time portion of the damages allocation logic. In South Dakota, the general/default SOL period is 3 years under SDCL 22-14-1.
Important limitation of this setup: No claim-type-specific sub-rule was found for narrowing that period in this configuration. That means the 3-year default governs the SOL portion of the result.
In practical terms, most Damages Allocation runs produce outputs that answer: What portion of my entered damages falls inside the actionable SOL window implied by SDCL 22-14-1, based on my dates? Here are the outputs you’ll typically see and how to interpret them:
Allocated damages amount
The dollar figure the tool assigns to damages that fall within the SOL window, based on your dates aligning with the 3-year rule under SDCL 22-14-1.Excluded damages amount
The portion of your total damages that the tool treats as outside the actionable time window. This does not automatically mean “no recovery” in every real-world dispute; it means the calculator’s SOL-based allocation logic does not include those amounts in the “allocated” bucket for this scenario.SOL-adjusted percentage (or a similar ratio output)
A share showing what percentage of your entered damages is counted as SOL-included. This is useful because it helps you see whether the allocation is robust or highly sensitive to your timing inputs (even if your total damages stay the same).Key date mapping / window indicator
Many runs show the boundary being used—i.e., the implied start/end of the 3-year lookback period used for the allocation. When that window shifts (because your input dates shift), the allocated vs. excluded split can change as well.
Pitfall to avoid: Don’t assume DocketMath “knows” your claim type. In this South Dakota setup, the tool uses the general 3-year SOL in SDCL 22-14-1 as the default because no claim-type-specific narrowing rule was identified here.
A helpful way to read each output is as a map from your inputs to the SOL rule:
- Damages tied to time inside the SOL window → allocated damages
- Damages tied to time outside the SOL window → excluded damages
If your output includes both a dollar amount and a percentage, use them together: the dollar amount tells you scale; the percentage tells you sensitivity.
To rerun or refine inputs, use the primary tool path: /tools/damages-allocation.
What changes the result most
Two runs can have the same total damages but produce very different allocation results. In DocketMath’s Damages Allocation workflow for South Dakota, the biggest drivers are usually (1) your timeline, and (2) how that timeline falls relative to the 3-year window under SDCL 22-14-1.
Use this checklist to predict what will move the numbers most:
1) The effective SOL window boundary (the 3-year lookback)
The allocation depends on how your timeline lands relative to a 3-year period under SDCL 22-14-1. If key dates move closer to (or farther from) the boundary, the inside/outside split can shift quickly.
- Move key event dates into the last 3 years → allocated damages often increases
- Move key event dates past the threshold → allocated damages often decreases
2) How the tool assigns amounts across time
The calculator is sensitive to when damages occurred in relation to your entered timeline. That sensitivity is greatest when:
- your damages are entered as a schedule by periods (e.g., months/years), or
- your damages are linked to event dates.
Even a relatively small timing change can reassign a portion of damages from “inside” to “outside” (or vice versa), which can materially change both the allocated dollars and the SOL-adjusted percentage.
3) Total damages vs. timing profile
- Changing total damages typically scales the results (allocated and excluded dollars often move together).
- Changing the timing profile (dates/periods tied to amounts) is what most often changes the split and therefore the percentage.
4) Date consistency and chronology
DocketMath’s allocation logic assumes the timeline you enter is coherent and chronological. If you input inconsistent dates (for example, a later damage period paired with an earlier event boundary), the output can still be produced, but the result may be misleading.
Before you treat the output as meaningful, confirm:
- “from/to” periods make sense
- event dates align with the damages schedule you intended
- the key dates you expect to be tested are the same ones the run is using
Practical reminder: Because this South Dakota configuration uses the general 3-year SOL under SDCL 22-14-1, the allocation will tend to be time-driven. If your real dispute depends on a different limitations theory or a claim-specific limitation period, you’ll likely need to adjust assumptions outside this tool rather than expecting a different sub-rule to appear in this setup.
Next steps
Once you understand what the outputs mean and what drives the split, you can use the results in a practical workflow:
Verify the SOL assumption in your run
For South Dakota (US-SD), DocketMath is using the general/default 3-year SOL under SDCL 22-14-1. Also confirm that your run does not rely on a claim-type-specific narrowing rule (none was identified in this configuration).Run a date sensitivity test
Make small, realistic adjustments to the most important date inputs (for example, ±30 or ±60 days) and compare:- how allocated damages changes
- how the SOL-adjusted percentage changes
- whether excluded damages grows faster than allocated damages
Capture a simple outcome snapshot
Record for your internal notes or case file:- total entered damages
- allocated damages (SOL-included)
- excluded damages (SOL-outside)
- the SOL window dates shown in the output
Use the output as a planning tool
Treat the Damages Allocation output as an “SOL-adjusted damages snapshot” you can reference when preparing a demand package, negotiation memo, or internal analysis. If you need to be careful on legal positioning, consult a qualified professional—this is not legal advice.
If you want to rerun with updated facts, start again at /tools/damages-allocation.