How to run Wrongful Death Damages in DocketMath for Mississippi

How to run Wrongful Death Damages in DocketMath for Mississippi

6 min read

Published May 6, 2026 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Step-by-step

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

This walkthrough shows how to run Wrongful Death Damages in DocketMath for Mississippi (US-MS) using jurisdiction-aware rules. It also explains how Mississippi’s general statute of limitations works for these claims in this calculator setup.

Note: This guide explains how to use DocketMath and interpret its outputs. It’s not legal advice.

1) Open the calculator

  1. Go to /tools/wrongful-death-damages
  2. Select Mississippi (US-MS) as the jurisdiction (if the interface doesn’t auto-detect it).

2) Understand the Mississippi limitations rule being applied

For Mississippi, DocketMath uses the general/default statute of limitations:

  • General SOL Period: 3 years
  • General Statute: Miss. Code Ann. § 15-1-49

Important: In this jurisdiction/case configuration, no claim-type-specific wrongful-death sub-rule was found. So the calculator applies the general 3-year period rather than a separate wrongful-death-specific carve-out.

3) Enter the dates that control the SOL analysis

In the calculator, you’ll typically provide dates that let DocketMath measure timeliness. Use dates that match your case record (for example: accident/incident date, date of death, and/or filing-related dates—whichever your DocketMath workflow requests).

Use these principles to choose the right dates:

  • Triggering event date (often date of death or incident-related date): The starting point for the limitation analysis.
  • Filing date / “as of” date: The date you want DocketMath to compare against the 3-year window.

How outputs change

  • If your filing/as-of date is within 3 years of the triggering event, DocketMath will treat the claim as potentially timely under the general SOL rule.
  • If it exceeds 3 years, the calculator’s SOL/timeliness section will flag out of time.

Because the limitation period comes from Miss. Code Ann. § 15-1-49 (3 years), the “within vs. beyond” boundary changes immediately if you adjust either the trigger date or the filing/as-of date.

4) Populate the damages inputs

Next, enter the damages components that the wrongful-death-damages calculator supports. Depending on the tool version, this often includes inputs such as:

  • Economic damages inputs (examples: lost wages / earning capacity)
  • Non-economic and/or other damages inputs (depending on what the UI exposes)
  • Any adjustment factors the calculator offers (for example, discounting/iteration features, if available)

Practical guidance for accurate results

  • Use consistent time units (e.g., annual vs. monthly) across all income-related fields.
  • Match the calculator’s expected format: if the UI expects an annual figure, don’t input a monthly number.
  • If you have multiple periods (before/after an event), only split them if the UI includes separate fields. Otherwise, roll the amounts into the appropriate single input the calculator provides.

5) Run the calculation and review the breakdown

After entering dates and damages:

  1. Click Calculate
  2. Review the output sections, which typically include:
    • Damages totals (by category, if the tool separates them)
    • A statute of limitations / timeliness indicator
    • Any intermediate calculations or line-item breakdown used to build totals

What to look for in the SOL/timeliness panel

Since DocketMath is using:

  • 3 years under Miss. Code Ann. § 15-1-49

your core sanity check is that the SOL panel reflects the trigger date and the as-of/filing date exactly as you intended. If the tool marks something “timely” or “out of time” in an unexpected way, the most common cause is that the relevant date fields were entered differently than you meant.

6) Iterate: update inputs to see how results move

A practical workflow is to test “what changes the answer” without changing everything at once:

  • Change only the dates (keep damages values constant) to confirm the SOL boundary behavior around the 3-year mark.
  • Change only damages assumptions (keep dates constant) to see which categories most affect the totals.

This approach helps you understand which inputs drive changes and supports cleaner internal review—without guessing.

Common pitfalls

The most common issues when running wrongful-death damages in DocketMath for Mississippi are typically about inputs and date selection, not the math.

  • missing a required input
  • using a stale rate or rule
  • ignoring calendar or holiday adjustments
  • skipping documentation of assumptions

1) Using the wrong limitation date basis

DocketMath’s timeliness analysis depends on the dates you enter. If the triggering date or the filing/as-of date is entered incorrectly, the calculator can still correctly compute a 3-year window under Miss. Code Ann. § 15-1-49—but the outcome may not match your intent.

Warning: The calculator won’t “correct” misunderstood date fields. If results seem off, verify the date inputs first.

2) Expecting a special wrongful-death SOL rule when none is configured

Because no claim-type-specific sub-rule was found in this jurisdiction setup, the calculator applies the general/default 3-year SOL period:

  • Miss. Code Ann. § 15-1-49

If your strategy depends on a different limitation framework than the one represented here, you may need to adjust your workflow assumptions accordingly.

3) Mixing time units in damages inputs

Examples of input mismatches:

  • Entering monthly earnings into a field that expects annual earnings
  • Entering hours-based figures into an annualized framework

These errors can produce totals that are internally consistent but inaccurate in real-world terms.

4) Modifying multiple assumptions at once

If you change dates and damages in the same run, it can be hard to tell what caused a change. A clearer method:

  • Adjust dates only → observe SOL indicator
  • Adjust damages only → observe damages totals

5) Overlooking the timeliness flag when reviewing results

Even if damages totals look reasonable, the SOL/timeliness section provides important context. In practice, teams often review both panels together before treating the outputs as usable.

Try it

Use this quick practice checklist to validate your own inputs in DocketMath:

Then do one targeted sensitivity test:

Open the Wrongful Death Damages calculator and follow the steps above: Run the calculator.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Related reading