How to run Damages Allocation in DocketMath for North Dakota

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for North Dakota (US-ND) using jurisdiction-aware rules. You’ll learn exactly what to enter, how the calculator behaves, and what outputs to check before you rely on them in work product.

1) Open the calculator and set the jurisdiction

1. Go to /tools/damages-allocation (or use the primary CTA).
2. Ensure the jurisdiction is set to North Dakota (US-ND).
3. Confirm you’re using the Damages Allocation calculator (not a different calculator mode).

What to look for

• A jurisdiction label like US-ND or North Dakota visible near the input panel.
• Any ND-specific toggles or wording that indicates jurisdiction-aware rules are active.

2) Identify the allocation “buckets” the calculator expects

Damages Allocation typically requires you to enter:

• Total damages (the amount to allocate)
• Eligible categories (for example, different damages components)
• Allocation parameters (how damages distribute across parties, time periods, or categories)

If you see multiple sections, treat them as separate “buckets” that will roll up into a final allocation table.

Quick sanity check

• If the total you enter does not match the sum of component entries you intend to use, outputs will still compute—so you’ll want to reconcile inputs before you export.

3) Enter case facts as numeric inputs (and keep units consistent)

In North Dakota runs, you’ll want to be consistent about the numeric meaning of each field. Common input types include:

• Amounts: enter in dollars (no commas; use plain numbers if the UI requests it)
• Percentages: enter as whole numbers (e.g., 35) or decimals (e.g., 0.35) depending on the field format
• Time windows: enter in days, months, or years based on the UI’s labels

Example workflow

• Start with Total damages.
• Then fill each damages component or party share.
• Finally, ensure any percentage/ratio fields add up correctly (or the UI confirms automatic balancing).

How outputs change

• If you change a component amount, the final allocation table updates instantly.
• If you change a percentage, the tool recalculates each corresponding share and the remainder (if applicable).

4) Use ND-aware settings (if present) to choose the allocation method

Some DocketMath configurations include an allocation approach selector. When you see options, choose the one that matches your modeling goal, such as:

• Allocation by damages category
• Allocation by party share
• Allocation by time period
• Allocation by fault or responsibility percentages (if included in the calculator)

Because you’re running US-ND, the tool may adjust labels, checks, or default behavior to fit that jurisdiction’s workflow conventions.

5) Review the allocation table and totals

After inputs, you should get:

• A table showing allocated amounts per category/party (depending on the configuration)
• A grand total (should tie back to your total damages input, subject to rounding)
• Any diagnostic warnings the tool provides (e.g., totals don’t reconcile)

Checklist for reconciliation

6) Export or copy results for your workflow

Once the allocation looks right:

• Use the UI’s copy/export option (PDF/CSV/export button depends on your interface).
• Save the run with a clear name like:

  • “ND Damages Allocation – Trial model – v1 (2026-04-15)”

Then, if DocketMath offers a way to compare versions, run a quick v2 after any edits (for example, changing a percentage or component amount).

7) Capture a brief “inputs & assumptions” note alongside results

To keep your record clean, write down:

• The inputs you used (especially total damages, allocation percentages, and component amounts)
• Any method selection you chose in the calculator
• The date/time you ran the model

This makes it easier to explain the math later without revisiting every assumption.

Common pitfalls

Damages allocation runs are easy to compute but easy to mis-model. Watch for these recurring issues when running US-ND in DocketMath.

1. Totals don’t reconcile

   • Symptom: Allocated amounts don’t sum to your Total damages.
   • Common causes:

     • A category left blank (defaults to 0)
     • Percentages not adding up to 100%
     • Rounding differences across multiple rows

2. Mixed allocation styles

   • Example: Entering some categories as fixed amounts while also entering percentage fields that drive the rest.
   • Result: A mathematically consistent outcome that doesn’t match your intended structure.

3. Incorrect percentage format

   • Many tools interpret 35 as 35%, while others interpret 0.35 as 35%.
   • If you enter the wrong format, every downstream allocation shifts materially.

4. Time-window mismatch

   • If the tool includes time-based components (e.g., before/after a date), confirm:

     • The time labels in the UI match your intended periods
     • The units (days vs months vs years) match the numbers you typed

5. Rounding creates small residuals

   • Even when everything “should” sum cleanly, totals can differ by a few dollars.
   • Strategy: identify whether the tool rounds per-row or at the final total and keep that consistent across versions.

6. Forgetting to verify ND-specific configuration

   • If the jurisdiction selector changes, you might lose ND-specific checks and defaults.
   • Quick fix: confirm US-ND remains active before exporting.

Try it

If you want to jump straight into a North Dakota run, start here:

• Open /tools/damages-allocation
• Confirm jurisdiction: **North Dakota (US-ND)
• Enter a simple scenario first (for example):

  • Total damages: 100,000
  • Two categories or parties with initial percentages (e.g., 60% / 40%) or fixed amounts
• Review:

  • The allocation table
  • The total reconciliation line
  • Any warnings or validation messages

Once the basic run matches your expectations, refine the model using your real numbers and save a versioned output.

For related workflow ideas, you can also explore other calculators and tooling via /tools/ before you commit to a final run:

• Go to /tools/damages-allocation for the calculator itself
• Browse supporting tools under /tools/ to align inputs across your case math

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