How to calculate pain and suffering damages in North Carolina

Direct answer

In North Carolina, there is no single “formula” in N.C. Gen. Stat. § 1B-1 et seq. that tells you how to calculate pain and suffering as a fixed statutory amount. Instead, pain and suffering is generally treated as non-economic damages—a category proved through evidence and assessed by the factfinder—while North Carolina uses the common-law rule of pure contributory negligence to determine whether the plaintiff can recover at all.

Because you’re asking about “calculation,” the practical way to use DocketMath for North Carolina is to:

1. Enter/allocate pain and suffering as a non-economic damages component (evidence-backed valuation), and then
2. Model North Carolina’s pure contributory negligence “recovery bar” so the tool’s outputs correctly reflect that any plaintiff negligence that is a proximate cause can eliminate recovery entirely.

Important default note: Your jurisdiction data did not find any claim-type-specific pain-and-suffering rule. So the guidance below uses North Carolina’s default framework (non-economic damages valuation + contributory negligence eligibility bar), not a special pain-and-suffering sub-rule.

Gentle disclaimer: This is general information to help you structure your inputs in DocketMath. It’s not legal advice, and your actual case can depend on fact-specific rulings.

What you need to know

1) Pain and suffering is usually a non-economic damages category

Pain and suffering typically includes harms like:

• physical pain,
• mental anguish,
• loss of enjoyment of life,
• other non-economic effects not tied to a specific bill or invoice.

In a damages-allocation workflow, that means you should treat pain and suffering as a non-economic line item that is:

• supported by medical and other records, and
• allocated alongside other damages categories (like medical expenses, lost wages, etc.) depending on how your DocketMath setup is structured.

2) Pure contributory negligence can bar recovery entirely

North Carolina retains pure contributory negligence. Under the rule stated in your provided authority (Smith v. Fiber Controls Corp., 300 N.C. 669 (1980)), any negligence by the plaintiff that is a proximate cause of the injury bars recovery entirely.

That “all-or-nothing” effect is the biggest North Carolina-specific driver you should reflect in DocketMath. If contributory negligence is applied as a proximate-cause finding, pain and suffering may drop to $0 even if your non-economic valuation input is non-zero—because the recovery bar controls.

3) Don’t confuse contribution with the plaintiff’s recovery eligibility

Your provided statutes include:

• N.C. Gen. Stat. § 1B-1 to § 1B-6 (Uniform Contribution Among Tortfeasors Act)

This Act generally governs contribution among joint tortfeasors—how blame/responsibility is shared between multiple defendants. It does not replace the plaintiff-level recovery bar created by pure contributory negligence.

So in DocketMath:

• Use contributory negligence inputs to model whether recovery is barred.
• Use tortfeasor allocation/contribution inputs (if available) to model how damages might be shared between defendants (without overriding the bar on the plaintiff’s recovery).

Step-by-step

Use this sequence to calculate and allocate pain and suffering damages in North Carolina (US-NC) in DocketMath, using jurisdiction-aware rules.

1. Open the calculator

   • Use the damages allocation workflow: /tools/damages-allocation

2. Confirm jurisdiction selection

   • Select US-NC to ensure North Carolina’s default framework is applied.

3. Enter pain and suffering as a non-economic damages input

   • In DocketMath, input your pain and suffering amount under the tool’s non-economic category (or the closest available label, such as “Pain & suffering”).
   • If the tool supports ranges, use a range based on evidence (but keep a consistent point estimate for your demand/settlement scenario).

   Practical evidence inputs you can align to your valuation:

   • injury type (soft tissue, fracture, burns, etc.)
   • symptom duration (days/weeks/months)
   • documented follow-up treatment dates
   • objective indicators tied to symptoms (exam findings, imaging reports)
   • credibility/support notes (how records substantiate severity)

4. Set contributory negligence inputs to model the recovery bar

   • If your scenario includes plaintiff negligence, set it in a way that reflects that the negligence is a proximate cause (this is the key trigger for the bar).
   • The expected output behavior is:

     • If the tool applies the pure contributory negligence bar, pain and suffering may become $0 (even if your non-economic valuation input is not $0).

