How to run Wrongful Death Damages in DocketMath for Connecticut

Step-by-step

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

This guide explains how to run Wrongful Death damages in DocketMath for Connecticut (US-CT) using the wrongful-death-damages calculator, with jurisdiction-aware timing based on Conn. Gen. Stat. § 52-577a.

1) Start the correct DocketMath tool

Open the primary calculator here: /tools/wrongful-death-damages

Once loaded, set the jurisdiction to Connecticut (US-CT). DocketMath’s jurisdiction selection ensures the calculator applies Connecticut-specific assumptions—especially for timing and limitation-period checks.

2) Confirm the limitation period rule you’re encoding (Connecticut)

For Connecticut, the general wrongful-death limitations period is governed by:

• Conn. Gen. Stat. § 52-577a
• General SOL Period: 3 years

DocketMath uses that default/general period unless you’ve provided a reason to apply a different rule (for example, a separate accrual or tolling scenario you’ve modeled explicitly).

Important: Your jurisdiction data indicates no claim-type-specific sub-rule was found. So the calculator should treat 3 years as the default period under § 52-577a for wrongful death timing purposes.

3) Enter the case basics that affect damages computation

While the exact UI labels can vary slightly, wrongful-death calculators typically require inputs like these (enter them as they appear in DocketMath):

• Decedent details

  • Decedent’s age (or date of birth / date of death, depending on the input method)
• Incident and timeline inputs

  • Date of death (and any date you use as the damages “as-of” point)
• Damages components

  • Economic loss inputs (commonly earnings-related fields)
  • Non-economic loss inputs (commonly pain-and-suffering-related or loss-of-life components—depending on the calculator’s design)
• Allocation or share modeling (if supported)

  • Whether to model damages as a total figure or split among claimants

As you enter values, watch how DocketMath updates the running total and category subtotals. The key workflow is: correct dates → correct eligibility/timing checks → correct damages math.

4) Use the Connecticut timing check in the workflow

If the tool includes a “limitations / timeliness” section (common in jurisdiction-aware calculators), make sure the dates you entered support that check.

A practical approach:

• Use the incident date or death date fields exactly as intended by the tool.
• Use the filing date field (if available) to compare against the 3-year period from Conn. Gen. Stat. § 52-577a.
• If the calculator has an “as-of” date, keep it consistent across all inputs so the tool doesn’t compare mismatched timelines.

5) Interpret the outputs as category math + timing context

DocketMath typically returns:

• Total wrongful death damages estimate
• Category breakdown (economic vs non-economic or similar buckets)
• Any timeliness indicator (if included in this calculator)

Now connect the output to your inputs:

• If your economic inputs change, you should see the economic subtotal move first, then the total.
• If your non-economic inputs change, the non-economic subtotal moves, often without affecting economic totals.
• If you change the filing date or “as-of” date, the timeliness check should change even when damages stay the same.

This separation helps you sanity-check results:

• Damages math should track your entered values.
• Timeliness should track the 3-year rule under Conn. Gen. Stat. § 52-577a.

6) Save or export results (and keep your assumptions)

If DocketMath supports saving, export, or generating a shareable view, store the scenario so you can compare alternatives. For example:

• Scenario A: lower economic loss, earlier filing date
• Scenario B: higher economic loss, later filing date
• Scenario C: same economics, adjusted non-economic assumptions

When you revisit the numbers, confirm that the Connecticut timing assumption remains anchored to § 52-577a’s 3-year general period, since no claim-type-specific sub-rule was identified in your provided jurisdiction data.

Common pitfalls

Wrongful-death estimates often fail for reasons that are unrelated to the damages math. In Connecticut, the most common issues map to timing and input hygiene.

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

1) Treating the limitations period as longer or shorter than 3 years

For Connecticut, this guide uses the general/default 3-year period under Conn. Gen. Stat. § 52-577a.

• Pitfall pattern: A user assumes the calculator will automatically apply a special wrongful-death sub-period.
• Reality based on your jurisdiction data: No claim-type-specific sub-rule was found for this workflow, so the 3-year general period is the default.

2) Mixing up “date of death,” “incident date,” and “filing date”

Even a correct 3-year rule can produce a wrong conclusion if the tool expects one date field and you supply another.

Checklist:

• Are you consistent with which date represents the “trigger” for the timing check?
• Did you enter the filing date in the correct field (if present)?
• Does DocketMath display the date comparison it used? If so, confirm it.

3) Changing one input category and misreading where the change shows up

If you adjust:

• economic inputs → economic subtotal and total should change
• non-economic inputs → non-economic subtotal and total should change
• filing/timing inputs → timing indicator may change even if damages don’t

When outputs don’t respond the way you expect, double-check:

• numeric entry formats (annual vs monthly; gross vs net)
• units (years vs months)
• whether DocketMath expects a single figure or a set of fields

4) Forgetting to update the jurisdiction selection to US-CT

If the calculator is left on another jurisdiction, timing assumptions and any modeled rules could change.

• Confirm the jurisdiction selector shows Connecticut (US-CT).
• Then verify you’re using Conn. Gen. Stat. § 52-577a timing logic (3 years, general/default).

Try it

Follow this quick workflow to validate that your DocketMath run behaves correctly for Connecticut:

• the timing check (including any “filing date”)
• Scenario 1: same damages, adjust filing date
• Scenario 2: same filing date, adjust economic inputs
• timeliness indicator changes only when timing inputs change
• damages totals change only when damages inputs change

If the output doesn’t follow those cause-and-effect checks, pause and re-check your entries—especially date fields and units.

Related reading

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