Distinguish a proposed date from a confirmed deadline

Before you begin

• Access to the matter and the event or document behind the proposed date.

What to do

1. Open the item and read its state before acting on the date. A proposed date is work for an attorney to review. Do not treat a task, reminder or suggested calculation as proof that the date was confirmed on the matter.
2. Inspect the trigger in the record. Identify the actual service, filing, judgment or notice event used by the proposal. An upload date or the day you opened the task is not a substitute for the event that starts the period.
3. Read the cited rule and counting explanation, then check the matter's forum and the recorded service method. Confirm that the inputs describe this matter. A familiar rule name does not establish that the rule applies here.
4. Have a licensed attorney review the proposal through the deadline confirmation flow. If the rule, trigger or forum cannot be established, keep the issue as a task for counsel. Do not enter a guessed date to clear the review queue.
5. After confirmation, inspect the matter's Deadlines view and the saved entry. If a read or save fails, resolve that failure before relying on the calendar. Keep the firm's existing deadline control in use while the entry remains unconfirmed.

What you should see

You can identify the proposal's trigger, authority and status, and distinguish a task awaiting counsel's decision from an entry confirmed on the matter calendar.

Limits and unresolved problems

Deadline coverage is limited to supported courts and rules. BRON does not supply a missing legal rule or decide whether it applies. A licensed attorney confirms the date before it goes on the calendar.

Product scope and requirements

• Deadline calculations and confirmation

Related guides

• Calculate a date and review it before calendaring
• Resolve a missing rule or conflicting deadline basis
• Review a deadline after its inputs change