How to run Settlement Allocator in DocketMath for Minnesota

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for Minnesota (US-MN). You’ll use DocketMath’s jurisdiction-aware rules and the general/default Minnesota Rule 23 timing period referenced in Minn. R. Civ. P. 23.01–23.05.

Primary CTA: /tools/settlement-allocator

1) Choose the Minnesota jurisdiction profile (US-MN)

1. Open DocketMath → Settlement Allocator here: /tools/settlement-allocator
2. In the calculator, set Jurisdiction to Minnesota (US-MN).

Why this matters: the allocator’s timing and allocation logic depends on the jurisdiction assumptions tied to the court rules used for allocation. If you leave the wrong jurisdiction selected, your outputs may not match Minnesota-specific expectations.

2) Enter the core settlement inputs

In the calculator fields, provide the settlement and claimant information the allocator needs. Typical inputs include:

• Settlement amount (total gross settlement)
• Number of claimants (or claimant-specific rows, if the UI uses a table)
• Claimant damages basis (the amount used to allocate—often a “damages” figure per claimant)
• Any caps or adjustments (if the UI supports them)
• Dates used for timing (if the UI requests dates to compute the allocation period)

If the UI uses claimant rows, fill each row with:

• Claimant name/identifier
• Allocable damages (or equivalent “basis” figure)
• Proportion inputs (if provided). Some versions compute proportions automatically from damages; others ask you to enter weightings.

3) Provide timing inputs consistent with Minnesota’s Rule 23 general/default period

If the calculator asks for dates, enter them in the format shown by DocketMath.

Use the timeline that corresponds to the allocator period under Minn. R. Civ. P. 23.01–23.05 (general Rule 23 timeframe).

Rule reference:

• Minn. R. Civ. P. 23.01–23.05
• Source: https://www.revisor.mn.gov/court_rules/cp/id/23/

4) Run the calculation and review the outputs

Click Calculate (or the equivalent button).

DocketMath will generate outputs that typically include:

• Allocated amount per claimant
• Allocation percentages per claimant
• Sanity-check totals (for example, that allocations sum correctly after any adjustments/caps)
• Timing-derived components (if the allocator separates periods or applies date-based logic)

Use this checklist in order:

• Sum check: allocated amounts match the settlement amount (after any specified adjustments/caps)
• Basis check: each claimant’s allocation proportion aligns with the damages basis you entered
• Timing check: date-based results reflect Minn. R. Civ. P. 23.01–23.05 default assumptions (not a claim-type-specific override)

5) Export or capture results for your workflow

If DocketMath offers export (CSV/PDF/share), use it. If not, at minimum, copy:

• The allocation table
• The inputs you used (especially settlement amount, each claimant’s damages basis, and any dates)
• The computed timing period indicators (if shown)

This makes it easier to verify results and rerun quickly if the settlement terms change.

Common pitfalls

Even with a solid input form, a few issues consistently derail allocation results. These are the most common when running Settlement Allocator (US-MN) in DocketMath:

1. Using a non-Minnesota Rule period

   • Symptom: the numbers seem off compared to other Minnesota runs.
   • Fix: confirm the jurisdiction dropdown is Minnesota (US-MN) before calculating.

2. Assuming claim-type-specific Minnesota sub-rules exist in this setup

   • Reality for this guide: Minn. R. Civ. P. 23.01–23.05 is treated as the general/default period. No claim-type-specific sub-rule was identified for this setup.
   • Symptom: you manually adjust timing for only certain claim types.
   • Fix: align to the default period used through Minn. R. Civ. P. 23.01–23.05.

3. Mismatched currency/units

   • Example: entering $250,000 in one field and 250 in another, or accidentally entering amounts “in thousands.”
   • Fix: verify formatting and units across all amount fields before running.

4. Non-summing allocation totals

   • Symptom: allocated amounts don’t total the settlement amount after calculation.
   • Common causes:

     • rounding settings
     • caps/adjustments entered inconsistently
     • claimant damages bases that don’t match allocation assumptions
   • Fix: check cap/adjustment fields first, then confirm each claimant basis value.

5. Date format inconsistencies

   • Symptom: the tool interprets dates incorrectly (for example, swapped month/day).
   • Fix: follow the exact date format required by DocketMath, then re-check the computed period indicators.

Validation tip: when troubleshooting, change one variable at a time (for example, only the settlement amount, or only one claimant’s damages basis). This makes it much easier to understand what caused the output change.

Try it

To validate your Minnesota setup quickly, run a mini-test in DocketMath → Settlement Allocator:

1. Open /tools/settlement-allocator
2. Set Jurisdiction = Minnesota (US-MN)
3. Use a simple scenario and run the calculator.

Quick validation checklist (10–15 minutes)

• Jurisdiction = Minnesota (US-MN)
• Enter a simple scenario:

  • 2 claimants
  • one settlement amount (single total)
  • clear damages basis values per claimant
• Provide dates that correspond to Minn. R. Civ. P. 23.01–23.05 (general/default Rule 23 period)
• Run the calculator
• Confirm:

  • both claimants appear in the allocation output
  • percentages add up to 100% (or within rounding tolerance)
  • allocations total to the settlement amount (after adjustments/caps, if you used them)

What to watch when inputs change

Try two controlled edits:

• Edit A: Settlement amount

  • Expect: each claimant’s allocated amount scales proportionally (unless caps/adjustments change the outcome).
• Edit B: One claimant’s damages basis

  • Expect: that claimant’s allocation percentage changes, with other claimants adjusting inversely to keep totals consistent.

When you’re done, save/export the output so you can compare results later if settlement terms or claimant bases change.

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations