How Settlement Allocator rules vary in North Carolina

What varies by jurisdiction

Run this scenario in DocketMath using the Settlement Allocator calculator.

Settlement allocation disputes often turn less on whether a settlement exists and more on how money gets assigned to potential claims, parties, and damages categories. In North Carolina, DocketMath’s Settlement Allocator (run via /tools/settlement-allocator) is designed to apply jurisdiction-aware rules—but the exact treatment can still vary based on the facts and the governing authorities tied to the settlement.

For North Carolina, start with the baseline:

• General statute of limitations (SOL) period: 3 years
• General statute referenced for the “default” period in this context: SAFE Child Act
• No claim-type-specific sub-rule was found: treat this as a default-only framing. That is, the 3-year period applies unless you have information showing a different, more specific limitation period is triggered by the settlement’s legal theory or underlying allegations.

That “default-only” framing matters. If a settlement covers multiple theories (for example, a mix of contract and tort, or allegations tied to a statutory scheme), the allocator may need additional inputs to determine whether the 3-year baseline is still the controlling timing rule—or whether another limitation period should override it.

In practice, North Carolina differences typically show up in three areas inside the allocator workflow:

1. Which SOL logic is selected

   • DocketMath uses the jurisdiction default unless you provide evidence that a different SOL structure should apply.
   • Output effect: allocation weights that depend on timeliness can shift, changing the recommended allocation across categories.

2. How “trigger dates” are provided

   • Many limitation-period frameworks depend on when a claim accrued or when key events occurred.
   • Output effect: changing the event date fed into the tool can move a category from “timely” to “time-barred,” altering allocation results.

3. How the settlement scope is characterized

   • If the settlement agreement identifies covered damages types, those descriptors can be used to map totals into allocable buckets.
   • Output effect: category mapping may change, affecting allocation percentages and dollar amounts.

Practical note: DocketMath can surface allocator outputs quickly, but the law applied is only as accurate as the inputs you provide (event dates, covered claims/damages language, and the jurisdiction rule set).

What to verify

Before running /tools/settlement-allocator (North Carolina: US-NC), verify the following items. These are the most common “inputs that determine outputs” when allocator logic is jurisdiction-aware.

• The governing rule or statute for the jurisdiction.
• Any local rule overrides or administrative guidance.
• Effective dates and whether amendments apply.

1) Confirm the jurisdiction setting (US-NC)

• Make sure the calculator is using North Carolina rules rather than a neighboring state set.
• Output effect: allocation can change even when the settlement amount stays fixed, because jurisdiction rules affect timing logic and category weighting.

2) Confirm the applicable SOL baseline is truly the “default period”

Your brief notes: “No claim-type-specific sub-rule was found. The above is the general/default period.”

In other words:

• Treat 3 years as the general/default SOL for the allocator’s North Carolina jurisdiction-aware timing logic.
• Only override it if you have specific information showing a different limitation period is triggered by the underlying legal theory/statute.

To anchor the “SAFE Child Act” context the brief references, North Carolina Department of Justice materials for victim and survivor guidance are a useful starting point for understanding the framework the allocator is reflecting in this content:

• https://www.ncdoj.gov/public-protection/supporting-victims-and-survivors-of-sexual-assault/

3) Identify the trigger date(s) you will input

Because SOL outcomes hinge on dates, confirm what date concepts you’re using:

• Event date(s): when the conduct occurred (or when the relevant harm manifested)
• Notice/accrual proxy date(s): if the settlement or complaint uses language like “discovered,” “reported,” “tendered,” or “filed”
• Settlement agreement date: sometimes provided for context, but it usually isn’t the accrual date for SOL purposes

Output effect: if your allocator input makes a category look timely under the 3-year default, it may receive a larger share than a category that appears outside the limitation period.

4) Match the settlement agreement language to allocator categories

Review the settlement terms for phrases such as:

• “for compensatory damages”
• “for medical expenses”
• “for pain and suffering”
• “for statutory damages”
• “any and all claims arising out of…”

Output effect: DocketMath’s allocation mapping may rely on these descriptors to distribute the settlement total into internally consistent buckets.

5) Confirm whether the settlement covers multiple legal theories

If a settlement covers several allegations, you should:

• Separate allegations by theory if the agreement allows
• Decide whether the allocator should treat categories as subject to the same 3-year default, or whether additional timing rules are likely

6) Keep records of the inputs you used

A practical documentation checklist:

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado