A docketing system tracks dates. An operations layer makes them actionable across mail, the DMS, AI tools, and client reporting. Add the layer.
Here is what a docketing system can't tell you on a Tuesday morning.
The senior paralegal opens the docket, scans the week. Everything is green.
The docket is wrong. There's a soft date that quietly slipped on Friday because nobody updated the spreadsheet that tracks the conditional triggers. There's an office action that came in over the weekend, sitting in the docket clerk's mail folder, not yet routed to the matter. There's an AI-drafted response written against last month's claim set, because the agent never saw the amendment that went out three weeks ago. The client portal still shows yesterday's status, even though three matters changed between 5 PM and 9 AM.
The docket says fine. Nothing about the morning is fine.
This isn't a docketing failure. The docket did its job. It tracked the dates it was given, on the events it was told about, by the people who told it. The work that's broken is the work that lives between the dates. And the work between the dates is what runs the firm. It's where matters get late, write-offs get bigger, and clients get wrong updates.
What is a docketing system built to do?
A docketing system is a reference system. The source of truth for when. Statutory deadlines. Filing dates. Owners. Status flags. Hard dates. Soft dates. Alerts at windows. That is what it does. Every modern docketing system does it well. FoundationIP. CPi. Inprotech. Others.
It does not coordinate work. It does not move a piece of mail from a queue to a matter. It does not hand context to the next person in a workflow. It does not surface what changed in the last twenty-four hours to a client portal. None of that is what a docketing system was built for. The firms that ask their docketing system to do those jobs are asking the wrong system the wrong question.
What does an operations layer do that a docketing system doesn't?
The operations layer is what makes the docketing reference actionable across the rest of the firm's tools. Six concrete jobs it does that no docketing system on the market does:
Routes incoming PTO mail to the right matter. The docket knows the matter exists. It doesn't know the email arrived in someone's inbox at 7:32 AM and is still sitting there at 4 PM.
Surfaces soft dates and conditional triggers. Soft dates aren't statutory. They live in spreadsheets, paralegal heads, attorney-specific routines. The operations layer is where they get tracked across the practice.
Coordinates handoffs. Paralegal to attorney. Attorney to client. Client back to paralegal. Foreign agent to in-house counsel. The docket records the deadline. The operations layer moves the work between the people.
Hands context to AI tools. Matter family. Workflow state. Client preferences. Without that, an AI tool drafts against stale information and produces a fluent answer to the wrong question.
Aggregates real-time work-in-flight. Not just "responses due in the next 30 days," but where every matter is, right now. Which paralegal queues are backed up. Which attorney has three responses in draft. Which client has matters waiting on approval.
Ties what changed in the docket to what gets shown to the client. When a soft date moves, the client portal reflects it. When an examiner mails an action, the next client report flags it. The operations layer closes that loop.
Three meanings of "orchestration" in vendor pitches this spring
The word "orchestration" is showing up in three different vendor pitches right now. They are not the same thing.
The first is AI-to-AI orchestration. An AI agent hands tasks to another AI agent inside a single drafting workflow. One drafts. One searches. One reviews. The output is a fluent draft. This is real, it's useful, and it sits above the workflow layer, not in place of it.
The second is network orchestration. A cross-firm marketplace where corporate IP departments find outside counsel without manual referrals. Some pitches compare it to Upwork or Deliveroo. Useful for the work-finding problem. It doesn't help the work get done once it's found.
The third is workflow orchestration. What an IP operations team needs every Tuesday morning. Mail intake reaches the docket. The docket reaches client reporting. Both reach the AI tools the partners are asking about. The "eight to ten tools" pain every vendor pitch names this spring is about this layer.
All three exist. None of them are the same problem. Adding a marketplace doesn't fix the eight tools. AI agents talking to each other don't fix the eight tools. The thing that fixes the eight tools is the layer that connects them.
Do I need to replace my docketing system?
The pitch we hear most often from firms evaluating IP technology this year is some version of "we're considering replacing our docketing system." Sometimes it's because the contract is up for renewal. Sometimes it's because a new platform pitch promised all-in-one. Sometimes it's because two firms came together in a merger and a decision is forced.
The replacement question is almost always the wrong question. Your docketing system is doing what it was built to do. Replacing it doesn't fix the routing problem, or the soft-date problem, or the AI context problem. Those problems sit between the docketing system and the rest of the firm. They don't sit inside it.
The right question is: what sits around the docket, and is that working? If the answer is "spreadsheets, paralegal heads, and email," then the missing piece is the operations layer. Not a different docketing system.
Where does PracticeLink fit?
PracticeLink is the operations layer. It reads from the docketing systems firms already chose, including FoundationIP, CPi, and Inprotech. It connects them to mail intake, document management, AI tools, client reporting, and forms. No migration. No rip-and-replace. The firm keeps the docket it knows. PracticeLink coordinates everything else around it.
Five of the top ten US patent-filing firms run PracticeLink on top of their existing docketing stack. The platform processes over 700,000 documents annually. The pattern across those firms is the same: the docket stays, the operations layer arrives, and the work between the deadlines moves cleanly for the first time.
What this comes down to
A docketing system is the source of truth for when. The operations layer is what turns that truth into work that moves. Most vendor decisions framed as "do we replace our docketing system" are really questions about an operations layer that's missing.
Naming the right layer is most of the work. If you are evaluating IP technology this year, the question to start with is not "should we replace our docketing system?" It's "what sits around our docket, and is it working?" The cost of naming it wrong shows up in write-offs, not in the renewal contract.
Common Questions
Do I need to replace my docketing system to add an operations layer?
No. The operations layer reads from your existing docketing system and coordinates work across the rest of your tools. PracticeLink integrates with FoundationIP, CPi, Inprotech, and others. There's no migration and no replacement.
What does an IP operations layer actually do?
Six concrete jobs: routes incoming mail to the right matter, surfaces soft dates and conditional triggers, coordinates handoffs between people, hands context to AI tools, aggregates real-time work-in-flight, and ties docket changes to what the client sees in the portal. None of these are jobs a docketing system is built to do.
How is an operations layer different from a network or marketplace?
A network is a marketplace between firms — corporate IP teams discovering outside counsel. An operations layer is inside a single firm — work moving between the firm's own systems and people. Both can exist. They aren't the same problem. The operations layer fixes the daily friction that vendor pitches name as the "eight to ten tools" complaint.
Does PracticeLink work with FoundationIP, CPi, or Inprotech?
Yes. PracticeLink reads from each of these and connects them to mail intake, the DMS, AI tools, client reporting, and forms. Firms keep the docketing system they've already chosen.
What does the docketing system still do once an operations layer is in place?
Everything it was built to do. The docket remains the source of truth for statutory deadlines, filing dates, owners, and status. The operations layer doesn't take that work over. It uses the docket as the reference system and adds the coordination work the docket was never designed to do.
How does this connect to AI tools the firm is already using?
AI tools need matter context, workflow position, and guardrails to act responsibly. Without an orchestration layer that holds those in one place, AI drafts against stale or partial information. With one, the AI reads from the same source of truth the rest of the firm uses. See Why AI Tools Fail Without an Orchestration Layer for the deeper version.
This post is part of our Pillar 2 series on the IP Operations Orchestration Layer. For the foundational framing, see The IP Operations Orchestration Layer. For how this connects to AI tools, see Why AI Tools Fail Without an Orchestration Layer. For the broader category we are naming, see What Is IP Operations?