Damages Allocation Guide for Northern Mariana Islands — Comparative Fault Rules

7 min read

Published March 22, 2026 • By DocketMath Team

What this calculator does

Run this scenario in DocketMath using the Damages Allocation calculator.

DocketMath’s Damages Allocation tool helps you estimate how a jury (or judge) may allocate damages among parties based on comparative fault in the Northern Mariana Islands (US-MP). It’s designed for situations where more than one person (or entity) may be responsible for the same harm and fault is contested.

At a high level, the calculator uses a comparative fault allocation model:

  • Assign percent fault to each responsible party (e.g., 70% plaintiff, 30% defendant—if the fact pattern supports it).
  • Apply those percentages to compute each party’s share of recoverable damages.
  • Handle common variations like total damages, economic vs. non-economic categories, and multiple defendants.

Note: This guide focuses on comparative fault-based allocation. It does not attempt to model every damage limitation, evidentiary issue, or specialized doctrine that may apply in a particular case.

What the output typically includes

Depending on how you run the tool, you’ll generally see:

OutputWhat it meansWhy it changes
Net damages recoverable (overall)Total damages reduced by plaintiff’s faultChanges when plaintiff’s % fault changes
Defendant share(s)Each defendant’s percentage of the remaining damagesChanges with how fault is split among defendants
Category splitsAllocation by damage type (if you enter categories)Changes when you enter different totals per category
Sanity checksWarnings if inputs don’t sum to ~100%Prevents unrealistic allocations

If you’re new to the workflow, start with the primary CTA here: /tools/damages-allocation.

You can also review related workflows in /tools via this link (handy for how DocketMath structures inputs): /tools/damages-allocation.

When to use it

Use DocketMath when you need a defensible, transparent way to estimate how comparative fault could affect recoverable damages in a Northern Mariana Islands case.

Good fit for these use cases

  • Car and pedestrian incidents where both parties’ conduct is contested.
  • Slip-and-fall disputes involving alleged negligence by a premises party and contributory conduct by a claimant.
  • Multi-defendant cases (e.g., two drivers, or a contractor + property operator) where fault is apportioned.
  • Scenarios where you want to test “what if” outcomes:
    • What happens if plaintiff’s fault is argued as 10% vs. 40%?
    • What happens if the fault split between two defendants changes from 60/40 to 50/50?

Situations where the tool may be less reliable

  • Cases driven mostly by strict liability or a doctrine that doesn’t hinge on comparative fault in the same way.
  • Damage calculations dominated by special statutes, caps, or mandatory offsets that aren’t modeled by the tool inputs you provide.
  • Disputes where fault allocation is uncertain to the point that percent fault would be speculative (the calculator can still run, but results will be scenario-based).

Step-by-step example

Below is a worked example using a hypothetical Northern Mariana Islands comparative fault setup. The goal is to show how inputs drive outputs, not to predict a real case result.

Scenario

A claimant is injured in a roadway incident involving two drivers and a pedestrian. Parties argue the claimant’s own behavior contributed to the accident.

  • Total proven damages (before allocation): $120,000
    • Economic damages: $70,000
    • Non-economic damages: $50,000

Fault is disputed; you enter these assumptions for the scenario:

  • Plaintiff (claimant): 25%
  • Defendant A (Driver 1): 50%
  • Defendant B (Driver 2): 25%

Step 1: Enter the damage totals

In the DocketMath calculator (/tools/damages-allocation), you would enter:

  • Total damages: $120,000
  • Category breakdown (optional but recommended):
    • Economic: $70,000
    • Non-economic: $50,000

How the output changes: If you enter only total damages, the calculator will allocate the same reduction proportionally. If you enter categories, you’ll see category-by-category outcomes.

Step 2: Enter comparative fault percentages

Add parties and percentages:

  • Plaintiff: 25
  • Defendant A: 50
  • Defendant B: 25

Sanity check expectation: Most comparative-fault models require the percentages to sum to 100%. If they don’t, the tool should flag a warning.

Warning: If your percentages add to 90% or 110%, the tool’s allocation math can produce misleading results. Adjust inputs until the totals make sense for your scenario.

Step 3: Apply the plaintiff fault reduction

A comparative fault model reduces the claimant’s recoverable amount by the claimant’s percentage fault.

  • Claimant’s non-recoverable share (25%):
    $120,000 × 0.25 = $30,000
  • Recoverable damages (after reduction):
    $120,000 × 0.75 = $90,000

Step 4: Allocate the remaining damages among defendants

Now allocate the remaining $90,000 across defendants based on their fault shares relative to the non-claimant fault.

Non-claimant fault = Defendant A 50% + Defendant B 25% = 75%

  • Defendant A share: (50 / 75) × $90,000 = $60,000
  • Defendant B share: (25 / 75) × $90,000 = $30,000

Example results summary

ComponentAmount
Total damages$120,000
Plaintiff fault (25%)-$30,000
Recoverable damages$90,000
Defendant A share (50% of non-claimant fault)$60,000
Defendant B share (25% of non-claimant fault)$30,000

What happens if the plaintiff’s fault changes?

Try a quick sensitivity run:

  • If plaintiff were found 10% at fault instead:
    • Recoverable = $120,000 × 0.90 = $108,000
    • Defendant A share = (50/90)×$108,000 = $60,000
    • Defendant B share = (25/90)×$108,000 = $30,000

Interestingly, in this specific scenario the defendants’ dollar totals stayed the same because the defendant fault percentages didn’t change—only the plaintiff’s portion did. In other fact patterns, different re-allocation arguments will move everyone.

Common scenarios

Comparative fault disputes come in recurring patterns. Here are practical examples you can mirror in DocketMath.

1) Two-party crash (plaintiff + one defendant)

Inputs:

  • Total damages: $80,000
  • Plaintiff fault: 20%
  • Defendant fault: 80%

Typical outcome logic:

  • Recoverable = $80,000 × 0.80 = $64,000
  • Defendant pays = $64,000

Use this when you expect a single defendant and the dispute is about proportional fault.

2) Multi-defendant allocation (split among two defendants)

Inputs:

  • Total damages: $200,000
  • Plaintiff fault: 30%
  • Defendant A: 45%
  • Defendant B: 25%

Allocation approach:

  • Recoverable = $200,000 × 0.70 = $140,000
  • Defendant A gets (45/70) × $140,000 = $90,000
  • Defendant B gets (25/70) × $140,000 = $50,000

3) Category-driven planning (economic vs. non-economic)

Sometimes teams want to understand how comparative fault affects each category for mediation demands or settlement ranges.

Example inputs:

  • Economic damages: $60,000
  • Non-economic: $40,000
  • Total: $100,000
  • Plaintiff fault: 35%
  • Defendant fault: 65%

Recoverable:

  • Economic: $60,000 × 0.65 = $39,000
  • Non-economic: $40,000 × 0.65 = $26,000
  • Total recoverable: $65,000

Run this when your settlement posture depends on how much of the claim is “hard” vs. “pain and suffering” style damages.

4) “All parties at fault” narratives

In some disputes, the parties frame fault broadly:

  • Plaintiff fault alleged: 40%
  • Defendant A: 35%
  • Defendant B: 25%

Recoverable:

  • $Total × 0.60 Defendants:
  • allocated proportionally among the non-plaintiff fault pool.

Use this if your briefing expects an apportionment among multiple actors.

5) “Extreme fault” scenario testing

Even if you don’t believe an extreme outcome is likely, it’s often useful to model outcomes across a range:

  • Plaintiff fault scenarios: 10% / 30% / 50%
  • Keep total damages constant

What you learn:

  • Whether your settlement range is fragile to fault arguments
  • Which damages categories matter most to the net number

Tips for accuracy

Getting the most reliable estimates from DocketMath depends on disciplined inputs. Use the checklist below.

Fault input checklist

Damages input checklist

Sources and references

Start with the primary authority for Northern Mariana Islands and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading