How to run Wrongful Death Damages in DocketMath for Vermont
7 min read
Published June 4, 2026 • By DocketMath Team
Step-by-step
Follow these steps to run Wrongful Death Damages in DocketMath for Vermont (US-VT). This walkthrough focuses on getting the right inputs, selecting the correct jurisdiction behavior, and understanding what the calculator is doing with Vermont’s wrongful-death statute.
Note: DocketMath’s workflow is designed for calculation support, not legal advice. Use the results to organize estimates and questions—not to replace a lawyer’s review.
1) Open the correct calculator
- Go to the tool: /tools/wrongful-death-damages
- Set the jurisdiction to Vermont (US-VT).
DocketMath’s wrongful-death calculator is designed to accept typical economic-damages inputs and then apply jurisdiction-aware rules based on your selections.
2) Confirm you’re using Vermont’s wrongful-death framework
Vermont’s wrongful-death action is authorized by 14 V.S.A. § 1492. The statute covers deaths caused by another’s wrongful act, neglect, or default, where the injured party would have been able to sue (to recover damages) if death had not occurred.
Practically, your setup should reflect:
- a qualifying wrongful act/neglect/default scenario, and
- a causal connection between the conduct and the death.
Your DocketMath run won’t determine liability—it estimates damages once you assume the scenario fits the wrongful-death framework.
Source: https://legislature.vermont.gov/statutes/section/14/1492
3) Enter the core economic inputs (the values that drive totals)
Use the calculator fields to input the decedent’s financial baseline and timeline assumptions. Field names can vary slightly by interface version, but wrongful-death damages tools typically ask for items like:
- Decedent’s income (or earning capacity)
- Expected work-life horizon (or remaining earning period)
- Growth / wage increase assumption (if offered)
- Discount rate / future value assumption (if offered)
- Assumed survival or loss period (if applicable in the workflow)
As you enter values, watch how the output updates. Many tools separate totals into:
- an income-based loss/future earnings component, and
- one or more additional modeled components (depending on the calculator’s design).
Tip: If you’re unsure which numbers the tool expects, pause and verify the calculator’s input units (for example, annual vs. monthly).
4) Add beneficiary/survivor weighting if your workflow supports it
If the DocketMath workflow asks for survivor or beneficiary details, fill them in carefully—this can significantly change the final distribution of damages.
Checklist (only complete what the tool requests):
- Number of beneficiaries (if requested)
- Allocation method (e.g., equal shares vs. custom shares, if offered)
- Any dependency scaling factor (if offered)
If you don’t have reliable allocation data, don’t force a single precise allocation. Instead, run multiple scenarios (for example, conservative / midpoint / aggressive assumptions) to see how sensitive the results are.
5) Apply Vermont timing behavior (clarify the “default” approach)
DocketMath will apply jurisdiction-aware timing behavior based on the jurisdiction configuration.
For Vermont, the jurisdiction notes you’re working from state:
- No claim-type-specific sub-rule was found, so the calculator should use the general/default period as the applicable timing behavior.
Warning: Don’t hunt for a “special wrongful-death damages” time rule inside the tool. If the jurisdiction notes indicate only a general/default approach, your US-VT runs should proceed using the default timing logic rather than attempting to apply a separate claim-type exception that isn’t available.
In other words: when you select US-VT, expect DocketMath to use the general/default period logic for the wrongful-death calculation model.
6) Review outputs and run sensitivity checks
After you complete inputs, review:
- Total estimated wrongful-death damages
- Component breakdown (e.g., income-based loss vs. other modeled components)
- Any assumption impact indicators (some tools show which assumptions most affect the total)
Then run sensitivity checks. A simple, practical approach:
- Adjust income by a reasonable step (commonly ±10% or the closest supported change)
- Adjust the time horizon (if the tool allows it)
- Adjust discount/growth assumptions (if offered)
This helps you understand what is driving the number rather than relying on a single estimate.
7) Save/export the result (so you can compare later)
If the tool offers export or sharing options, save:
- the jurisdiction setting (US-VT),
- the key assumptions you entered (income, horizon, discount/growth, beneficiary allocation if applicable),
- and the resulting totals.
This is especially useful if you later update wage documentation or run an additional scenario.
Common pitfalls
Pitfall 1: Assuming a Vermont “claim-type-specific” timing rule exists
If the jurisdiction notes indicate no claim-type-specific sub-rule was found, then:
- use the general/default period timing behavior, and
- don’t try to apply a special wrongful-death timing exception beyond what the US-VT calculator configuration supports.
Pitfall 2: Mismatching the calculator’s income basis (annual vs. monthly, etc.)
Wrongful-death totals can be off drastically if you enter the wrong unit. Confirm whether the calculator expects:
- annual vs. monthly earnings,
- gross vs. net figures,
- and whether your income input should include items like benefits/overtime (only include them if your income model matches the calculator’s structure).
Pitfall 3: Over-trusting a single-point estimate
One run can hide uncertainty. Wage projections, horizon assumptions, and discount/growth choices often shift results meaningfully. Instead of relying on one number:
- run a base case, and
- run at least one adjusted case with changed assumptions.
Pitfall 4: Not recording assumptions
Even for quick planning, document what you entered:
- income or earning capacity figure,
- loss/horizon period,
- discount/growth assumptions,
- and beneficiary allocation (if used).
This makes the output auditable and easier to refine.
Pitfall 5: Blending “eligibility/liability” questions into the damages math
14 V.S.A. § 1492 provides the wrongful-death cause of action structure when death is caused by another’s wrongful act/neglect/default and the injured party could have sued if death had not occurred.
DocketMath calculates damages assuming the scenario fits that framework. It doesn’t verify:
- whether the wrongful-act/neglect/default element is satisfied, or
- whether causation and other legal requirements are met.
Note: DocketMath helps compute damages estimates. It doesn’t verify liability. Keep those issues separate from the math.
Try it
To run your first Vermont (US-VT) wrongful-death damages estimate in DocketMath:
- Open /tools/wrongful-death-damages
- Select Vermont (US-VT)
- Enter:
- decedent income / earning capacity
- the loss horizon (or expected period)
- discount/growth assumptions if requested
- beneficiary allocation inputs if prompted
- Run the calculation
- Review:
- total damages
- the breakdown by component
- Do a sensitivity check:
- adjust income by ±10% (or the closest supported adjustment)
- rerun and compare totals
Quick sanity-check checklist (before you trust the output)
- Jurisdiction is set to US-VT
- You used the general/default period timing behavior (no claim-type-specific sub-rule found)
- Your income basis matches the calculator’s expectations (annual vs. monthly, etc.)
- You recorded the assumptions used for the run
- You ran at least one alternate scenario to see the range
If the output seems unexpectedly high or low, start by checking:
- time horizon,
- income magnitude/unit, and
- discount/growth settings.
Those typically explain most large swings.
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
