A docketing system catches the date. It doesn't move the response, the IDS, or the client update. See what carries the work after the date lands.
8:12 on a Monday. The docketing clerk opens the morning PTO mail, works through it, and by 9 the docket is clean. An office action on a continuation, response due in three months, matter number attached, examiner name captured, soft date set six weeks ahead of the hard one. Right tool, right time. The date got caught the moment the mail posted, exactly the way a docketing system is supposed to catch it.
Then the response has to get drafted. Checked against the file history. Routed to the attorney. Signed off. The IDS the case implies has to get built. The client should probably hear something.
None of that is in the docket. The date is. The work the date sets off is not.
That's the gap this whole piece is about. Not a broken docket. A docket doing its job perfectly while the work it triggers runs on inboxes, memory, and a spreadsheet somebody keeps in a tab.
What is a docketing system actually built to do?
Track dates. That's the job, and the good ones do it well. FoundationIP, CPi, Inprotech, and the rest. A docketing system is the source of truth for when. Statutory deadlines. Filing dates. Hard dates, soft dates, the alerts that fire at the windows. Who owns the matter, what status it's in.
Give the docket its due. It's the right tool for that job, and nothing on your desk does it better. When people say their docketing system is "old" or "limited," they usually mean it doesn't do things it was never built to do. That's not a flaw. That's asking a calendar to write the response.
Here's what a docketing system does not do. It doesn't draft the response the deadline demands. It doesn't check that draft against what the firm argued in the parent. It doesn't walk the IDS from a list of references to a filed form. It doesn't chase the attorney buried in three other finals. It doesn't tell the client anything. It records that a thing is due. It does not move the thing.
Where does the caught date actually go?
Follow one date and the gap gets concrete.
The office action posts. The docket catches it. Response due, say, in three months. Perfect so far. Now trace what has to happen before that caught date turns into a filed response, because every step is a handoff and not one of them lives in the docketing system.
- Someone has to read the action and check it against the file history, because on a continuation what the firm argued in the parent can limit what it's still allowed to claim. - The draft has to get attached to the right matter, in the right family, so the next person who opens the case sees it. - It has to get routed to the responsible attorney for the actual legal call. - The sign-off has to get chased, because that attorney is heads-down on other work. - Any IDS the case implies has to get built and filed on its own clock. - The time has to get billed to the right matter. - And the client has to get told, in whatever format that client expects.
The docket knows step zero. The date. Steps one through seven run on people, inboxes, and a paralegal's memory of who signs off on what. That's where a caught date goes to wait. And a date that's caught but not carried is still a date that can slip.
Why does a caught deadline still slip?
Because catching and moving are two different jobs, and only one of them has a system.
Watch what a soft date really is. It's the docketer's calculation, worked backward from the hard date, that says start this by here. It sits in the docket as a flag. But the actual starting, the routing, the nudge to the attorney, the follow-up when nothing comes back, none of that is automatic. It runs on whoever remembers. When that person is out, the soft date is a color on a screen.
The blunt version. Most missed deadlines I hear about weren't missed because the date was wrong. The date was right. The date was caught. The work it should have kicked off never got moving, or got moving and stalled at a handoff nobody was watching.
A drafted response in an inbox is not a filed response. An IDS built in someone's head is not an IDS on file. A status the client keeps asking about is a status somebody has to stop and rebuild. The docket says green the whole time. It isn't lying. It just can't see any of that.
What moves the work between the date and the client?
Right now, for most firms, the answer is people plus adhesive. Somebody carries each output to the next step by hand. That works until it's Friday, three attorneys are traveling, and the paralegal who knows the client's reporting quirks is on PTO.
The fix isn't a smarter docketing system. Your docketing system is already the right tool for its job. And it isn't ripping the stack out for one all-in-one platform that promises the handoffs disappear if you just migrate everything onto it. That's a migration project wearing a modernization costume, and the firms that lived through the last "one platform to rule them all" cycle can tell you how it went.
The fix is making the work move. Cleanly, visibly, from the moment the date is caught to the moment the client sees the result. The date the docket caught needs to trigger the draft, land it on the matter, route it to the attorney, hold it for review, and push the update to the client, without a person re-keying it between five screens every morning. This is one piece of a bigger question, which is what it really takes to modernize IP operations without buying your way into more sprawl. Modern isn't more tools. Modern is whether the work moves.
How PracticeLink moves the work a date sets off
PracticeLink sits on top of the docketing system a firm already runs and moves the work the docket can't. It doesn't replace the docket. It reads from it.
When the docket catches a date, PracticeLink is what carries the work that date triggers. It routes the response to the right matter and the right attorney, with the file history and the parent's prosecution attached, so the attorney reviews the legal call instead of first reconstructing where the case has been. It holds the draft for that sign-off and records it where the next person to open the case can see it. It runs the IDS and forms sequence through review to filing, so the paralegal's job shifts from assembling the package to checking it. It reads client-specific reporting rules from one place, so the report that needs a partner's eyes gets held for a partner's eyes every time, not just when the person who remembers the rule is in. Bring an AI tool, a document system like iManage or netDocuments, or a patent search into that flow and the same thing happens. The output finally has rails.
The docket keeps doing what it's good at. Catching the date. PracticeLink does the part nobody sells you a product for. Carrying the work from that caught date all the way to the client. That division of labor is why five of the top ten US patent filing firms run their operations this way, and why clients like Mintz, Buchanan Ingersoll & Rooney, and Lathrop GPM do too. Mail sorts about 50% faster and forms prep about 45%. But the number our clients actually bring up is the five or so billable hours a week their attorneys stop losing to chasing where things went. Client reporting satisfaction sits at 98%, because the client is finally seeing what happened on the matter instead of a status someone had to rebuild by hand.
See how PracticeLink works
Frequently asked questions
Does a docketing system move the work after it catches a deadline?
No. A docketing system tracks dates. It's the source of truth for when something is due, and the good ones do that job well. What it doesn't do is move the work the date sets off: drafting the response, checking it against the file history, routing it to the attorney, chasing the sign-off, building the IDS, billing the matter, and telling the client. Those steps run on people and inboxes unless something is built to move them.
If the date was caught correctly, how does the deadline still get missed?
Catching and carrying are two different jobs. A soft date can sit in the docket as a flag while the work it should trigger never gets moving, or stalls at a handoff nobody's watching. Most missed deadlines I hear about had a correct, caught date. What failed was the work between the caught date and the filed response, which usually runs on whoever happens to remember it.
Is the docketing system the problem?
No, and that's the point. The docket is the right tool for tracking dates, and firms that ask it to also route mail, chase sign-offs, and update clients are asking the wrong system the wrong question. The gap isn't the docket. The gap is that the work a date triggers has no system moving it. Fix that and the docket gets to keep doing what it's already good at.
Do I need to replace FoundationIP, CPi, or Inprotech to fix this?
No. Replacing your docketing system doesn't move the work any better, it just resets what you already trust for tracking dates. The fix is connecting the docket you run to the steps that follow it, so a caught date actually triggers the draft, the review, and the client update. Integrate, don't replace.
What's the difference between catching a date and moving the work?
Catching a date is recording that something is due, on the right matter, with the right response type. That's the docket's job. Moving the work is everything that has to happen next: the draft, the check against file history, the routing, the sign-off, the IDS, the billing, and the client update. A date can be caught perfectly and still go nowhere if nothing moves the work it sets off.
Where do soft dates actually break?
Soft dates are a calculation worked backward from the hard date, and they live in the docket as a flag. The break isn't the flag. It's that the starting, routing, and follow-up the soft date implies run on whoever remembers them. When that person is out, the soft date is a color on a screen and the work behind it doesn't move.