Oppositions, cancellations and infringement suits shouldn’t live in a Word file next to the portfolio — they should live on the mark itself, with hearing dates docketed like any other deadline.
Every serious trademark practice eventually litigates: an opposition against a confusingly similar application, a cancellation action, an infringement dispute, an appeal. Yet in most firms these live in a separate world — a Word file here, a court date in someone’s Outlook there — disconnected from the very mark they’re about. IPBases treats a dispute as what it is: a record attached to the trademark, with its own dates, status and history, visible wherever the mark is visible.
A case in IPBases is created directly from (and linked to) a trademark, and carries the fields dispute work actually runs on:
Because the case hangs off the trademark, the full context is one click away: the mark’s classes and status, its filing history, its documents, and the client behind it.
Dispute work is often the most sensitive data in the system. The Litigation module respects the same granular permission layer as everything else — you can grant case access to the litigation team and hard-deny it to everyone else, or switch the module off entirely for firms that don’t contest. And every change to a case lands in the append-only audit trail.
An opposition generates response work; response work generates fees. Because cases live beside the docketing engine and the billing module, the workflow stays in one system: record the opposition, task the response, invoice the work — with the official-fee and professional-fee split IP billing needs — and notify the client through the built-in mail. Contrast that with the usual reality: proceedings before bodies like the USPTO’s TTAB or a national office tracked in a standalone spreadsheet that the renewals team never sees.
Cases linked to marks, hearing dates in the deadline engine, permission-scoped access — litigation as part of the portfolio, not beside it.
Book a demo → See pricing →