Choosing the right Wrongful Death Damages tool for Brazil

Choose the right tool

If you’re trying to estimate wrongful death damages in Brazil (BR), the biggest risk usually isn’t “getting the math wrong”—it’s picking the wrong type of setup for the facts you actually have. DocketMath’s Wrongful Death Damages tool is built to help you structure and compute a damages range using jurisdiction-aware rules, but it will still reflect the inputs you choose. Your job is to make sure those inputs match what your case materials can support.

1) Start with the case type your evidence can support

In Brazil, wrongful death damages calculations typically depend on the claimant’s relationship, the extent of economic reliance/dependence, and the loss measurement over time. Before you touch any calculator, decide which scenario your evidence most strongly supports.

Use this quick checklist to confirm you have the essentials:

If you can’t check the middle items—especially proof of economic dependence—your outputs may still run, but the damages “story” may be harder to defend. In practice, the calculator can quantify the model; it cannot tell you which loss components your facts should include.

2) Confirm you’re using the right DocketMath calculator

For this use case, the correct entry point is DocketMath’s wrongful-death-damages calculator.

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

Inside the tool, you will typically enter inputs that influence:

• the economic loss component (often linked to the deceased’s earnings and claimant dependence),
• the time horizon / valuation window,
• and adjustment factors (for example, present value or discounting assumptions, if included in the model).

Your goal isn’t to “force” a single number—it’s to produce a structured baseline that you can explain and refine as you improve your inputs.

3) Map Brazil-specific modeling choices to the tool’s input fields

Even without giving legal advice, it helps to understand the practical drivers that usually determine wrongful death damages outcomes in Brazil. That way, you can choose sensible values and document why they’re reasonable.

If your case involves multiple beneficiaries, treat this as a modeling and allocation task:

• either run separate claimant scenarios and then aggregate, or
• run one consolidated scenario only if you can clearly allocate the support stream to the claimant set.

Either approach is fine—the key is making allocation explicit so you can explain what drove the increase.

4) Use an “input quality” check before calculating

A practical way to pick the right tool setup is to score how confident you are in each input before you run it. When inputs are uncertain, the output becomes primarily an assumption model—so you want to know that upfront.

Try this confidence scoring:

• High (3 points): documentary proof (pay slips, contracts, tax filings, bank records)
• Medium (2 points): credible estimates with a clear basis (past employment history, reliable ranges)
• Low (1 point): unsupported assumptions (generic averages not tied to the person)

Then total your score:

• If your total is 10–12, you can run a primary estimate immediately.
• If your total is 6–9, run a range by varying the least certain inputs.
• If your total is 0–5, prioritize rebuilding your factual record first—because the numbers will be dominated by assumptions.

5) Run sensitivity tests to avoid “single-number” traps

Wrongful death damages can be highly sensitive. In practice, small changes to the income baseline or dependency share can produce large swings across a longer horizon.

Within DocketMath, use a simple sensitivity workflow:

1. Scenario A (baseline): enter your best-available income baseline, dependency share, and time horizon.
2. Scenario B (single-lever variation): adjust only one major input at a time, such as:

   • income baseline (for example, ±10–20%),
   • dependency share (low/medium/high dependence, if the tool supports it),
   • time horizon (alternative windows grounded in your evidence envelope).

Then compare results. This helps you identify which assumption is doing most of the work, so your final range feels transparent rather than arbitrary.

6) Choose the output you can defend

After you run the tool, decide how you will use the result. Common defensible uses include:

• using the output as a baseline range for negotiation or planning,
• using it to identify missing inputs (what drives the number),
• benchmarking against prior computations or internal expectations,
• comparing scenarios across different claimant structures.

For stakeholder alignment (client, counsel, insurer, internal review), a range with documented assumptions is often more useful than a single point estimate.

To get started now, open: **/tools/wrongful-death-damages

Next steps

1. Collect the inputs DocketMath will ask for

   • Confirm the deceased’s income baseline (annualized)
   • Identify each claimant and the basis for dependency
   • Gather the death date and define the relevant valuation window

2. Use a baseline-first workflow, then sensitivity

   • Run a baseline scenario first.
   • Then run additional scenarios by changing only the lowest-confidence inputs.
   • Capture outputs alongside a short note explaining the reason for each change.

3. Align your calculation unit to your case structure

   • If you have one claimant, compute one scenario.
   • If you have multiple claimants, allocate and run separate scenarios (or apply clear allocation rules) to avoid double-counting the same support stream.

4. Create an audit trail

   • Save what you entered (income figures, dependency assumptions, horizon).
   • Keep an “input change log” (e.g., income updated, dependency share revised, horizon adjusted).
   • Use this log to quickly explain why the damages estimate moved.

5. Cross-check internally with related DocketMath utilities If your workflow involves building timelines or supporting document-based inputs for the valuation, it can help to review other DocketMath tools alongside the wrongful death calculator. A practical starting point is:

   • **/tools

6. Write a decision-ready summary When complete, capture:

   • the baseline estimate
   • the low/high range from sensitivity tests
   • which input drove the largest changes
   • what factual items still need tightening

If you want a fast, consistent launch path, begin directly at: **/tools/wrongful-death-damages

Related reading

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