How to run Damages Allocation in DocketMath for South Dakota

Step-by-step

This walkthrough shows how to run Damages Allocation in DocketMath for South Dakota (US-SD) using jurisdiction-aware rules grounded in your verified packet authority (see SDCL § 20-9-2). This is for workflow guidance, not legal advice.

1) Open the correct calculator

1. Go to the primary CTA: /tools/damages-allocation
2. Confirm you’re using the Damages Allocation calculator (the damages-allocation flow), not a general estimate tool.

2) Select the correct jurisdiction

1. In the calculator, choose South Dakota with jurisdiction code US-SD.
2. This ensures DocketMath applies the South Dakota rule structure associated with SDCL § 20-9-2.

3) Enter receipt data and allocation inputs

In DocketMath, Damages Allocation is typically driven by receipt/component lines plus one or more rule-influencing inputs.

For the verified packet, the key rule-related input to look for is:

• receipts.0.limitation_period (see SDCL § 20-9-2)

Practical approach:

• Populate each receipt/component row using the labels exactly as they appear in the DocketMath UI.
• If the UI includes a field explicitly labeled limitation period (or similar wording), fill it in using the receipts.0.limitation_period value implied by the SDCL § 20-9-2 logic that DocketMath is applying for US-SD.
• If you have multiple receipts/components, enter them on separate lines rather than combining them—this helps you later confirm whether limitation-period inputs affected the allocation the way you expected.

4) Set any fields that control the allocation logic

Complete every required field the calculator marks as mandatory.

When limitation period-type inputs are present, treat them as allocation drivers:

• Ensure you’ve set the limitation period value consistently for each receipt/component line where it applies.
• If DocketMath offers guidance text or help icons beside these fields, follow the format shown there (for example, whether the tool expects a specific kind of entry in the limitation-period field).

This step is where the rule structure linked to SDCL § 20-9-2 will most directly influence the outputs.

5) Run the calculation

1. Click Calculate.
2. Review both:

   • Component-level results (per receipt/component line), and
   • Summary totals (the rolled-up numbers)

Also watch for any validation messages or warnings related to limitation-period inputs. Even if the tool produces a result, warnings can signal that some rule inputs weren’t recognized in the way the UI expects.

6) Validate results using the tool’s own structure

This is a quick integrity check—not legal analysis.

Use these checks:

• Input coverage check

  • Did each receipt/component line you entered show up in the component results?
• Limitation-period impact check

  • For scenarios where you entered different limitation-period values across lines, do the component allocations reflect those differences?
• Arithmetic/consistency check

  • Does the sum of the component allocations match the tool’s reported total (or the totals shown in the relevant summary section)?

If something looks off, return to the receipt/component section and confirm the limitation period input(s) match the formatting and placement the calculator expects (including the field corresponding to receipts.0.limitation_period).

7) Export or capture outputs

When you’re satisfied with the run:

• Use DocketMath’s export/copy options (when available) to save:

  • Allocated totals
  • Component-level breakdowns
  • The limitation period inputs used for the run (so you can reproduce results later)

Keep a record of the exact values you entered so you can compare outputs across scenarios without guessing.

Common pitfalls

These are common issues when running Damages Allocation for South Dakota (US-SD) in DocketMath.

Pitfalls to watch

• Bucket mismatch

  • Entering receipts/components in a way that doesn’t match DocketMath’s expected categories can distort allocation results.
  • Fix by aligning your receipt/component lines to the tool’s rows rather than compressing everything into one line.

• Blank or implicit defaults for limitation-period inputs

  • The verified packet highlights receipts.0.limitation_period as the key rule-related value tied to SDCL § 20-9-2.
  • If those fields aren’t filled (or only filled on some lines), the allocation can behave inconsistently across components.

• Incorrect data format for limitation-period fields

  • If the UI expects a specific format (for example, a particular type of entry), don’t estimate.
  • Re-check the field help text and ensure the entry matches the UI’s expected format.

• Over-relying on the summary total

  • A total can look plausible even if only some components used the intended limitation-period inputs.
  • Always confirm component-level entries first, then treat the totals as a secondary check.

Quick diagnostic checklist

• South Dakota / US-SD jurisdiction selected
• All required receipt/component fields completed
• limitation period (corresponding to receipts.0.limitation_period) populated consistently where applicable
• The results include component-level outputs (not just a single blanket number)
• Export/capture includes the values used for the run

Try it

Use this mini test run to confirm the calculator is responding to your inputs before you finalize a full scenario.

1. Open /tools/damages-allocation
2. Select South Dakota (US-SD)
3. Enter:

   • At least two receipt/component lines
   • Distinct limitation period inputs for those lines (so you can see whether the SD-specific logic linked to SDCL § 20-9-2 changes the allocation)
4. Click Calculate
5. Compare outputs:

   • Do component allocations differ in a way that tracks your limitation-period inputs?
   • Does the sum of the allocated components match the reported total?

If behavior is consistent across the two lines, you can be more confident that your full dataset won’t be affected by hidden defaults or formatting issues.

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