Patricia keeps your docket. PracticeLink adds the operations layer: dashboards, US filings, client portals. No migration, whatever your roadmap does.
If your firm runs Patricia, you have something most IP practices don't. An IPMS configured by people who actually understand the work, refined over years of real prosecution. The rules match how your foreign agent network operates, how your jurisdiction-specific filings move, and how your docketers expect a family to be structured.
That's the asset. It's also the thing that makes the next question harder to answer, and a question more Patricia firms have been asking since Patrix joined Anaqua in April.
Where does Patricia end and the rest of the practice begin? When a client asks where things stand on a portfolio, the data is in Patricia. The format the client wants is not. When an attorney sits down to respond to an office action, the case is in Patricia. The drafting tool, the cited art, and the prior responses in the file history sit somewhere else. When a paralegal builds an IDS for a US filing, the references are in Patricia. The assembled package is not.
Patricia was built to manage IP. PracticeLink was built to make IP work move. They're designed to fit together, with no migration and nothing new for your IT team to stand up.
What Is Patricia?
Patricia is the long-running IPMS platform from Patrix, with roughly thirty years of continuous development and a customer base that runs from European boutiques to multi-jurisdictional law firms with global filing programs. If you're running it, you already know what makes it powerful. Deep customization. Strong handling of foreign filing workflows. Multi-jurisdictional case structures that other systems flatten. A configuration that reflects how your team actually files, not how a vendor thinks you should.
Patrix joined Anaqua in April 2026. The companies have stated that Patricia continues to be maintained and developed, with optional access to other Anaqua platforms as customer needs evolve. For most Patricia firms, the day-to-day hasn't changed.
What has changed is the context. Patricia firms now sit inside a larger portfolio. That isn't bad, and it isn't a forecast. It's just a fact worth noting when you're thinking about how to invest in operational infrastructure over the next several years. The most useful posture is one that doesn't depend on any single IPMS roadmap going one direction or another.
That's where PracticeLink fits. It's the operations layer five of the top 10 US patent filing firms already run alongside their docketing systems, and it works the same way on top of Patricia.
For a broader look at what "IP operations" covers beyond the IPMS, see What Is IP Operations?
What Stays in Patricia When You Add PracticeLink?
Adding PracticeLink doesn't ask you to migrate, reconfigure, or unwind anything you've built in Patricia. The point of an operations layer is to leave the system of record alone.
Prosecution deadlines and statutory dates. Patricia 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.
Foreign agent and party data. Patricia holds the master records for inventors, applicants, foreign agents, jurisdictions, and the relationships between them. PracticeLink references them, doesn't replace them.
Workflow rules and case logic. Whatever Patricia is already doing keeps doing it. The standard prosecution flow, the foreign filing milestones, and the jurisdiction-specific triggers all stay intact.
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 Patricia administrator does not have a migration project. Your docketing team keeps working in Patricia the way they do today. PracticeLink takes the parts of the day that were never really docketing work, the mail sorting, the spreadsheet reconciling, the report chasing, and handles those instead. That part is the whole point.
What Does PracticeLink Add to Patricia Firms?
PracticeLink connects to Patricia and uses the data as the foundation for an operations layer that covers what an IPMS was never designed to do alone. For Patricia firms specifically, here's what that layer does.
Cross-system workflow that ties Patricia to the rest of the stack. Patricia is one system. Your DMS is another. The drafting tool an attorney started using last quarter is another. The shared mailbox for foreign agent correspondence is another. PracticeLink connects to all of them and routes work between them. For an IT team trying to bring order to a sprawling stack, the layer is the thing that makes the existing tools work together instead of one more tool to babysit. A response draft generated by an AI tool gets attached to the right Patricia matter automatically. A document profiled to the DMS gets linked to the matter without anyone manually pasting a reference. The foreign agent's email gets classified and surfaced against the docket.
Dashboards and operational reporting that don't require IT. Real-time views of matter status, workload, deadline density, response cycles, foreign filing pipelines, and bottlenecks. The data is coming from Patricia. The configuration is happening in PracticeLink. Ops directors stop filing report requests and start watching the practice live.
Office action workflow that ties to Patricia docketing. When an office action arrives (US, EP, JP, anywhere), PracticeLink classifies it, links it to the right Patricia matter, and routes it to the right attorney. The response workflow kicks off with built-in checkpoints, task assignments, and deadline tracking tied to the dates already in Patricia. The attorney works the substance. PracticeLink handles the logistics.
US-side forms and citations using Patricia data. USPTO filing packages, IDS citations with cross-family references, forms with smart prefill from Patricia matter and party records. Foreign-language references include English translation pulled from public data. For Patricia firms with US filings, which is most of them, this closes a gap that's historically been filled by spreadsheets and a paralegal's afternoon.
Document intake feeding the matters in Patricia. Incoming mail captured from the shared inbox, classified by document type, linked to the right Patricia matter, routed to the right person, profiled to your DMS. Automatic. Firms running this see mail processing speed improve by 50%.
Client portals and reporting fed by current data. Branded portals and electronic tri-folds pull straight from Patricia 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%.
Soft-docket alongside the statutory docket. Attorneys set their own preparation dates and reminders in PracticeLink without touching the official Patricia docket. Personal task layer, not date-field changes.
Cross-matter and cross-client visibility. Roll up by client, by attorney, by jurisdiction, by technology, by anything in your Patricia data model. A practice leader can see the shape of the whole portfolio in a dashboard instead of running a project to find out. Foreign filing programs that span dozens of jurisdictions become legible in a single view.
How Does PracticeLink Connect to Patricia?
For teams evaluating how the systems connect:
Connection method. PracticeLink connects to Patricia through supported integration methods. The connection runs against the live Patricia database, not a periodic export.
Hosting and security. PracticeLink is cloud-native and hosted on Microsoft Azure. Single sign-on, role-based access controls, encryption in transit and at rest, 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 Patricia. Matter data, dates, party information, custom fields, history, configurations. A change in Patricia shows up in PracticeLink within minutes, with nobody clicking sync. The flow runs one direction. PracticeLink does not write back to Patricia 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, US-side forms and citations (IDS, USPTO 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 Patricia.
Setup and IT lift. The Patricia connection is part of the standard PracticeLink implementation. Your Patricia administrator is consulted, not displaced. No changes to your existing Patricia configuration are required, no new on-prem infrastructure, no firewall changes beyond standard SaaS allowlisting. IT lift is minimal by design, and we can put you in touch with IT leaders at peer firms who ran the same integration so you can hear what it actually took.
What If Your IPMS Roadmap Changes?
This is the question Patricia firms have been thinking about since April. It's also the question every law firm running an IPMS should be thinking about, regardless of vendor.
IPMS consolidation isn't new. The industry has been consolidating for two decades. Platforms get acquired. Roadmaps shift. Migration plans get announced, delayed, revised, and announced again. Most firms running a mature IPMS have been through this cycle at least once.
The pattern is familiar enough that it's worth naming explicitly. A firm picks an IPMS, configures it carefully, builds workflows around it, trains a team on it, and earns years of operational value from the choice. Then the vendor gets acquired, or the platform gets sunset, or the roadmap shifts toward a product the firm didn't buy. The firm now has a decision to make on a timeline the firm didn't set.
The lesson most operations leaders draw from this is straightforward. Don't tightly couple your operations layer to any single IPMS. Keep the IPMS you chose. Layer your workflow automation, document intake, client reporting, and cross-system visibility somewhere that doesn't depend on which IPMS is current.
That's what PracticeLink is.
PracticeLink works with Patricia. It also works with FoundationIP, CPi, Inprotech, and the other major IPMS platforms. The pattern is the same in each case. Read from the IPMS, leave it alone, run the operations layer on top.
If Patricia continues exactly as it is today, your PracticeLink layer continues exactly as it is today. If Patricia evolves into something different, whether that's a new name or a new place inside a larger product family, your PracticeLink layer continues. If your firm eventually decides to move to a different IPMS entirely, for any reason, on any timeline, your PracticeLink layer comes with you.
The orchestration layer doesn't care whose roadmap is current. That's the point.
What a Typical Day Looks Like
A docketing specialist at a mid-market US firm running Patricia 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 Patricia, and routed them to the attorneys and paralegals who need to act on them. Three US office actions, two notices of allowance, a restriction requirement, and a stack of foreign correspondence including an EPO examination communication from one of the firm's German agents and a JP rejection forwarded by a Tokyo associate. All sorted before anyone opened their laptop. The ops director opens a single dashboard and sees the day shape up before standup.
10:30 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 and prepares a US continuation. In the old workflow she'd open Patricia, pull family relationships across jurisdictions, export to Excel, cross-check against the citation tracker she maintains, and reconcile. Now the view is already there. Family members across US, EP, and JP. References already cited at the USPTO, references pending. Foreign-language references with English translations pre-pulled. 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.
2:00 PM. A partner emails the client team. He needs a snapshot of a client's active prosecution work before a 3 PM call. The client team sends a portal link. The portal is already current, pulled from Patricia, formatted to the client's preferences, with the foreign filings broken out by jurisdiction the way this particular general counsel likes to see them. He reads it on the way to the conference room.
4:30 PM. A senior associate prepping a response wants every case where the firm argued the same prior-art reference, across one client's portfolio. 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 the file histories he needs before he leaves the office.
None of this required a change to Patricia. The dates are where they've always been. The configurations are intact. Patricia still runs the docket. PracticeLink runs the operations around it.
If that morning sounds better than the one your team has now, the working session is where you find out what it would take to get there.
What If You're Already Running Patricia?
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 across multiple jurisdictions. The remaining question is whether everything around the IPMS runs with the same operations excellence as the IPMS itself.
If partners file report requests and wait days, that's not a Patricia problem. If ops directors can't watch the practice in real time, that's not a Patricia problem either. If paralegals toggle between Patricia, the DMS, the foreign agent inbox, the soft-date spreadsheet, and Outlook five times before lunch, that's not a Patricia problem. Patricia was built to be the IPMS, not the dashboard, the workflow engine, or the integration hub. 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. Firms like Buchanan Ingersoll & Rooney, Mintz, and Lathrop GPM keep their system of record and run the operations layer on top. 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, and let the operations layer absorb whatever IPMS volatility shows up over the next decade.
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 an operations layer on top of your IPMS.
Common Questions
Does PracticeLink replace Patricia?
No. PracticeLink is an operations layer that sits on top of Patricia. Your docketing team keeps working in Patricia exactly as they do today. PracticeLink reads from Patricia and surfaces the data through dashboards, client portals, US-side forms automation, and operational reporting that Patricia was never designed to deliver.
Can PracticeLink show data from custom Patricia fields?
Yes. Most firms that have run Patricia for years have built custom fields and configurations 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 Patricia configuration?
No. PracticeLink reads from Patricia and doesn't write back to date fields or configurations. Your Patricia administrator is involved in the connection setup but doesn't need to reconfigure anything to support PracticeLink.
What happens if Patricia's roadmap changes?
PracticeLink doesn't depend on any single IPMS roadmap. It works with Patricia today and integrates with FoundationIP, CPi, Inprotech, and the other major IPMS platforms. If Patricia continues as-is, PracticeLink continues with it. If Patricia evolves into something different, or if your firm eventually decides to move to a different IPMS for any reason, the operations layer comes with you. The orchestration layer doesn't depend on which IPMS is current.
What does Anaqua's acquisition of Patrix mean for Patricia firms?
Patrix joined Anaqua in April 2026. For most Patricia firms, the day-to-day hasn't changed. The longer-term question is how to invest in operations infrastructure without tying it to any single IPMS roadmap. That's what an operations layer is for. PracticeLink runs your dashboards, reporting, client portals, and workflow on top of Patricia, and it stays in place whether Patricia continues as it is, evolves into something different, or your firm later moves to another IPMS.
How current is the data PracticeLink shows?
Near real-time. The integration runs against the live Patricia database, not a nightly export. When something changes in Patricia, it shows up in PracticeLink dashboards and client portals within minutes.
Are there office action tools that sync with Patricia docketing?
Yes. PracticeLink manages the full office action response workflow tied to docket dates in Patricia. 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 Patricia. PracticeLink handles the work between receiving the action and filing the response.
Do partners and clients need Patricia 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 a Patricia seat or training.
Does PracticeLink help with foreign filing workflows?
Yes. Patricia is strong on foreign agent relationships and multi-jurisdictional case structures. PracticeLink adds the workflow layer on top: incoming foreign agent correspondence classified and linked to the right matter, deadline reminders for jurisdiction-specific milestones, and dashboards that roll up foreign filing pipelines by client, jurisdiction, or technology.
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 Patricia 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. We can send the full security package before the first conversation, so your IT team can start their review in parallel rather than waiting on a demo.
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.
What does the integration cost?
The Patricia 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.
Can PracticeLink work with other IPMS platforms too?
Yes. PracticeLink integrates with Patricia, FoundationIP, CPi, Inprotech, and others. The pattern is the same regardless of the underlying system. The IPMS 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 Patricia 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 a pilot would scope to. Most firms start with one practice group or one client portfolio, so the first commitment is small and the result is something you can take to the partners. You'll also have a clear answer to the question that's been on your mind since April: how to keep building your operations without it riding on any one IPMS roadmap. Schedule a conversation with our team.