How to run Damages Allocation in DocketMath for Minnesota

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Minnesota (US-MN) using jurisdiction-aware rules, with a specific focus on how the calculator applies the state general/default statute of limitations (SOL) timing for damages-related allocation.

1) Open the calculator with the right primary CTA

1. Go to DocketMath’s Damages Allocation tool here:
   /tools/damages-allocation
2. Confirm the calculator page shows the damages-allocation tool (the platform setting/identifier).

2) Set jurisdiction to Minnesota (US-MN)

In the tool’s jurisdiction selector:

• Choose Minnesota / US-MN

DocketMath uses this selection to apply the jurisdiction rules relevant to Minnesota. For Minnesota, DocketMath applies the general/default SOL period of:

• 3 years
• Grounded in Minnesota Statutes § 628.26

Important clarity: No claim-type-specific sub-rule was found for the calculator logic described in this guide. That means the guidance below applies to the default/general 3-year period, not a specialized SOL category.

3) Enter the damages inputs needed for allocation

Depending on the interface, you’ll usually enter inputs such as:

• Total claimed damages (or an equivalent overall amount)
• Damages categories (if the tool supports multiple buckets)
• Amount per category (for example, economic vs. non-economic, or other groupings the calculator prompts)

If the calculator supports allocation categories, keep these rules of thumb in mind:

• Make categories mutually exclusive (avoid double-counting the same dollars in multiple buckets).
• Ensure the sum of categories matches the “total” field (if both are present).
• Enter amounts in the same unit system (e.g., dollars—no mixing “thousands” with full values).

4) Add timing inputs that connect to the SOL window

Damages allocation typically needs a way to compare the damages timing to the SOL window. Look for fields like:

• Accrual date (or when the claim began to run)
• Filing date (or when the case was initiated)
• Sometimes additional date fields, depending on the tool prompts

For Minnesota default SOL calculations in this workflow:

• DocketMath uses 3 years as the general period per Minnesota Statutes § 628.26
• This default applies unless the tool/workflow applies a different, more specific sub-rule (the guidance here assumes none is present)

Practical example of how this changes outcomes:

• If your filing date falls within 3 years of the relevant accrual date, the calculator may treat more of the damages allocation as within the SOL window.
• If the filing is more than 3 years, more of the allocation may be shown as outside the default window.

5) Run the allocation calculation

Click the tool’s action button (commonly Calculate or Run).

After it runs, DocketMath should produce outputs such as:

• An allocated damages breakdown (by category and/or time segment)
• A summary of what portion appears within vs. outside the SOL window under the Minnesota default/general rules
• Any assumptions/notes included by the calculator

6) Review the output in a Minnesota-default context

When you review results, verify these items:

• The tool is using the 3-year window
• The basis shown/implicitly applied is consistent with Minnesota Statutes § 628.26
• The allocation is based on the general/default period, not a specialized claim-type SOL rule (since none was identified for this calculator logic)

A quick way to sanity-check:

• Look at the output labeling and/or any “within vs. outside SOL” indicators.
• If your filing date is close to the 3-year boundary, expect the allocation to be sensitive to your exact dates.

7) Export or capture results for your workflow

If the tool provides a download, copy, or shareable link:

• Use it to keep your inputs and results aligned across revisions

A good practice is to save:

• The exact accrual date you entered
• The exact filing date you entered
• The category amounts you entered (or the total)
• The resulting within vs. outside allocation figures

This makes it easier to compare “what changed” when you rerun the tool with updated dates or different category splits.

Common pitfalls

DocketMath can only allocate based on the inputs you provide and the jurisdiction rules it applies for Minnesota (US-MN). These issues commonly affect results:

• Using the wrong “starting” date

  • If the calculator asks for an accrual/trigger date, ensure it matches your damages-timing theory as you’re modeling it.

• Forgetting you’re using the general/default SOL period

  • In this workflow, the default is 3 years under Minnesota Statutes § 628.26.
  • Also remember: no claim-type-specific sub-rule was found for the calculator logic described here, so the output reflects default/general timing rather than a specialized category.

• Double-counting category amounts

  • If multiple categories are supported, ensure each dollar figure maps to one category only.
  • Double-counting can inflate your allocation regardless of SOL timing.

• Inconsistent units and data formatting

  • Mix-ups like entering dates in different formats (or using “thousands” for one category and full dollars for another) can distort the calculation.

• Over-interpreting “outside SOL”

  • Even when the calculator flags a portion as outside a SOL window, the tool’s output is a computational allocation model under the default rules.
  • Real-world outcomes can still depend on facts and Minnesota-specific legal nuances beyond what a calculator can determine.

Pitfall to watch: A small change to the accrual date or filing date can move you across the 3-year boundary and noticeably shift the “within vs. outside” allocation. Re-check dates before rerunning.

Try it

Use this quick test workflow to confirm your setup in DocketMath for Minnesota:

• Set jurisdiction to **Minnesota (US-MN)
• Enter:

  • Total claimed damages (or category amounts)
  • An accrual date
  • A filing date
• Run Damages Allocation
• Confirm the tool applies 3 years as the general SOL period tied to Minnesota Statutes § 628.26

What to expect when you change inputs

To see how output responds, run two controlled scenarios:

1. Run A: Within-window timing

   • Set the filing date to be 2 years and 11 months after the accrual date
   • Expectation: more damages are likely treated as within the default SOL window

2. Run B: Outside-window timing

   • Set the filing date to be 3 years and 2 months after the accrual date
   • Expectation: more damages are likely treated as outside the default SOL window

If the calculator behavior doesn’t match this pattern:

• Verify you selected US-MN (not another jurisdiction)
• Verify your dates are entered in the expected fields
• Check whether the tool includes any override or additional timing settings beyond the default/general period

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