Common Damages Allocation mistakes in North Dakota

The top mistakes

Run this scenario in DocketMath using the Damages Allocation calculator.

Damages allocation is where many North Dakota case teams lose time—and sometimes credibility in later filings. Using DocketMath’s damages-allocation calculator can help you structure numbers consistently, but it can’t fix inputs that don’t match North Dakota’s jurisdiction-aware approach to recoverable damages.

Below are the most common allocation mistakes we see when work is done without a US-ND (North Dakota)-aware structure.

1) Treating every dollar as “compensatory” without separating categories

A frequent issue is lumping multiple types of relief into one undifferentiated total—typically mixing:

• economic losses (often measurable),
• noneconomic losses, and
• any other categories that may require their own proof path.

Typical symptom: your allocation sheet has only one bucket (for example, “damages = total”), but the filing and evidence strategy depends on mapping amounts to the elements you’re proving.

How it shows up in DocketMath outputs: the math can be internally consistent, yet the allocation won’t explain how totals connect to the proof required for each category.

2) Ignoring timing—using “current” numbers for older periods

Another recurring error is applying one date (or one “as of” assumption) to multiple components when the alleged harm spans time.

That can distort components like:

• wage/earning loss by period,
• out-of-pocket expenses by reimbursement timing,
• medical costs by service date,
• and any timing-sensitive calculations you may perform.

Typical symptom: you allocate by category, but each component isn’t aligned to the period you’re actually proving.

DocketMath angle: if you enter dates inconsistently, you can end up with a total that adds up—while still being conceptually mismatched to the time period supporting each number.

3) Getting comparative fault handling wrong (or skipping fault allocation altogether)

In negligence cases, North Dakota’s comparative fault concepts can change how recoverable damages are calculated. A common error isn’t just miscomputing percentages—it’s skipping the right allocation stage or failing to apply the correct limits consistently.

Typical symptom:

• you calculate damages assuming 100% responsibility even after fault is assigned elsewhere, or
• you apply percentages but don’t apply the modified-comparative-fault cap/threshold logic in a consistent way.

4) Double-counting overlapping items (especially medical + future care)

Allocators sometimes count the same underlying need twice, such as:

• medical bills and a “future medical” figure that already assumes the same services, or
• lost wages plus reduced earning capacity without clarifying the underlying assumptions.

Typical symptom: two line items describe the same harm with different labels.

DocketMath angle: the calculator will sum what you input. It can’t detect overlap automatically—so inflated totals are often an inputs problem, not a math problem.

5) Using net numbers without documenting deductions and offsets

Many teams present amounts net of payments, reimbursements, or offsets. The error is reducing totals “somehow” and not documenting:

• what was deducted,
• what it was deducted from (medical vs. wages vs. other categories),
• and whether timing matters to your proof method.

Typical symptom: the line items don’t reconcile to invoices, statements, checks, or other records.

6) Confusing “liquidated” amounts with proof that still needs an evidence method

Not every number is equally document-ready. In practice, some damages are supported with clear records, while others rely on estimation assumptions.

Typical symptom: the allocation shows a confident number without capturing how it was derived—especially when the evidentiary basis is not directly “one invoice equals one number.”

7) Failing to reconcile the allocation back to the case theory

Even if the calculations are tidy, allocation can be unusable if it doesn’t track the theory of damages in the complaint and your proof plan.

Typical symptom: you can’t explain how each category supports the causes of action and elements you’re pursuing.

How to avoid them

You can reduce allocation mistakes quickly by using a disciplined workflow with DocketMath’s damages-allocation calculator, and treating results as a consistency check—not a substitute for proof planning.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

1) Start with a category map (not a single total)

Before you enter anything into /tools/damages-allocation, decide what buckets you’ll allocate (and why). For example:

• Economic losses (with sub-items)

  • medical (by service dates where possible),
  • out-of-pocket expenses,
  • lost wages by pay period/month range
• Noneconomic losses (if applicable)
• Any special/statutory damages categories you intend to plead
• Fault allocation (if your case type requires it)

Then use a checklist:

• Each line item belongs to a specific category
• Each line item has a date range (or a documented basis for not needing one)
• No underlying expense appears in two line items

2) Align components to the correct period

Build the allocation using service dates and payment dates where available.

• Medical: align to service dates (or at least the period being proved)
• Wages: align to pay periods or month ranges
• Expenses: align to the harm window and reimbursement timing you’re relying on

In DocketMath, this often produces a different total after you correct date alignment—especially for components sensitive to timing.

3) Use DocketMath output to validate your narrative

A practical sequence:

1. draft allocations from records,
2. enter them into DocketMath,
3. review outputs against your proof plan.

If totals don’t reconcile with your evidence strategy, treat it as a signal to revisit inputs (not to “tune numbers until they fit”).

4) Centralize comparative fault logic

For negligence cases with comparative fault, avoid spreading fault logic across multiple spreadsheets.

• Fault percentages sum correctly (commonly to 100%)
• Apply the same fault-adjustment logic consistently across affected categories
• Confirm you’re not calculating recoverable damages as if liability is 100% on the defendant

5) Document deductions at the line-item level

Instead of netting everything at the end, record deductions beside the items they offset:

• what the deduction is (reimbursement/offset),
• what it offsets (medical vs. wages),
• and when it occurred if timing matters to your proof approach.

This keeps the allocation easier to revise when new documentation arrives.

6) Prevent overlap with a “single source” rule

Adopt a simple rule:

• Each harm has one “owner” line item.
• If you include future care, define it as what’s beyond already-billed services.

Pitfall to watch: two items can both look like “medical,” but one may be past invoices while the other is future services. Without explicit separation, the allocation can be inflated while still looking plausible.

7) Reconcile back to the filing narrative before finalizing

Before you lock the allocation:

• Category totals match the damages theory you’re presenting
• You can point to the exhibit/record type supporting each category
• Fault-adjusted totals align with your case type’s liability framework

This step improves credibility and reduces rework under deadlines.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules