Workers compensation settlement guide for South Carolina
8 min read
Published May 29, 2025 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
Direct answer
Run this scenario in DocketMath using the Damages Allocation calculator.
In South Carolina, a workers’ compensation settlement is generally evaluated against a 3-year limitations period under the general statute of limitations in S.C. Code § 15-1—and no claim-type-specific sub-rule was identified beyond that default period. Use DocketMath’s damages-allocation tool at /tools/damages-allocation to model how settlement proceeds might be allocated across components (past vs. future, and related buckets) so you can see how the numbers change when timelines or amounts change.
Because workers’ comp settlements often involve lump sums, payment schedules, and possible future obligations, the timing “clock” can matter in how you document and negotiate the deal. Even when you are already at the settlement stage, understanding the general time bar can help you avoid proposing terms that later feel inconsistent with the limitations baseline.
Note: This guide is jurisdiction-aware for US-SC and references S.C. Code § 15-1 for the general limitations period. It’s not legal advice, and workers’ compensation procedures can involve additional rules that are not covered by this single limitations citation.
What you need to know
A workers’ compensation settlement may include several “money buckets,” such as:
- Past medical-related amounts (paid or reimbursable)
- Past wage loss / disability compensation
- Future wage loss / loss of earning capacity projections
- Impairment/disability payments (if structured as part of the agreement)
- Interest, attorney’s fees, and administrative costs (depending on how the settlement is drafted)
- Release consideration / confidentiality value (often reflected indirectly within the overall total)
The purpose of using DocketMath is to keep the settlement math organized: when you adjust one part (like past vs. future allocation), you can quickly verify that the total still matches and that you’re not double-counting components.
What changes the output in DocketMath?
When you run different allocation scenarios, outputs typically shift based on inputs like:
- Settlement total (lump sum amount or present value of structured payments)
- Past vs. future allocation (timing affects how you document what the payment is covering)
- The allocation categories you select (even if the tool groups them broadly)
- Proposed start dates for any future payments (helpful for aligning the timeline with your documentation)
- Any amounts already paid (so your settlement reflects remaining exposure)
Limits context in South Carolina (default rule)
For limitations timing in this guide, the baseline is:
- 3 years under S.C. Code § 15-1 (the general statute of limitations)
- No claim-type-specific sub-rule was found in the provided jurisdiction data, so treat § 15-1 as the default period for this guide.
This guide intentionally stays at the general baseline level. If you later discover a more specific rule that applies to your exact scenario or procedural posture, that more specific authority could supersede the default.
Warning: A “3-year general limitations period” is not the same thing as a “3-year settlement approval process.” Settlement approval timing and administrative scheduling can be separate from the general limitations clock.
Step-by-step
Follow these steps to build an allocation model in DocketMath and sanity-check it against the US-SC default limitations baseline.
1) Confirm the settlement “money number”
Collect:
- Total settlement amount (lump sum or structured total)
- Any offsets or amounts already paid
- Whether attorney’s fees are included in the stated total or are separate
Goal: Create a single settlement “pool” that you will allocate.
2) Break the pool into defensible components
Create a working list of allocation categories you will mirror in your settlement math, such as:
- Past wage loss
- Past medical-related amounts
- Future compensation components
- Any separate interest/fee line items (if applicable to how you’re modeling)
Tip: Even if these categories are not submitted verbatim to a tribunal, consistent internal documentation reduces confusion later.
3) Set timeline inputs for the model
Use dates that anchor your analysis, for example:
- Earliest relevant injury date (if known)
- Date of filing (if you have it)
- Date of settlement agreement (or anticipated approval date)
For this guide, the key limitations baseline is still:
- 3 years under S.C. Code § 15-1
Do not skip this step if you plan to compare scenarios (for example, “what if finalization happens sooner or later?”).
4) Run allocation scenarios in DocketMath
Open /tools/damages-allocation and enter inputs such as:
- Settlement total (or present value, if your workflow uses that)
- Past vs. future allocation amounts or percentages
- Previously paid offsets (if applicable)
- Any dates the tool prompts for timeline modeling
Then compare scenarios, such as:
- Scenario A: higher past allocation vs. lower future
- Scenario B: even split
- Scenario C: lower past allocation vs. higher future (while holding the total constant)
5) Translate outputs into settlement drafting language
After you review the allocation breakdown:
- Verify totals tie back to the settlement figure
- Make sure fee/interest components are not double-counted
- Confirm that your “past vs. future” timing aligns with how the settlement defines payment timing
6) Document the limitations baseline reference
In your settlement file notes (and not necessarily in the agreement text), keep a short, explicit record:
- “General limitations period: 3 years under S.C. Code § 15-1.”
- “No claim-type-specific sub-rule was found for this brief; treat § 15-1 as the default baseline.”
This helps keep your internal reasoning consistent if the settlement package is later reviewed.
Pitfall: Allocating nearly all settlement proceeds to “future” when the underlying wage loss and treatment were mainly in the past can create internal inconsistencies—especially if the file requires an explanation of what the settlement is intended to cover.
Key statutes and citations
What statute controls the default limitations window?
- S.C. Code § 15-1 — general statute of limitations: 3 years
Source: https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/BySection/Chapter_15/GS_15-1.html
How this is used in this guide:
- We use § 15-1 as the default baseline because the provided jurisdiction data did not identify a claim-type-specific sub-rule to apply instead.
How to use this citation in a practical workflow
In settlement preparation, § 15-1 is most useful for:
- Timing-aware document checklists
- Scenario comparisons where settlement finalization dates shift
- Internal notes explaining why the settlement is treated as timely under the general 3-year baseline
Warning: This brief uses only the general limitations citation you provided. If a specific rule applies to your exact fact pattern or procedural posture, it may control over the general baseline.
Common pitfalls
Here are the most common ways settlements and allocation math go wrong when timelines don’t line up with the numbers.
- Double-counting money buckets
- Example: treating attorney’s fees as both included in the settlement total and also as a separate add-on.
- Mixing “past” and “future” allocations without consistent date logic
- If you use a specific cutoff date in DocketMath, the settlement drafting should reflect that same cutoff logic.
- Relying on only one scenario
- You usually get better negotiation clarity by showing how changing the past/future split affects allocation while keeping the total constant.
- Confusing general limitations timing with settlement processing
- Administrative/approval steps are not necessarily the same as the general limitations clock.
- Not recording why you used the default baseline
- If someone later asks why you used § 15-1, you want the record: “3-year general limitations period under S.C. Code § 15-1; no claim-type-specific sub-rule identified in the provided data.”
Checklist before you finalize your numbers:
Run the numbers
Use DocketMath’s damages-allocation tool to stress-test your allocation before you commit to a settlement structure.
Try this quick modeling approach (3 scenarios)
Keep the same settlement total across runs, and adjust only the past/future split:
| Scenario | Past allocation | Future allocation | What you’re testing |
|---|---|---|---|
| A | Higher | Lower | Whether your core exposure is primarily historical |
| B | Even split | Even split | Balanced approach; checks internal consistency |
| C | Lower | Higher | Whether a structured/future-focused arrangement fits the timeline better |
Inputs to keep consistent across runs
- Settlement total (or present value)
- Previously paid offsets (if any)
- Any planned fee/interest treatment you will reflect in your draft
Inputs to vary deliberately
- Past vs. future split percentages or amounts
- Payment timing assumptions for any future component
How to interpret outputs
If outputs change materially based on small date shifts, pause and verify:
- Your past/future cutoff
- Whether the tool’s timeline assumptions match the limitations notes you are documenting under **S.C. Code § 15-1 (3 years)
Pitfall: Changing too many inputs at once makes it hard to identify whether the allocation shift is driven by the split itself or by timeline/date logic.
Start here
- Run DocketMath damages allocation: /tools/damages-allocation
