Why Statute Of Limitations results differ in Brazil

The top 5 reasons results differ

When DocketMath’s statute-of-limitations calculator produces different outcomes for “the same” claim in Brazil (BR), the gap usually comes from jurisdiction-aware inputs and how Brazilian timing rules get applied to each step of the case. Because limitation periods can depend on what you’re suing for and when key procedural facts occurred, small data differences can flip results.

Here are the five most common reasons:

1. **Different event dates are being used (the trigger isn’t one-size-fits-all)

   • Brazilian limitation analysis typically hinges on the date of accrual (when the claim became actionable), not the date of signing, sending, or filing.
   • If one run uses “contract date” while another uses “default date,” the output can change dramatically.

2. Claim classification changes the limitation period

   • The calculator needs a cause/claim type that maps to the relevant limitation window.
   • Misclassifying a claim is a common reason for conflicting numbers—especially where facts overlap (for example, damages tied to contractual performance that could be argued under different legal characterizations).

3. Interruption vs. suspension logic is being applied differently

   • Brazil recognizes distinct timing effects from interruption (often resetting) and suspension (often pausing) depending on the event.
   • If your dataset includes a “procedural milestone,” one scenario may treat it as interruption in one run and suspension in another, changing the remaining time.

4. Procedural milestones are missing or inconsistently recorded

   • Even when the claim type is correct, limitations results can differ if key events are absent (or recorded under the wrong field).
   • Data hygiene matters: one record might include a documented act that affects timing; another might only include a filing date or an update date.

5. Time zone / date precision issues

   • Brazilian calculations can be sensitive to exact dates.
   • Mixing “YYYY-MM-DD” with timestamps, or converting local time to UTC inconsistently, can create off-by-one-day (or larger) shifts—enough to move a case across a boundary when the calculator outputs day-based remaining time.

How to isolate the variable

Treat this like a debugging exercise: lock everything down except one input, then rerun DocketMath. The goal is to find which field (or assumption) is causing the output to flip.

Use this checklist:

A practical approach:

1. Run DocketMath once with Dataset A.
2. Run it again with Dataset B.
3. Then change only one of these at a time:

   • trigger/accrual date basis
   • claim type
   • interruption/suspension event date(s)
   • date precision/format handling

Once the output flips, the last change you made is your variable. If nothing flips after you try the obvious fields, the issue may be coming from a less visible assumption in your input mapping—like how milestones are categorized or which “event date” your pipeline feeds into the calculator.

If you want to reproduce the math quickly, start with the DocketMath tool via: /tools/statute-of-limitations .

Next steps

After isolating the variable, shift from “why it differs” to “how to prevent it next time”:

• Document your input definitions

  • Create a one-page “timing glossary” for your team:

    • Trigger/accrual basis (what exact date counts as accrual?)
    • What counts as an interruption-affecting milestone
    • What counts as a suspension-affecting milestone
• Standardize data collection

  • Require date-only fields for limitation-sensitive timestamps.
  • Require explicit event date fields for each procedural milestone, rather than reusing filing/update dates.
• Add a validation step before running DocketMath

  • Check that the claim type matches the facts you recorded.
  • Confirm milestone dates are present and not contradictory (e.g., a suspension event entered without its corresponding trigger context).
• Re-run with corrected inputs

  • Keep a before/after log of the DocketMath outputs so you can explain what changed during internal review.

Gentle disclaimer: this is about diagnosing why calculator outputs differ and improving input quality. It doesn’t substitute for legal advice or a case-specific legal assessment.

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator