Workers compensation settlement guide for South Carolina

Direct answer

For workers’ compensation settlement allocation math in South Carolina, use S.C. Code Ann. § 15-38-15 as the jurisdiction-aware anchor and run your allocation through DocketMath using the tool’s comparative-fault logic.

When your DocketMath setup uses the verified 51% bar threshold, treat allocations that place a party at 51% or more fault as crossing that threshold category; allocations that stay at 50% or less remain in the non-threshold category.

What you need to know

1) The statute citation you should rely on for allocation structure

In South Carolina, your settlement allocation workflow should reference S.C. Code Ann. § 15-38-15 (and, where relevant to your internal model, S.C. Code Ann. § 15-38-15(F)). The content here is written to align your DocketMath inputs/outputs with that statutory anchor.

2) How the verified 51% bar threshold affects allocation outputs

Your verified safe facts specify:

• Bar threshold percent: 51%

In DocketMath-style allocation workflows, that means your “allocation status” can change not only because of dollar amounts, but also because the comparative-fault inputs cross a categorical line.

A practical interpretation for using the tool outputs consistently in settlement paperwork:

• Fault share ≤ 50%: no 51% bar threshold category triggered
• Fault share ≥ 51%: 51% bar threshold category triggered

3) Why DocketMath matters for settlements

Settlements are often revised through negotiation. If you re-estimate fault inputs, you want the allocation results that populate the settlement statement to update cleanly—without manual transcription errors.

With DocketMath, the goal is:

• keep inputs reproducible,
• rerun calculations after edits,
• and carry forward allocation figures that match the latest agreed inputs.

Step-by-step

Below is a jurisdiction-aware workflow you can use with DocketMath for a settlement allocation draft in South Carolina.

1) Confirm your DocketMath model is the one you intend to use

Make sure the damages-allocation workflow is set to use the comparative-fault allocation approach tied to your South Carolina model anchored on S.C. Code Ann. § 15-38-15.

If your tool settings include allocation-type toggles, select the comparative-fault allocation type consistent with your settlement’s allocation framework.

2) Collect the allocation inputs

Create an inputs checklist you can reuse across drafts. At minimum, gather:

• Fault share percentages for each relevant party/cause under your agreed allocation scope
• The comparative-fault allocation type enabled in DocketMath
• The bar threshold behavior configured at 51% (per verified safe facts)

Checklist reminder: ensure your fault shares reflect the same scope the settlement is actually allocating—otherwise the math may be internally consistent but externally inconsistent with the settlement language.

3) Enter inputs into DocketMath

In the DocketMath damages-allocation workflow:

• Input the fault shares exactly as agreed for the draft you’re working on
• Confirm the comparative-fault bar threshold is set to 51%
• Keep a record of the input set you used for this draft (so you know what you reran later)

4) Run the allocation calculation

After running the tool, capture:

• the allocated shares / allocation figures produced by DocketMath
• whether the tool indicates the 51% bar threshold category was triggered
• the outputs you plan to map into the settlement statement

5) Map outputs into settlement statement line items

Convert the DocketMath output into the settlement-friendly structure your paperwork needs. Common mapping tasks include:

• translating each allocated portion into the corresponding settlement component (as your settlement agreement describes it)
• ensuring that the settlement narrative/labels match the allocation “category” returned by the tool (especially if the 51% threshold is triggered)
• preparing a short allocation summary for internal reconciliation

6) Rerun after negotiation changes (change control)

If the parties revise fault estimates during negotiation:

• update the fault share inputs
• rerun DocketMath
• replace the prior outputs in the settlement draft (do not “patch” numbers manually)

A simple process is to keep a draft-to-inputs linkage, for example:

Key statutes and citations

• Primary: S.C. Code Ann. § 15-38-15
  Use this as the controlling South Carolina citation anchor for the comparative allocation structure reflected in your settlement allocation approach.

• Related: S.C. Code Ann. § 15-38-15(F)
  If your internal allocation mechanics reference subsection-specific behavior, ensure the subsection is aligned with your DocketMath logic and any settlement drafting assumptions.

• Nelson v. Concrete Supply Co., 303 S.C. 243, 399 S.E.2d 783 (1991)
  This is a frequently cited decision in the broader allocation/distribution discussion context; keep it available for interpretation questions tied to your broader legal review process.

Practical drafting reminder: Align your settlement language with the same comparative framework your allocation math is using under S.C. Code Ann. § 15-38-15. The goal is consistency between paperwork and calculations.

Common pitfalls

1. Forgetting the 51% bar threshold category switch

   • If a fault share reaches 51% or more, the DocketMath output category can change.
   • Don’t only check the dollar totals—confirm whether the 51% bar threshold was triggered in the tool output.

2. Mixing fault scopes

   • If your settlement agreement allocates only certain parties/causes, but your DocketMath inputs include others, the “allocated damages” can become misaligned with the settlement’s intended scope.

3. Not rerunning after input changes

   • Updating fault shares without rerunning produces mismatched outputs and creates reconciliation problems.
   • Treat DocketMath output as derived from a specific input set.

4. Inconsistent threshold labeling in settlement text

   • If your draft text refers to one category but your tool run indicates the other (based on the 51% threshold), the settlement can contain internal inconsistencies.

5. Overlooking subsection alignment

   • If your drafting strategy depends on the mechanics reflected in S.C. Code Ann. § 15-38-15(F), make sure your internal checklists and tool logic assume the same approach.

Run the numbers

Use DocketMath’s damages-allocation workflow to compute the allocation using:

• the South Carolina comparative allocation anchor: S.C. Code Ann. § 15-38-15
• the verified comparative-fault bar threshold behavior: 51%

Primary CTA: /tools/damages-allocation

What to verify before exporting numbers into the settlement draft

• Comparative-fault allocation type is enabled in DocketMath
• The bar threshold configuration is set to 51%
• The tool output indicates whether the allocation is in the 51% bar threshold category or not
• The calculation was rerun after the most recent fault-share changes

Quick sanity checks you can do immediately

• If a key party input is 50%, confirm the output does not show the 51% bar threshold triggered.
• If a key party input is 51% or higher, confirm the output does show the threshold-triggered category.

Output handling checklist

After you run DocketMath:

• generate an allocation snapshot for the settlement file that includes:

  • the fault shares used,
  • the 51% bar threshold triggered status,
  • and the final allocation figures you will reference in the settlement statement

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