How to run Wrongful Death Damages in DocketMath for Montana

Step-by-step

Run this scenario in DocketMath using the Wrongful Death Damages calculator.

This guide shows how to run Wrongful Death Damages in DocketMath for Montana (US-MT) using jurisdiction-aware rules—so the calculator applies the correct Montana defaults. This is a workflow walkthrough, not legal advice.

1) Open the Montana wrongful-death calculator

1. Go to the primary calculator page: /tools/wrongful-death-damages
2. Confirm the jurisdiction is set to Montana (US-MT) in the tool (or select it if the UI prompts you).

2) Understand what DocketMath will calculate

Wrongful death calculations typically depend on:

• Who can recover (beneficiary categories)
• Economic losses (like income and support-related amounts)
• Non-economic losses (like certain forms of damages, depending on the model and inputs)
• Timing assumptions used to project losses

In DocketMath, you’ll enter numbers (and sometimes assumptions) that feed the model. Your job is to provide consistent, well-documented inputs so the output reflects your scenario.

3) Enter economic-loss inputs (income, support, and duration)

In the economic section, focus on the inputs that drive projected losses. Common fields you may see include:

• Decedent’s annual income (gross or net—use the tool’s label)
• Work-life or loss duration (or implied by age and timeline inputs)
• Contribution or support percentage (how much of income supported beneficiaries)
• Future earnings growth / discounting assumptions (if the tool provides them)

Input-to-output effect:

• Higher annual income generally increases economic damages.
• Longer duration increases total projected losses, often more than linearly depending on growth/discount assumptions.
• A lower support/contribution percentage can reduce damages substantially even if income is high.

4) Enter non-economic-loss inputs (if enabled in the tool)

Some wrongful death models include a non-economic component (for example, loss of companionship or emotional harms) using either:

• A fixed slider/amount, or
• A structured set of fields tied to severity or relationship factors

If DocketMath offers non-economic inputs, choose values that match the tool’s guidance and keep them consistent with how you describe the case facts in your file.

5) Add timeline and “when it happened” context for Montana

While wrongful death damages can often be computed without a limitation period, many workflows include dates for completeness—especially for case timelines and demand pacing.

For Montana, the general statute of limitations (SOL) for a personal injury action (often used as the default when no wrongful death–specific sub-rule is provided) is:

• 3 years, under Montana Code Annotated § 27-2-102(3) (general/default period)

This is the period you should apply when you’re following the default rule in the absence of a claim-type-specific sub-rule found for your workflow.

Important: Your content brief states no claim-type-specific sub-rule was found. So this guide uses the general/default 3-year period clearly and directly.

6) Make sure the tool’s outputs align with Montana’s default SOL approach

Run the calculator using your entered damages inputs first, then:

• Review the output panels (often include totals and breakdowns)
• Confirm whether the tool displays any SOL/timing assumptions
• If it displays a limitation period, ensure it matches 3 years for Montana default under **§ 27-2-102(3)

Output-to-assumption effect:

• If the tool uses dates to adjust the analysis window (for example, limiting the “recoverable” period), changing the incident date can change damages projections or time-based caps.
• If it doesn’t adjust damages by SOL and instead only provides a timeline flag, the financial output may stay the same, but your case timeline changes.

7) Review, export, and document your assumptions

Before you move from calculation to reporting:

• Capture a screenshot or export the results
• Document every input you changed and why (e.g., “income updated to 2022 tax return because X”)
• Keep a short assumptions note:

  • What income figure you used
  • What duration/growth/discount assumptions you selected
  • Whether non-economic damages were entered manually or via default settings

For most case workflows, the audit trail matters as much as the final number.

8) Use the calculator as a scenario runner (not a single “answer”)

Try multiple reasonable input sets:

• A conservative scenario (lower income growth, shorter duration, lower support)
• A baseline scenario (midpoint assumptions)
• An aggressive scenario (higher growth, longer duration, higher support)

This is where DocketMath is most useful: you can see sensitivity—what drives the total.

Checklist for scenario runs:

9) Tie outputs to Montana timing for next steps

For Montana, the default 3-year SOL anchor is:

• 3 years: **Montana Code Annotated § 27-2-102(3)

If you’re preparing a litigation or settlement timeline, use the statute date logic consistently:

• Choose the correct “trigger” date per your case record (the tool may label this)
• Apply a 3-year window under § 27-2-102(3) as your default limitation framework

Common pitfalls

Below are mistakes that commonly distort wrongful death damages runs—especially when pairing numbers with jurisdiction rules.

1. **Using the wrong SOL logic (or assuming it’s automatic)

   • If DocketMath only shows totals, you might forget the case timeline still depends on § 27-2-102(3)’s 3-year default.
   • Conversely, if the tool adjusts by timing, ensure the incident date matches your workflow’s “trigger” field.

2. **Mixing income types (gross vs. net)

   • If the tool expects annual net income but you enter gross (or vice versa), results can swing dramatically.
   • Fix: align with the tool label exactly, and use the same definition across scenarios.

3. Inconsistent duration math

   • Example: entering a “years until retirement” figure while also entering a “loss duration” field can double-count time depending on the tool’s structure.
   • Fix: populate only the fields the tool expects as mutually exclusive inputs.

4. Support percentage applied twice

   • Some workflows apply “support” as a multiplier; others bake it into income assumptions.
   • Fix: if the tool has both “income contribution” and “support percentage,” only use one method.

5. Non-economic damages entered without a coherent basis

   • If non-economic fields exist, keep them stable across sensitivity runs unless your hypothesis changes.
   • Fix: run economic-only comparisons first to isolate the drivers.

6. Forgetting the SOL guidance here is a default

   • Your brief states no claim-type-specific sub-rule was found. That means Montana’s 3-year general/default SOL is used.
   • Fix: treat this as the jurisdiction anchor for the workflow you’re running—not necessarily the only possible limitation approach for every factual posture.

Try it

Use DocketMath as a quick scenario tester for Montana wrongful-death damages.

1. Open /tools/wrongful-death-damages
2. Set jurisdiction to Montana (US-MT).
3. Run a baseline scenario:

   • Enter annual income
   • Enter duration (or the fields that imply duration)
   • Choose support/contribution
   • Enter non-economic inputs only if they’re part of your model run
4. Run two sensitivity tweaks:

   • Lower support (e.g., reduce support percentage by a small step)
   • Shorter duration (reduce duration by 1–2 years, if the tool allows)
5. Confirm the tool’s timing/timeline area aligns with Montana’s default SOL anchor:

   • **3 years under Montana Code Annotated § 27-2-102(3)

Quick verification checklist after each run:

Related reading

• Wrongful Death Damages Estimator Guide for Alabama
• Wrongful Death Damages Estimator Guide for Arizona
• Wrongful Death Damages Estimator Guide for Colorado