How to run Wrongful Death Damages in DocketMath for South Carolina

Step-by-step

This guide walks you through running Wrongful Death Damages in DocketMath for South Carolina (US-SC) using jurisdiction-aware rules. You’ll set the inputs that drive the calculation, then verify the timeline and assumptions so the outputs are defensible.

1) Open the correct calculator

1. Go to the tool: /tools/wrongful-death-damages
2. Confirm you’re running in the South Carolina (US-SC) jurisdiction context.

If you’re using a shared workspace or template system, double-check the jurisdiction selector before you run—wrongful death damages timelines and rule logic can differ by state.

2) Select the wrongful death scenario type

Choose the option that best matches the case posture you’re modeling—particularly whether the wrongful death calculation is being treated as derivative of an underlying injury theory (i.e., “what the injured person could have recovered if death had not occurred”).

South Carolina’s wrongful death framework is codified in S.C. Code Ann. § 15-51-10, which establishes liability when death is caused by another’s wrongful act, neglect, or default, and ties the claim to what would have been actionable “if death had not ensued.”
Source: https://www.scstatehouse.gov/code/t15c051.php

3) Enter the core economic and loss inputs

Exact input labels may vary slightly depending on your DocketMath interface version, but wrongful death damages models commonly depend on inputs like:

• Pre-death earnings (annual or monthly)
• Earnings growth / adjustment assumptions (if shown)
• Work-life horizon (how long damages are projected)
• Fringe benefits (if included)
• Household contributions (if included)
• Medical expenses (if your model allows medical to be entered for wrongful death damages)
• Other quantifiable economic losses you want incorporated

As you add values, watch how totals update in the summary panel. If the tool separates categories (for example, economic vs. other components), keep your allocations consistent with how you intend to explain the calculation.

4) Set the timeline inputs (and confirm the default time period rule)

Wrongful death in South Carolina is governed by S.C. Code Ann. § 15-51-10, and your provided jurisdiction note indicates:

• No claim-type-specific sub-rule was found.
• Therefore, you should use the general/default period rule as the period basis for the damages run.

In practical terms:

• If DocketMath asks for a damages period, use the default/general period it provides for US-SC.
• Avoid switching to a special “type-specific” time window unless the tool explicitly identifies it and that approach is supported by the relevant jurisdiction rule set.

5) Ensure the “what would have been actionable” premise is reflected

South Carolina’s statute is explicit that wrongful death liability depends on whether the wrongful act or neglect is such that it would have entitled the injured person to sue and recover if death had not ensued. That concept affects how you choose assumptions and avoid drifting away from what is properly “linked” to the actionable injury premise.

Checklist while entering numbers:

• Base economic assumptions on the injured party’s injury-era status (work/employment and related earnings assumptions) rather than unrelated post-death changes.
• If you’re importing numbers from another model (like an underlying injury/medical damages run), prevent overlap that could effectively double count the same amounts across different categories in DocketMath.

6) Apply adjustments and verify the output structure

Wrongful death damages outputs can change a lot depending on optional adjustments. Common ones include:

• Discounting / present value of future amounts (if the tool offers it)
• Offsets (for insurance payments or other modeled reductions, if supported)
• Uncertainty / ranges (if the tool lets you run low/high scenarios)

After you run:

• Review each line item in the breakdown (not just the grand total).
• Confirm the period length and the start/end assumptions implied by DocketMath’s timeline inputs.
• Verify that the total is incorporating exactly what you intended—e.g., projected economic losses, medical expenses (if selected), and any other toggled losses.

If you changed the horizon/period selection, rerun and compare results to ensure the tool is reflecting the new timeline the way you expect.

7) Save and export the result

Before you close the session, save the scenario so you can quickly rerun after you adjust:

• pre-death earnings,
• growth assumptions,
• horizon/period selection (staying within the US-SC default period rule),
• any optional discounting/adjustment toggles.

If DocketMath supports export, export the calculation summary alongside your assumptions list. That makes it easier to review later and to explain your damages math consistently during settlement discussions or evidence review.

Common pitfalls

These are the most common reasons wrongful death damages results come out incorrect or misleading when running DocketMath for US-SC.

1. Using the wrong timeline window

   • Your jurisdiction note states no claim-type-specific sub-rule was found.
   • If DocketMath offers alternative period modes, stick to the default/general period for US-SC unless the tool clearly identifies a rule-supported special alternative.
   • Impact: totals can swing materially when the period changes.

2. Double counting across categories

   • Example: entering the same medical expenses both as “medical” and again as part of another economic aggregation.
   • Impact: inflated totals that won’t reconcile with what you can support from your chosen evidence set.

3. Inconsistent earnings inputs

   • Example: entering monthly earnings in an annual field (or vice versa), or mixing gross/net assumptions without matching the tool’s expected basis.
   • Impact: scale errors that can look like timeline errors, but are actually unit mismatches.

4. Losing the statute’s derivative premise

   • S.C. Code Ann. § 15-51-10 ties wrongful death to what the injured party could have recovered “if death had not ensued.”
   • Impact: using assumptions that drift into unrelated future-life events rather than what is properly connected to the actionable injury premise.

5. Not auditing the breakdown

   • Relying on a single total and skipping per-line review.
   • Impact: you may miss that one line item changed because of a toggle, offset, or period setting you didn’t intend to use.

Quick self-check: If you alter only one input (like earnings growth) but multiple categories or line items move unexpectedly, pause and review the tool’s toggles and breakdown logic.

Try it

To validate your workflow in DocketMath for South Carolina, run a quick sanity check before entering real numbers.

1. Set pre-death earnings to a simple, round figure you can verify quickly.
2. Use the default/general period for US-SC (since no claim-type-specific sub-rule was found in the provided jurisdiction note).
3. Keep optional non-economic categories off (if the tool allows you to toggle them) so you can confirm the economic/math behavior first.

Then run two scenarios:

• Run A (baseline): your round earnings + default/general period
• Run B (one-variable change): change only one input (for example, earnings growth or horizon)

What you’re looking for:

• The Run B total should move in the expected direction when the single variable changes.
• If the total moves the wrong way, or barely changes, review:

  • whether you entered earnings in the correct units,
  • whether the timeline is truly the default/general period,
  • whether discounting/present value toggles are affecting results,
  • whether the jurisdiction is still US-SC.

Once the direction and breakdown behavior make sense, replace the round numbers with your real assumptions and save/export the final scenario.

Related reading

• How to calculate Wrongful Death Damages in Texas — Full how-to guide with jurisdiction-specific rules
• How to calculate Wrongful Death Damages in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Wrongful Death Damages in Philippines — Worked example with real statute citations