How to run Damages Allocation in DocketMath for South Carolina

Step-by-step

This guide shows how to run a Damages Allocation calculation in DocketMath for South Carolina (US-SC) using jurisdiction-aware rules, then interpret the results. It’s written to be practical, not legal advice—treat the output as a structured starting point for your analysis and adjust for case-specific facts.

1) Open the calculator

1. Go to the primary CTA: /tools/damages-allocation.
2. Set Jurisdiction: South Carolina (US-SC) in the jurisdiction picker (or the first “Jurisdiction” field, depending on your UI).

2) Confirm the SOL (statute of limitations) rule basis

For South Carolina in this Damages Allocation workflow, DocketMath uses the general/default SOL period. This is because no claim-type-specific sub-rule was found for this particular workflow.

Use the default rule like this:

• General SOL period (default): 3 years
• General statute: S.C. Code Ann. § 15-1
• Source: https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/BySection/Chapter_15/GS_15-1.html

What to expect in the tool: the calculator will apply the 3-year general/default timing logic when determining what portion of your damages falls within vs. outside the SOL window.

3) Choose the allocation method (how DocketMath distributes amounts)

Damages Allocation typically requires you to select a method that matches your workflow. In DocketMath, look for a method selector and descriptions that explain how the calculator will allocate damages, such as:

• Allocate by days within covered vs. uncovered periods
• Allocate across damage categories (if the form supports multiple damage lines)
• Allocate using provided schedules (if you enter per-period amounts)

Why this matters: even with the same dates and dollar amounts, switching allocation methods can change the breakdown of totals (e.g., how much ends up labeled “within SOL”).

4) Enter timeline inputs (these drive SOL coverage)

Fill in the required date fields. Exact labels can vary by UI, but the logic generally follows these roles:

• Accrual / earliest relevant date: the start point the tool uses for counting
• Filing date: the point that determines what portion falls within the SOL window
• Any additional period dates your selected allocation method uses (for example, damages period start/end)

Because the SOL period here is 3 years, the date relationships control the output:

• More overlap between your damage timeframe and the 3-year covered window → more damages allocated as within SOL
• Later filing relative to the accrual/start date → potentially fewer damages days fall within SOL → more allocated as outside SOL

5) Enter damages inputs (what you want allocated)

Enter the dollar amounts the calculator requests. Common patterns include:

• A total claimed damages amount
• Optional breakdowns by period or by category (if supported)

Best practice: if the tool asks for both a “total” and separate line items, verify the line items sum to the total expected by DocketMath. If you use multiple lines, keep the structure consistent (same currency basis and same underlying assumptions).

6) Review how “SOL coverage” changes the allocation output

After you run the calculation, DocketMath should display an output that reflects:

• Allocated amounts within the covered (SOL) period
• Potentially excluded or “outside SOL” amounts
• A totals summary (often showing both “within SOL” and “outside SOL” components)

Practical effect of South Carolina’s default 3-year rule:

• If your earliest relevant date and filing date create a wider overlap, the tool will generally produce a larger “within SOL” allocation.
• If your filing falls later (relative to the start/accrual date), the “within SOL” portion may shrink because more days fall outside the 3-year window.

7) Use the results panel to sanity-check

Before using the output, verify the inputs and logic the tool applied:

• Confirm the run indicates it is using the South Carolina default 3-year SOL basis
• Check for obvious date issues (for example, if filing date appears before accrual/earliest relevant date)
• Look for day counts or period summaries (if shown) to ensure the “within SOL” and “outside SOL” split matches your expectations

8) Save/export your run (so you can iterate)

If DocketMath provides options like:

• Save run
• Download results
• Copy breakdown

Use them. Damages allocation is often iterative; small date changes (even by weeks) can shift which days land inside the 3-year default SOL window and therefore change the allocation.

9) Document assumptions for future runs

When you’re comparing scenarios later, record:

• Which date you used as accrual / earliest relevant date
• Which SOL basis you relied on (here, the general/default 3-year rule under S.C. Code Ann. § 15-1)
• Which allocation method you selected
• Any adjustments you made between runs

This makes it easier to explain why Version A differs from Version B.

Quick reference: inputs that usually affect output the most

Common pitfalls

Avoid these issues when running Damages Allocation in DocketMath for South Carolina:

• Forgetting the SOL is the general/default 3-year rule

  • This workflow uses the general SOL period of 3 years under S.C. Code Ann. § 15-1.
  • No claim-type-specific sub-rule was found for this workflow, so specialized limitations periods may not be modeled automatically.

• Using inconsistent or swapped dates

  • Ensure the earliest relevant date you enter matches the factual basis you’re modeling.
  • Swapping date order can invert the “within SOL” vs. “outside SOL” split.

• Mixing unit bases or scales

  • Example: entering monthly amounts in one section while entering annual amounts in another can distort totals and allocation.

• Changing the allocation method during comparisons

  • If you adjust inputs to compare scenarios, keep the method the same; otherwise, differences may reflect method changes rather than factual timing changes.

• Not confirming allocation is day-based vs. schedule/category-based

  • Some methods allocate by day counts, while others allocate by category or schedule. Confirm which method is active before interpreting the breakdown.

• Assuming totals automatically reconcile

  • If the UI asks for both totals and line items, verify that line items sum correctly to the total used by the calculator.

Try it

1. Open /tools/damages-allocation.
2. Select South Carolina (US-SC).
3. Enter the key timeline fields:

   • Accrual/earliest relevant date
   • Filing date
   • Any additional period dates required by your chosen allocation method
4. Enter the damages amount(s) you want allocated (total and/or line items, as requested).
5. Review the output and compare:

   • Within SOL allocated amount vs. Outside SOL allocated amount
6. Run at least two versions to see sensitivity:

   • Version A: your original dates and assumptions
   • Version B: change one timeline input (for example, move the accrual/earliest relevant date forward by 30–90 days)
7. Confirm in the results (or configuration summary) that the calculator is applying the 3-year general/default SOL logic under S.C. Code Ann. § 15-1.

If you want faster iteration, save/export each run so you can compare breakdowns side-by-side after refining facts.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules