Why Damages Allocation results differ in Brazil

The top 5 reasons results differ

When you run DocketMath’s damages-allocation calculator for Brazil (BR), differences almost always come from jurisdiction-aware modeling choices—not from random math. Below are the five most common causes of allocation result drift across cases, even when the “same” dispute is being analyzed.

1. **Expense characterization (what you call “damages” vs “costs”)

   • Brazilian damages modeling often separates recoverable loss components from other expenditures.
   • If one dataset treats (for example) certain administrative spend as part of “damages,” while another treats it as “costs,” the allocation basis changes—shifting both the percentages and the totals.

2. **Timing assumptions (accrual dates and event alignment)

   • Allocation outputs can change sharply when parties anchor “start dates” differently:

     • breach/event date,
     • notice date,
     • or the valuation/final judgment date.
   • Even small timing differences can matter if the calculator proration logic depends on time-weighting across periods.

3. **Causation split across claims (single harm vs multiple harm channels)

   • If your inputs separate “damages channels” (e.g., direct loss vs downstream loss) using different category definitions, DocketMath may allocate across categories in a different order or with different weights.
   • This often appears when:

     • Claim A includes categories X + Y in one run but only X in another.
     • Claim B overlaps partially with A in one run, but not in the other (because shared harm is defined differently).

4. Currency handling and FX normalization

   • Brazil analyses frequently include multi-date amounts (e.g., invoices, payments, or damages measurement points).
   • If one run keeps amounts tied to their original currency/date and another normalizes everything to a single reference date—using different FX inputs or exchange-rate timing—the allocation ratios can move.

5. Uncertainty ranges and confidence-weighted inputs

   • If your inputs include ranges (quantities, unit prices, recovery rates) and you model uncertainty explicitly, DocketMath may allocate using expected values and variance-aware logic.
   • Two runs can produce different outcomes even if the “mean” numbers look the same, because the uncertainty bounds can change how expected allocation is computed.

How to isolate the variable

Use a structured diagnostic pass in DocketMath to pinpoint the exact driver. The goal is to change one assumption at a time, so you can attribute the delta to a specific modeling choice.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

1) Create three runs: baseline, perturbation, comparison

• Run A (Baseline): Use your current Brazil (BR) inputs exactly as entered.
• Run B (Perturbation): Change only one variable (e.g., accrual date anchor, FX normalization method, or expense characterization).
• Run C (Comparison): Change that same variable back—or switch to the alternative you suspect.

2) Lock everything else

Before comparing Run A vs Run B (and Run C), verify these are consistent in DocketMath:

• Damages category mapping (which line items go into each component)
• Accrual / event dates (start and end anchors)
• Currency and FX reference handling
• Any ranges or confidence inputs
• Claim overlap settings (whether multiple claims share the same harm base)

3) Compare outputs using a “difference signature”

Create a quick comparison table focused on where the results diverge:

If you want a direct starting point, use the tool here: damages allocation in /tools and review your input mapping before rerunning.

Next steps

1. Standardize your input taxonomy

   • Create a checklist for every run:

     • What counts as a “damages component” vs “cost”
     • Which date anchors you use for accrual and valuation
     • Whether all amounts are normalized to one reference date

2. Document the “allocation basis”

   • Write one sentence per run so reviewers can spot mismatches fast, for example:

     • “Damages components X/Y include line items 12–31; currency normalized to reference date D; accrual starts at event E.”
   • This prevents mixing assumptions across iterations.

3. Run a minimal-change test suite

   • Do up to five controlled reruns—one per top cause:

     • expense characterization
     • timing anchors
     • causation split
     • FX normalization
     • uncertainty/confidence bounds

4. Reconcile conflicts by aligning definitions

   • When two parties disagree, the gap is often an input-definition gap.
   • Align component definitions, time anchors, and currency treatment—then re-run to test whether the gap closes.

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