How to run Wrongful Death Damages in DocketMath for New Mexico

Step-by-step

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

This guide walks you through running Wrongful Death Damages in DocketMath for New Mexico (US-NM) using jurisdiction-aware rules. We’ll also pin down the New Mexico statute of limitations used in the workflow so you can see how the timeline affects the output.

1) Open the New Mexico Wrongful Death Damages calculator

Go to the primary CTA:

• /tools/wrongful-death-damages

When the calculator loads, confirm your jurisdiction is set to US-NM (New Mexico). If your workspace supports overrides, avoid switching jurisdictions mid-run, because limitation periods and downstream assumptions are jurisdiction-specific.

2) Enter the core case facts the calculator needs

DocketMath’s wrongful-death-damages calculator typically requires inputs that describe (a) the death date and (b) the people or categories of damages that can be claimed.

Use the exact dates relevant to your case:

• Date of death (required for timing calculations)
• Any damage category selections that match what you’re modeling (for example, economic-loss-style inputs and/or other damage components exposed by the tool)

If you’re unsure which people qualify for inclusion in a model, you can still run the calculator for scenario planning—just be consistent about what you include and track it as a modeling assumption.

3) Add the timeline inputs and verify the limitation period rule

For New Mexico, DocketMath applies the general/default statute of limitations for wrongful death claims.

• General SOL period: 2 years
• General statute citation: N.M. Stat. Ann. § 31-1-8

There is no claim-type-specific sub-rule found for this workflow, so the calculator uses the default “general” 2-year limitations period rather than a specialized wrongful-death period.

What to check in the UI:

• The calculator should reference a limitation window derived from N.M. Stat. Ann. § 31-1-8.
• The output may flag whether the proposed claim timing falls within the limitation period.

4) Understand how the limitation rule changes the outputs

Once you enter Date of death, DocketMath can compute a deadline using the 2-year SOL tied to N.M. Stat. Ann. § 31-1-8.

Then it uses that timing to adjust how results are displayed. Common patterns you may see in the results panel:

• A “timely vs. potentially time-barred” indicator
• A dismissal-risk note (depending on the calculator’s UI design)
• A change in whether the tool emphasizes damages totals or also highlights limitation constraints

Even if you’re only doing damages modeling, the SOL check often affects presentation and interpretation. Treat that as a screening layer rather than a definitive legal conclusion.

5) Review the damages inputs and interpret result sensitivity

Next, focus on the numeric inputs that feed the damages math. In many wrongful death models, output totals are highly sensitive to:

• Income-related assumptions (if your calculator includes them)
• Duration/years-of-loss parameters
• Any multipliers or category weights exposed by the tool
• Whether you include multiple damage components

To make your results actionable:

• Run at least two scenarios (for example, baseline vs. conservative income assumptions).
• Watch which line items move the most.
• Record the dates you used, since even a small date change can flip the SOL timing indicator.

6) Save/export your run for comparison

After you confirm the jurisdiction rule and limitation window are correct:

• Save the run (if your workflow supports it).
• Export or copy the results so you can compare multiple scenarios.

When you compare runs, keep the Date of death identical unless the purpose is to test timing sensitivity.

7) Confirm you’re using the New Mexico default SOL logic

Before you finalize interpretation, do a quick “sanity check” against the jurisdiction notes:

• New Mexico SOL period used in this workflow: 2 years
• Authority: N.M. Stat. Ann. § 31-1-8
• No claim-type-specific sub-rule found for this calculator flow
• Therefore: default/general period governs the SOL logic

If the calculator shows a different period, stop and re-check the jurisdiction selection and the calculator’s “rules” or “assumptions” panel.

Common pitfalls

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

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Capture the source for each input so another team member can verify the same result quickly.

1) Accidentally using a non-New Mexico jurisdiction

If your workspace defaults to another state, you might see different SOL periods and different timeline logic.

Quick check: Look at any jurisdiction label (US-NM) and any statute citation shown in the calculator.

2) Confusing “date of death” with “date of filing”

The SOL computation for the limitation screen is typically tied to the date of death (start anchor) and then applied to the time window.

If you enter a different date in the wrong field, the tool can:

• produce an incorrect SOL deadline, and
• label the scenario as timely or not in error.

3) Assuming a claim-type-specific SOL rule exists in this workflow

For this DocketMath setup, the guidance is explicit: no claim-type-specific sub-rule was found, so the calculator uses the general/default 2-year SOL under N.M. Stat. Ann. § 31-1-8.

4) Changing too many variables at once

Damages modeling can be sensitive. If you change:

• dates,
• economic assumptions, and
• damage categories

in a single run, you’ll struggle to determine what drove differences between outputs.

Use controlled changes:

• one scenario change at a time (dates only, or income only).

5) Treating the SOL indicator as a final legal determination

Even with correct inputs, the limitation screen in a tool is best viewed as:

• a screening flag, and
• an input-integrity check.

In real litigation, additional factual and procedural elements can matter. The calculator is focused on modeling and timeline logic tied to N.M. Stat. Ann. § 31-1-8, not on full case adjudication.

Try it

Use DocketMath’s wrongful-death-damages tool for New Mexico and run a small test set.

Checklist before you click Calculate:

Suggested mini-workflow for sensitivity testing (2 runs):

1. Run A (baseline):

   • Use your best estimate for income/economic inputs
   • Keep category selections consistent

2. Run B (conservative):

   • Reduce the economic assumption(s)
   • Keep Date of death unchanged (so the SOL screen doesn’t flip)

If results show a big swing between A and B, that’s a useful signal about what drives the outcome in the tool. If results show no change, double-check that your inputs are actually connected to the selected damage components.

Want to compare behavior across tools? You can also review related DocketMath guidance:

• Primary calculator: /tools/wrongful-death-damages
• General walkthroughs: /blog

Related reading

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