Worked example: Treble Damages in Brazil

Example inputs

This worked example shows how DocketMath applies a treble-damages style calculation for Brazil (BR) using jurisdiction-aware rules. The goal is to illustrate the mechanics—what inputs matter, how they flow through the calculator, and which assumptions most affect the output.

Scenario

A company (“Claimant”) sues a supplier (“Defendant”) in Brazil for a monetary loss tied to a breach of contract. Under the legal theory used in this example, the damages are treated as multipliable (i.e., a base amount becomes a multiple).

To keep the example focused on the treble-damages workflow, we model:

• Base damages (principal loss): computed damages before any multiplier
• Trebling factor: 3× (treble)
• Cap/adjustment logic: none in this illustration (so you can see the pure treble effect)

Inputs used in DocketMath (Brazil / BR)

These are the values we set so DocketMath performs a straightforward “treble-only” run:

• jurisdiction: BR (Brazil)
• baseDamages: R$ 150,000
• multiplier: 3
• includeInterest: false (keeps output centered on trebling)
• interestRateAnnual: not used (because includeInterest = false)
• interestStartDate: not used (because includeInterest = false)
• capEnabled: false
• capAmount: not used (because capEnabled = false)

For traceability, here’s the “math structure” we’re exercising:

How to interpret baseDamages in this example

In DocketMath treble-damages mode, baseDamages is the starting number that gets multiplied. If your case includes other components (e.g., contractual penalties, reimbursable expenses, or legally mandated additions), those components may need separate modeling rather than being folded into the base number—otherwise you can double-count.

Example run

You can run this scenario via the primary CTA: Run treble damages in Brazil.

Run the Treble Damages 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-by-step calculation (as modeled)

With baseDamages = R$150,000 and multiplier = 3, the treble-damages output is:

1. Treble multiplier application

   • R$150,000 × 3 = R$450,000

2. No interest / no cap adjustments

   • includeInterest = false → R$450,000 remains unchanged
   • capEnabled = false → no ceiling is applied

Output summary

DocketMath should display (or allow you to export) results that look like this:

What you should watch during the run

Even though this example is simple, jurisdiction-aware calculators usually have hidden decision points. In DocketMath’s treble-damages flow for BR, the most meaningful “behavioral” toggles for this example are:

• Multiplier source and enforcement

  • Here, we set multiplier = 3 explicitly.
  • If you change multiplier, the result moves linearly (see next section).

• Adjustment modules

  • Interest and caps are common adjustment modules.
  • By setting includeInterest = false and capEnabled = false, we isolate the trebling behavior.

Quick sanity check

A treble calculation should always satisfy:

• If baseDamages increases by R$10,000, the total should increase by R$30,000 (because of 3×).

This invariant is a useful validation while you’re entering inputs.

Sensitivity check

Now we test how the treble total changes when you adjust key inputs. This is where DocketMath is especially helpful: you can stress-test results quickly, instead of recalculating manually each time.

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 to baseDamages

Keep multiplier fixed at 3 and vary the base:

Rule of thumb:

• trebleDamagesTotal = baseDamages × 3
• so a change of Δ in baseDamages produces a change of 3Δ in total.

Sensitivity to multiplier

Hold baseDamages constant at R$150,000 and vary multiplier:

This makes the multiplier the biggest “lever” after baseDamages. In practice, the multiplier can depend on the legal characterization and which element of the claim is being trebled—so align your DocketMath inputs with the theory you are modeling.

Sensitivity to caps (if you enable them)

In this example run, capEnabled = false. If you turn caps on later, your total may stop increasing even when baseDamages rises.

Here’s a hypothetical cap illustration (not enabled in the main example):

• capAmount = R$500,000
• baseDamages = R$200,000 → raw treble = R$600,000 → capped = R$500,000

Sensitivity to interest inclusion

We left includeInterest = false to keep the demonstration clean. Once you enable interest, outcomes typically become sensitive to:

• interestStartDate (when the timer begins)
• interestRateAnnual (rate)
• whether the calculator uses simple vs. compound interest (depending on implementation)

If you enable interest and then reuse a baseDamages number that already includes interest, you may create a mismatch between what you intend to treble and what you intend to add separately.

Practical checklist for running sensitivity tests:

Related reading

• Treble Damages Calculator Guide for Alabama
• Treble Damages Calculator Guide for Arizona
• Treble Damages Calculator Guide for Colorado