How to run Wrongful Death Damages in DocketMath for Montana
7 min read
Published June 4, 2026 • By DocketMath Team
Step-by-step
This guide shows how to run Wrongful Death Damages in DocketMath for Montana (US-MT) using jurisdiction-aware setup. It focuses on the workflow and the key Montana legal hook for wrongful death actions, not on legal advice.
Note: In Montana, a wrongful-death action is maintained by the personal representative of the decedent’s estate when the death is caused by the wrongful act or neglect of another. See Mont. Code Ann. § 27-1-512.
1) Start the correct calculator
- Go to the primary CTA: /tools/wrongful-death-damages
- Select Jurisdiction: Montana (US-MT) if your DocketMath interface prompts you to choose a jurisdiction.
- Confirm the calculator mode matches “Wrongful Death Damages” (not survival damages or a different personal injury module).
2) Enter Montana-relevant case facts (inputs that typically change outputs)
DocketMath’s wrongful-death calculator generally relies on a structured set of inputs. Use the fields provided and align them to what your case record supports.
Use this checklist to drive your data entry:
- Decedent information (e.g., age at death, work history or earning basis if included)
- Economic damages inputs (such as expected earnings and time horizon)
- Non-economic damages inputs (if the calculator includes pain-and-suffering or similar categories)
- Loss-of-support / beneficiaries assumptions (if the calculator separates categories)
- Mitigation / offsets (if the calculator provides fields for adjustments)
- Discounting assumptions (if DocketMath includes a present-value or discount-rate control)
- Reasonable time window for projected losses (if you can choose it)
Even if DocketMath uses a consistent model across jurisdictions, your Montana-specific numbers and assumptions are what will meaningfully change results.
3) Use the Montana wrongful-death legal basis as your “case anchor”
When you’re preparing the record behind your numbers, keep the Montana wrongful-death cause-of-action element in view:
- Montana wrongful death action: “A personal representative of a decedent's estate may maintain an action for wrongful death when the death of the decedent was caused by the wrongful act or neglect of another.”
Mont. Code Ann. § 27-1-512
In practice, this affects your workflow because you’ll usually need:
- proof the claimant is the personal representative (executor/administrator, as applicable), and
- a causation theory tied to the wrongful act or neglect.
DocketMath won’t validate legal standing—so record that support in your case notes alongside your damages inputs.
4) Set expectations for the statute of limitations (SOL) behavior in DocketMath
For Montana, DocketMath should treat the SOL as the default “general” period unless you’re using a module that has a more specific wrongful-death rule.
- General SOL Period: 3 years
- General statute reference: Mont. Code Ann. § 27-1-512
Warning: Your content brief notes that no claim-type-specific sub-rule was found for wrongful death. That means you should treat this as the general/default 3-year SOL and not assume a different or shortened SOL for wrongful death unless another Montana provision explicitly applies to your scenario.
If your DocketMath UI asks for a filing-date or incident-date, enter dates consistently:
- Incident date (date of death or date of wrongful act, depending on the calculator’s prompt)
- Filing / filing-intake date (or projection date)
This helps DocketMath flag SOL risk or compute time-dependent values if the tool uses date-driven logic.
5) Run the calculation and interpret the outputs
After inputs are complete:
- Click Calculate.
- Review outputs in three layers:
- Category totals (economic vs non-economic, if separated)
- Adjusted total (discounting, offsets, caps if the calculator includes them)
- Summary range / final figure (depending on the tool’s format)
A practical sanity-check:
- Does the economic component track the decedent’s age and expected earning horizon?
- Do beneficiary assumptions drive the same direction as your case narrative?
- If you change the time horizon or earnings, does the total increase/decrease in a plausible way?
6) Iterate: update inputs to see how the result changes
DocketMath is most useful when you run controlled scenarios. Try these iterations:
- Increase/decrease projected earnings by a small percentage (e.g., ±10%) and observe whether economic damages move in a predictable way.
- Adjust the projection horizon (e.g., shorter life expectancy assumptions vs longer) to see the sensitivity.
- If the calculator offers non-economic or beneficiary-distribution fields, test whether different beneficiary counts change totals as the model suggests.
This turns the calculator into a defensible scenario analysis tool rather than a one-shot estimate.
7) Document assumptions for later review
Before you move your numbers into a brief, demand package, or settlement worksheet, save or record:
- each assumption you entered (earnings basis, time horizon, discounting, offsets)
- each date used (incident date and filing date inputs, if present)
- the Montana wrongful-death legal anchor: Mont. Code Ann. § 27-1-512
DocketMath outputs should be traceable back to your inputs, so your later review has a clear audit trail.
Common pitfalls
These are frequent issues when running wrongful-death damages calculations in Montana using a general wrongful-death model.
Note: Montana’s wrongful-death action is statutorily tied to a personal representative bringing the claim under Mont. Code Ann. § 27-1-512. If your case team’s role assumptions are wrong, your damages work product may not align with the case posture even if the math is internally consistent.
Pitfalls to avoid
- Using the wrong jurisdiction setting
- If DocketMath defaults to a different state, you may accidentally apply incorrect model assumptions.
- Assuming a special SOL rule exists for wrongful death without checking the tool’s structure
- As your brief notes, the period should be treated as the general/default 3-year SOL when no claim-type-specific rule is found.
- Inconsistent dates
- Mixing “date of death,” “date of incident,” and “date of filing” can break SOL calculations and any date-based weighting.
- Overriding economic inputs without a clear evidentiary basis
- Earnings and horizon assumptions can materially swing totals—document why each figure exists.
- Forgetting discounting / present value controls
- If the tool provides discount-rate settings, failing to apply the intended assumption can distort the final total.
- Misreading category outputs
- Some calculators show “totals” and “adjusted totals.” Confirm whether offsets or discounting are already reflected in the line you rely on.
Try it
Use DocketMath’s wrongful-death damages calculator for Montana with a workflow that supports iteration and review:
- Choose Montana (US-MT).
- Enter your case facts into the calculator fields, focusing on:
- earnings/economic assumptions,
- time horizon assumptions,
- any beneficiary or distribution fields,
- offsets/mitigation,
- and any discounting settings.
- Include date inputs so the tool can apply the general/default 3-year period (as directed by your provided note).
- Run the calculation.
- Perform at least two scenarios:
- one conservative (lower earnings horizon or reduced earnings),
- one more favorable (higher earnings horizon or earnings).
- Record your assumptions alongside the legal anchor:
- Mont. Code Ann. § 27-1-512 (wrongful death action maintained by the personal representative for deaths caused by wrongful act or neglect).
If you want to speed up scenario testing, treat each input category as a “knob”:
- change one knob at a time,
- compare output deltas,
- and keep a short log of the assumptions that produced each outcome.
Related reading
- How to calculate Wrongful Death Damages in Texas — Full how-to guide with jurisdiction-specific rules
- How to calculate Wrongful Death Damages in Philippines — Full how-to guide with jurisdiction-specific rules
- Worked example: Wrongful Death Damages in Philippines — Worked example with real statute citations
