Choosing the right Attorney Fee tool for Brazil

6 min read

Published April 15, 2026 • By DocketMath Team

Choose the right tool

Run this scenario in DocketMath using the Attorney Fee calculator.

Choosing the right DocketMath Attorney Fee tool for Brazil (BR) is mostly about making sure your inputs match the fee model you’re actually dealing with. Brazilian fee workflows often mix court-ordered fees, settlement-driven fees, and contract provisions—so the “right” setup is the one that mirrors your scenario, not just the one that looks closest on the surface.

This guide focuses on choosing the correct setup for the Attorney Fee calculator in DocketMath, using jurisdiction-aware rules for Brazil (BR) and showing you how the outputs shift as you change inputs.

Note: This article explains how to use DocketMath for estimation and workflow planning. It does not replace advice from a qualified Brazilian legal professional for any specific case.

1) Start with the fee scenario (your “model”)

Before you touch the calculator, decide which fee model your matter fits. In practice, attorneys in Brazil commonly encounter these patterns:

  • Court-ordered attorney fees (often tied to case outcomes and procedural stages)
  • Contractual attorney fees (agreed in a fee instrument between client and attorney)
  • Settlement-related fees (terms negotiated in the settlement, sometimes including attorney fees)

In DocketMath, the Attorney Fee tool is most useful when you select the scenario that aligns with the inputs you can reliably provide—typically the fee base and the rate or calculation rule (percentage vs. fixed, or other options available in the tool UI).

2) Confirm what the tool needs from you (inputs that drive the result)

When you use the /tools/attorney-fee workflow for Brazil, you’ll typically be asked for fields that determine how the fee is computed, such as:

  • Fee type / calculation method (percentage vs. fixed, or similar modeling choices in the tool UI)
  • Fee base (the monetary value the attorney fee is computed from, such as a claim amount or recovery amount)
  • Rate / multiplier (if modeled as a percentage or stepped rate)
  • Adjustments by scenario (for example, options that align with procedural posture or negotiated terms, depending on the tool)

Because you’re in Brazil (BR), treat these inputs as part of a jurisdiction-aware configuration step. Your output will change drastically if you:

  • use the wrong base (claim amount vs. recovery amount),
  • apply a rate meant for a different fee model, or
  • enter a calculation method that doesn’t match how the fee is expected to be determined in your scenario.

3) Use a fast “input-quality checklist” before running the calculator

To avoid meaningless numbers, confirm your inputs meet a basic quality threshold:

If you can’t confirm one of these items, you can still run the calculator—but interpret the output as a planning sensitivity range, not as a close estimate of final fees.

4) How outputs change in Brazil (BR) when inputs change

Here’s what typically drives the Attorney Fee estimate in a tool like DocketMath:

Input you changeWhat usually happens to the outputPractical example (illustrative)
Fee base increasesTotal estimated fees increase proportionally (for % methods)Base 100,000 at 10% → fee 10,000
Rate increasesFees increase proportionally (for % methods)10% → 15% increases the fee by 50%
You switch calculation methodOutput may jump or fall sharplySwitching % of base to fixed fee changes scaling
You swap claim base vs. settlement baseOutput changes because the reference number changesClaim 200,000 vs. settlement 120,000 materially alters % results

To keep your workflow tight, use an iterative “what-if” approach:

  1. Run once with the best-known numbers.
  2. Change one input at a time (base or rate).
  3. Note how the output moves.

This produces a practical planning range for client updates and internal budgeting—without treating the result as a definitive determination.

5) Use the DocketMath Attorney Fee tool with the right workflow entry point

DocketMath provides a targeted calculator entry point for the attorney-fee workflow. Your selection is less about “which tool name” and more about aligning the tool’s inputs to your computation path.

  • If you primarily need a % of a known monetary base, configure the tool for that method and feed the correct base.
  • If you’re modeling settlement-style outcomes, use the settlement figure as your base where it fits your scenario.
  • If you’re modeling contract-driven fees, align the inputs to the contract’s computation rule (again: estimate planning, not an official ruling).

If you want to start immediately, use the primary CTA:

  • /tools/attorney-fee

Next steps

Once you’ve selected the right configuration approach for Brazil (BR), you can turn the calculator into a repeatable process for your team.

After you run the Attorney Fee calculation, capture the inputs and output in the matter record. You can start directly in DocketMath: Open the calculator.

Step 1: Decide which number set you’re estimating from

Pick one anchor set for the first run:

  • Claim anchor: best when the fee base is tied to the original claim valuation.
  • Recovery anchor: best when the fee is tied to actual recovery or awarded amounts.
  • Settlement anchor: best when fees are computed from settlement terms.

Run DocketMath once and save the estimate as a matter-file planning note.

Step 2: Run two scenarios to bracket uncertainty

Fee outcomes often hinge on procedural and negotiation variables. A practical bracket is:

  • Scenario A (conservative): use the lowest plausible fee base for your file.
  • Scenario B (most likely): use the best-known fee base.

Then compare outputs. The difference helps you explain how much risk is tied to base choice.

Step 3: Validate units and formatting before exporting

The most common mistakes are arithmetic and formatting issues:

If DocketMath shows a breakdown (e.g., fee base, rate, computed fee), use it to sanity-check quickly.

Step 4: Store the logic so future revisions are faster

After your first run, capture the assumptions so you can update quickly later. A minimal record to keep:

  • Fee model used (percentage/fixed/other option shown in the tool UI)
  • Fee base chosen (claim, recovery, or settlement)
  • Rate applied (exact numeric value)
  • Output estimate and generation date

If your workflow includes other case metrics, you can also cross-check planning context in related DocketMath tools (for example):

  • /tools/case-timeline

Step 5: If inputs are incomplete, use DocketMath for sensitivity—not certainty

When a key input isn’t finalized (e.g., the fee base isn’t known yet), avoid forcing one definitive number. Instead:

  • Run using a reasonable base estimate.
  • Adjust the base by ±10–25% and observe output changes.
  • Use that bracket for planning and confirm the base later.

Warning: Avoid treating an attorney-fee calculator output as a binding legal determination. In Brazilian matters, final fees can depend on case outcome, procedural posture, and how the relevant fee rule is applied to the facts.

Related reading