Damages Allocation Guide for North Dakota — 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 applies North Dakota’s comparative fault rules to help you estimate how a total damages amount might be split among multiple parties based on their percentage of fault.
Under North Dakota law, the “allocation” concept typically appears as:
- Fault percentages assigned to each person/entity involved in the event, and then
- A damages share calculated for each party based on those percentages.
This guide shows how to think about those inputs and how the output changes when fault percentages or damages inputs change. It’s designed for practical planning and case evaluation—not legal advice.
Note: This calculator helps with allocation math. It does not determine fault or establish liability. In real cases, courts decide fault based on evidence and instructions to the jury or factfinder.
When to use it
Use DocketMath’s comparative fault damages allocation tool when you have (or are modeling) the following in a North Dakota context:
- More than one party is allegedly responsible (e.g., drivers in a crash, multiple contractors on a property claim, co-defendants in a business dispute).
- You have a fault breakdown you want to test, such as:
- A jury verdict form showing fault percentages, or
- Litigation planning assumptions (e.g., “What if Plaintiff is 25% at fault?”).
- You want to translate fault percentages into:
- Net shares for each party (who pays what), and
- An estimate of the overall recovery (e.g., whether Plaintiff’s share is reduced).
- You’re evaluating settlement range using a damages number plus fault assumptions.
The tool is especially useful because changing just one percentage (like shifting fault from 20% to 30%) can noticeably change each party’s exposure.
Quick eligibility checklist (math-ready inputs)
Step-by-step example
Below is a concrete example you can mirror in DocketMath’s damages-allocation tool: Damages Allocation Calculator.
Scenario: Multi-party car accident (three parties)
Assume:
- Total damages (before fault reduction): $200,000
- Fault percentages:
- Driver A: 60%
- Driver B: 25%
- Driver C: 15%
Step 1: Enter the total damages
- Total damages: $200,000
Step 2: Enter fault percentages by party
- A: 60%
- B: 25%
- C: 15%
Step 3: Calculate each party’s share
A simple allocation approach looks like:
| Party | Fault % | Estimated damages share |
|---|---|---|
| Driver A | 60% | $200,000 × 0.60 = $120,000 |
| Driver B | 25% | $200,000 × 0.25 = $50,000 |
| Driver C | 15% | $200,000 × 0.15 = $30,000 |
| Total | 100% | $200,000 |
Step 4: Interpret who reduces whom
In many typical “plaintiff vs. defendants” models, you’ll focus on:
- Plaintiff recovery reduced by plaintiff’s assigned fault; and/or
- Each defendant’s payment proportional to its assigned fault.
Because party roles can vary (sometimes the “plaintiff” is one of the faulting parties), DocketMath’s tool is most helpful when you label parties clearly:
- “Your side” vs. other parties, and
- Which share you treat as recoverable.
Common scenarios
Comparative fault allocation shows up in a variety of contexts in North Dakota. Here are common patterns—and what changes in the tool.
1) Plaintiff partially at fault (classic “recovery reduction” model)
Model:
- Plaintiff: 20% fault
- Defendant 1: 50% fault
- Defendant 2: 30% fault
- Total damages: $100,000
Math effect:
- Plaintiff’s net recovery (if you treat defendants as the payers for the full damages base) often becomes:
- $100,000 × (1 − 0.20) = $80,000
Then each defendant’s share of the recoverable amount is proportional to their fault among the responsible parties as you model it.
Example allocation table (using the fault-split)
| Party | Fault % | Share of $100,000 |
|---|---|---|
| Plaintiff | 20% | $20,000 |
| Defendant 1 | 50% | $50,000 |
| Defendant 2 | 30% | $30,000 |
If you’re modeling net recovery for Plaintiff, the “at-fault portion” is the slice attributed to Plaintiff.
2) Multiple defendants, plaintiff fault is low or high
Two quick swings to test with the calculator:
- Low plaintiff fault (e.g., 5%):
- Plaintiff net recovery is close to total damages.
- High plaintiff fault (e.g., 60%):
- Plaintiff recovery drops sharply, leaving less exposure for defendants in proportion to their fault.
Use the tool to see how sensitive the estimate is to fault percentage changes.
3) Cross-claims and more than one claimant
Some cases include:
- A plaintiff with fault, plus
- Cross-defendants with assigned fault, and sometimes
- Multiple claimants.
In those situations, you’ll benefit from creating a party list that includes every participant you want allocated in the tool. The key is consistency:
- Make sure every percentage corresponds to a named party.
4) Fault percentages don’t sum to 100%
Juries sometimes produce allocations that, once converted, may not sum neatly to 100 due to rounding.
DocketMath’s calculator flow generally assumes you provide percentages that can be normalized. If your numbers are close (like 33/34/33), you’ll still get a clean allocation.
Warning: If your inputs total far from 100% (for example, 70% across known parties but 30% missing), the tool’s output won’t match the scenario you intend. Add the missing party or explicitly decide how you want to handle “unknown fault.”
5) Settlements and partial payment planning (math budgeting)
While comparative fault drives allocation, settlements often depend on negotiation. This calculator still helps because you can:
- Model fault allocation, then
- Set an estimated exposure baseline for each party.
For example, if you have:
- Total damages estimate: $250,000
- Defendant shares based on fault:
- Defendant A: 40%
- Defendant B: 60%
You can estimate:
- A’s proportional exposure: $100,000
- B’s proportional exposure: $150,000
Then you can compare settlement offers against that baseline.
Tips for accuracy
These practical steps will reduce surprises when you run multiple what-if rounds in DocketMath.
Use consistent party labels
Create names you’ll reuse across scenarios:
- “Plaintiff”
- “Defendant A”
- “Defendant B”
- “Third-party”
- “Employer” or “Contractor” (if included in your model)
When party names stay consistent, you can compare outputs across different fault assumptions.
Double-check units for damages
Confirm the damages figure you enter is in the same unit you want out:
- If you input $200,000, the output will be in dollars.
- If you’re modeling medical bills only, input medical bills only—don’t mix categories unless you mean to.
Suggested approach: build a total
If you have component damages, sum them before entering:
- Medical expenses: $X
- Lost wages: $Y
- Property damage: $Z
- Non-economic damages: $W (if you’re including them in your model)
Then:
- Total damages = X + Y + Z + W
Normalize or correct percentages intentionally
If you’re using trial-verdict numbers, use them as given. If you’re using estimates, decide:
- Are you treating the fault as “all parties known,” or
- Do you need an “other/unidentified” bucket?
A simple checklist:
Run sensitivity tests
Comparative fault is often litigated. Instead of one run, do 3–5:
This gives you a range rather than a single point estimate.
Keep role perspective straight
Some inputs are “who has fault,” while outputs might reflect:
- who pays, and/or
- who recovers.
Before reading outputs, decide which side you’re tracking:
- “My side’s recoverable share,” or
- “Each defendant’s proportional exposure.”
Pitfall: Treating every party’s share as “payment owed” can be wrong if the scenario involves a claimant who both contributes to fault and seeks recovery. In many models, the claimant’s fault reduces what they can recover, not what they pay.
Related reading
Related reading
- Damages Allocation Guide for Alabama — Comparative Fault Rules — Complete guide
- Damages Allocation Guide for Alaska — Comparative Fault Rules — Complete guide
