Damages Allocation rule lens: North Dakota
6 min read
Published April 15, 2026 • By DocketMath Team
The rule in plain language
Run this scenario in DocketMath using the Damages Allocation calculator.
In North Dakota, many civil “damages” disputes come down to who pays what share when multiple causes contribute to a loss. The core allocation lens is:
- North Dakota uses comparative fault (not joint-and-several allocation by default).
- A defendant is generally responsible for damages in proportion to that defendant’s percentage of fault.
- If a plaintiff’s fault is involved, the plaintiff’s recovery is typically reduced by their share of fault.
- North Dakota also has limits and special rules that can affect available categories of damages and how liability is apportioned across parties.
From a practical perspective, DocketMath’s Damages Allocation approach for US-ND is designed around one question: what percentage allocation inputs produce a legally consistent damage distribution for the claim type you’re working on.
Note: This post focuses on the allocation lens used in calculations. It’s not legal advice, and it won’t cover every fact pattern (for example, whether a particular claim falls under a specific damages category or procedural posture).
What “comparative fault” means for allocation
North Dakota’s comparative fault framework is codified in N.D. Cent. Code § 32-03.2-02 (often cited in litigation materials as the comparative negligence statute). In plain language, it supports allocating liability based on each party’s fault percentages, with the plaintiff’s recovery reduced by their share.
Key implications for calculators and workpapers:
- Percentages must total 100% (or be normalized by the method used in your workflow).
- Damages are distributed by allocation, not by who caused the “last” harm or who is “more responsible” in a non-mathematical sense.
- If the factfinder assigns the plaintiff a share, their recovery decreases accordingly.
Where allocation can change outcomes
Beyond the general comparative fault rule, allocation can be affected by:
- Multiple defendants (each gets an assigned fault percentage).
- Multiple injuries / claim components (allocation may need to be applied per component).
- Different damage types (economic vs. noneconomic; punitive damages may have additional constraints depending on claim and statute framework).
- Setoff or credit concepts that may interact with the net recovery figure (not the same thing as allocation, but it changes the numbers you report).
Because DocketMath is used for jurisdiction-aware calculations, you’ll want to be clear whether you’re allocating:
- Total compensatory damages across parties, or
- A specific damages bucket (e.g., past economic loss only) across parties, or
- A per-party liability cap/limit (if your workflow models those limits separately).
Why it matters for calculations
A damages allocation rule lens isn’t academic—it changes the math your spreadsheet (or case team) produces. In North Dakota, the comparative fault approach has several calculation consequences you can model with confidence when building a DocketMath run.
Small differences in the rule text can change the output materially. Using the correct jurisdiction and effective date ensures the calculation aligns with the authority that applies to your matter.
1) Allocation changes the “who pays” distribution
If you’re splitting damages among multiple defendants, comparative fault means the allocation is driven by fault percentages.
Example logic (allocation mechanics):
- Total damages = $200,000
- Plaintiff fault = 10%
- Defendant A fault = 60%
- Defendant B fault = 30%
A DocketMath-style output should reflect:
- Plaintiff recovery reduced to $200,000 × (1 − 0.10) = $180,000
- Defendant A share = $180,000 × (60% / (60%+30%)) = $120,000
- Defendant B share = $180,000 × (30% / (60%+30%)) = $60,000
The key is normalization: once you reduce by plaintiff fault, you typically allocate the remaining amount among the defendants based on their relative fault shares.
2) Small percentage changes can swing large dollars
Because damages scale linearly with allocation, a 5–10% movement can be material.
Checklist for impact review:
3) You need to document assumptions for defensibility
Damages allocation work often becomes discoverable work product. A clean DocketMath run can help you show:
- the inputs used,
- the allocation logic applied,
- and how outputs changed when fault percentages changed.
That documentation supports credibility when presenting your numbers to stakeholders.
4) Output alignment matters for reporting
Court pleadings, settlement ranges, and internal memoranda often use different “figures”:
- gross damages,
- plaintiff net damages after reduction,
- total defendant exposure by allocation,
- and (separately) offsets/credits.
Don’t mix them in one line item. In DocketMath workflows, keep:
- allocation (fault-based distribution) separate from
- offset/credit (netting out other amounts)
If your internal template combines them, label the lines explicitly.
Warning: Comparative fault allocation is not the same thing as recovery offsets from collateral sources or statutory credits. If your case involves those concepts, apply them as a separate step so the allocation lens remains interpretable.
Use the calculator
DocketMath’s Damages Allocation tool is designed to translate North Dakota’s allocation lens into a repeatable calculation workflow.
If you’re using the tool on US-ND, start here:
Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.
Step 1: Open the calculator
Use the primary CTA:
- /tools/damages-allocation
Step 2: Enter allocation inputs (fault percentages)
Typical inputs you’ll model:
- Total damages (or a specific damages bucket)
- Plaintiff fault % (if applicable)
- Defendant fault % for each defendant
- Whether damages should be allocated across parties (vs. plaintiff net only)
Practical input rules:
Step 3: Understand how outputs change
As fault inputs change, these outputs will adjust:
| Input change | What typically changes in outputs |
|---|---|
| Increase plaintiff fault % | Lower plaintiff net recovery; higher effective defendant shares among remaining fault |
| Shift fault from Defendant A to Defendant B | Defendant A liability decreases; Defendant B increases (net remains reduced by plaintiff fault first) |
| Add/remove a defendant with non-zero fault | Rebalances defendant shares across the remaining parties |
| Change total damages | Scales all outputs proportionally (allocation percentages stay the same) |
Step 4: Export and scenario-test
Use scenario testing to support settlement ranges and internal decision-making:
If you’re preparing a memo, keep the scenario table next to the DocketMath output so readers can see the assumptions quickly.
Step 5: Keep a quick “math sanity check”
After you receive outputs, verify:
Pitfall: A common spreadsheet error is allocating the full damages total across all defendants without first reducing by plaintiff fault. That produces defendant sums that are too large under a comparative fault framework like N.D. Cent. Code § 32-03.2-02.
Sources and references
Start with the primary authority for North Dakota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.