How to run Damages Allocation in DocketMath for North Carolina

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for North Carolina (US-NC). The workflow below is jurisdiction-aware, but it’s not legal advice—think of it as a practical setup checklist so your numbers reflect how North Carolina treats liability and contribution.

Jurisdiction/statute context: North Carolina’s Uniform Contribution Among Tortfeasors Act is N.C. Gen. Stat. § 1B-1 to § 1B-6, which governs contribution among joint tortfeasors (i.e., how defendants share liability for amounts owed). It does not replace the plaintiff-bar effect of contributory negligence.

Important: No claim-type-specific sub-rule was found in the source brief. Treat the guidance in this setup as the general/default period for the US-NC Damages Allocation jurisdiction rules.

1) Open the correct tool and select the calculator

1. Start at the primary CTA: /tools/damages-allocation
2. Confirm the calculator is set to Damages Allocation.
3. Set jurisdiction to North Carolina (US-NC) so DocketMath applies North Carolina-specific logic.

2) Gather the figures you’ll enter (inputs)

Damages Allocation typically requires you to supply inputs like:

• Total damages (the base number before allocation/contribution logic)
• Plaintiff fault / negligence factor (as applicable in your workflow)
• Defendant fault / negligence factor(s) (especially if multiple defendants are included)
• A contribution-ready structure (e.g., multiple tortfeasors/defendants)

If you’re unsure which fields map to your case, use the tool’s prompts and input labels. The goal is to collect what the tool expects, not to guess how fields correspond.

3) Enter fault factors and confirm units

In North Carolina workflows, the outputs you see will be strongly influenced by two concepts:

1. Pure contributory negligence (plaintiff fault can bar recovery entirely if it is a proximate cause)
2. Contribution among joint tortfeasors under N.C. Gen. Stat. § 1B-1 to § 1B-6 (allocation/sharing among defendants)

Practical checks before you run:

• Use the scale the tool expects. If DocketMath expects percentages, enter 0–100 consistently. If it expects decimals, enter 0.0–1.0 consistently. Don’t mix formats across parties.
• Keep fault inputs aligned across scenarios. When troubleshooting, change one variable at a time (often plaintiff fault) so you can tell what caused the output shift.

4) Run the calculation

1. Click Calculate (or the tool’s equivalent run action).
2. Review the output sections in this general order:

   • Plaintiff recovery impact (the plaintiff-bar logic is usually reflected here)
   • Allocation among defendants (if multiple defendants were modeled)
   • Contribution-related adjustments (to reflect contribution logic under § 1B-1 to § 1B-6)

5) Interpret outputs using North Carolina rules (what changes and why)

North Carolina’s pure contributory negligence is often the biggest “switch” affecting outcomes:

• If the tool’s logic determines the plaintiff’s negligence is a proximate cause, the plaintiff’s recovery may be reduced to zero.
• The Uniform Contribution Among Tortfeasors Act (N.C. Gen. Stat. § 1B-1 to § 1B-6) then addresses how liability is shared among defendants—but it does not override the rule that contributory negligence can bar the plaintiff’s recovery.

What to expect in practice:

• More plaintiff fault (holding other inputs constant) can dramatically reduce “plaintiff recovery,” potentially yielding a 0 recovery outcome.
• More or less total damages will typically scale the dollar results if the plaintiff is not barred. But the key question is whether plaintiff recovery survives the contributory negligence logic.

6) If you have multiple defendants, validate the contribution structure

If your case involves more than one defendant, confirm:

• The tool is configured to model multiple tortfeasors/joint parties.
• You entered fault factors for each defendant that reflect how you want the tool to allocate responsibility.
• You included all defendants you intend to be part of the allocation/contribution computation (omitting a party can distort allocation among those remaining).

7) Document your run assumptions for repeatability

Before exporting or saving results, record:

• The exact fault inputs you entered (plaintiff and each defendant)
• The total damages number used
• Whether the run included one defendant or multiple defendants

This makes it easy to run controlled “what-if” tests. For example, if you change plaintiff fault from 10% to 30%, you should be able to explain why plaintiff recovery changed without reworking other assumptions.

Common pitfalls

Most “wrong result” experiences in DocketMath Damages Allocation come from input mismatches or misunderstanding how North Carolina’s rules map to outputs.

• Forgetting it’s pure contributory negligence (not comparative).
  Under North Carolina’s common-law rule, plaintiff negligence that is a proximate cause can bar recovery entirely (see Smith v. Fiber Controls Corp., 300 N.C. 669 (1980)).

• Mixing fault input formats.
  Example: entering 0.3 for one party and 30 for another without confirming the tool’s expected scale.

• Omitting a defendant when modeling multiple parties.
  Allocation and contribution outputs depend on who is included in the modeled set.

• Assuming the tortfeasor contribution statute controls plaintiff recovery.
  N.C. Gen. Stat. § 1B-1 to § 1B-6 governs contribution among tortfeasors. Plaintiff-bar effects come from contributory negligence principles (not the contribution statute).

• Assuming claim-type-specific sub-rules exist in this setup.
  Per the brief, no claim-type-specific sub-rule was found. Treat this setup as the general/default period for North Carolina within this tool configuration.

Pitfall example: If you only adjust total damages, dollar amounts may move—but if the output is 0 (or changes sharply), the underlying driver is often plaintiff fault and the contributory negligence logic.

Try it

Use DocketMath to run a quick scenario and confirm you understand how North Carolina logic affects results.

Quick testing checklist

• Set jurisdiction to North Carolina (US-NC)
• Enter a baseline total damages value
• Run scenario #1 with low plaintiff fault
• Run scenario #2 with higher plaintiff fault (proximate-cause scenario in contributory negligence terms)
• If modeling multiple defendants, keep defendant fault inputs consistent between runs so changes are attributable to plaintiff fault

What you should expect to observe

If your results don’t match what you expect from these patterns, re-check:

• the fault input scale/units
• whether you modeled all defendants
• whether plaintiff fault is left at a default unintentionally

Need to move from inputs to calculations quickly? Use the tool here: /tools/damages-allocation .

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance

North Carolina statutes referenced in this guide

• N.C. Gen. Stat. § 1B-1 to § 1B-6 (Uniform Contribution Among Tortfeasors Act) (chapter page): https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/ByChapter/Chapter_1B.html
• Common-law contributory negligence: Smith v. Fiber Controls Corp., 300 N.C. 669 (1980)