Inputs you need for Deadline in Brazil

Inputs you will need

Run this scenario in DocketMath using the Deadline calculator.

To run Deadline in Brazil (BR) in DocketMath, gather the inputs below. These are the data points that typically control the countdown: the event/trigger date, the deadline type (what kind of “prazo” it is), and any jurisdiction-aware rules the tool applies for Brazil.

Use this checklist to confirm you have what you need before you click /tools/deadline.

Input checklist (Brazil)

• Examples you’ll choose from in the tool: filing a document, response period, appeal deadline, or another “from event date” deadline.

  • Usually the date of notice, publication, or service that begins the deadline.
  • Set the tool to Brazil (BR) so the calculator uses Brazil-specific logic.
  • Some deadline categories differ by procedural context (e.g., civil vs. labor, federal vs. state), and DocketMath may request a selector.
  • Check whether your case has a known suspension or special regime that the tool can account for (for example, periods the court recognizes as non-countable, depending on the selected category).
  • Ensure the calculator uses the correct local date interpretation so you don’t shift by a day.
  • Some categories need extra inputs to match the correct procedural rule set (e.g., whether the deadline is for a specific filing).
  • If you don’t have the exact service/notice date, the tool can only calculate from the date you enter—so pick the source of truth you have.

Note / disclaimer: This tool-based guidance is informational and helps you compute dates from the inputs you provide. It’s not legal advice. If you’re unsure which date starts the clock, double-check the wording in your notice and the case record.

Where to find each input

Below are practical places to locate each input in Brazil matters. Use the source you trust most—typically the court system materials and the official notice text.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Deadline type / event category

• Where to find it:

  • Your procedural document listing deadlines (often a court communication, decision summary, or scheduling notice)
  • The document you received that describes “prazo” (time limit) and what must be filed

• How it changes your output:

  • Choosing the wrong category changes the computation rule (length, counting method, or how non-countable days are handled).

2) Trigger date (event date)

• Where to find it:

  • The portal/case system docket entry that includes the notice/publication/service timestamp
  • The official text attached to the communication (for example, phrasing like “publicado em…”, “juntada…”, “ciência…”, or similar language)
  • The date shown on the “expediente” or notification event in the case timeline

• How it changes your output:

  • A deadline “from event date” depends on exactly which date starts the clock.
  • If a notice entry shows multiple relevant timestamps (posting and acknowledgement, for example), align the trigger date with the tool definition for the selected deadline type.

3) Court / proceeding context (if prompted)

• Where to find it:

  • The case header: court name, division, and procedural class
  • The system’s “vara” / chamber / jurisdiction labels

• How it changes your output:

  • Different procedural tracks can have different deadline structures.
  • If DocketMath asks for context, match what appears in the case record.

4) Special time regimes or suspension periods (if applicable)

• Where to find it:

  • Court announcements (often posted on the court’s official page)
  • Decision text indicating a specific suspension or a non-countable period
  • Case management orders affecting time computation

• How it changes your output:

  • When the tool accounts for non-countable periods, the “last day” may move forward even if the raw deadline length would otherwise end earlier.

5) Time zone / local day boundary (if prompted)

• Where to find it:

  • The case system typically displays dates in the local court time standard
  • If the tool requires a setting and you’re using a practical default, use the court’s local date conventions (for example, Brazil local date interpretation)

• How it changes your output:

  • Most deadline calculators operate at the date level, but a time zone mismatch can create an off-by-one-day result near midnight boundaries.

6) Document type details (only if required)

• Where to find it:

  • The order describing what you must file (the specific procedural action)
  • The procedural notice specifying the filing category

• How it changes your output:

  • Some deadline types split based on the exact procedural action required.

Run it

Ready to calculate? Follow this workflow using DocketMath.

1. Open the calculator: /tools/deadline
2. Select:

   • **Jurisdiction: Brazil (BR)
   • Deadline type / event category matching the notice or order
3. Enter:

   • Trigger date (the event date that starts the time period)
4. Add any required extra inputs:

   • Court/proceeding context, special regime selectors, or filing details (only if the tool asks)
5. Review:

   • The computed deadline date
   • Any intermediate indicators (for example, “last day” vs. “earliest day” depending on how DocketMath displays results)
   • The explanation panel describing how the calculator derived the result

Practical output check (before you rely on the number)

Use this quick “sanity test” against your expectations:

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