Spreadsheet checks before running Attorney Fee in Brazil

What the checker catches

Run this scenario in DocketMath using the Attorney Fee calculator.

DocketMath’s Brazil attorney-fee spreadsheet checker is built to prevent common “spreadsheet-driven” mistakes before you run the attorney-fee calculator for BR (Brazil) matters. Rather than treating the calculation like a black box, it checks the inputs and jurisdiction-aware rules that usually determine whether a result is conceptually consistent.

In a typical Brazil (BR) workflow, the checker focuses on these categories:

• Missing or mismatched fee components

  • Example: your sheet includes a “base claim amount” field but leaves the “attorney fee basis” blank. In that case, the calculator may apply defaults or an unintended basis, producing a misleadingly clean number.
• Wrong calculation base

  • The attorney-fee basis concept used in many Brazilian fee setups may not match other spreadsheet fields like “total judgment,” “amount in dispute,” or “paid amounts.”
  • The checker flags when your selected “fee base” doesn’t align with the way your sheet is structured, so you don’t accidentally calculate fees on the wrong reference amount.
• Unit and currency confusion

  • Common spreadsheet slips include entering BRL values while labeling them like “R$ per month,” or mixing “nominal” and “real” amounts in the same calculation path.
  • The checker verifies that numeric fields look consistent (for example: no impossible negative bases, and no obvious scaling errors that would distort the fee).
• Inconsistent dates

  • Timing can matter in fee modeling. The checker ensures required date fields are present and that the chronological order makes sense for the formula chain.
• Percentage vs. fixed fee inconsistencies

  • If your spreadsheet mixes a “% of basis” field with a “fixed” fee field, the checker warns you to confirm which mode is active.
  • This prevents silent misinterpretation (e.g., applying a percentage formula when the value you entered was meant to be a fixed amount).
• Cross-cell formula drift

  • Spreadsheet errors often come from references. If a “fee basis” source cell is updated but dependent cells still reference an old range, results can become stale or oddly stable.
  • The checker looks for suspicious dependency patterns that commonly indicate broken or outdated formula links.

Pitfall to avoid: A spreadsheet can produce a “precise-looking” attorney-fee number even when the fee basis is wrong. The goal of the checker is structural validation—checking relationships, required inputs, and jurisdiction-aware logic—not merely confirming arithmetic.

Think of this tool as a pre-flight validation step. It doesn’t replace legal judgment, and it isn’t legal advice; it’s a quality-control layer to reduce avoidable spreadsheet logic errors, rework, and confusion later.

When to run it

Run DocketMath’s attorney-fee checker in a Brazil workflow at the moments when spreadsheet mistakes are most likely to enter (or propagate) into your calculation:

• Before your first full calculation

  • As soon as you’ve populated the fee inputs—even if you’ve only filled part of the sheet.
• After any data import

  • CSV uploads, OCR extraction, or copy/pasting totals from a judgment PDF can introduce formatting issues (commas vs. decimals, date formats, missing fields).
• After you change a single “anchor” input

  • Especially: fee basis amount, percentage rate, effective/procedural date fields, and calculation mode (percent vs fixed).
• Before exporting, emailing, or sharing a result

  • Treat the checker as your final sanity check step when the computed number will be presented to others.

A simple operational rhythm:

1. Enter/confirm fee basis and rate/mode fields
2. Confirm required dates and any procedural-event timing fields
3. Run the checker
4. Re-run the calculator only if inputs are consistent (or if you intentionally override with a clear note)

What you should expect to see in outputs

The checker may change outcomes even if you didn’t manually edit the final number, by:

• Blocking calculation when required fields are blank or internally inconsistent.
• Recomputing dependent values when it detects scaling/unit mismatches.
• Highlighting specific cells/fields that drive the mismatch, so you can fix the source rather than “tuning the output.”

Use this quick checklist while reviewing results:

Try the checker

To validate your Brazil attorney-fee spreadsheet inputs, start from the tool entry point:

• Primary CTA: /tools/attorney-fee

A practical “try it” flow:

1. Open the tool

   • Go to /tools/attorney-fee.
2. **Set jurisdiction to Brazil (BR)

   • Confirm the BR rule set before importing values.
3. Populate the fee inputs first

   • Prioritize: fee basis amount, fee rate (percentage or fixed), and any required date fields for the scenario.
4. Run the checker

   • Review flagged items (missing fields, inconsistent units, conflicting calculation modes).
5. Adjust spreadsheet fields

   • Fix the flagged inputs/cells (not only the final output).
6. Re-run the checker

   • Aim for a clean pass before you trust or share the computed attorney-fee figure.
7. Proceed to calculation

   • Once inputs are consistent, the attorney-fee output is more reliable.

When testing, try two quick scenario changes to see how outputs respond:

Related reading

• Worked example: attorney fee calculations in Vermont — Worked example with real statute citations
• Attorney Fees Guide for Alaska
• Attorney Fees Guide for American Samoa