Worked example: Damages Allocation in North Carolina

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

This worked example shows how DocketMath’s “damages-allocation” calculator can help you organize and allocate claimed damages using North Carolina-specific time rules where relevant. It’s not legal advice; treat it as a practical model for understanding how inputs can affect results. You can run the calculator here: /tools/damages-allocation.

Scenario (fictional, for illustration)

You’re preparing a civil claim involving multiple damage categories arising from the same underlying facts. You have three damage buckets:

• Economic losses (e.g., medical bills, missed wages): $18,400
• Non-economic damages (e.g., pain and suffering): $52,000
• Punitive damages (if sought): $12,500

You also have a timeline you want the model to filter using North Carolina’s general statute of limitations period.

Key date inputs used for the allocation model

Because the brief specifies North Carolina’s General SOL Period = 3 years, this example treats the limitation window as a general/default 3-year gate (no claim-type-specific sub-rule is applied—see next section). The model inputs are:

• Date of alleged harm / triggering event (start): 2022-05-10
• Filing date (end): 2025-05-20

Confirming the rule being applied (and what we’re not doing)

DocketMath is used here with a general/default limitations period, consistent with the provided jurisdiction notes:

• General SOL Period: 3 years
• SAFE Child Act: referenced as jurisdiction context (see “Related reading” note below), but no claim-type-specific sub-rule was found in the inputs you provided.

In other words, this example does not assume a specialized timing rule tied to a particular cause of action. It intentionally applies only the general 3-year gate.

Important note: The brief explicitly states that no claim-type-specific sub-rule was found, so this worked example uses North Carolina’s general/default 3-year SOL period rather than a specialized rule for a particular claim type.

Damage-category allocation inputs

In addition to the timeline inputs, this simplified model uses allocation weights to represent how you might distribute claimed categories inside the calculator:

In a real workflow, you’d adjust these weights to match how your case theory or drafting approach allocates categories. The key lesson of the example is how the SOL gate changes recoverable results.

Example run

Below is a representative sequence you’d follow in DocketMath → /tools/damages-allocation for a North Carolina-style workflow using the general 3-year period.

Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Apply the “3-year window” logic

North Carolina’s general statute of limitations period is 3 years (per the brief’s jurisdiction data). With these inputs:

• Start: 2022-05-10
• End (filing): 2025-05-20
• Time elapsed: 3 years + 10 days

Because the filing date falls just outside a strict 3-year measurement from the start date, this example demonstrates how the limitation gate can materially change which portions are treated as recoverable in the calculator’s simplified output logic.

Step 2: Allocate across damage categories, then apply the time gate

Next, the model uses your category amounts and weights. However, because this run uses only the general/default 3-year rule (and no claim-type-specific sub-rule), the time gate prevents the categories from being treated as timely under this simplified approach.

In this worked run, the model output “time-adjusted recoverable %” is 0.00 for each category.

Why it zeros out in this run: the calculator is treating the start-to-filing timeline as not meeting the general 3-year window, and the example does not apply any additional, claim-type-specific timing rule.

Step 3: Total damages allocation result

Total time-adjusted recoverable damages (modeled):
$0 + $0 + $0 = $0

Practical takeaway: in this example’s simplified model, the SOL timing input dominates the allocation. If the timeline fails the general 3-year gate, the recoverable share can collapse to zero—even if the category amounts and weights look reasonable.

Jurisdiction-aware context (SAFE Child Act reference)

Your jurisdiction data includes the “SAFE Child Act” and a North Carolina DOJ support page:

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

For this worked example, the key point is procedural: we do not convert that narrative reference into a specialized limitations sub-rule, because the brief instructs that no claim-type-specific sub-rule was found. The model here intentionally applies only the general/default 3-year SOL period.

Gentle disclaimer: this is a demonstration of how to use DocketMath with the inputs provided. Limitations questions can depend on facts and specific legal doctrines not captured by a generic calculator.

Sensitivity check

The goal of a sensitivity check is to show how small timing changes can shift outcomes. Here are two quick “what if” runs you can mimic in DocketMath.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity A: Move the filing date back inside the 3-year window

Change only the filing date:

• Filing date (end): 2025-05-09 (instead of 2025-05-20)

Now the elapsed time is 2 years 364 days, which falls within the general 3-year period.

Modeled expectation: under the simplified time-gate logic used in this example, the calculator’s time-adjusted recoverable % may shift to 1.00 across categories.

Total recoverable damages (modeled): $82,900

What this demonstrates: a small date adjustment can flip the SOL “gate,” and that can swing the allocation from $0 to the full modeled amounts.

Sensitivity B: Keep filing date constant, move the trigger start later

Return filing to the original end date (2025-05-20), but move the triggering start:

• Trigger start: 2022-05-20 (instead of 2022-05-10)

Now the elapsed time is exactly 3 years (2022-05-20 → 2025-05-20).

Modeled expectation: a strict 3-year boundary often treats an “exactly 3-year” timeline as timely. In that case, the calculator may again produce 1.00 recoverable % for each category.

Result expectation: again $82,900 total recoverable damages (modeled), under the same simplified assumptions as Sensitivity A.

Pitfall to remember: the “triggering event” date can be disputed in real cases. Even small differences may matter when a tool applies a hard 3-year rule.

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