Abstract background illustration for How to run Wrongful Death Damages in DocketMath for Rhode Island

How to run Wrongful Death Damages in DocketMath for Rhode Island

6 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Step-by-step

This guide walks you through running Wrongful Death Damages in DocketMath for Rhode Island (US-RI) using jurisdiction-aware rules. The calculator you’ll use is:

Note: This walkthrough focuses on how to operate DocketMath and apply the Rhode Island wrongful-death framework in the calculator. It doesn’t provide legal advice.

1) Confirm the wrongful-death eligibility trigger (Rhode Island default rule)

Rhode Island’s wrongful-death cause is anchored in statute: R.I. Gen. Laws § 10-7-1. The statute sets up the basic structure:

  • If a person’s death is caused by the wrongful act, neglect, or default of another, and
  • The same act would have entitled the injured party to sue for damages if death had not occurred, then
  • The proper party may bring an action for wrongful death.

In DocketMath, you’re generally modeling that “if death had not ensued” concept by entering the economic loss assumptions the tool needs, then using the wrongful-death damages framework to produce the totals.

2) Start the calculator

  1. Select Rhode Island (US-RI) if the tool prompts for jurisdiction.
  2. Proceed to inputs.

If you want a broader refresher on how DocketMath organizes financial inputs, you can review: /tools.

3) Enter the economic-damages inputs

Wrongful death calculations often depend on economic components (and assumptions about future support). In DocketMath, you’ll typically provide inputs like:

  • Annual earnings (or baseline income)
  • Fringe benefits (if separated in the tool)
  • Work-life horizon (e.g., the years until retirement or another end-of-horizon choice the tool supports)
  • Growth rate / inflation assumptions (if the tool allows)
  • Discounting / present value settings (if modeled)
  • Personal consumption / support share (how much of income would have been available to dependents/beneficiaries)

How inputs change outputs

Use this mapping to sanity-check what you’re seeing:

Input you enterWhat it affects in the resultCommon consequence of a higher value
Higher annual earningsProjected support and present valueLarger wrongful-death damages (usually)
Higher “support percentage” / lower consumptionPortion allocated to beneficiariesLarger wrongful-death damages
Longer horizonMore years of projected supportLarger wrongful-death damages
Higher growth rateFuture earning projectionsLarger future totals → larger present value

4) Add non-economic components if the tool provides them

Some wrongful-death calculators include non-economic damages (for example, loss of society or companionship). Whether DocketMath includes explicit non-economic line items depends on what fields are available in the Wrongful Death Damages tool.

If you see non-economic fields in the calculator:

  • Fill them using the tool’s expected format (single value vs. range/lump-sum).
  • Keep your assumptions consistent with how the tool aggregates categories.

If you don’t see non-economic fields, don’t try to force them—your output will reflect only the categories the tool actually models.

5) Set the Rhode Island timing rule (limitations period)

DocketMath may ask for a limitations setting or a case timeline input. For this Rhode Island setup, your jurisdiction data indicates:

  • General SOL Period: 3 years
  • General Statute: R.I. Gen. Laws § 10-7-1
  • And importantly: No claim-type-specific sub-rule was found.

Because no claim-type-specific sub-rule was identified, you should apply the general/default period clearly as the governing limitations period in your DocketMath configuration:

  • Use a 3-year limitations period as the default for this Rhode Island wrongful-death setup.

Warning: Don’t assume there’s a shorter or specialized wrongful-death SOL sub-rule in Rhode Island unless the DocketMath jurisdiction configuration explicitly provides one. Your current jurisdiction data indicates only the general/default 3-year period.

6) Review jurisdiction-aware outputs

After you submit inputs, DocketMath should produce outputs such as:

  • Economic damages totals (often presented as present value)
  • Aggregated wrongful-death damages totals
  • A timing-related flag or computed deadline if the tool includes limitations logic

Before exporting or saving, quickly verify:

  • The projection/horizon you selected matches your scenario (e.g., retirement age vs. tool default)
  • Percentages and shares are entered in the correct field (and formatted correctly)
  • The limitations period shown by the tool is 3 years for Rhode Island under this configuration

7) Export or save your run

Use DocketMath’s save/export feature to keep a record of:

  • The selected jurisdiction (US-RI)
  • Your key numeric assumptions
  • The computed totals
  • Any limitations-related outputs

This also makes it easier to rerun controlled scenarios later—like adjusting support share or changing horizon—and compare results consistently.

Common pitfalls

  1. Using the wrong limitations period

    • This Rhode Island setup uses the 3-year general SOL period.
    • Your jurisdiction data states no claim-type-specific sub-rule was found, so switching to another period would contradict the configuration.
  2. Misunderstanding the “if death had not ensued” link

    • R.I. Gen. Laws § 10-7-1 ties wrongful death to what the injured person could have recovered had death not occurred.
    • In practice, that means your calculator inputs should align with the tool’s “baseline/economic loss” logic before the wrongful-death framework is applied.
  3. Confusing “support share” with “consumption share”

    • Many calculators use one of these concepts directly. Entering both (or entering values intended for one field into another) can create double-counting or distortion.
    • If the tool asks for one method, use that method only.
  4. Changing one input and reading too much into the output

    • Adjusting “annual earnings,” for example, can interact with growth, horizon, and present value settings.
    • Do a minimal-change test: adjust one assumption at a time and confirm the output changes in the expected direction.
  5. Assuming non-economic damages are always included

    • Some models compute only economic loss.
    • If non-economic fields are absent or left blank, the total will reflect whatever categories are actually modeled in DocketMath.

Try it

Use this controlled run checklist in DocketMath for US-RI:

  • Set jurisdiction to Rhode Island (US-RI)
  • Enter baseline income numbers (annual earnings + any modeled benefits)
  • Set a projection horizon that matches the tool’s structure
  • Provide one support/consumption method (don’t enter both if the tool only expects one)
  • Confirm limitations/timing uses 3 years (default per jurisdiction data)
  • Submit and review totals
  • Re-run once with only one changed assumption (e.g., horizon shortened by 2 years) to confirm the output responds

Then compare the two runs:

  • If the horizon decreases, projected support (and likely present value) should decrease.
  • If support share decreases (or consumption increases, depending on how your inputs are structured), the economic damages total should decrease.

Note: If your output doesn’t move after a change, re-check that you edited the correct field (for example, “earnings” vs. “growth rate”) and that the tool recalculates after submission.

Related reading