How to calculate Offer Of Judgment Analyzer in Brazil

How to calculate Offer Of Judgment Analyzer in Brazil

8 min read

Published February 27, 2026 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Quick takeaways

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

  • DocketMath’s “Offer Of Judgment Analyzer” for Brazil (BR) helps you model outcomes tied to an offer of settlement and the downstream costs/fee consequences that can follow in civil litigation.
  • Your result is only as good as your inputs—especially the offered amount, the claim/expected judgment amount you’re comparing against, and any timing parameters your case strategy uses.
  • Brazil’s key moving parts for this workflow typically include:
    • Whether the offer is within the scope of the rules that can trigger costs/fees consequences.
    • The comparison basis (e.g., how the final judgment amount relates to the offer).
    • The impact of updates/interest/monetary correction on the comparison.
  • Use the tool to generate a scenario table (e.g., offer at 20%, 50%, 80% of claimed/expected value) rather than relying on a single number.

Note: This guide explains how to run and interpret DocketMath’s calculator for Brazil. It’s not legal advice, and it can’t replace a jurisdiction-specific review of your exact procedural posture.

Inputs you need

Before you run DocketMath’s Offer Of Judgment Analyzer for Brazil via /tools/offer-of-judgment-analyzer, collect the inputs you’ll feed into the calculator. For Brazil workflows, you’ll typically want the following.

Use this intake checklist as your baseline for Offer Of Judgment Analyzer work in Brazil.

  • jurisdiction selection
  • key dates and triggering events
  • amounts or rates
  • any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

Case and financial inputs

  • Claim amount (baseline): the amount used to compare the offer against what the court ultimately grants (or the closest proxy you have, such as the complaint value).
  • Offered amount: the settlement amount you propose in the offer of judgment.
  • Monetary update / correction approach:
    • Whether you want the comparison to use nominal values or updated values.
    • If updated, the update method and/or a date range you want to apply inside your model (even if you approximate).
  • Costs/fees assumptions (optional but recommended):
    • Your model’s assumption for court costs (custas) and attorney fees (honorários sucumbenciais) if you want a more realistic “net” estimate.
    • If you exclude these, the analyzer will focus primarily on the offer-vs-judgment comparison logic.

Timing and procedural context (jurisdiction-aware)

Because Brazilian consequences often turn on whether and when the offer is made, DocketMath’s Brazil ruleset may ask for one or more timing inputs such as:

  • Offer timing relative to key milestones (e.g., after a particular procedural event).
  • Type/format of offer: if the tool supports selectable options, match them to the procedure you’re modeling.

Quick input checklist

How the calculation works

DocketMath’s Offer Of Judgment Analyzer for Brazil (BR) is designed to model the practical impact of a settlement offer by translating your inputs into comparison outcomes and scenario results.

DocketMath applies the Brazil rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.

Step 1: Convert your numbers into a “comparison basis”

The analyzer’s first move is to establish the basis for comparing:

  • If you select nominal comparison, the tool compares:
    • Offered amount vs. judgment (or expected judgment) amount using raw figures.
  • If you select updated comparison, the tool compares:
    • Updated offered amount vs. updated judgment amount

Why it matters: monetary correction and interest can change the effective offer ratio, which can move the result across thresholds that affect the tool’s cost/fee consequence branch.

How this changes outputs:
Even if your offered amount “looks close” to the claim, the updated comparison can shift the ratio up or down enough to change which consequence path the analyzer chooses.

Step 2: Determine the comparison ratio (offer as a percentage)

Once the comparison basis is set, the tool calculates:

  • Offer ratio = Offered Amount / Expected Judgment Amount

Practical modeling patterns:

  • High offer ratio scenarios (e.g., 80–100%): more likely to align with favorable comparisons.
  • Low offer ratio scenarios (e.g., 20–40%): more likely to trigger unfavorable cost/fee outcomes if the final judgment matches or exceeds the offer.

Step 3: Apply Brazil’s jurisdiction-aware decision logic

DocketMath then applies a Brazil-specific ruleset that maps the comparison outcome and timing context into consequences. Conceptually, it works like this:

  1. Eligibility check
    The tool checks whether your inputs satisfy the procedural conditions that typically activate consequences (for example, timing relative to procedural milestones).
  2. Outcome mapping
    The tool compares the offer vs. the expected/assessed judgment amount according to the logic implied by the ruleset you selected or that the Brazil configuration assumes.
  3. Consequence estimate
    If eligible and if the comparison meets the rule’s criteria, the analyzer estimates impacts on:
    • Costs
    • Attorney’s fees (depending on how you configured the calculator inputs)

Common pitfall: entering an offer amount on a different update basis than the expected judgment baseline. A nominally generous offer can become effectively smaller after correction, changing which branch the tool selects.

Step 4: Produce scenario results (and a net estimate, if enabled)

Finally, DocketMath outputs results that typically include:

  • Whether the modeled offer comparison triggers the more favorable branch
  • Estimated consequence magnitude (sometimes shown as ranges or deltas depending on what you enabled)
  • A scenario breakdown so you can see how changing a single variable shifts your outcome

Practical workflow:
Run a small scenario set (usually 3–5 scenarios) such as:

  • Offer at 25%, 50%, and 75% of the expected judgment value
  • Keep everything else constant
  • Identify which scenario(s) flip the analyzer’s branch

Step 5: Interpret results as “decision support,” not certainty

Even a well-fed model can diverge from real outcomes because:

  • Courts decide amounts based on evidence and legal classification.
  • Timing and procedural compliance can affect eligibility.
  • Costs/fees depend on what the court actually determines in your case.

Still, the analyzer is useful for identifying where your case model is “knife-edge” versus robust.

Common pitfalls

Use these checks to avoid analysis errors when you calculate with DocketMath for Brazil.

  1. Mixing updated and nominal values

    • If you model an updated offer but compare it to an un-updated judgment baseline, the offer ratio can be distorted.
  2. Using the wrong baseline for “expected judgment”

    • If you use complaint value while the real assessed amount is likely much lower or higher, the offer ratio can mislead you about consequences.
  3. Ignoring timing inputs

    • If the analyzer’s BR logic branches by procedural timing and you leave timing blank (or approximate too loosely), the tool may apply the wrong eligibility path.
  4. Forgetting attorney fees/cost configuration

    • If you enable fees/costs estimation, confirm your assumptions reflect your case strategy; otherwise you may overstate or understate the net impact.
  5. Optimizing around a single number

    • Offer strategy modeling benefits from a scenario table, because outcomes can flip at certain comparison bands.

Warning: Don’t treat the tool’s branch selection as a substitute for confirming the offer’s procedural compliance (form, timing, and record). The analyzer assumes your inputs accurately represent what was filed and when.

Sources and references

This article focuses on how to use DocketMath’s Offer Of Judgment Analyzer for Brazil (BR). The substantive legal triggers and timing mechanics behind costs/fees consequences tied to settlement offers can depend on the current Brazilian procedural framework and any updated interpretations.

  • Brazilian Civil Procedure Code (Código de Processo Civil / CPC): provisions relating to offers of settlement and allocation of litigation costs/fees
  • General rules for monetary correction and interest affecting amounts used for comparison (as applied in civil claims)

Because your specific scenario may depend on your procedural posture and the type of offer modeled, you should cross-check details against the CPC provisions that match your case type and the precise procedural moment you’re modeling.

Next steps

  1. Open DocketMath’s calculator: /tools/offer-of-judgment-analyzer
  2. Enter your Brazil inputs:
    • Claim/expected judgment baseline
    • Offered amount
    • Update method (nominal vs updated) and any correction parameters
    • Timing/eligibility details (if prompted)
    • Fees/costs settings (optional)
  3. Run at least these scenarios:
  4. Compare results:
    • Identify the offer ratio that flips the analyzer’s branch
    • Note the offer amount that produces the best modeled net effect under your assumptions
  5. Re-run after updates:
    • Your expected judgment baseline changes
    • Your correction dates/method change
    • Your timing assumptions change

If you want a shortcut, keep most variables constant and change only the offered amount first—this reveals how sensitive the outcome is to offer size.

Related reading