How to run Damages Allocation in DocketMath for Brazil

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Brazil (BR), using jurisdiction-aware rules and a practical, repeatable workflow to produce consistent allocation output. This is a product workflow guide, not legal advice—use it to structure calculations and document your assumptions.

1) Open the Damages Allocation calculator (BR)

1. Go to the primary CTA: /tools/damages-allocation
2. Confirm you’re running with Brazil (BR) jurisdiction context (the calculator should reflect BR-specific logic or presets).
3. Start a new run (or duplicate an existing scenario) so you can compare variations later (for example, different “as of” dates or category assumptions).

2) Set the allocation basis

In DocketMath, Damages Allocation distributes a total damages figure across defined categories using the Brazil (BR) calculation structure.

Decide what you want the tool to allocate:

• Total to allocate (e.g., total damages claimed, or another case-defined total)
• Which allocation categories apply to your scenario
• Which method the calculator should use (jurisdiction-aware presets for BR help you avoid accidental configuration drift)

Checklist

3) Enter the date timeline (so BR rules can apply)

Brazil calculations commonly depend on time-based components—so your timeline inputs matter to the output.

Typical fields you’ll see:

• Start date (e.g., when the obligation began or when damages became due)
• End date / “as of” date (the snapshot date for the damages calculation)
• Optional intermediate dates if the UI supports stage-based periods

Tip: Keep your dates consistent across scenarios so you can isolate how changing allocation inputs (categories, rates, totals) affects outputs, rather than changing multiple variables at once.

4) Configure inflation/adjustment and interest parameters (BR preset behavior)

Damages allocation in BR may involve adjustments and/or time-based components. In DocketMath, this typically appears as:

• A Brazil preset (jurisdiction-aware defaults), or
• Manual fields for custom assumptions

Recommended approach

• If you see a BR preset, use it for the first run.
• Only switch to manual configuration if your case file requires a specific assumption you can clearly explain and reproduce.

If you must enter manual rates

• Enter the rates and the calculation basis exactly as your case file specifies.
• Match the frequency the UI offers (e.g., monthly vs. yearly), and use the units shown next to each input.

Common unit pitfall: entering an interest rate as “5” when the UI expects “0.05” (or mixing annual vs. monthly). Always verify the units displayed by the input fields.

5) Add parties / responsibility settings (only if your scenario requires it)

Some Damages Allocation setups include responsibility split options. Use them only when your scenario truly needs them—otherwise you risk changing the meaning of the output.

Options you might encounter:

• Single responsible party vs. multiple parties
• Percent allocations
• A choice between allocating a total vs. allocating per-party amounts

If your scenario is a straightforward single-actor case, keep responsibility configuration minimal so the output focuses on allocation mechanics.

6) Map categories to the total

This is where the tool is doing most of its work: you specify how DocketMath should distribute your total damages across categories.

Depending on the UI, you may choose one of these input styles:

• Category amounts (you provide amounts per category; DocketMath checks the totals)
• Category percentages (you provide weights; DocketMath calculates category amounts)
• Blended approach (some categories fixed, some computed), if the UI supports it

Practical workflow

• Decide whether you’re operating on amounts or percentages for this run.
• If you use percentages, ensure they add up to 100% (or to whatever reconciliation rule the calculator expects).
• If you use amounts, ensure the category amounts sum to the total damages input.

Always verify after calculation

• If inputs don’t reconcile, DocketMath may reject the run or redistribute based on its reconciliation rule.
• Review the allocation summary before saving.

7) Run the calculation and review the allocation output

Once inputs are ready:

1. Click Calculate.
2. Review the output panels, typically including:

   • Allocated category amounts
   • Any adjusted totals as-of your selected end date (if adjustment is enabled)
   • Breakdowns of time-based components (e.g., interest/adjustments) per category

Review checks

• Confirm category amounts sum to the expected total (or adjusted total, if BR settings apply changes).
• Confirm the date-driven components reflect your timeline inputs.
• Confirm rates and frequency reflect your intended method.

8) Save the scenario and export your results

For repeatable litigation or internal review workflows, save your scenario so it’s easy to rerun with controlled changes.

If DocketMath offers export (PDF/CSV), consider exporting for:

• Internal memos
• Stakeholder sharing
• Change tracking (scenario name + inputs)

Example naming convention

• BR - Damages Allocation - AsOf 2026-04-15 - Preset BR

Common pitfalls

These are the issues most likely to distort a Brazil allocation run—each one can materially change the results.

• Date mismatch across inputs

  • Start/end dates that don’t align with the rest of your case model can shift accumulated components.
  • Fix: standardize your “as-of” date across scenarios you intend to compare.

• Percentages that don’t reconcile

  • Category percentages that don’t sum to 100% (or don’t match the calculator’s required total) can trigger redistribution.
  • Fix: validate the allocation summary immediately after calculation.

• Rate unit errors

  • Entering “6” instead of “0.06”, or mixing annual vs. monthly frequency, can drastically inflate (or deflate) outcomes.
  • Fix: confirm the unit and frequency shown next to each rate input before running.

• Overriding BR presets without documenting why

  • Switching from jurisdiction-aware presets to manual fields can change the basis of calculation.
  • Fix: only override when needed, and document the assumption in your scenario notes (if available) so others can reproduce it.

• Using multiple-party settings when you don’t need them

  • Responsibility splits can change per-party allocations and make outputs harder to interpret.
  • Fix: align configuration with the scenario’s intended responsibility model.

Try it

Run a first Brazil (BR) scenario using a tight, controlled configuration so you can validate outputs quickly.

Quick-start checklist:

After the run:

• Compare allocated category totals to your expected structure.
• Change one variable at a time (for example, only the end date) and rerun to see how outputs move.
• Save a second scenario (example: ... - AsOf 2026-05-15) to measure sensitivity.

If you want to streamline repeated work, use DocketMath calculators in parallel while keeping your timeline consistent across models. For example, you can treat the /tools/damages-allocation output as the canonical reference for category totals, and align other runs to the same timeline inputs.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules