How to run Wrongful Death Damages in DocketMath for South Carolina

Step-by-step

Run this scenario in DocketMath using the Wrongful Death Damages calculator.

This guide walks you through running Wrongful Death Damages in DocketMath for South Carolina (US-SC) using jurisdiction-aware settings. It focuses on the workflow and the key inputs that change your outputs—not legal strategy or advice.

1) Open the calculator

Start here for the correct tool and claim type:

• /tools/wrongful-death-damages (Primary CTA)

2) Confirm South Carolina jurisdiction (US-SC)

In the tool’s jurisdiction selector, choose South Carolina (US-SC). This matters because DocketMath applies jurisdiction-aware assumptions, including the statute of limitations logic used in this run.

If your interface includes something like “inherit jurisdiction from profile,” still verify the calculator shows US-SC before you calculate.

3) Enter the wrongful death damages inputs

DocketMath’s wrongful-death-damages calculator typically centers on inputs such as:

• Compensation model inputs (for example, the categories of damages you’re modeling)
• Timing inputs (often tied to the date of death and/or when the claim is filed)
• Economic inputs (commonly earning-related inputs, depending on what the calculator asks)
• Present value / discounting inputs (if offered)

Because calculator configurations can vary, treat this step like a checklist:

1. Fill every required field to generate outputs.
2. Double-check units and formats (e.g., years vs. months, dollars vs. thousands).
3. Keep inputs consistent when rerunning (so you can tell which changes affected the result).

4) Set (or review) the statute of limitations check

For South Carolina in this calculator run, the time-bar logic uses the general/default period you provided:

• General SOL Period: 3 years
• General Statute: GS 15-1
• Source: https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/BySection/Chapter_15/GS_15-1.html

Important: No claim-type-specific sub-rule was found in the jurisdiction data. That means DocketMath should use the general default 3-year period under GS 15-1, rather than a wrongful-death-specific limitation, for the configuration you’re running.

5) Connect the SOL inputs to your timeline

Depending on the calculator UI, you may see inputs such as:

• Date of death
• Date of filing
• Event date / accrual date (sometimes framed differently depending on the product design)

Make sure the date pair matches what the tool expects. For example:

• If the calculator measures from date of death, but you accidentally enter an event/accrual date, the SOL check—and any downstream “within/outside limitations” output—can become inconsistent.

If you’re unsure what each date field represents in the UI, pause and read the field label and any helper text. Consistency here is one of the biggest drivers of correct timing results.

6) Run the calculation and interpret outputs

After you click Calculate, review the outputs carefully. Common elements you should look for include:

• Damages totals (often broken into categories)
• SOL status output (for example, “within limitations” vs. “outside limitations”)
• Assumption summaries (jurisdiction-aware settings may be shown here)

If the SOL check fails, the calculator may still compute damages depending on how it’s designed. In that case, treat the limitations result as a timing flag (a gating/viability indicator), not as an adjustment factor that replaces the damages math.

7) Iterate: adjust inputs and watch output changes

A practical way to validate your setup is to change one input at a time and rerun:

• Increase or decrease an earnings-related input → category totals should shift accordingly.
• Change the timeline dates (death vs. filing) → the SOL status should move based on the tool’s limitation logic.
• Adjust any discounting or present value options (if available) → the total(s) may change, while the SOL timing flag should remain tied to the dates.

Use DocketMath like a sensitivity tool. When inputs are entered correctly, small changes should produce explainable output changes.

Common pitfalls

Wrongful death damage calculations are sensitive to both numbers and date logic. These are the most common issues when running DocketMath (US-SC):

• Assuming a wrongful death–specific SOL when none is detected

  • Your jurisdiction data explicitly notes: no claim-type-specific sub-rule was found.
  • As a result, DocketMath should rely on the general/default 3-year period under GS 15-1 for the configuration you’re running.
  • If you see multiple limitation settings in the UI, confirm the calculator is using the general/default approach.

• Mixing date fields

  • Entering date of death in the field meant for date of filing (or vice versa) can flip the SOL check.
  • Also watch for date formatting (some interfaces accept YYYY-MM-DD, while others use a localized format).

• Inconsistent currency and economic assumptions

  • If the tool asks for annual earnings, don’t enter a monthly figure without converting.
  • If there’s a gross vs. net choice, keep it consistent across runs so you can compare results meaningfully.

• Not reviewing jurisdiction-aware assumption summaries

  • Because DocketMath applies jurisdiction-aware rules, it may summarize key assumptions.
  • Use those summaries to confirm you’re calculating under South Carolina (US-SC) and the GS 15-1 general/default SOL logic.

• Over-interpreting the SOL output as “the only number that matters”

  • SOL status is about timing and whether the claim appears timely under the tool’s logic.
  • Damages totals are separate calculations based on your entered economic and damages inputs.
  • If both damages totals and an SOL flag are shown, keep that conceptual separation when you interpret the output.

Try it

Use this quick, controlled test to validate your setup for South Carolina (US-SC):

1. Open /tools/wrongful-death-damages
2. Select **South Carolina (US-SC)
3. Enter your baseline inputs
4. Verify the limitation logic uses:

   • 3 years under GS 15-1
   • General/default period (because no wrongful death–specific sub-rule was found)
5. Click Calculate

Now iterate carefully:

• One adjustment at a time:

  • Change only the filing date (keep everything else constant) → rerun
  • Then change only an earnings-related input (keep dates constant) → rerun

What you should expect:

• Damages totals should move when you change damages/economic-related inputs.
• SOL status should move when you change the timeline/date inputs.

If outputs don’t change when you expect them to, re-check that the modified field is connected to the calculation (some calculators only use certain inputs when toggles are enabled).

Related reading

• Wrongful Death Damages Estimator Guide for Alabama
• Wrongful Death Damages Estimator Guide for Arizona
• Wrongful Death Damages Estimator Guide for Colorado