Skip to content
Arrange a meeting

Product reference

Deadlines: how it works

Follow the discovery request to its actual service trigger, rule and count. Review a corrected source without silently moving the confirmed date.

On this page

Return to deadlines

Availability

Limited availabilityCovers the courts and rules listed in the documentation.
Supported work
Trace a proposed date to the event that started the clock, the governing rule and the count counsel needs to confirm.
Start with
North Harbor’s request remains proposed and unserved. No response date is calculated. If Rule 34(b)(2)(A) applies, its 30-day period starts at actual service, subject to any stipulation or court order changing it.
Key limit
BRON calendars dates only for the courts it models. Elsewhere it offers a suggestion, with a warning. Calendar export is an .ics file; there is no Google or Outlook sync.

Some capabilities have their own availability or configuration requirements, shown below.

Before you start

  • North Harbor’s request remains proposed and unserved. No response date is calculated. If Rule 34(b)(2)(A) applies, its 30-day period starts at actual service, subject to any stipulation or court order changing it.
  • A served, filed or entered document on the matter, with how and when it was served: the day, the method and the proof. A deadline runs from that trigger, never from today.
  • The matter's court, recorded as court name, jurisdiction and type. BRON reads them together and stops if they contradict each other. An attorney-confirmed forum is required before rule-based computation.
  • A court BRON models: a federal rule in a federal court, or a cited rule for that state and that deadline. Other courts get warned suggestions only.
  • Forward rule counts use federal, Nevada and Florida holiday calendars; other states use a shared set without state-specific holidays. California has a separate backward-counting calendar. Clerk-specific closures still require review.
  • Backward pretrial rules cover federal courts, California and a limited Florida proposal-for-settlement cutoff. An unmodeled rule stays undated and names its trigger; the operative order still needs review.
  • A default jurisdiction for the firm. Settings, then Readiness, shows whether it is set.
  • The actual source, service method, cited authority, counting inputs and any operative scheduling order or stipulation. Rule defaults do not establish that an order left the period unchanged.
  • A licensed attorney to confirm the trigger, authority and exact proposed date.

How it works

Identify the act that starts the clock. Inspect its source, service method, cited rule and count. A licensed attorney confirms the proposed date before calendaring; corrected service evidence brings it back for review.

What actually started this clock, and what must counsel confirm before calendaring it?

From evidence task to procedural date

  • Wait for the act that starts the clock

    The request drafted to investigate notice is preparation. Its actual service supplies the possible response trigger. Read the recorded proof and service method before counting, then connect the reviewed date to the originating request and the task on Your Day.

  • Revisit a corrected trigger without rewriting the calendar

    If the service record changes, inspect the new source, rule and calculation. Counsel decides whether to accept the proposed recalculation. A factual dispute about notice in the underlying case does not itself supply a procedural deadline or a limitations date.

Where a date starts

  • The trigger comes from the document

    BRON reads the event that starts the clock, such as service or entry of an order, from the document itself. The date must appear in the document, and an uncertain reading is dropped rather than guessed.

  • Record the service method and its proof

    How and when papers were served is recorded against the document: the day, the method, the proof and the page it appears on. Several deadlines can run from that one record, and nobody retypes it.

  • Check the court, jurisdiction and matter type

    BRON reads the court name, jurisdiction and matter type together. Contradictions stop the calculation. An attorney must confirm the forum before its rules produce a date; a later court change requires that confirmation again.

How it is counted

  • Counted under the forum's own rule

    Available

    The trigger day is excluded, and a last day on a weekend or court holiday rolls to the next open day under that forum's own rule, such as Federal Rule 6(a), New York's General Construction Law or Texas Rule 4.

  • The service method changes the date

    Mail adds three days under the federal rules. California, New York, Texas and Florida apply their own mail extensions, in their own order. Electronic service adds two court days in California and nothing federally.

  • Court holidays by forum

    Forward rule counts use federal, Nevada or Florida holiday calendars; other states use a shared set without state-specific holidays. California has a separate backward-counting calendar. Each calculation names its calendar; clerk-specific closures still need review.

  • A second calculation checks the first

    A second calculator works out each date a different way. If the two disagree, BRON raises an item saying not to calendar the date until an attorney resolves it.

Going on the calendar

  • An attorney confirms every calendared date

    A licensed attorney reviews the trigger, authority and exact date before calendaring. Until then it is a task, listed apart and marked not calendared. A failed save reports that no deadline row is confirmed created and asks for a retry.

  • Only courts BRON has rules for

    A date is calendared only with a federal rule in a federal court, or a cited rule for that state and that deadline. Elsewhere BRON can suggest a date with a warning, and the suggestion stays off the calendar.

  • Keep the rule and calculation with the date

    Available

    A calendared date keeps its rule, trigger, service method, period, forum and citation, and the document that started it, so the date can be checked and disputed later.

  • Export to your own calendar

    Export confirmed deadlines as an .ics file for your own calendar app. BRON does not sync with Google or Outlook calendars.

  • Read the operative order before accepting the default

    A scheduling order can set dates that displace a rule default. Dates read from an order remain suggestions with the quoted source for review; an attorney confirms each before calendaring.

  • Keep reminders tied to the recorded date

    Upcoming and overdue reminders use the recorded deadline and its reminder settings. They appear as matter tasks. Completing a workflow does not establish that a filing landed; a person must close the deadline.

  • A failed read leaves the docket unknown

    A failed docket read reports that it could not be checked. It cannot establish that no suggestions or deadlines exist. Retry the read before relying on the list.

