How to run Wrongful Death Damages in DocketMath for North Carolina

Step-by-step

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

Below is a practical walkthrough for running Wrongful Death Damages in DocketMath for North Carolina (US-NC). This focuses on how to set up the calculator and interpret results using jurisdiction-aware rules for NC.

1) Start the calculator

1. Open DocketMath and go to the tool:

   • /tools/wrongful-death-damages
2. Confirm the jurisdiction is set to North Carolina (US-NC).

If you don’t see a jurisdiction selector, look in the tool’s settings, profile, or “jurisdiction-aware” options. The goal is to ensure the calculator’s NC mode is active before you enter dates and loss figures.

2) Understand what DocketMath will calculate

In most damage calculators (including wrongful-death-focused workflows), the results usually come from:

• Time-based components (often tied to past losses and/or future projections)
• Economic loss assumptions (like wages/income, work-life expectations, and any multipliers used by the model)
• Optional non-economic components (some calculators include them; others focus on economic totals only)

When DocketMath shows separate lines (for example, “economic” versus “total”), treat “total” as the aggregate number the tool is modeling, not a guarantee of how a court would value damages. Your inputs determine what the model estimates.

3) Enter the date information (critical for timing)

DocketMath may request one or more of these fields (labels vary by tool version):

• Date of injury
• Date of death
• Date of filing (or another trigger tied to timing logic)

Use the dates that match your case documentation.

For North Carolina, the default general SOL period shown in your jurisdiction configuration is:

• General SOL period: 3 years

Your jurisdiction data also references the SAFE Child Act. However, the brief you provided also states that no claim-type-specific sub-rule was found. That means the calculator should use the 3-year default general period as the fallback when a more specific wrongful-death timing rule is not identified.

Jurisdiction clarity you should keep in mind for NC:

• Because no claim-type-specific sub-rule was found, the 3-year default general period is the fallback.
• The SAFE Child Act reference is present, but applicability depends on the underlying facts—so don’t assume it automatically applies to every wrongful-death scenario.

4) Input economic and loss assumptions

Next, enter the economic figures the tool asks for. Common fields include:

• Gross earnings / income (annual or monthly—use the unit specified by the input label)
• Employment details (if the calculator requests them)
• Expected work-life / projection horizon (if editable or required)
• Medical or other direct costs (if the model includes them)

Practical tip: keep units consistent. For example:

• If DocketMath asks for annual income, don’t enter a monthly number without converting.
• If it asks for pre-tax vs post-tax, follow the label exactly.

5) Set any adjustments the calculator offers

Some DocketMath calculators include toggles or modifiers that can materially change the estimated damages, such as:

• Age-based adjustments
• Dependency-related factors
• Present value / discounting settings
• Cap/multiplier settings (if part of the model)

If DocketMath offers jurisdiction-aware controls, keep US-NC active so outputs align with the NC configuration and default timing fallback described above.

6) Review the output breakdowns before relying on totals

Before using a single “headline” number, review the tool’s component breakdown. A good workflow is to confirm:

• Past economic loss (if shown)
• Future economic loss (if shown)
• Any category totals
• Any “adjusted” figures (if the tool applies limitations or model constraints)

If the tool allows expanding sections, do it. Breakdowns help you identify which inputs most strongly affect the estimate.

7) Use a “what-if” loop to test sensitivity

After your first run, change one variable at a time and observe how results move. This helps you avoid trusting a single output that might be driven by one sensitive input.

Typical sensitivity checks include:

• Changing income by a known percentage (e.g., ±10%)
• Changing the projection horizon (if editable)
• Shifting whichever date field controls the limitation-period logic (if your tool indicates it)

A quick sensitivity run helps you confirm the model behaves logically and that your inputs match what you intended to estimate.

Common pitfalls

Wrongful death damages estimates can swing significantly with small input changes. Watch for these common issues when running the US-NC wrongful death damages workflow in DocketMath.

• Forgetting the default SOL fallback when no claim-type-specific rule is found
  Your jurisdiction data indicates: General SOL period: 3 years and no claim-type-specific sub-rule was found.
  So the 3-year default general period is the fallback.

• Mixing up dates used for timing logic
  Using the wrong date as the “trigger” (injury vs death vs filing, depending on what the tool asks) can change time-based modeling and any SOL-related logic.

• Entering income in the wrong unit
  If the tool requests annual income and you enter a monthly number, you can inflate or deflate results by roughly a factor of 12. Always follow the input label.

• Assuming the SAFE Child Act automatically applies to every scenario
  Even though the jurisdiction data includes a SAFE Child Act reference, applicability depends on the underlying facts. Use DocketMath to estimate; don’t assume legal applicability without matching facts.

• Relying on totals without checking line items
  Totals can hide which assumptions caused the output. If results look unexpectedly high or low, inspect the component breakdown and identify which input drove the change.

Pitfall to remember: even if US-NC is correctly selected, leaving a date blank or entering an incorrectly formatted date can still produce an output. Treat the output as only as reliable as the inputs—always verify date fields and the jurisdiction mode before exporting or saving results.

Try it

Follow this checklist to run a clean first estimate in DocketMath using the Wrongful Death Damages tool for North Carolina:

When you compare runs, you’re looking for consistency. For example:

• If a 10% income change produces a roughly proportional change in the output, that suggests your inputs are being interpreted as expected.
• If a tiny change causes a huge swing, revisit the most sensitive fields—often dates, projection horizon, or multiplier/adjustment settings.

If DocketMath offers an export/save workflow, use it to capture your assumptions (inputs, dates, and any toggles). That makes it easier to compare scenarios and re-check your work later.

Related reading

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