How to run Wrongful Death Damages in DocketMath for Rhode Island

Step-by-step

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

Follow these steps to run Wrongful Death Damages in DocketMath for Rhode Island (US-RI). This walkthrough focuses on wiring the calculator inputs correctly so the outputs reflect Rhode Island’s jurisdiction-aware rules—especially the general statute of limitations (SOL).

1) Open the Rhode Island wrongful-death damages calculator

Start at the primary call to action:

• /tools/wrongful-death-damages

In DocketMath, select the jurisdiction as Rhode Island (US-RI) if the interface prompts for it (or confirm it’s already selected).

2) Confirm the SOL setting used by the calculator

For Rhode Island, the available jurisdiction data for this run is the general default SOL period—not a claim-type-specific one.

Use this rule in your setup:

• General SOL Period: 1 year
• General Statute: General Laws § 12-12-17
• Source: https://codes.findlaw.com/ri/title-12-criminal-procedure/ri-gen-laws-sect-12-12-17/

Because the jurisdiction brief states no claim-type-specific sub-rule was found, your DocketMath run should treat this as the default period:

• Default SOL in this workflow: 1 year (General Laws § 12-12-17)

If the calculator shows an “effective SOL” or “time window” field:

• set it to 1 year
• ensure it’s tied to General Laws § 12-12-17
• avoid leaving it blank (which can cause unintended defaults) or using a different state’s value

3) Enter the key damages inputs

Wrongful-death damages workflows commonly depend on inputs like:

• Economic losses (often income-related categories)
• Non-economic losses (if the DocketMath template supports them)
• Time horizons / multipliers (depending on how the tool is designed)

Go through the DocketMath input fields one by one and enter values with two goals:

1. Make numbers consistent with the scenario dates (incident/death, filing, and/or evaluation date).
2. Keep units aligned (years vs. months; amounts in dollars; any “per year” assumptions).

A practical approach:

• Gather the incident date and filing date (or “evaluation date”) from your working file.
• Use those to drive any fields the UI uses for “time elapsed,” “age of case,” or SOL logic.

4) Set the relevant timeline dates (SOL-aware)

If DocketMath asks for dates, populate them carefully:

• Date of death / incident date (the event anchor)
• Date of filing (or the date you’re assessing timeliness against)
• Optional: calculation date if the UI separates it from filing

DocketMath should then apply Rhode Island’s default SOL of 1 year (General Laws § 12-12-17) to determine whether the timeline falls inside the SOL window.

How the output changes based on SOL

When SOL logic is enabled, outputs typically shift in one or more of these ways (exact wording varies by UI):

• If within SOL (≤ 1 year): the calculator proceeds with the damages computation normally.
• If outside SOL (> 1 year): the tool may flag the scenario as time-barred for timeliness purposes, which can:

  • change a “recoverable” or “timely” status indicator, and/or
  • limit the conclusions shown, and/or
  • alter parts of the display even if the arithmetic damages could still be computed

5) Review the jurisdiction banner / “Rhode Island rules” summary

Before you finalize, check the calculator’s summary panel (or any jurisdiction label). You’re looking for:

• US-RI selected
• SOL displayed as 1 year
• Citation shown as General Laws § 12-12-17, or otherwise clearly described as the Rhode Island default period

If the UI doesn’t explicitly show the statute text:

• compare the displayed SOL length to confirm it matches 1 year
• confirm it isn’t inheriting another jurisdiction’s settings

6) Generate results and capture the breakdown

After you run the calculation:

• Check for a damages breakdown (commonly economic vs. non-economic, plus any subcategories).
• Confirm whether the tool provides:

  • a timeliness indicator based on the default 1-year SOL
  • a total damages figure
  • intermediate outputs (such as annualized loss × time horizon), if the UI includes them

Export or copy the results summary for repeatability. The goal is that if you rerun the same scenario with a corrected input (especially dates), the output changes in a predictable way.

Common pitfalls

These issues commonly cause incorrect or misleading results when running jurisdiction-aware calculations like wrongful-death damages in DocketMath for Rhode Island.

• In this workflow, the Rhode Island default SOL is 1 year tied to General Laws § 12-12-17.
• The jurisdiction brief explicitly states no claim-type-specific sub-rule was found. Use the default 1-year SOL for this configuration.
• Incident/death date vs. filing date are not interchangeable.
• If SOL logic is based on the order/difference between these dates, swapping them can flip the “within SOL” result.
• Example: entering monthly income into a per-year field (or vice versa) can produce totals off by a factor of 12.
• If the output summary doesn’t clearly show US-RI and 1-year SOL, pause and re-check:

  • the jurisdiction selector
  • the SOL field/value
  • any “effective SOL” or “time window” controls
• If the tool indicates the matter is outside SOL, treat the results as procedurally constrained even if the damages arithmetic still displays.

Try it

Use this checklist to run a clean Rhode Island scenario in DocketMath:

• General SOL Period: 1 year
• General Statute: General Laws § 12-12-17
• Date of death / incident
• Date of filing (or evaluation date)
• Damages breakdown
• Timeliness indicator based on the default 1-year SOL

If you want to validate that DocketMath’s Rhode Island SOL wiring behaves as expected, stress-test with a small date change:

1. Keep all damages inputs constant.
2. Adjust only the filing date by ± 90 days.
3. Compare runs:

   • watch the SOL-based timeliness flag first
   • see whether the damages display changes only in the ways you’d expect from a timeliness toggle

This helps confirm the tool is using the US-RI default 1-year SOL (General Laws § 12-12-17) in the workflow.

Related reading

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