5. Avoid double-counting non-economic harms

   • If DocketMath separates “pain and suffering” from other non-economic categories (e.g., “emotional distress”), make sure your entries describe distinct harms.
   • A common approach is to keep “pain and suffering” broad enough to cover the non-economic concept you intend, and then avoid entering overlapping emotional-distress amounts in addition—unless your strategy is to separate truly different categories.

6. If multiple defendants are involved, allocate among tortfeasors (optional step, dependent on your tool)

   • If your workflow includes tortfeasor allocation, you can allocate pain and suffering among defendants using contribution-style logic.
   • Remember: N.C. Gen. Stat. § 1B-1 to § 1B-6 is about contribution among tortfeasors, not whether the plaintiff can recover in the first place.
   • Therefore, you still need contributory negligence inputs to reflect the plaintiff recovery bar.

7. Run at least two scenarios to see the effect of contributory negligence

   • Scenario 1 (recovery available): model no contributory negligence proximate cause (or the tool’s equivalent “no bar” setting).
   • Scenario 2 (recovery barred): model plaintiff negligence as a proximate cause.

   What to compare:

   • the pain-and-suffering line item
   • total recoverable damages (if your tool computes totals)

8. Export or record your assumptions

   • Save the assumptions you used (injury duration, evidence support, and the negligence/proximate-cause modeling you chose).
   • Your “math” may be straightforward, but your credibility comes from how your pain-and-suffering input matches the record.

Key statutes and citations

• Uniform Contribution Among Tortfeasors Act (contribution among joint tortfeasors)

  • N.C. Gen. Stat. § 1B-1 to § 1B-6
  • Source (as provided): https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/ByChapter/Chapter_1B.html
  • How it fits your calculator: if DocketMath includes tortfeasor contribution/allocation, this is the statutory framework your tool is likely referencing for that aspect.

• Pure contributory negligence (plaintiff recovery bar)

  • Smith v. Fiber Controls Corp., 300 N.C. 669 (1980)
  • Core rule (per your jurisdiction data): North Carolina retains common-law pure contributory negligence—any plaintiff negligence that is a proximate cause of the injury bars recovery entirely.

Default rule clarity (no claim-type-specific sub-rule found)

Your provided jurisdiction data indicates no claim-type-specific sub-rule specific to pain and suffering. Therefore, the approach above uses North Carolina’s default framework rather than a special pain-and-suffering formula.

Common pitfalls

• Assuming there’s a statutory “pain and suffering multiplier” in § 1B

  • The N.C. Gen. Stat. § 1B-1 et seq. materials you provided relate to contribution among tortfeasors, not a fixed pain-and-suffering calculation formula for a single plaintiff.

• Not modeling the contributory negligence recovery bar

  • If your scenario involves plaintiff negligence, failing to set the proximate-cause trigger can lead DocketMath to show recoverable pain and suffering when recovery may actually be barred under Smith v. Fiber Controls Corp.

• Mixing up contribution vs. recovery eligibility

  • Tortfeasor allocation/contribution can matter between defendants, but it does not negate the plaintiff-level bar from pure contributory negligence.

• Double-counting non-economic categories

  • Entering both “pain and suffering” and overlapping “emotional distress” can inflate totals without clearer evidentiary separation.

• Using one number without sensitivity checks

  • Pain-and-suffering valuation is evidence-driven and may vary. Run alternate assumptions (shorter vs. longer duration, different severity descriptions) to understand how sensitive the output is.

Run the numbers

A simple way to run DocketMath so your pain-and-suffering outputs make sense under North Carolina’s rules:

1. Enter your non-economic pain and suffering estimate (evidence-backed).
2. Run:

   • Run A (no proximate-cause contributory negligence bar): capture the pain-and-suffering output and total.
   • Run B (proximate-cause contributory negligence applied): capture the pain-and-suffering output and total again.
3. Compare results:

   • If Run B shows pain and suffering reduced to $0, that reflects North Carolina’s pure contributory negligence recovery bar under Smith v. Fiber Controls Corp.
4. Document the key modeling assumptions:

   • what facts supported the duration/severity inputs
   • what facts were assumed for the contributory negligence/proximate-cause step

This scenario testing is often the fastest way to validate that your **DocketMath