Choosing the right Pre Post Offer Damages Split tool for Brazil

7 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.

Choose the right tool

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

If you’re splitting damages amounts for a pre–post offer period in Brazil (BR), DocketMath’s Pre Post Offer Damages Split tool can help you produce a consistent, worksheet-style split—as long as you choose the tool configuration that matches your case model facts.

Brazil timelines and damages mechanics can vary by case. So the “right” tool choice is less about finding one perfect calculator and more about aligning your inputs to jurisdiction-aware judgment logic you already use internally—especially around (1) what you mean by the “offer” date and (2) how the split boundaries are treated.

What the DocketMath tool is designed to do (and what to confirm first)

DocketMath’s pre-post-offer-damages-split is designed to allocate a total damages figure across two time windows:

Pre-offer period: from a defined start date up to the offer date (depending on your selected convention, the offer date may be included/excluded in this window)
Post-offer period: from the offer date through your end date (often your judgment date or calculation cutoff)

Because the tool’s output depends on these boundary assumptions, take a few minutes to confirm your internal definitions before you enter numbers.

1. Confirm what “offer” means in your model

In BR-related work, “offer” can mean different things. Your tool inputs should reflect the anchor your analysis uses:

An offer/proposal event in the case timeline (e.g., procedural filing/record)
The date you treat as the economic change-point for your damages split

Practical tip: If you have an existing spreadsheet, try to copy the same “offer date” logic into the tool so you can compare results apples-to-apples.

2. Confirm what total you’re splitting

You’ll typically be either:

Splitting one consolidated total damages amount into pre and post components, or
Splitting already-separated components (e.g., principal vs. costs), then summing the outputs

If your case model treats components differently over time, splitting them together can hide timing differences.

3. Decide how you want rounding and day counts handled

Outputs can shift even when the overall total stays the same if the tool uses:

Calendar-day counting vs. another convention
Inclusive vs. exclusive boundary counting (for example, whether the offer date is attributed to pre or post)
A rounding approach (if the tool rounds per step or at the end)

Pitfall to avoid: Selecting a boundary convention that attributes the offer date to the wrong window (pre vs. post) can produce a meaningful difference—especially when pre and post windows are uneven in length.

Tool-selector guidance: pick the setup that matches your Brazilian facts

Use this checklist to choose the configuration in /tools/pre-post-offer-damages-split that will produce a defensible split for BR.

A. Choose the correct “basis” for the total you’re splitting

In DocketMath, you’ll generally model one of these patterns:

Time-proration of a total: you have one consolidated damages number and prorate it across the two time windows
Accrual/daily-rate style modeling: you have (or can derive) rate-like assumptions, and the tool reflects rate application rather than simple proportion-of-time

If you’re unsure: start with time-proration because it’s deterministic—same inputs → same split—making it easier to audit internally.

B. Anchor the “offer date” correctly

Brazil case timelines can make the “offer date” choice sensitive. Ensure your “offer date” matches your internal computation anchor for the start of post-offer logic.

Common anchors teams use include:

Date the offer/proposal was filed or recorded
Date your internal model treats the counterparty as effectively exposed to the offer
Date already used in your prior spreadsheet (to avoid accidental drift)

DocketMath will reflect your anchor exactly, so changing the date without updating boundary conventions typically changes outputs.

C. Decide how the tool should treat start/end boundaries

You will usually be asked to choose conventions such as:

Whether the offer date belongs to pre or post
What the end date represents (judgment date, calculation cutoff, or another cutoff in your model)

For an internal workflow, it’s best to keep a single consistent convention across BR calculations. That way, review discussions focus on assumptions—not on subtle counting differences.

D. Confirm whether you’re splitting one component or multiple

If your damages include multiple items with different timing characteristics, produce higher-quality results by:

Running separate splits per component (e.g., principal vs. costs vs. other categories), then summing outputs, or
Using a combined total only when all included components follow the same period boundaries and timing treatment in your model

This reduces the risk of embedding mismatched timing into one prorated split.

Quick comparison: setups and what changes in the outputs

Setup you choose in DocketMath	Best for	What to expect in the output
Time-proration of a total	One consolidated BR damages number	Pre/post shift with window length using day-count driven proportions
Accrual/daily-rate style modeling	You already model accrual behavior	Split reflects rate application more than simple proportional time
Multiple components split separately	Principal + other items with different timing	Each component’s split changes independently; totals add cleanly
Single combined total	All components share the same timing logic	Split stays consistent but may mask category-specific timing differences

Jurisdiction awareness (BR): how to align your model without overstepping

DocketMath can help you keep the mathematics consistent and auditable, but it can’t replace case-specific legal interpretation. The best way to keep BR outputs grounded is to treat your “offer” definition as a model input you document.

A practical documentation approach for BR work:

Write down: “Offer date used for this split = ___” (procedural or recorded date)
Track: “Boundary convention = offer date belongs to pre/post”
Track: “Day-count method = calendar days (per tool configuration)” (or whatever the tool uses in your run)

That makes it easy to answer reviewer questions like: “Why is the post-offer number higher in the calculator than in the spreadsheet?”

Next steps

Open DocketMath’s calculator
- Use this primary CTA: /tools/pre-post-offer-damages-split
Select the split basis
- Choose time-proration if you start from a consolidated BR damages total
- Choose accrual/rate style inputs if your internal model already uses accrual logic
Enter the core dates
- Start date: beginning of the damages measurement window
- Offer date: your anchor for when post-offer computation begins
- End date: your calculation cutoff (often judgment date)
Pick boundary conventions
- Decide whether the offer date is counted in pre or post
**Split the right unit(s)
- If damages include multiple components with different timing assumptions, run separate splits per component and then sum
Sanity-check the day-weighting
- Check whether the pre vs. post windows produce a result directionally consistent with your expectations (e.g., longer window → typically larger share)
Export/record assumptions for auditability
- Keep a short note in your case work:
  Offer definition + boundary convention + day-count approach used by the tool configuration

If you’re also coordinating other BR calculations, you may want to structure your workflow around your broader timeline first (so date conventions don’t drift), and then run splits.

For example, before you finalize date boundaries, you can review supporting DocketMath utilities under /tools to maintain consistency across your model’s dates and conventions:

/tools (to locate related BR calculation utilities and keep date conventions aligned)

Warning: A common source of mismatch in internal review is changing the offer date while keeping a boundary convention that still attributes the offer date to the opposite window than your earlier spreadsheet assumed.