How to calculate Statute Of Limitations in Brazil
7 min read
Published April 15, 2026 • By DocketMath Team
Quick takeaways
Run this scenario in DocketMath using the Statute Of Limitations calculator.
- Brazil’s statute of limitations (“prescrição”) is generally calculated using base prescription periods set by Brazilian statutes (commonly the Brazilian Civil Code), plus jurisdiction-aware special rules that depend on the type of claim and the timeline events in your case.
- DocketMath’s Statute of Limitations calculator (Brazil / BR) helps you compute the latest likely deadline by modeling:
- the start/triggering event date (when the claim became enforceable),
- any interruption or suspension events, and
- the base prescription period applicable to that claim category.
- Most “gotchas” come from:
- using the wrong event date,
- confusing interruption vs. suspension mechanics, or
- choosing the wrong legal category (civil/contract/consumer/labor/criminal can follow different timing rules).
- For Brazilian matters, treat this as case-management math, not legal advice. The correct deadline may depend on procedural history and the precise legal characterization of the claim.
Note: This post explains how to calculate and model prescription using DocketMath—not how to decide legal merits.
Inputs you need
Before you open DocketMath’s statute-of-limitations tool, gather the items below. The calculator can only be as reliable as the inputs you provide.
Use this intake checklist as your baseline for Statute Of Limitations work in Brazil.
- cause of action category
- accrual date
- discovery date (if applicable)
- tolling periods or pauses
- jurisdiction-specific period
If any of these inputs are uncertain, document the assumption before you run the tool.
Core inputs (almost always required)
- Jurisdiction: Brazil (BR)
- Cause of action category (pick the legal bucket that best matches your claim)
- Examples to distinguish:
- Contract / civil liability
- Property-related claims
- Tort / civil damages
- Consumer-related claims (often has special timing rules)
- Start date (the “dies a quo” in plain terms): the date the claim became enforceable—commonly when the wrongful act occurred or when the right to sue accrued.
- Base prescription period: the number of years/months corresponding to the relevant legal rule for that category.
Timeline adjustments (often the difference between “filed in time” and “too late”)
- Interruption events (dates)
- These are events that reset the running of prescription under Brazilian law.
- Common examples in practice include certain types of judicial steps (the exact effect depends on procedural posture and statutory basis).
- Suspension events (date ranges)
- These are events that pause the running of prescription temporarily due to legal or factual circumstances.
Optional but valuable inputs
- Verification date: the date you’re checking the deadline (e.g., “today is 2026-04-15”).
- Filing date: if you want to check whether a specific lawsuit or administrative step happened before the computed deadline.
How outputs change based on inputs
- Change start date → the computed deadline shifts accordingly.
- Change base period → the deadline moves by the size of the base prescription period (years vs. months can be decisive).
- Add interruption → the deadline typically moves forward because the period restarts after interruption.
- Add suspension → the deadline extends because the clock paused during suspension.
How the calculation works
DocketMath’s Statute of Limitations (BR) approach is a structured timeline model. Think in terms of clock rules:
- A base clock starts on the start date for the claim category.
- Suspensions pause the clock for specified periods.
- Interruptions reset the clock, after which it runs again (under the applicable period logic).
- The calculator produces:
- a computed end date (the “latest likely prescription date”), and
- optionally, whether a given filing date is on or before that deadline.
Step-by-step timeline model (what DocketMath computes)
Step 1: Set the base prescription end date
- Start with:
Start date + base prescription period = provisional end date
(Example structure—illustrative only)
- Start date: 2023-01-10
- Base period: 3 years
- Provisional end date: 2026-01-10
Step 2: Apply suspension periods
For each suspension date range:
- The calculator adds the suspended duration to the provisional end date (i.e., it pauses the clock).
- Example:
- Suspension: 2024-06-01 to 2024-08-31
- The clock does not run during that time, so the end date moves forward by the pause duration.
Step 3: Apply interruption events (reset logic)
For each interruption date:
- Prescription is treated as interrupted, which in a timeline model generally means:
- the running clock stops and then restarts after the interruption date (with the applicable period logic).
In practice, that often looks like:
- “clock runs until interruption,” then
- “clock restarts at interruption,” continuing to the next adjustment event, and finally
- reaching the computed end date.
Warning: Interruption and suspension are easy to mix up in case files. Suspension extends; interruption can create a more dramatic restart effect. Entering the wrong event type can change the result by months or years.
Step 4: Output comparisons
If you enter a filing date, the calculator evaluates:
- Filed on or before computed end date → “likely within time” (math outcome)
- Filed after computed end date → “likely time-barred” (math outcome)
DocketMath’s value is transparency: you can see which inputs were used and how each adjustment moved the timeline.
Common pitfalls
Below are issues that regularly produce incorrect deadlines in Brazil when computing prescription using timeline methods (including DocketMath).
- using the wrong cause-of-action period
- skipping tolling or suspension windows
- treating discovery as accrual without support
- missing choice-of-law constraints
1) Using the wrong “start date”
Many prescription mistakes come from selecting a date that isn’t the accrual moment for the claim.
Checklist:
2) Selecting the wrong legal category (base period mismatch)
Prescription periods vary by claim type. If the base period is wrong, timeline adjustments may not rescue the result.
Checklist:
3) Treating an interruption as a suspension (or vice versa)
Mechanics differ:
- Suspension → clock pauses
- Interruption → clock resets/restarts
Checklist:
4) Overlapping adjustment windows
Overlapping suspension ranges can lead to double-counting.
Checklist:
5) Not re-running after adding procedural history
Real cases evolve. Prescription outcomes can depend on what happened in the litigation timeline.
Checklist:
Pitfall: A common workflow error is computing a deadline once, then later finding a documented procedural step that interrupts or suspends running—without entering it in DocketMath and recalculating.
Sources and references
Brazil’s prescription framework is primarily anchored in the Brazilian Civil Code (Lei nº 10.406/2002), with additional special rules in other statutes depending on claim type. For modeling, you’ll need to rely on the statutory rule your workflow uses to determine:
- the base prescription period for the claim category, and
- the statutory grounds for interruption or suspension applicable to the procedural steps in question.
Because prescription rules can vary materially by legal category (and sometimes by procedural context), the most practical “source” for your calculation is the rule you used to set the base period and adjustments inside DocketMath.
If you’re building a defensible internal worksheet, you can treat DocketMath outputs as a timeline math record aligned with the legal text your team is using.
Next steps
- Open DocketMath’s Statute of Limitations calculator:
/tools/statute-of-limitations - Define the claim category and enter:
- the start date,
- the base prescription period, and
- any suspension or interruption events (with exact dates/ranges).
- Enter your filing date (if you want a “timely or not” check).
- Review the calculator’s computed end date and validate:
- whether the start date matches your accrual theory,
- whether each adjustment event is correctly typed (pause vs. reset),
- whether suspension windows overlap or are duplicated.
- Save/export the timeline so you can quickly re-run if facts or procedural history change.
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