When something changes

  • Review the date when its inputs change

    If the service method, trigger or forum behind a confirmed date changes, BRON proposes a recalculated date. It never moves the date itself.

  • Dependent dates follow their trigger

    Available

    When a trigger moves, the open suggestions that run from it are recalculated, and dates an attorney confirmed are left alone. A deadline whose event has not happened is listed without a date, naming the event.

  • A judge's practices, once verified

    Available

    A judge's individual practices are added to a suggestion only where an attorney has verified them, and the suggestion carries the date of that verification.

  • Flag a date that passed without confirmation

    If a computed date passes without anyone confirming it, BRON raises an item on the matter, because nothing put that date on the calendar.

What it reads from

  • Served, filed and entered documents
  • Service records: the day, the method and the proof
  • The court, the judge and local rules
  • Scheduling and trial-setting orders
  • Contract notice and cure periods

Who can do what

  • Counsel confirms the proposed count and any recalculation. The originating request and Your Day task keep the date attached to the procedural work it governs.
  • A licensed attorney confirms the trigger and the date before a deadline goes on the calendar. Until then it is a task, listed separately.
  • Creating, editing, cancelling or completing a deadline each stop for approval, and calendaring needs a licensed attorney. Cancellation retains the record rather than deleting it.
  • The assistant reads the event that starts the clock. It cannot confirm its own date.
  • A judge's individual practices are added to a suggestion only where an attorney verified them, with the date of that verification.
  • If the two calculators disagree, an attorney resolves it before the date is calendared.
  • Upcoming and overdue reminders use the recorded deadline and its reminder settings. Finishing a workflow does not establish that the filing landed; a person closes the date.
  • If an input behind a confirmed date changes, a person decides whether to accept the recalculated date. Nothing on the calendar moves until then.

What it produces

  • The matter's calendar, and the list of proposed dates
  • Your Day and the daily brief
  • Workflows tied to a date
  • The matter's chronology
  • Calendar files (.ics) for your own calendar

Limits

  • BRON calendars a date only with a federal rule in a federal court, or a cited rule for that state and that deadline. For any other court it gives a warned suggestion and calendars nothing.
  • Forward rule counts use federal, Nevada and Florida calendars; other states use a shared set without state-specific holidays. California has its own backward-counting calendar. The calculation names the calendar used; local closures and orders still require review.
  • Backward pretrial rules cover federal courts, California and a limited Florida proposal-for-settlement cutoff. This is not coverage of every pretrial obligation. An unmodeled rule stays undated, naming its trigger; counsel must check the operative order.
  • Court orders, stipulations and verified local or judge-specific rules may change the applicable period. An unconfirmed or changed forum must be resolved before rule-based calculation resumes.
  • A stored calculation lets a date be checked and disputed. It does not make the date right. This is attorney work product, not legal advice.
  • Deadlines export as .ics files. There is no sync with Google or Outlook calendars.

What BRON will not do

  • Count from today.

    A litigation period runs from service, filing or entry of judgment. A date counted from the day someone opened the matter would look like a real deadline and have no basis.

  • Let the assistant confirm its own date.

    The assistant has to use the date the attorney stated, word for word, and cannot mark it confirmed. A licensed attorney on the matter sees the exact date and its rule first, and an approval cannot be replayed.

  • Calendar a federal period on a state matter.

    A suggestion may show a federal period with a warning. Calendaring needs a federal rule in a federal court, or a cited rule for that state and that deadline, and BRON names which one it could not find.

  • Apply trial-court periods to a court it has no rules for.

    Bankruptcy courts, the courts of appeals and the Supreme Court run on their own rules. Without a modeled rule for that court and deadline, BRON names the gap instead of substituting a trial-court period.

  • Guess the service method.

    “Hand delivered, confirmed by email” names two methods, and the extension differs by method. BRON treats the method as unknown, adds no extension, and says the method was not established.

  • Start a deadline from a client's report of when papers arrived.

    A client's photo of an envelope can propose a service date for an attorney to confirm. It starts no deadline until the attorney does.

  • Mark a deadline met because a workflow finished.

    A workflow can end without the filing landing. A person closes the date.

When something goes wrong

  • No date is manufactured from today, the prospect’s account or an unresolved fact in the merits dispute.
  • An uncertain reading of the trigger is dropped rather than guessed.
  • For a court BRON does not model, a suggestion carries a warning and no date is calendared. The message names what is missing.
  • If a service description names two methods, BRON adds no extension, which gives the earlier date, and says the method was not established.
  • If the two calculators disagree, an item says not to calendar the date until an attorney resolves it.
  • A stipulation, a corrected proof of service or a corrected forum brings a confirmed date back for review with a recalculated date. Nothing on the calendar changes by itself.
  • A changed court withdraws the old forum confirmation and holds rule-based calculation until the forum is confirmed again. It does not silently move calendared dates.
  • A failed docket read means the list could not be checked, not that no deadlines or suggestions exist. Retry before relying on it.
  • A failed calendar save reports that no deadline row is confirmed created. A failed move reports its failure; a date changed during approval requires a refresh and review of the live date.
  • A deadline whose event has not happened is listed without a date, naming the event it waits on.
  • A computed date that passed without confirmation raises an item, because nothing put it on the calendar.
  • A calendared date missing what a recalculation needs is marked as asserted rather than calculated.