Inputs you need for Damages Allocation in Montana
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Damages allocation in Montana often comes down to providing DocketMath with the right amounts and dates so the damages-allocation workflow (jurisdiction-aware for US-MT) can run consistently.
Before you start, gather these inputs as a checklist. Even small data differences (especially dates) can change time-feasibility indicators and downstream allocations.
Note / disclaimer: This is a practical setup guide for using DocketMath and does not provide legal advice.
Core damages inputs (money amounts)
Examples: medical bills, lost wages, out-of-pocket costs. Examples: pain and suffering, loss of enjoyment of life. Examples: amounts already paid by a relevant payer that you intend to reflect as offsets in your workflow.
Timeline inputs (date-based)
The date the claim “accrued” under your case theory. For many damage calculations this aligns with the injury date, but use your case-specific understanding. The date the action was filed (or the filing date you’re using in the model). Some workflows use multiple time segments; only enter what DocketMath requests.
Parties / allocation structure inputs
Who should receive responsibility allocation in your model. Percentages, roles, or other allocation drivers depending on how your matters are structured inside your DocketMath workflow. Entities or damage categories you want excluded from allocation.
Montana timing note (important for running the tool)
Montana’s general statute of limitations (SOL) framework uses a 3-year default period for many civil claims. This is the general/default period, not a claim-type-specific rule (the content below reflects that default). In DocketMath, these date inputs may be used to flag whether the matter appears time-bounded under the default framework.
- General SOL Period (default): 3 years
Montana Code Annotated § 27-2-102(3)
Source: https://www.nolo.com/legal-encyclopedia/montana-personal-injury-laws-and-statutes-of-limitations.html?utm_source=openai
Where to find each input
Below is a practical map for where to source each input in typical Montana litigation files.
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.
Money amounts
- Medical and treatment documentation
- Itemized billing, provider statements, invoices, EOBs (explanations of benefits), treatment summaries.
- Use these to total your economic damages (medical, care-related costs) and any other categories your workflow defines.
- Employment and payroll records
- Pay stubs, wage statements, employer letters.
- Use these to support economic damages for lost wages/wage-loss calculations.
- Case settlement and payment history
- Payment letters, remittance documentation, insurer correspondence, disbursement statements.
- Use these to identify offsets/credits you plan to include in DocketMath.
- Damages demand or expert summaries
- For non-economic damages totals (e.g., pain and suffering), demands and/or expert narratives often contain your aggregated numbers.
- If you’re using your own modeled totals, confirm the line items roll up cleanly into the “economic” vs “non-economic” buckets you enter.
Date inputs
- Accrual date
- Commonly tied to the injury date, but confirm it matches the factual trigger and legal theory you’re using for your allocation.
- Check pleadings, disclosure timelines, and your case chronology.
- Filing date
- Stamped filing date or docket entry date from your court record.
- Additional event date(s) (if requested by the calculator)
- Use the same chronology you relied on for damages periods (e.g., treatment milestones, key recovery/termination dates), but only enter them when DocketMath asks for them.
Parties / allocation structure inputs
- Your internal allocation spreadsheet or case worksheet
- Often contains responsibility percentages and participant roles already.
- Pleadings / discovery narratives
- Helps justify which parties are included and what you classify as excluded.
- Useful when your DocketMath participants need alignment with your factual record.
Run it
Once your inputs are compiled, open DocketMath and run the damages-allocation calculator for Montana (US-MT) using the primary CTA:
- Primary CTA: /tools/damages-allocation
Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.
Montana jurisdiction rules you should expect in the workflow
For timing feasibility, DocketMath uses the general/default SOL period when no claim-type-specific sub-rule is applied in the input set you’re using.
- General SOL Period (default): 3 years
Montana Code Annotated § 27-2-102(3)
Source: https://www.nolo.com/legal-encyclopedia/montana-personal-injury-laws-and-statutes-of-limitations.html?utm_source=openai
Because this is the default/general period, the workflow description here should be treated as a baseline—not a guarantee that every claim type will be analyzed the same way.
How outputs change when you adjust inputs
Use this quick cause-and-effect guide:
- Move the filing date later/earlier (relative to the accrual date)
- DocketMath may change the time-feasibility / SOL flag under the 3-year default.
- Adjust economic vs. non-economic damages totals
- Allocation outputs may redistribute dollar shares across your defined buckets/participants according to the calculator’s structure.
- Add or remove offsets/credits
- Net available damages can change, which can alter the final allocated amounts.
Practical pitfall to watch
- If your accrual date is off by months, the matter may flip from a “feasible” to “not feasible” time-indicator under a 3-year default framework. Before finalizing, double-check the event you’re using as the accrual trigger.
Minimal run checklist (to reduce reruns)
After running, review outputs for:
- Any SOL/time-feasibility indicators driven by the 3-year default
- The allocated damages broken out by your categories/participants
Gentle note: This is a workflow checklist. It doesn’t replace a legal review of SOL accrual/tolling or claim-specific rules.