Skip to main content
You are a paralegal at a mid-sized IP firm responsible for docketing renewal deadlines across 200+ client marks in 12 jurisdictions. Missing a deadline means losing rights, and potentially a malpractice claim. You need a system that surfaces every upcoming deadline with enough lead time to prepare filings. This guide walks through building a renewal management workflow with the Signa API.

Prerequisites

  • A Signa API key with trademarks:read scope
  • A list of trademark IDs (or office-native identifiers) for the client marks you docket

1

Understand deadline types by jurisdiction

Not every jurisdiction has the same deadline structure. The Signa API computes deadlines based on jurisdiction-specific rule sets (rules defined for 21 jurisdictions, independent of which offices currently have live trademark record data, see the coverage note below). Start by reviewing the rules for your key jurisdictions.
Key differences across jurisdictions:
US marks have the most complex deadline structure. In addition to renewal, you must file a Section 8 Declaration of Use between years 5-6 after registration, and optionally a Section 15 Declaration of Incontestability at year 5. Missing the Section 8 results in cancellation, even if the mark is in active use.
Rule coverage (GET /v1/deadline-rules) and trademark record coverage are tracked separately: rules exist for all 21 supported jurisdictions today, while ingested trademark record data is live for a subset of offices and expanding. See Data Freshness & Coverage for which offices currently have live records.
2

Collect deadlines across your client marks

Every GET /v1/trademarks/{id} response includes a deadlines array. Each entry already carries a computed status (future, window_open, due_soon, in_grace, or missed), an urgency (routine, upcoming, critical, in_grace, or missed), and days_until_due, so you do not need to reimplement that triage logic client-side. Fetch each client mark (or use Batch Get Trademarks for up to 100 at a time) and collect the deadlines that fall inside your docketing horizon.
Expected output:
3

Triage by urgency

Group the collected deadlines by the urgency field the API already computed, no client-side date math required:
4

Handle US-specific Section 8 and Section 15 declarations

US marks require more than simple renewal. Filter the deadlines you already collected by jurisdiction and type to identify which declarations are needed.
US Declaration timeline for a mark registered on 2021-01-20:
Section 15 (incontestability) is optional but highly valuable. It eliminates most grounds for cancellation. The window opens at year 5 and remains open indefinitely, but the mark must have been in continuous use for 5 consecutive years with no pending proceedings.

Deadline rules by jurisdiction

Beyond the five jurisdictions above, Signa computes deadlines for all 21 supported jurisdictions. All of them use a 6-month grace period: Call GET /v1/deadline-rules for the full, current rule set, including the remaining jurisdictions (BR, BX, DK, FI, IS, NO, PH, PL, SE, TH, VN) not itemized here.

Class coverage

A renewal review is a natural time to also check whether your registered classes still match your business. List your marks filtered to the classes you care about and diff against your target list:
TypeScript
Repeat the same query per jurisdiction (add an offices filter) to build a jurisdiction x class coverage matrix for the portfolio.

Keep watching for status changes

Refreshing this roll-up nightly from your job scheduler works, but it means you only find out about a status change when you poll. A portfolio watch with trigger_events: ["trademark.status_changed"] over your client marks pushes an alert the moment a mark’s status flips (for example to expired or cancelled), so a missed renewal surfaces the same day the office records it instead of waiting for your next scheduled run. Pair the watch with a webhook to route it straight to your docketing queue. If you still want a scheduled roll-up alongside the watch, run the batch fetch from step 2 nightly and diff the results against the previous run:
TypeScript

What’s next

M&A Due Diligence

Audit an acquired portfolio’s coverage and deadlines before a deal closes.

Opposition Tracking

Monitor proceedings that could affect the renewability of contested marks.