Worked example: Pre Post Offer Damages Split in Brazil

6 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

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

This is a worked example of a pre/post offer damages split in Brazil using DocketMath and jurisdiction-aware rules. It explains the calculation mechanically—not as legal advice.

Scenario

You’re estimating damages where:

  • Liability and damages are being assessed in Brazil.
  • There is an offer (proposta/oferta) and the case later proceeds to a judgment (or settlement terms).
  • You want to split damages into:
    • Pre-offer period (amount that accrues before the offer)
    • Post-offer period (amount that accrues after the offer)

Inputs you’ll provide to DocketMath

In DocketMath, use the calculator:

  • /tools/pre-post-offer-damages-split

Set the following inputs in the tool:

  • Jurisdiction (BR): Brazil
  • Start date: 2023-03-15
    (This is the beginning of the timeline the tool uses to compute the pre/post allocation.)
  • Offer date: 2024-03-15
  • End date for the calculation: 2025-03-15

Damages-related inputs:

  • Claim principal (damages base): BRL 200,000
  • Awarded amount / final damages used for the split: BRL 200,000
    (In real cases, you may choose a different figure depending on whether you’re modeling the judgment result or another “final” number used for allocation.)
  • Interest method toggle: use the tool’s Brazil jurisdiction-aware setup (default)

Offer-treatment mechanics:

  • Offer treatment (beneficial vs non-beneficial): in this worked example, assume the modeled offer is beneficial under the tool’s Brazil rules.

Note: Brazilian litigation mechanics tied to offers can be nuanced (timing, form of the offer, and how the court treats it). This tool is built to follow its own jurisdiction-aware split logic; if the procedural posture differs, validate your inputs against the case record.

Time basis used in the example

To make the example concrete, the example dates create two equal spans:

  • Total period: 2024-03-15 → 2025-03-15 = 365 days (non-leap-year span)
  • Pre-offer: Start date → Offer date
    2023-03-15 → 2024-03-15 = 365 days
  • Post-offer: Offer date → End date
    2024-03-15 → 2025-03-15 = 365 days

Summary of the inputs:

InputValue
JurisdictionBR
Start date2023-03-15
Offer date2024-03-15
End date2025-03-15
Claim principal / baseBRL 200,000
Awarded amount modeledBRL 200,000
Offer treatment in toolBeneficial
Days pre-offer365
Days post-offer365

Example run

Here’s a full walkthrough as if you’re using DocketMath → /tools/pre-post-offer-damages-split.

Run the Pre Post Offer Damages Split calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Select the tool and jurisdiction

  1. Open the calculator: /tools/pre-post-offer-damages-split
  2. Set:
    • Jurisdiction = **Brazil (BR)

Step 2: Enter dates and damages base

Enter:

  • Start date: 2023-03-15
  • Offer date: 2024-03-15
  • End date: 2025-03-15
  • Claim principal: BRL 200,000
  • Awarded/judgment amount used for the split: BRL 200,000
  • Offer treatment: Beneficial (as modeled)

Step 3: Let DocketMath apply its split logic

After you run the tool, DocketMath will return output fields including:

  • Pre-offer damages component
  • Post-offer damages component
  • Total
  • Timing-related fields showing how much time falls before vs after the offer (useful for validation)

Because the example is symmetric (365 days pre and 365 days post), the time window lengths are equal. However, the difference between pre and post components can still arise from the tool’s Brazil jurisdiction-aware offer split mechanics—i.e., the offer changes how the calculation allocates amounts across the timeline.

Worked numbers (illustrative mechanics output)

Assuming the tool yields results consistent with its Brazil rules for a beneficial-offer scenario, you might see:

ComponentAmount
Pre-offer componentBRL 92,000
Post-offer componentBRL 108,000
Total damages estimateBRL 200,000

In this simplified example, the components sum to the BRL 200,000 input because the tool’s split is modeled as an allocation of the selected final figure across pre vs post periods (rather than adding multiple independent “totals” on top of the base).

Output interpretation checklist

Use this checklist to confirm the run matches your intent:

Pitfall: If you input the “sent” date of the offer but the procedural record treats a different date as effective, the pre/post boundary can shift by weeks—changing the post-offer component materially in a longer timeline.

Sensitivity check

A sensitivity check tests how much the result changes when you modify one input while holding the rest constant. This helps you understand which assumptions drive the pre/post split.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity test A: Offer date shifts by +30 days

Change only the offer date:

  • Offer date: 2024-04-14 (instead of 2024-03-15)

Keep everything else the same:

  • Start date: 2023-03-15
  • End date: 2025-03-15
  • Base/award: BRL 200,000
  • Offer treatment: Beneficial

New time split:

  • Pre-offer: 2023-03-15 → 2024-04-14 = 396 days
  • Post-offer: 2024-04-14 → 2025-03-15 = 334 days

Directionally, you should expect:

  • Pre-offer share increases
  • Post-offer share decreases

Illustrative output comparison:

ComponentBefore (Offer 2024-03-15)After (Offer 2024-04-14)
Pre-offer componentBRL 92,000BRL 104,000
Post-offer componentBRL 108,000BRL 96,000
TotalBRL 200,000BRL 200,000

Depending on the tool’s interest/adjustment configuration, your total may or may not remain fixed in real-world modeling. Always check the tool output fields directly.

Sensitivity test B: Toggle offer treatment logic

Keep dates constant (use 2024-03-15) and change:

  • Offer treatment: Non-beneficial (the alternative option in the tool)

Directionally, you’d expect:

  • The tool’s allocation changes in favor of the less favorable side relative to the beneficial case (the exact direction depends on the jurisdiction-aware mechanics encoded in the calculator).

Illustrative directional comparison:

ComponentBeneficial offerNon-beneficial offer
Pre-offer componentBRL 92,000BRL 110,000
Post-offer componentBRL 108,000BRL 90,000
TotalBRL 200,000BRL 200,000

Quick sensitivity takeaways

For diligence, run at least:

This quickly shows whether the split is stable or whether the offer-treatment assumption dominates.

Related reading