How to run Damages Allocation in DocketMath for South Dakota

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide explains how to run Damages Allocation in DocketMath for South Dakota (US-SD) using jurisdiction-aware rules. For this South Dakota run, no claim-type-specific sub-rule was found—so the general/default statute of limitations (SOL) period applies.

1) Open the South Dakota damages allocation calculator

1. Open the primary tool page: /tools/damages-allocation
2. Confirm the jurisdiction selector is set to South Dakota (US-SD).

2) Verify the SOL rule that will drive timing inputs

DocketMath will apply South Dakota’s general limitations period for the relevant timing logic.

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

3) Enter the core allocation inputs

Damages Allocation is typically driven by (a) the damages components/amounts you want allocated and (b) the date(s) the calculator uses for SOL/timing outcomes. In DocketMath, enter each calculator field using the values from your case record.

Use this checklist while entering data:

• Dates: Use the correct “event” date(s) and the date you’re measuring from (e.g., the date prompted by the calculator such as accrual-related dates vs. filing-related dates).
• Damage components: Enter each category you want reflected in the allocation (for example: principal, interest, fees, or other components supported by the calculator).
• Amounts: Use your ledger/damages worksheet figures—not rounded estimates. Proportional allocations can shift noticeably if category values are approximated.

If DocketMath provides optional fields:

• Include optional components only if they are supported by your documentation.
• Leave fields blank when a component is not applicable, rather than forcing the tool to allocate unsupported buckets.

4) Select allocation methodology (if prompted)

Some versions of Damages Allocation let you choose how allocations are computed (for example, proportional vs. a custom/bucket-based approach). Choose the method that matches your damages model:

• Proportional allocation: Best when you have a total damages figure split into categories with known shares.
• Custom allocation: Best when your model assigns specific amounts to specific buckets.

After selecting a methodology, confirm that the categories you entered map correctly to the allocation buckets you expect.

5) Run the calculation

Click the calculation/run button.

DocketMath will return results that typically include:

• Allocation totals by category/bucket
• Any calculated timing/SOL-related flags or cutoff effects
• Summary figures you can reuse directly in drafts

6) Read outputs the way DocketMath is “thinking”

Treat the output as a transformation of your inputs.

Key patterns to check:

• If timing is outside the 3-year window: DocketMath may reduce or exclude portions treated as outside the limitations timeline, depending on the tool’s internal logic.
• If timing is within the window: DocketMath will generally allocate according to your entered component amounts and the selected methodology, without SOL-based reduction.

7) Adjust one input at a time and re-run

To understand how sensitive the results are (especially near the SOL boundary), use an “edit loop”:

• Keep all amounts constant.
• Change only one date (or one damage component).
• Re-run and compare which output lines move.

A quick way to interpret the delta:

• If results change, identify whether it looks driven by SOL/timing logic (cutoff/flag behavior) or by allocation proportions/methodology (bucket share changes).
• If results don’t change, the modified input may be non-driving for that run, or it may be outside the tool’s decision boundary.

8) Capture results for your workflow

After you run:

• Copy the summary numbers into your internal damages worksheet.
• Save the breakdown in a litigation timeline, exhibit outline, or similar work product.
• Record the exact inputs, especially dates, so you can reproduce the same run later.

Gentle reminder: this walkthrough is about using DocketMath and understanding its outputs, not about giving legal advice.

Common pitfalls

Avoid these mistakes when running Damages Allocation for South Dakota in DocketMath:

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

1) Using the wrong SOL assumption

South Dakota’s general period is 3 years under SDCL 22-14-1.

• Don’t apply a different period unless the calculator explicitly provides a selection that overrides the default.
• Don’t assume a claim-type-specific SOL exists for this run—none was identified here.

2) Misaligning “event date” vs. “measurement date”

Damages allocation often depends on which date is used as the key timing anchor.

• Confirm the date you enter for the prompt truly matches the tool’s “event” vs. “measurement” concept.
• Use a consistent date format across entries (e.g., MM/DD/YYYY), as required by the interface.

3) Rounding or inconsistent totals

Proportional allocation can shift when category amounts are rounded differently than the overall total.

• Keep precision consistent across inputs.
• Prefer ledger-matched totals and avoid manual re-typing errors.

4) Filling irrelevant categories

Optional fields can create “phantom” buckets if you accidentally populate something that shouldn’t be included.

• Enter only components you intend to allocate.
• If the tool allows it, leave non-applicable categories blank rather than forcing $0 (unless the interface requires a numeric value).

5) Not stress-testing results near the boundary

Because the governing SOL here is 3 years, boundary-adjacent inputs are where results are most sensitive.

• Re-run after verifying key dates against source documents.
• If you see unexpected cutoff behavior, test the same date from two different documents (e.g., complaint vs. ledger/timeline entry) to confirm consistency.

Try it

Ready to run a South Dakota Damages Allocation in DocketMath?

1. Open the tool: /tools/damages-allocation
2. Ensure jurisdiction is set to South Dakota (US-SD).
3. Enter:

   • The relevant dates
   • The damages components you want allocated
4. Run the calculation.
5. Review outputs—especially any lines tied to:

   • **SDCL 22-14-1 (general SOL: 3 years)

Quick self-check before you rely on the results:

• Did you intentionally use the general 3-year SOL logic (not a claim-specific override)?
• Are your key dates supported by the underlying record?
• Are your allocation categories consistent with your damages worksheet?
• After changing any boundary date, did you re-run to confirm the impact?

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules