Worked example: Damages Allocation in South Carolina
6 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Damages Allocation calculator.
This worked example shows how DocketMath’s damages-allocation calculator can model damages outcomes in South Carolina (US-SC) when you have multiple damage components (for example, medical expenses plus lost wages) and you need to allocate totals consistently for reporting, settlement modeling, or case planning.
Gentle note: This is an educational walkthrough. It’s not legal advice, and real cases can involve claim-specific limitations rules, tolling, or other complexities that aren’t modeled here.
Jurisdiction-aware timing rule used (South Carolina)
For timing inputs, DocketMath applies the general/default statute of limitations unless a more specific one is configured. In South Carolina, the general limitations period for civil actions is 3 years under S.C. Code Ann. § 15-1 (the general/default period):
Note: No claim-type-specific sub-rule was found for this example. That means the general 3-year default period is used here, not a special shorter/longer period for a particular cause of action. If your claim type has a different limitations period, your SOL gate may change.
Example scenario (fictional facts, for demonstration)
Assume a plaintiff brings claims arising out of an incident that caused both economic and non-economic harm. You want to allocate estimated damages across categories and compare scenarios, while also checking whether the filing date passes the 3-year timing gate.
Key dates
- Incident date: January 10, 2023
- Filing date: February 20, 2026
**Damage components (estimates)
- Medical expenses: $18,500
- Lost wages: $7,250
- Property damage: $3,400
- Pain & suffering (non-economic): $24,000
- Punitive damages estimate: $0 (kept at zero for this run)
**Allocation framework in DocketMath (what you’re modeling)
- Total damages = sum of all categories
- Allocation % = each category ÷ total (so the model stays internally consistent)
- Timing gate: whether filing falls within the 3-year window based on § 15-1 (general/default rule)
Input checklist (what you’d enter in DocketMath)
Use these as your DocketMath “worked example” inputs:
- Incident date: 01/10/2023
- Filing date: 02/20/2026
- Medical expenses: 18500
- Lost wages: 7250
- Property damage: 3400
- Pain & suffering: 24000
- Punitive damages: 0
- Jurisdiction: **South Carolina (US-SC)
- Statute of limitations rule selected: **General/default period (3 years, S.C. Code § 15-1)
Example run
Now run the scenario through DocketMath’s damages-allocation calculator.
Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Timing gate (3-year general/default SOL)
Under S.C. Code Ann. § 15-1, the general limitations period is 3 years.
- Incident date: 01/10/2023
- Filing date: 02/20/2026
- Elapsed time: 3 years, 41 days
Because the filing occurred 41 days after the 3-year general period ends, the timing gate fails under the general rule used in this example.
Warning: This example uses only the general 3-year default. If a real case involves a claim type with a different limitations period (or tolling), the SOL gate—and therefore the practical outcome—could change substantially. Ensure DocketMath’s configuration matches the claim type you’re evaluating.
Step 2: Compute category totals
Sum the provided damage components:
- Medical expenses: $18,500
- Lost wages: $7,250
- Property damage: $3,400
- Pain & suffering: $24,000
- Punitive damages: $0
Total estimated damages
- $18,500 + $7,250 + $3,400 + $24,000 + $0
- = $52,150
Step 3: Allocate percentages across categories
DocketMath calculates allocation shares so your reporting totals reconcile to the same $52,150:
| Category | Amount | Allocation % |
|---|---|---|
| Medical expenses | $18,500 | 35.46% |
| Lost wages | $7,250 | 13.90% |
| Property damage | $3,400 | 6.52% |
| Pain & suffering | $24,000 | 46.02% |
| Punitive damages | $0 | 0.00% |
| Total | $52,150 | 100.00% |
Step 4: Output summary you can use
A typical DocketMath output for this run combines the allocation model and the timing gate:
- Allocated total damages: $52,150
- Allocation breakdown: as shown in the table above
- SOL gate (general/default): Fail (filed after the 3-year period under § 15-1)
Practical takeaway: even though the damages math is straightforward, the SOL timing gate affects whether the claims are viable under the rule applied in this example—this can influence settlement posture, demand structuring, and how component reasoning is presented.
If you want to run the same style of model for your own inputs, use DocketMath here: /tools/damages-allocation.
Sensitivity check
Small changes in inputs can flip either (a) the allocation proportions or (b) the SOL gate. Below are two targeted “what-if” checks you can run in DocketMath to see which lever matters more.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Sensitivity A: Filing date near the 3-year boundary (timing flips)
Keep damages identical and change only the filing date.
**Baseline (from above)
- Incident: 01/10/2023
- Filing: 02/20/2026
- Result: SOL gate fails
Try these:
Scenario A1: Filing on 01/10/2026
- Elapsed time: exactly 3 years
- Result under general rule: Pass (timing within 3 years)
Scenario A2: Filing on 01/11/2026
- Elapsed time: 3 years + 1 day
- Result: Fail (timing falls outside the 3-year window)
Takeaway: Around the boundary, the model’s viability conclusion can change based on days, even when damages are unchanged.
Sensitivity B: Rebalancing damage components (allocation shifts)
Keep filing date unchanged (still failing the general SOL gate), but adjust category assumptions.
Example: reduce pain & suffering and increase medical costs:
- Medical expenses: $22,000 (up $3,500)
- Pain & suffering: $20,500 (down $3,500)
- Lost wages: $7,250 (unchanged)
- Property damage: $3,400 (unchanged)
New total
- $22,000 + $7,250 + $3,400 + $20,500 = $53,150
**New allocation % (selected)
- Medical: 22,000 / 53,150 ≈ 41.39%
- Pain & suffering: 20,500 / 53,150 ≈ 38.58%
Takeaway: Allocation percentages can shift meaningfully when category assumptions move, even if the overall totals are in the same ballpark.
What to record for decision-making (practical checklist)
When you run sensitivity checks in DocketMath, capture:
- Which dates were used for SOL gating under **S.C. Code Ann. § 15-1 (3 years general/default)
- Whether you changed only the filing date or also changed damages categories
- The allocation table for each scenario (so totals remain reconcilable)
- Any “boundary crossing” days (for example, filing 1 day after the 3-year mark)
Pitfall: If you recompute allocation totals without re-running the SOL gate, you can end up with inconsistent case narratives—your damages math may be correct, but the viability conclusion could be based on the wrong timing input.