How to run Wrongful Death Damages in DocketMath for Pennsylvania

Step-by-step

This guide shows how to run Wrongful Death Damages in DocketMath for Pennsylvania (US-PA) using the Wrongful Death Damages calculator. You’ll enter the date-driven and damages inputs, and the tool will calculate a wrongful-death damages figure using jurisdiction-aware logic for Pennsylvania.

Start by opening the calculator:

• Primary CTA: /tools/wrongful-death-damages

1) Confirm you’re using the correct theory: Pennsylvania wrongful death

Pennsylvania wrongful death is authorized by statute. Under 42 Pa.C.S. § 8301(a), an action may be brought to recover damages for a death caused by another’s wrongful act or neglect, unlawful violence, or negligence, when no action for damages was brought by the injured individual during life.

In practice, make sure you are using the wrongful-death calculator for wrongful-death-type damages, not a different theory (for example, a survival-focused damages workflow). If the tool/workflow you’re using doesn’t match your claim theory, you may get numbers that look precise but don’t match what you’re modeling.

2) Set the date-driven inputs the calculator needs

Wrongful death damages calculations typically depend on key dates (and sometimes a modeled “window” between them). In DocketMath, open the Pennsylvania wrongful death damages section and enter the dates the tool asks for.

Use this checklist while you type:

• Date of injury / causation event (if prompted)
• Date of death
• Start/end dates for the damages period (if the tool asks for a period rather than only raw dates)

When there are both “event dates” and “calculation period dates,” be careful to enter each into the field the tool labels. The goal is to ensure the calculator computes the damages time period you intend to model.

3) Add economic damages inputs (what money numbers go in)

Wrongful death models commonly include economic components such as loss of earnings and related financial impacts. In DocketMath, you may see fields like:

• Annual earnings / income
• Fringe benefits / employer contributions (if included in the calculator)
• Work-life assumptions (such as retirement/end-of-earning period, if requested)
• Discounting or adjustment factors (only if the tool provides them)

As you enter numbers:

• Keep units consistent (e.g., annual vs monthly).
• Use the same currency throughout.
• If the tool distinguishes before-tax vs after-tax modeling, choose the option that matches your approach and stay consistent across all related inputs.

4) Add noneconomic or other damages inputs (only if the workflow includes them)

Some workflows may also include categories such as:

• funeral expenses
• other non-economic items or category-based harms (depending on the tool design)

If DocketMath includes dedicated fields/toggles for these categories, enter amounts directly. If it does not, don’t force additional amounts into the wrong field—use your broader case workflow to handle those items outside this calculator if needed.

5) Choose any jurisdiction or scope toggles

Many calculators include options that affect which categories are included or how adjustments are applied.

For Pennsylvania (US-PA), use the US-PA jurisdiction code workflow that’s already selected when you open the Pennsylvania calculator. If you see checkboxes/toggles (for example, include/exclude certain categories), use them to match your modeling scope.

6) Run the calculation and interpret the output

Click Calculate (or the equivalent button). Then review:

• Total wrongful death damages (the headline number)
• Category breakdown (if displayed)
• Time-window effects (whether changing the modeled end date changes the earnings-loss component)
• Any assumption sensitivity the tool provides

A practical sanity-check method:

• Change one assumption or date (for example, adjust the modeled end date by a meaningful increment like 12 months).
• Confirm the total changes in the direction you expect.
• If the output doesn’t move, verify you edited a field the calculator actually uses (some tools request both event dates and period dates).

7) Save/export your scenario (if available)

If your DocketMath workflow supports saving or exporting:

• save your Pennsylvania run,
• then compare scenarios (for example, different earnings assumptions),
• and keep a clear “baseline” version as you update inputs after discovery.

Common data-entry issue: entering monthly income into a field labeled annual income can inflate or deflate the result by roughly a factor of 12. DocketMath will compute faithfully—wrong units are the most frequent cause of misleading outputs.

Common pitfalls

These issues most often cause wrongful death outputs to be misleading in Pennsylvania runs of DocketMath.

1. Using the wrong claim category

   • Wrongful death under 42 Pa.C.S. § 8301 is distinct from other damages theories.
   • If you use a wrongful death calculator but your scenario should be modeled under a different claim framework, the output may be directionally wrong even with correct numbers.

2. Mixing up “statutory framework” vs “tool modeling inputs”

   • Statute (42 Pa.C.S. § 8301): authorizes wrongful death damages based on the general wrongful-death framework (including the condition that no action was brought by the injured person during life).
   • Tool inputs: determine the dates/period and amounts you’re modeling.
   • Keep these roles separate: the tool helps you compute damages based on what you enter; it doesn’t replace legal theory selection.

3. Assuming claim-type-specific sub-rules exist in the tool

   • The jurisdiction note you’re working from indicates: “No claim-type-specific sub-rule was found. The above is the general/default period.”
   • Translation for practice: don’t assume the calculator applies extra special wrongful-death-only timing rules beyond its general/default logic when a specific sub-rule isn’t available in the underlying configuration.

4. Unit and rounding mismatches

   • Income: monthly vs annual
   • Time: days vs months vs years
   • Percentage/factor inputs (e.g., entering 0.03 vs 3 where the tool expects a specific format)

5. Forgetting to align category toggles with your intent

   • If the calculator offers “include funeral expenses” (or similar), leaving it off can understate totals.
   • Conversely, entering a funeral amount into one category while also enabling a toggle that adds funeral expenses elsewhere can double count.

Quick input audit checklist (before relying on results)

• Dates are correct and refer to the correct events
• Income fields match the tool labels (annual vs monthly)
• Include/exclude toggles match your modeling scope
• Categories were entered once (avoid double counting)
• You ran at least one single-variable sanity check (for example, a controlled date change)

Try it

Follow this hands-on sequence to validate your Pennsylvania run in DocketMath:

1. Open the calculator: /tools/wrongful-death-damages
2. Confirm the tool is set to Pennsylvania (US-PA) behavior.
3. Enter:

   • the date of death
   • your income/earnings inputs (using the exact units the field requests)
   • the damages period (or the end date) the worksheet requests
4. Click Calculate.
5. Review:

   • the total
   • the breakdown by category (if shown)
6. Make one controlled adjustment:

   • change the end date by 12 months (or the smallest meaningful step the tool allows)
   • confirm the total moves in the expected direction

Finally, compare your output to your own expectations:

• Does the total roughly align with the modeled earnings period you intended?
• Are any optional noneconomic categories included only if you intended them?

If you’re building multiple scenarios (e.g., different earnings or work-life assumptions), save each run so you can compare outputs side-by-side.

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