How to run Settlement Allocator in DocketMath for North Carolina

Step-by-step

Below is a practical walkthrough for running Settlement Allocator in DocketMath for North Carolina (US-NC) using jurisdiction-aware rules.

1) Open the correct tool

1. Go to the primary call-to-action: /tools/settlement-allocator
2. Select North Carolina (US-NC) as the jurisdiction.

If you’re already in DocketMath, you can also navigate from the tool list—use /tools/settlement-allocator to make sure you’re opening the right calculator.

2) Understand the timing rule the tool uses (North Carolina default)

For North Carolina, this Settlement Allocator workflow is anchored to the general/default period for Rule 23 allocation timing referenced in N.C. Gen. Stat. § 1A-1, Rule 23.

• Rule cited: N.C. Gen. Stat. § 1A-1, Rule 23
• Source: https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/BySection/Chapter_1A/GS_1A-1,_Rule_23.html

Important scope note for this build:
No claim-type-specific sub-rule was found. That means the tool uses the general/default period rather than splitting timing by claim category.

Why this matters in practice: If your case facts would normally trigger a claim-type-specific timing provision elsewhere, you’ll want to confirm whether this calculator’s “default only” assumption matches your situation.

3) Enter the inputs required by Settlement Allocator

In the DocketMath calculator UI, you’ll typically provide inputs such as:

• Total settlement amount: the gross settlement pool you intend to allocate
• Allocation factors: the inputs that determine how the pool is distributed (for example, weights based on categories, damages components, or other factor fields the tool requests)
• Any caps / limits (if the UI prompts for them)
• Timing/period inputs (if the tool asks you to confirm a Rule 23-related period)

A useful way to think about the inputs:

• The tool needs a single total pool to allocate.
• It then needs a distribution method, which is driven by your allocation factors.
• If timing/period fields exist, they can trigger “within period” vs. “outside period” behavior, depending on what the tool implements.

Quick consistency checklist (to avoid preventable output surprises):

• Ensure the settlement amount you enter matches the pool you intend to allocate (e.g., gross vs. net of fees/costs—use the definition your agreement or workflow requires).
• Make sure the allocation factors match the format expected by the UI (percentages vs. numeric weights).
• If a period field is shown, ensure it aligns to the Rule 23 default period, since no claim-type-specific sub-rule was found in this North Carolina workflow.

4) Run the allocation calculation

1. Click Calculate (or the equivalent button in the interface).
2. Confirm the jurisdiction shown during the run is North Carolina (US-NC).
3. Review the computed allocation per participant/category.

How timing can affect results:

• Even if the numeric split is driven primarily by your allocation factors, timing-related inputs/assumptions can affect whether the tool treats results as compliant with the expected Rule 23 allocation timing logic or flags related issues.

5) Review the outputs and what they mean

Settlement Allocator typically returns outputs like:

• Allocated amounts: the portion of the total settlement assigned to each participant/category
• Proportions/shares: the basis the tool used to generate the split
• Summary totals: a reconciliation check to confirm allocations sum to the settlement amount

Use these quick sanity checks:

• Do the allocated amounts reconcile to the total settlement (allowing for rounding)?
• Do the shares look proportional to your allocation factors (e.g., higher weights lead to larger allocations)?
• If the tool shows any timing confirmation/warnings, verify they reflect the Rule 23 default period assumption rather than any claim-type-specific logic.

6) Export or save the allocation results

If DocketMath provides an export option (PDF/CSV, or a copyable results table), save your run for documentation and repeatability.

A practical workflow:

• Save your first run as a “Base allocation”
• If you later adjust inputs (settlement amount, factors, or timing), rerun and compare results—ideally changing one variable at a time so you can attribute output changes correctly.

Common pitfalls

These are frequent issues when running Settlement Allocator in DocketMath for North Carolina (US-NC).

Pitfall checklist

• Assuming claim-type-specific timing rules are applied.
  For this North Carolina build, no claim-type-specific sub-rule was found, so the tool uses the general/default period tied to N.C. Gen. Stat. § 1A-1, Rule 23.
• Entering net settlement when the workflow expects gross (or vice versa).
  If your agreement defines the distributable pool differently, match your calculator input to that definition.
• Mismatched allocation factor format.
  If the UI expects percentages and you enter weights (or vice versa), the tool may normalize in a way that creates unexpected results.
• Skipping the totals reconciliation check.
  Rounding can create a small residual—always confirm the output summary totals and understand what the tool does with rounding.
• Using the wrong jurisdiction selection.
  Double-check that the run is actually North Carolina (US-NC) before relying on outputs.

Statute-aware reminder (Rule 23 default period)

This North Carolina workflow is anchored to N.C. Gen. Stat. § 1A-1, Rule 23, and—crucially for this build—relies on the general/default Rule 23 period because no claim-type-specific sub-rule was found.

• Source: https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/BySection/Chapter_1A/GS_1A-1,_Rule_23.html

Try it

If you want to run a first-pass allocation quickly:

1. Open /tools/settlement-allocator
2. Choose North Carolina (US-NC)
3. Enter:

   • A total settlement amount
   • The allocation factors you want to use to distribute across claimants/categories
   • Any period/timing input requested (remember: Rule 23 defaults apply because claim-type-specific sub-rules weren’t found for this workflow)
4. Click Calculate
5. Confirm:

   • Allocations reconcile to the total (allowing for rounding)
   • Shares align with your input weights/factors
   • Any Rule 23 timing confirmation/warnings match your intended period

Practical input-tuning tips:

• If outputs look “too spread out,” your factors may be too evenly weighted.
• If outputs look “too concentrated,” verify you didn’t enter values as raw numbers when the UI expects percentages (or vice versa).
• If the tool flags a period/timing issue, rerun after carefully adjusting the timing field—then re-check the jurisdiction remains US-NC.
• When comparing scenarios, change only one variable at a time (e.g., settlement amount first, then factors) so you can interpret which input drove the change.

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations