Inputs you need for Pre Post Offer Damages Split in Brazil

5 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Inputs you will need

Run this scenario in DocketMath using the Pre Post Offer Damages Split calculator.

To run a Pre/Post Offer Damages Split in Brazil with DocketMath, you’ll need a focused set of inputs that (1) define the offer cut-off date and (2) specify how damages accrue on each side of that date. This article is written for a calculator workflow like pre-post-offer-damages-split (BR).

Note: This is a practical walkthrough to help you assemble inputs for analysis. It doesn’t replace legal advice or case-specific strategy.

Core inputs (the ones that usually change the result)

“Offer” characterization inputs (to keep the cut-off consistent)

Currency and rounding inputs

Optional but useful inputs (improve traceability)

Where to find each input

Use the checklist below to locate each input in your case file or internal spreadsheet. The goal is consistency—particularly around which “offer” date is effective and which dates define your accrual window.

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.

Dates

Offer date / effectiveness date
- Look in: settlement correspondence, court filings, procedural records, acceptance/response documents.
- If your documents show multiple dates (e.g., offered vs. effective), choose the one you’ll model as effective, and record that choice.
Damages start date
- Look in: complaint/demand statement, contract dates, breach date, invoice date(s), or the first date you can justify accrual.
- If there are multiple breach events, you typically have two modeling options:
  
  (1) a single earliest start date for a combined model, or
  
  (2) a component-based approach with different start/end ranges per component.
Damages end date
- Look in: valuation cutoff (settlement execution date), court judgment date, or your internal measurement date.

Amounts

**Total claimed damages amount (or component amount)
- Look in: damages memo, claim statement, schedules annexed to pleadings, or your internal damages spreadsheet.
- If your memo already separates heads of loss, input those components directly rather than forcing one “total” number.

Interest/accrual rule

Which accrual rule you’re modeling
- Look in: your calculation methodology notes, damages memo, and any available calculation templates or prior orders.
- DocketMath needs a consistent rule selection so pre- and post-offer periods accrue coherently.

Currency and formatting

Currency
- Look in: claim documents and any court calculation template.
- Confirm whether the figure is already in BRL (R$) or requires conversion before you input it.

Run it

Before you run, make sure you can answer these questions consistently—because they directly control the output split between pre-offer and post-offer damages:

Which exact date is the boundary? (Offer date/effectiveness date)
When does accrual start and stop? (Damages start/end dates)
How should money change across time? (Interest/accrual rule; whether the input is treated as accruing)

Step-by-step in DocketMath

Open the tool:
- Go to /tools/pre-post-offer-damages-split.
Enter jurisdiction:
- Ensure Brazil (BR) is selected.
Enter the time inputs:
- Damages start date
- Offer date (cut-off)
- Damages end date
Enter the value/modeling inputs:
- Total claimed damages amount (or components)
- Damages type basis
- Interest/accrual rule selection
Enter formatting:
- Currency and rounding preference
Click run and review results.

What the output will do (and what to check)

DocketMath calculates a damages split by time period, typically producing fields like:

Pre-offer damages: value attributable to the period before the offer boundary
- Most affected by: offer date/effectiveness date, damages start date, accrual rule.
Post-offer damages: value attributable to the period after the boundary
- Most affected by: offer boundary, damages end date, accrual rule.
Total split check: a sanity check that pre + post align with your modeling basis.
Accrual factors by period (if shown): any modeled time-based growth/interest applied separately to each side.

Quick validation checklist (common mistakes to avoid)

Pitfall: Using an “offer date” that differs from the record’s date of effectiveness (sent vs. received vs. formalized) can shift the boundary enough to materially change the pre/post split.

How to interpret the split in practice

After running:

Compare proportions: If post-offer dominates unexpectedly, re-check the boundary (offer effectiveness date) and the accrual rule.
Verify totals: If your total claimed amount doesn’t match the sum of modeled components, decide whether DocketMath should treat your input as:
- a combined total allocated over time, or
- principal/component amounts with accrual applied consistently to each.

If needed, you can run the calculator iteratively by component (e.g., different invoice periods or heads of loss) and then sum results into your final damages schedule.