How to run Deadline in DocketMath for Brazil

Step-by-step

Run this scenario in DocketMath using the Deadline calculator.

Here’s a practical walkthrough for running Deadline in DocketMath for Brazil (BR). The goal is to calculate timeframes accurately using jurisdiction-aware rules, then turn the result into something you can use in your case workflow.

1) Open the Deadline calculator

1. Go to /tools/deadline
2. Confirm you’re in the Deadline calculator view.

2) Set the jurisdiction to Brazil

1. Find the Jurisdiction selector.
2. Select Brazil (BR).

Why this matters: Brazil has its own procedural timing concepts. DocketMath uses the jurisdiction setting to apply the correct rule set for the calculation.

3) Choose the deadline “type” (the triggering event)

DocketMath’s Deadline calculator typically requires the deadline trigger—the event date/time from which counting begins—and then the deadline length.

Use the Deadline workflow like this:

• Trigger date/time: the date/time of the procedural event that starts the clock (for example, service/notification, filing date, publication date, or another “clock start” date—use whatever your rule specifies)
• Deadline length: the number of days or time period in the instruction (for example, “15 days”)
• Counting mode: if offered, select the mode that matches the rule you’re applying (commonly calendar days vs business days)

If you’re unsure which mode applies, use your underlying document to make the best identification (e.g., from order text, rule citations, or a timing schedule), and validate against your internal checklist.

4) Enter the start date precisely

Deadlines are sensitive to time granularity. When DocketMath prompts for:

• Date only: enter the exact calendar date shown in your record.
• Date & time: enter the time shown in your docket entry (or the time your organization records).
• Time zone: make sure it matches how events were logged in your system.

Tip: If your internal system stores events in UTC but your court docket effectively reflects local time, you can see off-by-one-day differences near midnight. If the result looks unexpectedly early/late, re-check time zone handling first.

5) Enter the deadline duration

Provide the duration fields:

• Days/weeks/months (whatever the calculator supports)
• Any extension/adjustment inputs if the tool exposes them

When you change the duration, DocketMath recalculates:

• the computed due date
• and, when available, intermediate markers such as count start / count end

6) Decide whether to account for non-working days

Depending on the procedural context, Brazilian deadlines may require excluding weekends and/or holidays.

If DocketMath offers options such as:

• exclude weekends
• exclude holidays
• use jurisdictional non-working day rules

choose the option that matches your rule set. When a holiday list or calendar selection exists, pick the one your team uses consistently.

Common error: counting “calendar days” when the procedural rule intends “business days.” That single choice can shift a due date by multiple days, especially across weekends and public holidays.

7) Review the output and capture it

After running the calculation, review the result fields to ensure they match what you intended to count.

Look for fields such as:

• Deadline due date
• Days counted
• Start date used for counting
• Rule mode (e.g., calendar vs business handling)
• possibly a breakdown of the effective counting window

Then copy the due date into your docket workflow and record the parameters you used (jurisdiction, trigger, duration, counting mode). This helps preserve auditability and makes future review easier.

8) Run “what-if” scenarios for confirmation

Even with jurisdiction-aware rules, it’s smart to sanity-check results by running close variants that commonly occur in practice:

• Shift the start date by 1 day (for cases where service is recorded on one date but deemed on another)
• If allowed by your documents, compare calendar vs business day counting
• Change duration (for example, “10 days” vs “15 days”) if multiple instructions could apply

DocketMath’s fast recalculation makes these comparisons practical. Use the variant that best matches the controlling instruction and your documented interpretation.

Common pitfalls

Use this checklist to avoid the issues that most often break deadline calculations in Brazil.

• counting from the wrong triggering event
• ignoring court-closed days or holiday rules
• mixing calendar days with court days
• missing time-of-day cutoffs for filing

Checklist: deadline calculation integrity

Common failure patterns

1. Off-by-one-day due to trigger timing

   • An incorrect time zone or entry time can shift the effective start into the next day.

2. Wrong counting methodology

   • Discrepancies are often about how days are counted (calendar vs business), not the arithmetic.

3. Holiday handling mismatches

   • If DocketMath offers an option to exclude holidays and it’s left off (or the wrong calendar is selected), the due date can land on a non-working day.

4. Confusing filing date with deemed service/notification date

   • For many triggers, the clock start may be a deemed date rather than the actual filing/receipt date. Your instruction text should clarify which date starts the count.

Try it

1. Open the calculator: /tools/deadline
2. Set **Jurisdiction = Brazil (BR)
3. Enter:

   • Trigger date (the procedural event date)
   • Deadline duration (e.g., 15 days)
   • Ensure counting mode and non-working day/holiday settings match your rule
4. Click Calculate
5. Confirm:

   • the due date looks reasonable around weekends/holidays
   • the tool’s start date aligns with the event you intended to count from

If you want a quick validation approach, run two calculations:

• Variant A: counting mode as you believe the rule uses
• Variant B: swap calendar vs business counting (only if your rule interpretation genuinely permits either method)

If the due date changes only slightly (e.g., 0–1 days), your trigger and counting method are likely consistent. If it changes by multiple days, pause and re-check the trigger definition and counting settings before using the due date.

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations