NOA & Statement of Use Reminders, on a Cadence

The problem: the deadline clients least expect

When an intent-to-use application clears opposition, the USPTO issues a Notice of Allowance. That starts a six-month clock to file a Statement of Use proving the mark is actually in commerce — or to file a request for a six-month extension, up to five times, for as long as three years total. It feels like a win, so clients relax exactly when they should be gathering specimens.

Miss the SOU deadline without a timely extension and the application is abandoned. Every dollar and every month the client spent getting the mark allowed is lost, and they start over at the back of the line. The NOA window is also the most procedurally intricate deadline in prosecution: it is really a chain of extension deadlines, each with its own filing and its own next window. Tracking it by memory is how allowed marks die.

How Upcoming Notices handles the NOA / SOU family

Upcoming Notices watches every open NoticeOfAllowanceSOU and NoticeOfAllowanceExtension deadline in your portfolio and queues the right client reminder as each one enters its window — whether that is the initial SOU, an extension request, or the SOU due at the end of an extension chain.

Tiered cadence across the extension chain

Because the NOA window is a sequence of six-month periods, the cadence repeats cleanly for each one. Counted back from the official due date of whichever period is active:

60, 30, 14, 7, and 1 day before the deadline. The same cadence applies to each link in the extension chain, so a mark on its third extension is reminded just as reliably as one facing its first SOU. Each tier is a separate documented outreach.

Reminders that match where the mark actually is

The NOA family is stateful, and Upcoming Notices respects that. A mark whose SOU is still due surfaces a file-your-SOU reminder; once the SOU has been filed and the deadline moves to awaiting-USPTO verification, that reminder clears from the queue on its own, so a client is never nagged to file something they already filed. Sending a filed-and-pending follow-up — an invoice or a status confirmation — is then a separate step you trigger from the mark or a batch, not an automatic queue notice. The queue tracks the deadline's real status instead of blindly firing on a date.

Blockers, so you never send into the dark

Before a mark becomes sendable, Upcoming Notices checks it against real filing blockers — a missing client email, a deadline that is no longer actionable, an inactive mark, or the same reminder already sent inside the three-day cooldown. Blocked marks appear with the reason so you can fix and re-queue instead of guessing why someone was skipped.

Batch review, then send

Every mark with an upcoming NOA, SOU, or extension deadline lands on one screen, grouped by how soon it is due, each row showing the mark, serial number, next due date, and its countdown. You select the ones that are ready, generate and review the drafts, deselect anything that needs a personal note, and send the rest — one email per notice, each with its own countdown. The most procedurally fiddly family in your docket becomes a short, confident review.

The loop, closed

Track each period from the Notice of Allowance, remind the client on a cadence tuned to where the mark is in the chain, help them approve and pay, then verify the SOU or extension actually posted to the USPTO. Upcoming Notices is the outreach half of that loop for the deadline clients are most likely to under-estimate. It promises no outcome, only that the deadline was never invisible and the client was never left guessing.