Most missed client communications are not the result of a missed deadline. The deadline is sitting in the docket, correctly calculated. What fails is the handoff: the reminder that should have gone to the client three weeks ago, the invoice that never got sent, the office action the client never heard about until it was almost too late to respond. The deadline was visible to you and invisible to the person who needed to act on it.
Upcoming Notices is built to close that gap. It reads the deadlines already in your docket, groups them into client-ready reminders, and holds them in a review queue until you approve each one. This article explains exactly how it works: what the feature is, which deadlines it covers, how a notice is generated, what stops one from sending, how payment links attach, and how you review and send in a single pass on a Friday afternoon.
What Upcoming Notices Is
Upcoming Notices is a review-first client reminder system. It sits on top of the deadlines DeadlineDocket already tracks from the USPTO TSDR record, and it does one thing well: it queues the client-facing communication needed for every approaching deadline and puts it in front of you — you generate the draft and review it before it goes out.
The emphasis is on review-first. Upcoming Notices never sends a client email on its own. It queues what is coming due, groups it by urgency, flags what is blocked, and drafts only when you tell it to. You decide what sends, to whom, and when. This is a deliberate design choice. Client communication about a legal deadline is an act of judgment, not a mail merge, and the system is built to support that judgment rather than replace it. For the reasoning behind that stance, see how we think about automating client notices safely.
The result is a workflow that feels like clearing a queue. Each item is a mark with an approaching deadline, the reason it is here, and a clear indication of whether it is safe to send. When you are ready, you generate the draft for the items you have chosen, review each one, and send. You work down the list, draft and approve what is ready, fix what is not, and skip what should wait.
Which Deadline Families It Covers
Upcoming Notices draws from the same deadline families DeadlineDocket tracks across the trademark lifecycle. Each family maps to a communication built for that moment in prosecution or maintenance:
- Office action responses: When an office action is outstanding and the response deadline is approaching, Upcoming Notices prepares a client notice explaining that a response is required and by when. This covers both the initial response window and extension deadlines.
- Notice of Allowance and Statement of Use: After a Notice of Allowance issues, the six-month Statement of Use clock starts. Upcoming Notices covers the initial SOU reminder, extension reminders, and urgent late-stage reminders while the filing is still due. Once the SOU is filed and the deadline moves to awaiting-USPTO verification, that reminder clears from the queue automatically; a filed-and-pending follow-up, such as an invoice or status note, is a separate manual template you send from the Communications page.
- Section 8 and Section 9 maintenance: The post-registration maintenance filings, including the combined Section 8 & 9 renewal, are long-cycle deadlines that are easy to lose track of. Upcoming Notices surfaces them well in advance so the client can be contacted while there is still runway.
- Registration and collections follow-ups live elsewhere: Type-agnostic communications, such as a registration-issued congratulations note or a final follow-up on an outstanding invoice, are available as manual templates on the Communications page, not as items in the Upcoming Notices queue.
Because the notices are driven by the deadline type on each mark, the right message is matched to the right moment automatically. An office action notice is only ever prepared for a mark with an open office action deadline; an SOU reminder is only prepared for a mark in the Statement of Use window. You are never choosing a template from a dropdown and hoping it fits.
How Notices Appear: The Cadence
A single deadline does not produce a single notice. Different deadline families warrant different reminder rhythms, because the amount of client runway differs. A maintenance window is open for a year; an office action response is due in months; an SOU extension is a tighter clock. Upcoming Notices reflects that with tiered cadences keyed to the official due date:
- Office action responses surface at 60, 30, 14, 7, and 1 day before the due date, tightening as the deadline nears.
- Section 8 and Section 9 maintenance surface much earlier, at 180, 120, 90, 60, and 30 days out, because contacting the client, confirming continued use, and gathering specimens takes time.
- Notice of Allowance and Statement of Use deadlines surface at 60, 30, 14, 7, and 1 day before the due date.
The point of the cadence is persistence without noise. A reminder that fires once and disappears is a reminder you can miss on a busy day. A tiered cadence keeps the deadline in your queue as it approaches, escalating as the date nears, so a mark cannot quietly fall off your radar between the first alert and the deadline itself.
What “Why This Is Here” Means
Every notice in the queue can explain itself. Next to each item is the reason it appeared: the deadline family, the specific mark, the due date, and where in the cadence this reminder falls. Nothing lands in your queue without a traceable cause tied to a real deadline on a real mark.
This matters for trust. A queue full of items you cannot explain is a queue you stop trusting, and a review system you do not trust is one you stop using. By making the “why” explicit, Upcoming Notices lets you verify at a glance that a reminder is warranted before you approve it. If a notice appears for a mark you have already handled outside the system, you see immediately why it surfaced and can skip it with confidence rather than wondering whether the system knows something you do not.
What Blocks a Notice From Sending
Not every drafted notice is ready to go out, and Upcoming Notices is explicit about why. Each item in the queue is either sendable or blocked, and when it is blocked, the reason is shown. Common blocks include:
- No client contact on file: A notice cannot send without a recipient. If the mark has no client name or email, the notice is held and flagged so you can add the contact before sending. Contact details can be applied to a group of marks at once.
- Recently emailed: If a reminder for this same deadline already went out in the last few days, the notice is flagged so you do not send a duplicate for the same filing. The check is scoped to the specific deadline, not the client in general — a reminder for one deadline never hides a notice for a different deadline on the same mark, so nothing gets silently dropped.
- Inactive mark or deadline: If the underlying mark or deadline is no longer active, for example because the deadline was met, verified, or cancelled, no notice is prepared. Only genuinely actionable deadlines produce sendable notices.
Blocks are not errors to be worked around; they are guardrails. Each one represents a case where sending would have been premature, redundant, or misdirected. Seeing the block, and its reason, lets you resolve the underlying issue, add a contact, confirm the deadline, rather than blindly firing off a message.
How Payment Links Work
Many of these notices are not just reminders; they are the moment you ask the client to approve work and, often, to pay for it. Upcoming Notices supports attaching an amount and a payment link to a notice so the client can act in the same message that informs them.
The payment link is processor-agnostic. It carries the amount and points the client to your payment page, without locking you into any single billing provider. The fee comes from the template's default amount, which you configure in advance; the link is built to match it. For a maintenance invoice, this turns a reminder into a self-contained request: here is the deadline, here is the work, here is how to approve and pay.
As with everything else in Upcoming Notices, the notice carrying that amount and link is drafted for your review, not sent automatically. You see the figure before the notice goes out.
How Batch Review and Send Works
The heart of Upcoming Notices is the batch review pass. Rather than handling notices one message at a time, you review a whole cadence tier at once, grouped by urgency, so the items due soonest surface first and nothing slips through while you work down a longer list.
A typical pass looks like this:
- Open the queue. Every mark with a notice due in the current window is listed, grouped by how soon it is due, each with its due date, a countdown, and its send status.
- Scan the blocks. Items that cannot send are flagged with a reason. Resolve what you can, add a missing contact, fix a template missing its default amount, and set aside what should wait.
- Generate and review the drafts. Select the items you are ready to act on and generate their drafts. Each one is a starting point written for the specific deadline; read it in the review panel, edit it if your judgment says so, and confirm the recipient.
- Send the batch. Approve the ready items and send them together. The system records what sent, what failed, and what was skipped, so you have a clear audit of the pass.
The design goal is a Friday-afternoon workflow: a single, focused session where you clear the week's approaching client communications, know exactly what went out, and leave nothing hanging. You are reviewing and approving in bulk, but every individual message still passed under your eyes before it sent. You can see the same batch structure in action on the Upcoming Notices feature page.
Why This Is Safer Than a Spreadsheet
The alternative most firms fall back on is a spreadsheet of client contacts, a folder of email templates, and the discipline to check both regularly. It works until it doesn't, and the ways it fails are exactly the ways Upcoming Notices is built to prevent. For a fuller treatment of this comparison, see spreadsheets versus docketing software.
- A spreadsheet does not push. It waits for you to open it. Upcoming Notices surfaces deadlines on a cadence, so an approaching deadline finds you rather than waiting to be found.
- A spreadsheet does not know the deadline type. You choose the template by hand, and the wrong one goes out. Upcoming Notices matches the message to the actual deadline family on the mark.
- A spreadsheet does not prevent duplicates. Nothing stops you from emailing the same client the same reminder twice. Upcoming Notices suppresses recent duplicates automatically.
- A spreadsheet does not flag missing contacts. A blank email cell is silent until the reminder simply never sends. Upcoming Notices makes the missing contact a visible block, not an invisible gap.
- A spreadsheet has no record of what went out. Upcoming Notices records every send, so you can answer, months later, exactly what the client was told and when.
None of this removes your judgment from the loop; it protects it. The system handles the mechanical parts, calculating the deadline, matching the message, catching the duplicate, flagging the gap, so that your attention goes to the decision that actually requires an attorney: whether this client, on this mark, should hear from you now, and what you want to say.
To see how Upcoming Notices fits with the rest of DeadlineDocket's deadline tracking and TSDR verification, visit the features page, or review the latest additions on the what's new page.