How to run Settlement Allocator in DocketMath for Minnesota

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

Below is a practical walkthrough for running Settlement Allocator in DocketMath for Minnesota (US-MN). The goal is to allocate a settlement amount across common claim categories using jurisdiction-aware rules—so you don’t have to manually compute timelines or override assumptions.

1) Open the tool for the correct calculator

Start at the primary call-to-action:

• Go to /tools/settlement-allocator

If you’re navigating from elsewhere in DocketMath, look for the calculator named “Settlement Allocator.”

2) Confirm the jurisdiction selection is Minnesota

In the jurisdiction selector:

• Choose Minnesota
• Ensure the jurisdiction code shows US-MN

This matters because DocketMath uses Minnesota’s general/default statute of limitations when a more specific rule isn’t applied.

3) Understand the limitations period DocketMath will apply (Minnesota)

For Minnesota, the general SOL period is 3 years, under Minnesota Statutes § 628.26.

• General/default limitations period: 3 years
• Statutory reference: Minnesota Statutes § 628.26
• No claim-type-specific sub-rule was found for this workflow: DocketMath will treat this as the default period unless you provide inputs that indicate a different timing rule should be used.

4) Enter your key inputs (and how they change outputs)

Settlement Allocator typically needs a date/timing anchor and a settlement total, plus any category/eligibility inputs the tool provides. Use the fields that match your workflow.

A. Timeline anchor (the date that drives the “start” of the clock)

• Enter the event/occurrence date (for example, the date of the incident) that should start the limitations period for your model.
• If the tool asks for a different timing anchor (such as a notice or filing-related date), use the one that best matches how you’re modeling the settlement.

How it affects outputs:
When you change date inputs, DocketMath’s internal timeline logic shifts. That can affect whether amounts are treated as within the default 3-year window or outside it, based on Minnesota’s general/default approach.

B. Settlement amount (the total to allocate)

• Enter the total settlement you want allocated across categories.

How it affects outputs:
The tool’s allocation math scales from this total—so category amounts should generally add up to your entered settlement total (subject to rounding).

C. Allocation/category inputs (how the tool splits the total)

• If the calculator provides category toggles or weight fields, select the categories that best match how the settlement is structured in your scenario.
• If the tool allows custom categories, use them only if you can map those categories to the settlement terms.

How it affects outputs:
Changing category weights typically changes the distribution across categories while keeping the overall total the same.

5) Run the allocator and review the limitations-aware results

Click Run / Calculate in the tool.

After the run, review:

• Allocated amounts per category (often shown as a breakdown table)
• Any timeline/eligibility indicators tied to the 3-year default rule
• Summary totals to confirm the allocations reconcile with your settlement amount

If DocketMath shows a “default rule applied” indicator (or similar message), treat that as your confirmation that Minnesota Statutes § 628.26 with a 3-year general/default period is being used.

6) Adjust inputs based on what the output tells you

Use a quick iteration loop:

• If category allocations look unexpectedly high/low, adjust:

  • the timeline anchor date
  • the category eligibility/weights (based on what the settlement terms actually support)
• Rerun until the breakdown reflects the settlement structure you intend to model.

This is the most practical part of DocketMath: you can test how date changes and selection/weight choices affect the final allocations quickly.

Common pitfalls

Even with good inputs, a few issues commonly skew allocation results for Minnesota. Watch for these:

• Using the wrong date anchor

  • If you enter an incident date when your model should start from a different date (like a notice date), the 3-year window may shift.

• Assuming a special statute applies without providing claim-type inputs

  • This workflow uses the general/default 3-year period from Minnesota Statutes § 628.26.
  • Because no claim-type-specific sub-rule was found for this workflow, the tool may not reflect a different SOL unless the tool inputs support it.

• Entering a settlement total that doesn’t match the agreement

  • Small mismatches can create rounding differences across categories, making reconciliation harder.

• Overriding weights without settlement-term support

  • Category weights should match the settlement terms (or a clearly defined modeling assumption). Arbitrary weight changes can make allocations hard to defend.

• Ignoring tool warnings

  • DocketMath may flag date range issues or indicate assumptions. Those messages matter—review them before treating results as final.

Gentle caution: Because this walkthrough relies on Minnesota’s general/default 3-year rule (Minn. Stat. § 628.26), you may get misleading results if your scenario truly depends on a different, claim-specific limitations period and the tool is still treating everything under the default window.

Try it

To run Settlement Allocator for Minnesota (US-MN) in DocketMath:

1. Open /tools/settlement-allocator
2. Set jurisdiction to **Minnesota (US-MN)
3. Enter:

   • your event/timeline anchor date
   • your total settlement amount
   • any category weights or category selections the tool asks for
4. Click Run / Calculate
5. Verify:

   • the output totals match the settlement amount
   • the tool applies the 3-year default SOL logic based on Minn. Stat. § 628.26
   • any timeline/eligibility notes align with your expectations

Quick self-check before relying on results:

When you’re ready to refine, update one input at a time (usually the timeline anchor first) and rerun to see how the allocations change.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado