Abstract background illustration for How to run Settlement Allocator in DocketMath for South Carolina

How to run Settlement Allocator in DocketMath for South Carolina

6 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for South Carolina (US-SC) using jurisdiction-aware rules. You’ll enter the numbers the calculator needs, confirm the allocation basis, and validate the output.

Note: This walkthrough focuses on running DocketMath and understanding how its South Carolina rule set is applied. It isn’t legal advice.

1) Open the correct tool

Start here to launch the calculator directly: /tools/settlement-allocator.

If you’re already in DocketMath, navigate to the Settlement Allocator calculator and choose South Carolina (US-SC) as the jurisdiction.

2) Confirm the rule basis used for South Carolina

DocketMath applies a South Carolina class-action allocation framework grounded in S.C. R. Civ. P. 23 (general/default rule).

One key detail: no claim-type-specific sub-rule was found for this calculator configuration. That means the calculator uses the general/default period under the rule set you selected, rather than a claim-category-specific schedule.

3) Enter the allocation inputs (and map them to outcomes)

Settlement Allocator typically depends on inputs that represent what each party/class member’s “share” should be based on and what pool is being allocated. In DocketMath, you’ll provide the inputs the calculator requests for the allocation run.

Use this checklist to ensure your inputs are consistent:

  • Total settlement amount (the money pool to allocate)
  • Distribution units / weights (what drives proportionality)
  • Party/class member amounts or the data field used to derive them (depending on the tool’s configuration)
  • Any caps, exclusions, or adjustments that DocketMath exposes for the jurisdiction mode you selected
  • Eligible population basis (if the tool asks for who is included)

Why this matters:

  • Changing units/weights usually changes relative shares (everyone’s result can shift proportionally).
  • Changing the total settlement amount scales outputs while preserving proportionality (assuming weights and eligibility stay the same).

4) Check that you’re using the correct jurisdiction mode (US-SC)

Before you run, verify:

  • Jurisdiction is set to South Carolina (US-SC)
  • The rule basis shown by the tool corresponds to S.C. R. Civ. P. 23

If you switch jurisdictions (e.g., to a state with a different allocation framework), the same numeric inputs can yield materially different outputs because the rule set affects how DocketMath interprets eligibility/period logic.

5) Run the calculation

Click Calculate / Run / Allocate (the button label may vary slightly in the UI). DocketMath will compute settlement allocations according to the selected jurisdiction’s rule configuration.

6) Review outputs in three layers

After results render, review them in this order to catch issues quickly:

  1. Totals check

    • Do the allocations sum to the total settlement amount (minus any tool-defined adjustments)?
    • If you used caps/exclusions in input, confirm the remaining pool is allocated correctly.
  2. Recipient share logic

    • Do higher-weight recipients receive larger shares?
    • If all weights are identical, allocations should generally be equal (subject to caps/exclusions).
  3. Time/rule-driven components

    • Where DocketMath applies South Carolina’s logic under S.C. R. Civ. P. 23, confirm the output matches the mode you intended.
    • Because this configuration uses the general/default period (no claim-type-specific sub-rule was found), you should not expect claim-category-specific timing differences from this run.

7) Export or capture the result set

If DocketMath provides export/download options (CSV, PDF, or a report view), save the run so you can reference:

  • Inputs used (so you can rerun later)
  • The allocation table
  • Any summary metrics (total allocated, excluded portion, etc.)

If you’re iterating, keep versioned exports such as:

  • “Settlement Allocator US-SC v1” (first pass)
  • “Settlement Allocator US-SC v2” (after correcting weights or exclusions)

Common pitfalls

Settlement Allocator runs best when inputs and assumptions match the tool’s jurisdiction logic. These are the issues that most often cause unexpected results in a US-SC run.

Warning: Output discrepancies typically come from input mismatches (weights, eligibility basis, totals) rather than a failure of the math itself. Treat input validation as the first troubleshooting step.

1) Using the wrong jurisdiction mode

  • Symptom: allocations differ from a prior run you expected to match.
  • Fix: confirm you’re on South Carolina (US-SC) before calculating.

2) Assuming claim-type-specific timing exists in this configuration

Because no claim-type-specific sub-rule was found, DocketMath applies the general/default period under S.C. R. Civ. P. 23 for the selected South Carolina rule set.

  • Symptom: you expected different timing/period assumptions by claim category, but results don’t reflect that.
  • Fix: adjust your inputs to represent eligibility consistently under the general/default period (or use a different configuration/workflow if your process requires claim-category modeling).

3) Totals not reconciling due to caps or exclusions

If you input caps per recipient, excluded recipients, or adjustment pools, the tool may allocate less than the full settlement amount unless it provides an “unallocated remainder” mechanism.

Checklist:

  • Do allocations sum to total (or to the expected reduced pool)?
  • Does the output include an excluded or unallocated line item?

4) Confusing “weights/units” with “fixed amounts”

Common input mix-up:

  • If you provide weights but meant to provide actual dollar amounts, shares will be proportional to the weights rather than fixed.

Quick test:

  • If every recipient has the same weight, the output should generally be equal shares (again subject to caps/exclusions).

5) Editing inputs after exporting without re-running

  • Symptom: you share an export that doesn’t match the latest run.
  • Fix: save outputs immediately after each run and keep input versions aligned.

Try it

To run a South Carolina settlement allocation right now:

  1. Set jurisdiction to South Carolina (US-SC).
  2. Provide:
    • total settlement amount,
    • distribution units/weights (or per-recipient amounts—depending on the form),
    • any caps/exclusions/eligibility basis requested by the tool.
  3. Click Calculate.
  4. Validate:
    • allocations sum as expected,
    • higher weights get higher shares,
    • rule-driven logic reflects S.C. R. Civ. P. 23 using the general/default period (since no claim-type-specific sub-rule was found).

Sanity-check tip (small change test):

  • Double one recipient’s weight and rerun.
  • Expected behavior: that recipient’s allocation increases, and others’ shares decrease proportionally (subject to caps/exclusions).

Related reading