Inputs you need for Damages Allocation in Minnesota
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Damages Allocation calculator.
To allocate damages in a Minnesota case using DocketMath (jurisdiction: US-MN), you’ll want to gather a compact set of case facts and financial details. DocketMath’s damages-allocation calculator uses those inputs to help you model how damages totals may be allocated across categories and time.
Below is an input-checklist you can follow before you run the calculator.
Core damages inputs (financial amounts)
Allocation and adjustment inputs (how you want totals split)
- how medicals were calculated,
- how wage loss was derived (hours, rate, time period),
- how the end date was selected.
Minnesota timing input (for limitation logic in the model)
Even when you’re not claiming a specific type of case, Minnesota uses a general/default statute of limitations period. For this calculator workflow, the general SOL is:
- General Statute of Limitations (default): 3 years under Minnesota Statutes § 628.26 (general/default period noted for this workflow)
You should treat this as the baseline when no claim-type-specific sub-rule is identified.
Note: No claim-type-specific sub-rule was found for this workflow. That means the 3-year default (Minn. Stat. § 628.26) is what the jurisdiction-aware model applies when you don’t have a more specific limitation rule.
(Gentle disclaimer: this is a practical modeling workflow description, not legal advice. If your matter involves specialized limitation rules, consult a qualified attorney.)
Where to find each input
Use the following “source map” so you’re not hunting blindly. You’re aiming for repeatable documentation, especially when you later need to defend assumptions.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
Dates
- Claim start date / end date
- Look in: incident reports, contract dates, employment records, medical records, correspondence, and pleadings.
- Practical tip: ensure your “start” corresponds to when damages actually began accruing (not just when a dispute started).
Monetary amounts
- Past damages amount / future damages amount
- Look in: itemized bills (medical, repairs), payroll history, pay stubs, expert reports, spreadsheets used for settlement demand, and any prior computations.
- If you only have a single lump sum, break it down into categories so DocketMath can allocate more meaningfully.
Offsets / credits
- Insurance payments, reimbursements, recoveries
- Look in: EOBs (explanations of benefits), insurance payment summaries, release documents, and settlement statements.
- Keep documentation that shows the amount and basis of each credit.
Minnesota limitations baseline
- General 3-year default
- The model’s timing logic points to the default general SOL period tied to Minn. Stat. § 628.26.
- Your primary reference for the general period in this workflow is the Minnesota statute and the jurisdiction summary used to configure the calculator.
Run it
Once you’ve collected the checklist items, you can run DocketMath → damages-allocation (jurisdiction-aware: US-MN).
Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
Quick run sequence
- Open the calculator: /tools/damages-allocation
- Enter:
- claim start date
- claim end date
- past damages amount
- future damages amount (if applicable)
- any allocation categories you want modeled
- offsets/credits
- Confirm that the calculator is using the general/default SOL baseline:
- 3 years under Minn. Stat. § 628.26 for this workflow
- Review the allocation output and any assumptions summary the tool provides.
How the outputs typically change when inputs change
Use these “cause-and-effect” checks so you can sanity-check results quickly:
Moving the claim start date forward
→ often reduces the modeled time window for recoverable damages (if the model trims amounts outside the limitation period).Changing the claim end date
→ can expand or narrow the accrual window for past damages, and may affect the boundary between past vs. future allocations.Increasing future damages
→ should increase the future allocation bucket; watch whether offsets/credits reduce totals in either bucket.Adding offsets/credits
→ usually reduces net damages totals; verify whether DocketMath applies credits before or after category allocation in the calculator settings.
Warning: If you enter a single lump-sum damages figure without dates or category detail, the model can still produce totals—but the allocation breakdown may be less defensible. For litigation-quality modeling, provide itemized components and dates that match your documents.