Inprotech keeps your docket. PracticeLink runs the layer above it: dashboards, client portals, IDS, forms, mail intake. No migration, no IT tickets.
Your Inprotech database holds more practice data than anyone in your firm can see.
Decades of matters, custom fields, configured workflows, prosecution history, party data, fee schedules, foreign agent relationships. It's all in there. Inprotech is doing its job, and most firms running it have invested years tuning it to fit the way they work.
The question isn't whether the data exists. It's who can see it, when, and in what form.
A partner asks for a snapshot of a client's portfolio. The ops director wants to know which matters are running hot this week. The client wants to log in and see current status. Each of those questions sends someone to Inprotech, then to a custom report, then to Excel, then to a Word doc. By the time the answer lands, the question has moved on.
Inprotech was built to manage the practice. PracticeLink was built to make the practice visible. They're designed to work together.
What Is Inprotech?
Inprotech is Clarivate's IP management platform, originally built by CPA Global and inherited when Clarivate acquired CPA in 2020. It's one of the most widely deployed IPMS platforms in the world, especially at large law firms and corporate IP departments that need deep configurability.
If your firm runs Inprotech, you know what makes it powerful. Custom fields where you want them. Workflow rules tuned to how your team actually files. A history that goes back as far as your firm has been using it. That depth is the asset.
It's also where the friction starts. The more configured Inprotech is, the more the data it holds depends on someone who knows how to get it out. Custom queries. Saved searches. Report writers. IT tickets. The data is rich. The path from data to decision is long.
For a broader view of what "IP operations" covers beyond docketing, see What Is IP Operations?
What Stays in Inprotech When You Add PracticeLink?
Adding PracticeLink doesn't ask you to migrate, reconfigure, or unwind anything you've built in Inprotech. The point of an operations layer is to leave the system of record alone.
Prosecution deadlines and statutory dates. Inprotech remains the docket. PracticeLink reads from it and never writes back to the date fields.
Custom fields and configurations. Years of tuning don't get thrown away. PracticeLink reads custom fields directly and surfaces them in views your team can actually use.
Workflow rules and event logic. Whatever Inprotech is already doing on the docket side keeps doing it.
Party, agent, and entity data. Inprotech holds the master records. PracticeLink references them, doesn't replace them.
Historical data. Every matter, every event, every history line stays where it is. PracticeLink works against the live database, not a one-time export.
Your Inprotech administrator does not have a migration project. Your docketing team does not learn a new system. That part is the whole point.
What Does PracticeLink Add to Inprotech?
PracticeLink connects to Inprotech directly and uses the data as the foundation for an operations layer. Most of what it adds shows up as one thing: views of your practice that didn't exist before.
Dashboards that don't require IT. Real-time views of matter status, workload, deadline density, response cycles, and bottlenecks. The data is coming from Inprotech. The configuration is happening in PracticeLink. Ops directors stop filing report requests and start watching the practice live.
Cross-matter and cross-client visibility. Roll up by client, by attorney, by technology, by jurisdiction, by anything in your Inprotech data model. Custom fields you've maintained for years finally show up in views the rest of the firm can read.
Office action workflow. This is the one people ask about most. PracticeLink syncs with Inprotech docketing to manage the full office action response cycle. The office action comes in, gets classified against the right Inprotech matter, gets routed to the right attorney. The response workflow kicks off with built-in checkpoints, task assignments, and deadline tracking tied to the docket dates already in Inprotech. The attorney works the substance. PracticeLink handles the logistics.
Near real-time sync. The connection pulls incremental updates throughout the day. Not a nightly batch. Not a manual export. When something changes in Inprotech, PracticeLink reflects it within minutes. Your paralegals and attorneys see current data without wondering if it's stale.
Client portals fed by current data. Branded client portals and electronic tri-folds pull straight from Inprotech and refresh as the data changes. One configuration per client. After that, the portal stays current without anyone touching it. Client reporting runs 30% faster across firms using PracticeLink for this, and reporting satisfaction sits at 98%.
Practice data, surfaced for partners. A partner asks where a portfolio stands before a panel review. A lateral candidate asks what the firm runs and whether they can see their book on day one. A client asks for write-off and realization context on flat-fee matters. Each of those questions used to require a project. Now it requires a link. The view is current, formatted, and shows what the partner actually needs to see.
Document intake feeding the matters in Inprotech. Incoming mail captured from the shared inbox, classified, linked to the right Inprotech matter, routed to the right person, and profiled to your DMS. Automatic. Firms running this see mail processing speed improve by 50%.
Forms and citations using Inprotech data. USPTO filing packages, IDS citations with cross-family references, forms with smart prefill from Inprotech party and matter data. Forms preparation runs 45% faster.
Soft-docket alongside the statutory docket. Attorneys set their own preparation dates and reminders in PracticeLink without touching the official Inprotech docket. Personal task layer, not date-field changes.
What a Typical Day Looks Like
A docketing specialist at a firm running both systems might start their morning like this:
8:30 AM. Overnight mail has already been processed. PracticeLink captured 47 incoming documents from the shared mailbox, classified each one, linked them to the right matters in Inprotech, and routed them to the attorneys and paralegals who need to act on them. Three office actions, two notices of allowance, a restriction requirement, and a stack of foreign correspondence. All sorted before anyone opened their laptop. The ops director opens a single dashboard and sees the day shape up before standup.
10:00 AM. A senior paralegal pulls up live matters for one of the firm's anchor clients. She needs to confirm IDS status across a patent family before the team reviews a new prior-art search. In the old workflow she'd open Inprotech, run a saved search, export to Excel, cross-check against the citation tracker she maintains, and reconcile. Now the view is already there. Family members, references already cited, references pending, attorney of record. She adds two new references from yesterday's search, previews the package, and sends it through the review workflow. The attorney approves it by 11. Twenty minutes total. Last year, this was a two-hour job.
11:30 AM. A partner emails the client team. He needs a snapshot of a client's active prosecution work before a 2 PM call. The client team sends a portal link. The portal is already current, pulled from Inprotech, formatted to the client's preferences. He reads it on the elevator.
3:00 PM. A senior associate asks how many continuations the firm has filed for a specific client in the last twelve months. In the old workflow that's a custom report request to IT, scheduled for next Tuesday. In the new workflow it's a view that already exists. He has it before his next call.
None of this required a change to Inprotech. The dates are where they've always been. The configurations are intact. Inprotech still runs the docket. PracticeLink runs the operations around it.
How Does PracticeLink Connect to Inprotech?
For teams evaluating how the systems connect:
Connection method. PracticeLink connects to Inprotech directly through supported integration methods. The connection runs against the live Inprotech database, not a periodic export.
Hosting and security. PracticeLink is cloud-native and hosted on Microsoft Azure. SSO, role-based access controls, encryption, and audit trails are built in. Our written security best-practices documentation and recent penetration testing reports are available on request before any pilot conversation.
Data flow. PracticeLink reads from Inprotech. Matter data, dates, party information, custom fields, history, configurations. Changes in Inprotech show up in PracticeLink without anyone clicking sync. PracticeLink does not write back to Inprotech date fields. Your system of record stays the system of record.
What PracticeLink adds on top. Dashboards and operational reporting, client portals and branded reports, document intake and classification, forms and citations (IDS, filing packages), soft-docket management, workflow automation, and the Planner for color-coded date visibility.
DMS integration. PracticeLink also connects to netDocuments and iManage. Documents profiled to the right matter with metadata derived from Inprotech.
Setup and IT lift. The Inprotech connection is part of the standard PracticeLink implementation. Your Inprotech administrator is consulted, not displaced. No changes to your existing Inprotech configuration are required, no new on-prem infrastructure, no firewall changes beyond standard SaaS allowlisting. IT lift is minimal by design.
What If You're Already Running Inprotech?
You have the hard part done. The data is captured, the dates are tracked, the configurations reflect years of decisions about how your firm files. The remaining question is whether anyone outside the docketing team can actually see what's in there.
If partners file report requests and wait days, that's not an Inprotech problem. If ops directors can't watch the practice in real time, that's not an Inprotech problem either. Inprotech was built to be the system of record, not the dashboard. Those are different jobs. And the gap between them is what PracticeLink fills.
Five of the top 10 US patent filing firms run PracticeLink alongside their docketing systems. Our longest-tenured clients have been with us through multiple platform generations and several of their own leadership changes. The pattern repeats: keep the system of record you've spent years tuning, add the layer that makes its data usable across the firm.
For firms consolidating their tool stack rather than expanding it, PracticeLink is the layer that absorbs the work currently living in spreadsheets, shared inboxes, and the half-built automations that nobody fully owns. One layer, not another point solution.
A few things worth saying clearly. PracticeLink was built by people who ran IP operations before they built software. Our team carries more than 150 combined years inside IP practices. We don't touch your statutory dates, and we don't take ownership of work that has to live inside your firm. Your audit trail is your audit trail. Your liability model doesn't change because there's a visibility layer on top of your docket.
Common Questions
Does PracticeLink replace Inprotech?
No. PracticeLink is an operations and visibility layer that sits on top of Inprotech. Your docketing team keeps working in Inprotech exactly as they do today. PracticeLink reads from Inprotech and surfaces the data through dashboards, client portals, and operational reporting that Inprotech was never designed to deliver.
Can PracticeLink show data from custom Inprotech fields?
Yes. Most firms that have run Inprotech for years have built custom fields that hold information critical to how they actually work. PracticeLink reads those fields and surfaces them in dashboards and reports without requiring a re-mapping or migration.
Does PracticeLink change anything in our Inprotech configuration?
No. PracticeLink reads from Inprotech and doesn't write back to date fields or configurations. Your Inprotech administrator is involved in the connection setup but doesn't need to reconfigure anything to support PracticeLink.
How current is the data PracticeLink shows?
Near real-time. The integration runs against the live Inprotech database, not a nightly export. When something changes in Inprotech, it shows up in PracticeLink dashboards and client portals within minutes.
Are there office action tools that sync with Inprotech docketing?
Yes. PracticeLink manages the full office action response workflow tied to docket dates in Inprotech. When an office action arrives, PracticeLink classifies it, routes it to the right attorney, and kicks off the response workflow with task assignments and deadline tracking. The statutory dates stay in Inprotech. PracticeLink handles the work between receiving the action and filing the response.
Do partners and clients need Inprotech logins to see anything?
No. That's the point. Partners see firm-level views through PracticeLink dashboards. Clients see their own portfolio through a branded client portal. Neither needs an Inprotech seat or training.
What does the integration cost?
The Inprotech integration is included with PracticeLink. There's no separate licensing fee for the connection. Pricing depends on your firm's size and configuration. Talk to our team for specifics.
How long does it take to set up?
The Inprotech connection is part of the standard PracticeLink implementation. There's no separate integration project, and your Inprotech administrator doesn't have to reconfigure anything to support it.
What does the security review look like?
Most firms route PracticeLink through their standard SaaS security review. We provide our written security best-practices documentation, recent penetration testing reports, a detailed security questionnaire, architecture diagrams showing the Inprotech connection and Azure hosting topology, and references from IT leaders at peer firms who completed the same review. SSO is supported. There is no custom security model to evaluate.
Can we pilot this with one practice group before committing firm-wide?
Yes. Most engagements start with a pilot. One practice group, one client portfolio, or one workflow (often client reporting or document intake). Pilot scope is decided with you in the first conversation, not pushed from a template. Full rollout follows once the pilot lands.
Can PracticeLink work with other docketing systems too?
Yes. PracticeLink integrates with Inprotech, FoundationIP, CPi, and others. The pattern is the same regardless of the underlying system. The docketing system holds the data. PracticeLink makes it visible and operational.
Ready to See It?
The first conversation isn't a pitch deck. It's a working session with an IP operations advisor from our team. We walk through your Inprotech data model, look at the custom fields you've built, and show you what the integration looks like against your actual matters. By the end you'll know what would be visible, what would be automated, and what the pilot would scope to. Schedule a conversation with our team.