How to interpret Wrongful Death Damages results in Brazil

What each output means

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

DocketMath’s Wrongful Death Damages calculator for Brazil (BR) converts the case inputs you select into a damages estimate you can compare across scenarios. The results are best treated as a modeling output—useful for understanding the arithmetic behind your assumptions, but not a substitute for a court’s final determination.

In most runs, you’ll see two layers:

1. A computed damages figure (the “headline” number you compare across options).
2. Supporting components that explain what is included and how the model builds up the total.

Because wrongful-death damages can be computed in different ways depending on the facts and the way categories are presented, focus on the structure of the output: identify what each line represents, then connect those lines to the inputs you entered.

Common output lines to look for

• Total wrongful death damages (estimated)
  This is the calculator’s headline total—the sum of the included damage categories based on your inputs. If you change an assumption, the headline number is expected to move in response, often following the biggest component changes.

• Loss-of-support component (if shown separately)
  This portion generally represents the economic impact on dependents. If the UI displays sub-totals or converted amounts (for example, monthly vs. annual presentation), the underlying loss-of-support calculation is often the main driver of the headline result.

• Time-period or duration-based component (if shown separately)
  Some outputs break the estimate across a modeled timeline (for example, a horizon tied to a dependency or endpoint assumption). If duration appears as an input or affects an intermediate step, it can increase the total by extending the number of time slices the model includes.

• Present value / discounting (if shown separately)
  If the calculator expresses future amounts in present terms, it may use discounting based on timing. Discounting can shrink future values, and the size of the effect often grows as the modeled horizon lengthens.

• Assumptions and scenario flags (if shown)
  DocketMath may indicate which scenario settings or toggles were applied—such as which categories are counted. These flags can change the headline total even if the economic inputs (like income) look unchanged.

Gentle note (Brazil-specific context): Wrongful-death outcomes often depend heavily on proof and legal framing. DocketMath helps you interpret the math of the inputs you choose, but you should confirm that your inputs align with how the claim and dependency/loss are documented in your case materials.

A quick checklist for interpreting a result

When reviewing any run, follow this workflow:

• Identify the headline total and the main component(s) that feed it
• Note the exact inputs corresponding to those components
• Check whether present value/discounting is active and what settings were used
• Confirm whether scenario toggles altered what categories were included

What changes the result most

In wrongful-death modeling, the biggest swings usually come from a small group of inputs. For Brazil (BR), in DocketMath the most influential drivers are typically:

These inputs have the biggest impact on the final number. Adjust them one at a time if you need a sensitivity check.

• date range
• rate changes
• assumption changes

1) Economic loss “size” inputs (income/earnings/proxy figures)

If the calculator uses an income-related number, it commonly impacts the loss-of-support component directly.

How to recognize this in the output

• If the total and the loss-of-support component move together when you test scenarios, the income/proxy input is likely the dominant driver.

Practical pattern

• Raising the income base often increases the headline total in a near-proportional way—assuming the time horizon and discounting stay the same.

2) Dependence duration / modeled timeline

If the model includes a dependence or timeline horizon—either as an explicit input or through an assumption—then extending that period can raise damages quickly.

How to recognize this

• The output may show timing-split totals or the duration may affect intermediate calculations feeding the total.
• When duration changes, the headline total typically changes even if income is unchanged.

3) Discounting / present-value settings (timing math)

When present-value logic is applied, the discount rate (or timing rules) can materially shift the estimate, especially over longer horizons.

How to test

• Keep income and duration constant, then compare results with different discount/present-value settings (or different scenario presets, if the tool provides them).
• If the total shifts noticeably, discounting is likely a key driver.

4) Category inclusion (what the calculator counts)

Two scenarios with the same income and duration can produce different totals if the set of included categories changes.

What to check

• Ensure you didn’t unintentionally toggle categories while doing “what-if” comparisons.
• Confirm any checkboxes/flags shown in the DocketMath results match the scenario you intend to represent.

5) Inputs that seem “minor” but multiply over time (scaling/growth/age endpoints)

Some calculators use demographic or scaling factors (like growth assumptions or age-related endpoints). These can be smaller in the UI but still have an outsized effect because they apply repeatedly across the model’s timeline.

Avoiding confusion

• Change one input at a time for controlled comparisons.
• If you change multiple assumptions together (income + duration + discounting), it becomes hard to tell which factor caused the difference.

Next steps

Use DocketMath for interpretation and documentation by running a small set of controlled comparisons.

1. Re-run the model with scenario pairs

• Pair A (baseline): your current set of inputs
• Pair B (one change): adjust only one high-impact driver (typically income, duration, or discounting)
• Record which output lines change the most (headline total vs. loss-of-support vs. timing/discounting)

1. Build a simple comparison table Use a structure like this:

1. Map results back to the evidence you can support

• If the model uses an income proxy, ensure it corresponds to what you can document (e.g., earnings records or other supported proxies).
• If it relies on a duration endpoint, verify that it reflects the dependency timeline you can support with your case materials.

1. Document assumptions and settings If DocketMath shows scenario settings, capture them alongside the results so reviewers can see what the model assumed.

To start right away from the calculator, use:

• /tools/wrongful-death-damages

If you want to explore the broader tool ecosystem, you can also review:

• /tools

Related reading

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