Inputs you need for Treble Damages in Brazil
4 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
To use DocketMath’s treble-damages calculator for Brazil (BR), gather the inputs below first. Treble-damages outcomes in Brazil depend heavily on which legal theory you’re under and whether you can substantiate the required elements with documents and timelines.
Note: This is a data-prep guide for running DocketMath. It’s not legal advice, and it won’t replace an attorney’s case-specific analysis.
Use this checklist to confirm you have everything the calculator needs:
- Examples of triggers you might select in DocketMath:
Finally, collect these supporting details so you can validate your numbers and timelines before running the calculator:
What changes when an input changes?
| Input you set | Typical impact on treble result |
|---|---|
| Base amount (BRL) | Multiplies directly (e.g., BRL 100,000 → BRL 300,000 before any adjustments) |
| Event date / filing date | Changes how time-based components are applied (interest/monetary correction) |
| Offsets / prior payments | Reduces the base used for the multiplier (helps prevent double counting) |
| Trigger selection | Determines whether the calculator applies a treble multiplier at all and how it structures the calculation |
Where to find each input
Below are practical places to pull each item from in the real world. The goal is to shorten your time-to-run inside DocketMath.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
1) Claim type trigger
Where to find it:
How to use it in DocketMath:
- Choose the trigger that matches the legal basis you’re testing.
- If you’re unsure, run the calculator under each plausible trigger in a spreadsheet first—then converge.
2) Base amount (BRL)
Where to find it:
Tip:
- If your damages are split (e.g., principal vs. ancillary), decide whether DocketMath should treat ancillary amounts as part of the “base amount” in your workflow.
3) Event date and filing date
Where to find it:
Common pitfalls to avoid:
- Don’t use “last communication date” unless it’s tied to a specific legal event in your theory.
- Make sure event date is consistent across the complaint narrative and the calculation inputs.
4) Interest and monetary correction approach
Where to find it:
If you already have a damages worksheet:
- Reconcile whether it includes interest/monetary correction. Then match DocketMath’s setting so you don’t double-count.
5) Offsets / prior payments
Where to find it:
Rule of thumb:
- Only enter offsets you can document clearly. Unverified offsets can misstate the base.
Run it
Once you’ve gathered the inputs, you’re ready to calculate. In your workflow, do this:
- Open the tool here: /tools/treble-damages
- Enter:
- Claim type trigger
- Base damages amount in BRL (and subtract any documented offsets)
- Event date and filing date
- Interest/monetary correction selection
- Review the breakdown DocketMath shows (base → multiplier → time-based adjustments).
Practical run sequence (recommended)
- Step A: Run with interest/monetary correction turned off.
- Purpose: confirm your base amount and multiplier logic first.
- Step B: Run again with your selected interest/correction approach.
- Purpose: validate the time component after you’ve locked the base.
- Step C: If your case has uncertainty in trigger selection, run:
- Trigger 1 vs. Trigger 2
- Then compare results side-by-side.
Comparison checklist (before you finalize)
Warning: If you enter both (a) a base amount that already includes interest/monetary correction and (b) also enable interest/correction in DocketMath, the output can effectively overstate damages.