Worked example: Deadline in Brazil

6 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Example inputs

Below is a worked example of how to calculate a Brazilian deadline using DocketMath with jurisdiction-aware rules (jurisdiction code BR). This example focuses on a common deadline pattern: computing a deadline based on an event date, with automatic treatment of weekends and Brazilian business-day conventions.

Note: This walkthrough shows how the calculator behaves in a typical scenario. It’s not legal advice, and it won’t replace rules that may be case-specific (for example, special statutory time limits, court orders, or suspension periods).

Scenario (worked example)

You need to determine the last day to file a document. The “trigger” date is when something occurs (for example, receipt of notice, publication, or another procedural event). For this example:

Jurisdiction: Brazil (BR)
Event date (trigger date): 2026-04-10 (Friday)
Time period: 10 business days
Time zone: local time (no conversion in this example)
Calendar assumptions:
- The deadline is computed in business days
- Weekends are excluded automatically

Why these inputs matter

In a deadline calculator, these fields drive almost everything:

Event date determines the starting point for counting.
Number of business days determines the “distance” to the deadline.
Jurisdiction (BR) tells DocketMath which calendar logic to apply.

To be concrete, here are the inputs you’d enter before running the calculation:

Input	Value	What it changes in the output
Jurisdiction	BR	Selects Brazil-specific deadline rules/calendars
Trigger date	2026-04-10	Sets the first day for counting logic
Period type	Business days	Controls weekend/holiday handling
Amount	10	Determines how many business days to add
Start/Include behavior	Uses DocketMath’s default for “trigger date + period”	Avoids manual off-by-one errors

If your workflow uses a different period type (e.g., calendar days) or a different trigger (e.g., publication vs. receipt), the result will shift accordingly when you run DocketMath.

Example run

Run the deadline calculation in DocketMath using the calculator tool at:

Primary CTA: /tools/deadline

Run the Deadline 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 1 — Configure the calculation

In the deadline calculator:

Choose Jurisdiction: BR
Set Trigger date to 2026-04-10
Choose Period: Business days
Set Number of days: 10

Step 2 — Observe the computed deadline

When DocketMath applies the Brazil/business-day counting logic, it will count 10 business days from the trigger date according to its built-in convention for deadline computation.

Because 2026-04-10 is a Friday, the business-day increments look like this (weekends skipped):

Fri 2026-04-10 (Day 1)
Mon 2026-04-13 (Day 2)
Tue 2026-04-14 (Day 3)
Wed 2026-04-15 (Day 4)
Thu 2026-04-16 (Day 5)
Fri 2026-04-17 (Day 6)
Mon 2026-04-20 (Day 7)
Tue 2026-04-21 (Day 8)
Wed 2026-04-22 (Day 9)
Thu 2026-04-23 (Day 10)

✅ Computed deadline (end of period): 2026-04-23

In practice, “last day” may be treated as end-of-day in your jurisdictional workflow. DocketMath typically returns the date you should target operationally.

Step 3 — Turn the date into an action plan

A practical way to use the output is to generate tasks backwards from the deadline. For example, with a 2026-04-23 deadline:

T-2 business days: final internal review / document upload preparation
T-1 business day: formatting, attachments, and confirmation of submission readiness
Deadline day: last-mile filing and system confirmation

That means you’d typically focus around:

Deadline-eve: 2026-04-22 (Wednesday)
Backstop / readiness: 2026-04-21 (Tuesday)

Pitfall: Manual counting with calendar days instead of business days is a common source of off-by-two-to-three-day errors—especially when the trigger date falls near a weekend. Using the correct period type in DocketMath is the guardrail.

Sensitivity check

Small changes in inputs can materially change the computed deadline. Use this section to sanity-check your assumptions before you rely on the result.

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 A: Change the period type (business days vs. calendar days)

Keep the same trigger date: 2026-04-10, but switch the period:

Scenario A1: 10 business days → 2026-04-23 (matches the main example)
Scenario A2: 10 calendar days → deadline lands earlier/later because weekends are counted

Quick calendar-day sketch (counting calendar days):

Day 1: 2026-04-10
Day 2: 2026-04-11
Day 3: 2026-04-12
Day 4: 2026-04-13
Day 5: 2026-04-14
Day 6: 2026-04-15
Day 7: 2026-04-16
Day 8: 2026-04-17
Day 9: 2026-04-18
Day 10: 2026-04-19

So under a “calendar day” model, you’d land on 2026-04-19.

Takeaway: if your procedure uses “dias úteis” (business days) vs “dias corridos” (calendar days), the deadline will not match.

Sensitivity B: Move the trigger date by 1 day

Try a nearby trigger date to see weekend effects:

New trigger: 2026-04-11 (Saturday)
Period: 10 business days

Because Saturday isn’t a business day, the effective counting start is typically pushed to the next business day. Under that effect, you’ll generally see the deadline move later versus a Friday trigger.

Operational implication: if your trigger date might be “received on” versus “published on,” it can be worth running both versions and aligning to the procedural definition used in your filing context.

Sensitivity C: Switch jurisdiction code (BR → other)

If you reuse a similar workflow across matters, change jurisdiction and watch how the deadline output behaves.

Same trigger date and business-day count
Different jurisdiction may have different business-day conventions or holiday calendars

Warning: Even within Brazil, some deadlines can be affected by court systems, local judicial calendars, or suspension regimes. DocketMath helps with baseline date logic; it doesn’t override case-specific directives or matter instructions.

Sensitivity summary table

Here’s a compact view of what changes what for this example:

Change	From → To	Likely effect on deadline
Period type	Business days → Calendar days	Deadline often changes substantially because weekends count
Trigger date	Friday → Saturday	Deadline typically moves later due to weekend exclusion
Jurisdiction	BR → other	Output can shift because calendar rules differ

If you want the exact computed dates, rerun the tool for each scenario—this section is meant to validate your setup before committing to a filing schedule.