Inputs you need for Damages Allocation in Brazil
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Damages Allocation calculator.
To allocate damages in Brazil using DocketMath (tool: /tools/damages-allocation), you’ll need inputs that determine (1) what damages “heads” get allocated, (2) how timing affects calculations, and (3) how the allocation split is justified by your evidence. This checklist is practical and intended to help you produce a consistent, audit-friendly allocation dataset (not a substitute for legal analysis).
Use this as your pre-flight list:
Claimants / plaintiffs (as listed in the case)
Defendants / respondents
Any joint/several posture you intend to model (if known from pleadings)
Pick the categories you want DocketMath to allocate (for example: compensatory loss, direct damages, interest-bearing components, and/or other agreed categories)
If the case uses multiple “heads of claim,” list them separately so the tool isn’t forced to treat different concepts as one bucket
Event date(s) (e.g., contract breach date, infringement/loss occurrence date, or another event date tied to your claim)
Valuation date (the date you want results expressed as)
Any claim period start/end dates if your model uses them (for example, a defined time window for the alleged loss)
Principal amounts per category (and per party, if your source splits by claimant/defendant)
Currency (typically BRL). If your figures are already converted, keep them labeled as such and avoid re-converting inside the model.
Allocation percentages (when a contractual or evidentiary basis supports a fixed split), or
Quantity-based drivers (when you can convert facts—such as units, invoices, hours, deliveries—into proportions)
Whether allocation should be equal split, proportional, or custom by component
For proportional models: the denominator you will use (e.g., total invoices, total work performed, total impacted units)
Decide whether your damages model includes interest/monetary adjustment as:
- separate inputs, or
- amounts that are already included in “all-in” figures
If separate: provide the interest basis dates you will use for each component
Quantitative support you can attach or summarize internally: invoice lists, purchase orders, payroll/job logs, delivery records, ledgers, or expert annex data
Goal: make the allocation logic defensible and repeatable, even if numbers are refined later
Gentle note: DocketMath can operationalize your allocation strategy from structured inputs, but it can’t confirm whether your chosen categories/dates align with how “damage” is framed in your specific Brazilian pleadings. Treat outputs as a computation aid, not legal advice.
Where to find each input
Use the map below to locate the information that will populate DocketMath effectively.
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) Dates
Check:
Brazil-specific workflow tip: If the pleadings describe a time window for the alleged loss, enter start/end dates per component rather than using a single blanket date for all heads. This keeps the time logic consistent with the theory you’re modeling.
2) Principal amounts per category
Check:
If your source already breaks amounts by party (or by cost center), preserve that granularity—your allocation drivers will work better.
3) Allocation drivers (percentages or denominators)
Check:
Common pitfall: applying one allocation percentage to every damages component when different components have different evidentiary drivers. If possible, enter drivers per category.
4) Interest and adjustment components
Check:
Run it
After gathering inputs, run the process in DocketMath using the Brazil context and the allocation calculator at:
- /tools/damages-allocation
A straightforward run-through:
- Open /tools/damages-allocation
- Set jurisdiction context to **Brazil (BR)
- Create an allocation set for the damages categories you want to model
- Enter, for each category/component:
- Category name and principal amount (and party split if available)
- Dates (event date, valuation date, and claim period dates if applicable)
- Allocation method: equal, proportional, or custom
- Allocation drivers: percentages or denominators/quantities
- Interest/adjustment approach: separate vs included
What you should expect from the outputs
DocketMath typically produces:
- Category-level allocations showing how each head is split across parties
- Party-level summaries (totals per claimant/defendant based on your drivers)
- A date-aware computation view where the valuation timing changes the final expression of amounts
How outputs change when you tweak inputs (high-impact examples)
- Change valuation date: party totals can shift if your model treats time-based components as separate or explicitly date-driven.
- Switch “equal split” → “proportional”: results move toward the party with larger evidentiary weight (invoices/units/hours).
- Enter drivers per category: overall totals may remain similar, but the distribution across parties can change materially.
Consistency check (important): if you mix all-in figures with “interest enabled” as separate components, you may overstate damages. Ensure each monetary field represents the same component definition across categories.