Why Statute Of Limitations results differ in Brazil

The top 5 reasons results differ

When DocketMath shows different statute-of-limitations outcomes in Brazil, the variation is usually driven by inputs—especially which claim clock rule and which starting/trigger assumptions you selected.

In Brazil, a common baseline is the Civil Code’s general prescriptive period: 10 years under Código Civil (Lei nº 10.406/2002), Art. 205. From there, results can change because DocketMath applies a jurisdiction-aware mapping from your claim type to the relevant limitation period, and it may also apply tolling based on your inputs (including the absolutely_incapable flag).

Here are the five most common causes of mismatched results:

1. Category mismatch (claim type → limitation period)

   • If your facts align with a specific claim category, but the calculator is fed general instead, you’ll often see 10 years when you expected a shorter category period.
   • Common Brazil category periods you may see in inputs:

     • General: 10 years
     • Alimony: 2 years
     • Guardianship accounting: 4 years
     • Tort: 3 years
     • Rent: 3 years
     • Innkeeper/food supplier: 1 year
     • Insurance vs. insurer: 1 year
   • Practical takeaway: category selection is frequently the biggest difference-maker after the start date.

2. Accrual / “start” date anchoring

   • Even with the correct category, outputs can differ if the “start of prescription” (the calculator’s anchor date/trigger) is not the same between runs.
   • If you compare two scenarios, confirm you’re using the same accrual/start assumptions in both.

3. General rule used as a default (not a universal override)

   • Many people expect the “general” period to always win.
   • In DocketMath’s Brazil logic, the 10-year general outcome is most likely when the claim doesn’t map cleanly into one of the narrower category buckets in your inputs.

4. Tolling / suspension assumptions: “absolutely_incapable”

   • Your verified facts packet includes:

     • tolling_rules.absolutely_incapable: true
   • Turning this on (or off) can materially extend the computed period, even when the underlying base category period (e.g., 2, 3, 4, 5, or 10 years) remains the same.

5. Instrument-specific classification (document/instrument type)

   • If your dispute involves a debt tied to an instrument/document, classification matters.
   • The packet’s instrument-related periods include:

     • Liquid debt written in instrument: 5 years
     • Negotiable instrument: 3 years
   • A small labeling difference can therefore explain why two outputs don’t match.

Pitfall to watch: the same fact pattern can yield different results simply because one run used a specific category (like “tort”) and another used general, or because the tolling/anchor assumptions differed.

How to isolate the variable

Use DocketMath like a controlled experiment: change one input at a time and log how the output moves.

1. Sanity-check the baseline

   • If your output isn’t 10 years, it likely means the calculator is applying a non-general category bucket or a tolling/suspension input.

2. Run “General” vs the category you believe matches

   • Pass the claim as general (10 years).
   • Then rerun using the closest matching bucket from your claim inputs (e.g., tort = 3, rent = 3, alimony = 2, guardianship accounting = 4, innkeeper/food supplier = 1).
   • If the output “snaps” from 10 to 2/3/4/1, category mapping is your cause.

3. Confirm tolling is consistent

   • Your packet sets absolutely_incapable to true.
   • If you’re comparing two results, ensure you didn’t unintentionally change this flag between runs.

4. Lock the same start/anchor assumption

   • Prescription timing is extremely sensitive to the anchor/trigger you provide.
   • When comparing runs, verify the same “start event” logic is being used in both.

5. If it’s a document/instrument dispute, normalize instrument labels

   • Keep the instrument type consistent:

     • liquid debt written in instrument (5 years) vs negotiable instrument (3 years)

For repeatable runs, use the DocketMath tool here: /tools/statute-of-limitations

Next steps

1. Choose one claim bucket to represent the facts (e.g., “tort” vs “general”) and rerun.
2. Align the start/anchor input so both runs use the same prescriptive commencement assumption.
3. Verify tolling settings—especially absolutely_incapable: true—are the same in every comparison.
4. Document your run settings (category, start date/trigger, and tolling toggle) so you can explain why one output differs from another without guessing.
5. Use the 10-year general outcome as a sanity check (Art. 205) when you’re unsure whether you’re accidentally getting routed into a narrower bucket.

Gentle note: This is diagnostic guidance for using the calculator consistently, not legal advice.

Related reading

• Statute of limitations in United States (Federal): how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Why statute of limitations results differ in United States (Federal) — Troubleshooting when results differ
• Statute of limitations reference snapshot for United States (Federal) — Rule summary with authoritative citations