How to run Wrongful Death Damages in DocketMath for Indiana

Step-by-step

This guide shows how to run Wrongful Death Damages in DocketMath for Indiana (US-IN) using jurisdiction-aware rules and the calculator wrongful-death-damages. It’s written to help you model damages consistently—not to provide legal advice.

1) Open the correct tool

• Use this direct link: /tools/wrongful-death-damages
• Confirm the jurisdiction is set to Indiana (US-IN) in the tool’s jurisdiction selector (if your workflow includes one).

2) Identify the action type the calculator is modeling

DocketMath’s wrongful-death-damages calculator is aligned to Indiana’s wrongful death cause of action.

Indiana’s wrongful death framework generally provides that when a death is caused by the wrongful act or omission of another, the personal representative may bring the action, and the statute describes what damages may be included. See Ind. Code § 34-23-1-1 (including language authorizing damages such as reasonable medical, hospital, funeral expenses, among other categories described in the remainder of the statute).

In practice, your DocketMath run should reflect:

• Wrongful death damages, and
• The kinds of damages Indiana allows within that statute’s structure.

3) Enter the “statute-backed” damage categories the calculator requests

Ind. Code § 34-23-1-1 contemplates damages that may include reasonable medical and hospital expenses and reasonable funeral expenses, among other categories described in the remainder of the statute. Depending on how DocketMath labels the inputs, the tool may ask for separate fields that correspond to those categories.

How to enter values correctly

• Enter amounts paid or reasonably incurred, backed by supporting documents where possible (e.g., invoices, billing statements, itemized estimates).
• Use the exact units the tool expects (typically dollars).
• If the tool has category-specific fields (for example, medical vs. funeral), enter each amount in its matching field rather than combining them first.

Practical input guidance

• If you have medical bills, use the total that corresponds to the “medical/hospital” field (not an all-in demand that also includes funeral, non-medical losses, etc.).
• If you have funeral invoices, enter the reasonable funeral amount in the matching field.

4) Add “expense vs. other” components separately if the tool distinguishes them

It’s common for wrongful death damage models to split:

• Expense-style damages (like medical/hospital and funeral), versus
• Other statute-aligned categories (whatever additional lines the tool supports).

DocketMath may structure inputs so that some figures are treated as expense damages and others as non-expense damages. Use each field exactly as labeled—this is a common place where runs go wrong.

5) Review assumptions and jurisdiction mapping in the tool output

After entering your inputs:

1. Run the calculator.
2. Check the output breakdown.
3. Confirm the jurisdiction tag remains US-IN.

You should see a total wrongful death damages figure plus a breakdown aligned to the categories the tool implements for Indiana.

6) Make a second run to test sensitivity

To improve confidence in your model:

• Create a variant run adjusting one major input at a time (for example, changing funeral cost or medical/hospital expenses).
• Compare the totals from the two runs.

This kind of sensitivity check helps you understand which input drives most of the calculated total—and whether your biggest numbers look reasonable.

7) Capture the statute linkage for your workflow

For documentation purposes, keep a note that the action premise is rooted in Ind. Code § 34-23-1-1—and that the statute includes reasonable medical/hospital and reasonable funeral expenses as part of the wrongful death damages framework (along with additional categories described elsewhere in the statute).

This won’t change the DocketMath math by itself, but it makes it easier to explain where your input categories came from later.

8) Confirm your timing logic (default rule vs. claim-type-specific rule)

A key implementation note for this jurisdiction/model is:

• No claim-type-specific sub-rule was found.
• That means you should treat the period as the general/default period in DocketMath’s jurisdiction-aware rules where timing affects the run.

Concretely:

• Use the tool’s default period logic tied to Indiana’s general wrongful death framework (configured in DocketMath for US-IN).
• Avoid searching for (or overriding) a special sub-rule for a particular “sub-type” unless DocketMath explicitly provides one.

Common pitfalls

Below are the most frequent mistakes people make when running the Indiana wrongful death damages calculator in DocketMath.

• Mixing pre-death and wrongful death categories

  • If the tool distinguishes expenses from other categories, keep numbers in the matching fields.
  • Don’t assume every “loss” number belongs in a wrongful death category just because it relates to the deceased.

• Double counting the same amount

  • Example: entering funeral costs both as “funeral” and again inside a broader “total expenses” field (if the tool provides both kinds of inputs).

• Using an estimate without tying it to the input category

  • Medical/hospital categories and funeral categories typically need amounts you can justify with records or itemization.
  • If you only have a rough estimate, consider using the best available supporting documents rather than mixing categories.

• Forgetting the jurisdiction setting

  • Accidentally leaving the jurisdiction at another state will change rules and output assumptions.

• Assuming a missing sub-rule exists

  • Because no claim-type-specific sub-rule was found, don’t override the tool’s default period logic for Indiana unless DocketMath explicitly provides a different rule.

• Not running a second scenario

  • Without a variant run, it’s easy to miss that one input (often medical bills or expense categories) dominates the final total.

Try it

Here’s a quick way to validate your Indiana run in DocketMath. Think of it as a minimal checklist to confirm you’re entering data in the right places and that the output looks internally consistent.

Quick checklist

• Jurisdiction set to Indiana (US-IN)
• Opened calculator: wrongful-death-damages
• Entered reasonable medical/hospital expenses consistent with the damages concept in Ind. Code § 34-23-1-1
• Entered reasonable funeral expenses consistent with the damages concept in Ind. Code § 34-23-1-1
• Entered any additional statute-aligned categories required by the tool fields
• Ran the calculator once and reviewed the total + breakdown
• Ran a second scenario changing only one major number to check sensitivity
• Verified timing period uses the general/default period (no claim-type-specific sub-rule found)

What to look for in the output

Use the breakdown to quickly sanity-check:

• Did the tool compute a sum from the categories you entered (not a vague or placeholder estimate)?
• Do the largest line items match what you’d expect from your records (often expense categories first)?
• Does the output explicitly reflect Indiana (US-IN) rules in the jurisdiction indicators?

If results feel unexpectedly high or low, rerun with cleaner inputs—for example, re-enter medical totals from itemized statements—and compare whether changes are proportional to your edits.

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