How Settlement Allocator rules vary in North Carolina

What varies by jurisdiction

Settlement allocation rules aren’t uniform across legal systems or even across court practice within the same country. In North Carolina, a practical way to think about “what varies” in a Settlement Allocator workflow is the procedural framework that governs whether (and how) a settlement is treated as a class settlement—because allocation typically depends on which claimants are included and what settlement mechanics apply before allocation can be implemented.

For North Carolina, DocketMath’s Settlement Allocator should be aligned with the governing class-action procedural structure in the North Carolina Rules of Civil Procedure, specifically N.C. Gen. Stat. § 1A-1, Rule 23.

One concrete variation point you’ll often see when you compare jurisdictions is the time window and procedural prerequisites tied to class handling—those choices can change the “period” (or baseline timing) you enter into allocation models and can affect what documents or eligibility assumptions you need to justify the allocation.

North Carolina: rule base used for time/procedure alignment

• N.C. Gen. Stat. § 1A-1, Rule 23 provides the general framework for class actions in North Carolina.

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

Important limitation (as identified in the jurisdiction research):

• No claim-type-specific sub-rule was found that would carve out different default periods based on claim type.
• As a result, your North Carolina allocator setup should start from the Rule 23 general/default period, not from claim-type-specific “special periods.”

How that affects the allocator result (what changes in the output)

When you run DocketMath’s Settlement Allocator for North Carolina, the output can shift based on:

• Which time/procedure parameters you input

  • Use the Rule 23 general/default period approach (no claim-type split).
• Whether your settlement description implies the relevant class settlement procedural steps

  • Even if your allocator math is correct, the “fairness” of allocation often depends on class mechanics and eligibility.
• How you map case-specific allocation inputs

  • For example: mapping claim-level eligibility counts, tiers, or weights into shares of the total settlement.

In short: North Carolina’s Rule 23 general/default baseline keeps the configuration simpler than jurisdictions that require claim-type-specific period logic—but it still requires procedural consistency between your dataset assumptions and the settlement’s class-handling framework.

What to verify

Before you rely on allocator numbers produced by DocketMath, verify the items below. These checks focus on data accuracy and procedural alignment, not legal advice.

1) Confirm you are allocating under a class-action settlement framework

Use Rule 23 as your anchor:

• Rule reference: 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

If your matter is not a class action (or not being treated procedurally as such for settlement purposes), a Rule 23–oriented allocator configuration may be inappropriate.

2) Use the general/default period (not a claim-type split)

Because no claim-type-specific sub-rule was identified, the North Carolina configuration should not create different periods by category.

Checklist

• Your allocator “period” parameter matches the general/default Rule 23 setup
• Your dataset does not assume different periods for different damages or claim categories
• Your documentation supports the single baseline period approach

3) Map DocketMath inputs to Rule 23–consistent settlement facts

DocketMath’s Settlement Allocator typically converts settlement totals and claim-level inputs into allocated shares. For North Carolina, the procedural verification is about ensuring your inputs track what the settlement is doing under the Rule 23 class framework.

Verify:

• The total settlement amount entered matches the settlement figure intended for allocation
• Claim-level weights / tiers / eligibility markers (if used) are consistent with the settlement’s structure
• The allocator input list includes only the claimants/items eligible under the settlement’s class definition

4) Document your assumptions for auditability

Even when a model is mathematically correct, a settlement allocator can be challenged if assumptions are unclear. Create an “assumption record” for North Carolina runs.

Include:

• Rule basis used: Rule 23 (N.C. Gen. Stat. § 1A-1, Rule 23)
• Period basis: general/default period (no claim-type split)
• Input definitions: what each dataset column represents, and how it maps to allocator fields

5) Run a sensitivity check

Settlement allocation outputs can move when inputs change. Before finalizing, run at least two scenarios:

• Scenario A: baseline allocator inputs
• Scenario B: conservative adjustment to the biggest driver (commonly weights or eligibility counts)

This is especially useful when class definitions are complex, because small eligibility differences can change shares.

If you want to apply the North Carolina configuration in DocketMath

Start with: /tools/settlement-allocator

Quick workflow to keep the North Carolina setup consistent

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

Sources and references

• N.C. Gen. Stat. § 1A-1, Rule 23 (North Carolina Rules of Civil Procedure—class actions).
  https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/BySection/Chapter_1A/GS_1A-1,_Rule_23.html