Every IP team has two workflows: the one on paper and the one that actually runs. Mapping the real one takes one afternoon, one matter type, and a whiteboard. Here's the method.
Ask anyone on your IP team to describe the prosecution workflow and you'll get the clean version. Five steps. Clear handoffs. A straight line from PTO correspondence to client update.
Now ask someone to walk you through what actually happened on a specific matter last Tuesday.
Different story. The clean version skips the reply-all thread where three people clarified who was handling the response. It skips the manual folder check because the document didn't auto-file. It skips the "I just pinged Sarah" step that shows up in no system anywhere.
Every firm has two workflows: the one on paper and the one that actually runs. Mapping the real one takes less time than you think. And what it reveals is worth the afternoon.
Why This Matters
Firms that have mapped their prosecution workflows consistently find 30-40% more steps than anyone expected. Not because people are doing unnecessary work. Because the gaps between systems create invisible labor that nobody tracks.
The paralegal who reformats data from one system before entering it into another. The docketing specialist who checks email for PTO correspondence that should have routed automatically. The attorney who keeps a personal spreadsheet of client preferences because the matter management system doesn't store them.
None of these steps show up in a process document. All of them eat time every day.
You don't need a consultant for this. You don't need a six-month project. One matter type. One afternoon. A whiteboard or a shared doc. That's it.
Pick Your Matter Type
Start with utility patent prosecution. It's the highest-volume, most-repeatable workflow in most IP practices. You run it often enough to know the real steps, not just the documented ones.
If your firm is trademark-heavy, pick a trademark registration instead. The method works the same way. The point is choosing something your team does frequently enough that they can describe what actually happens, not what's supposed to happen.
One matter type. Not five. Not "all of prosecution." One.
Six Checkpoints to Trace
Every prosecution workflow passes through six moments where work changes hands or moves between systems. Trace each one honestly.
1. Mail arrives. PTO correspondence hits the inbox. Maybe multiple inboxes. Who sees it first? Does it route automatically or does someone manually forward it? How long does it sit before the right person opens it?
2. Docketing logs it. The deadline enters the system. But what about the context around it? The attachment, the related matter history, the notes about what happened last time this came up. Where does that information go?
3. Attorney gets notified. How? An email? A dashboard alert? A tap on the shoulder during a hallway conversation? And how long between "docketing logged it" and "the attorney actually knows about it"?
4. Work product gets created. The response, the amendment, the IDS update. Where does the attorney draft it? Where does it go for review? Is there a version control system or is it "final_v3_REAL_final.docx" in someone's downloads folder?
5. Filing package gets assembled. Forms, signatures, attachments, fee calculations. How many systems does this touch? How many times does someone re-enter the same data?
6. Client gets updated. Status report, invoice note, portal update. Who handles this? When does it happen relative to the filing? And where does the data come from? If the answer is "I pull it from three places and compile it manually," write that down.
At each checkpoint, capture four things: the system used, the person involved, whether the step is manual or automated, and a rough time estimate. Don't overthink the time. "About 15 minutes" is fine. "Anywhere from 10 minutes to two hours depending on the client" is even better. That variance is data.
What the Map Reveals
You'll see patterns. Every firm does.
The most common: more manual steps than expected. Not big, dramatic failures. Small ones. The copy-paste between systems. The email that serves as a notification because the actual system doesn't alert the right person. The "I just check it every morning" routine that works fine until someone's out sick.
You'll find single-person dependencies. One paralegal who knows where everything is, who carries context in their head that exists nowhere else. That's not a compliment to the paralegal. It's a risk to the firm.
And you'll find steps that exist only because two systems don't talk to each other. A human being serving as the integration layer between tools that should be connected is the most expensive middleware you can buy.
Don't editorialize while you're mapping. Just record what's real. The patterns will be obvious enough.
What to Do With It
Three things. Not ten.
Circle the manual handoffs. Every spot where a person moves information from one place to another by hand is a candidate for error, delay, and wasted time. You don't have to fix them all. But now you can see them.
Identify the single-person dependencies. Ask yourself: if this person is out for two weeks, what breaks? If the answer is "a lot," that's your biggest operational risk. It's also the easiest one to ignore because it hasn't failed yet.
Share the map with someone who wasn't in the room. A fresh set of eyes catches things the people closest to the workflow have stopped noticing. The step everyone works around but nobody questions. The workaround that became permanent five years ago.
The Afternoon Is the Easy Part
Most firms are surprised by what they find. Not because their teams are doing anything wrong. Because the real workflow is always more complex than the assumed one, and nobody had looked at it end-to-end before.
That surprise is useful. It's the difference between "we have a process" and "we understand our process." And it's the starting point for treating IP operations as a real discipline, not just something that happens around docketing.
One matter type. One afternoon. A whiteboard. Start there.
Common Questions
How long does mapping a workflow actually take?
A single matter type, with the right people in the room, usually takes two to four hours. The "one afternoon" promise isn't a marketing line. It's the realistic window for one workflow, one whiteboard, and a few honest conversations.
What if my team can't agree on the "real" workflow?
That's data. If three people describe the same prosecution workflow three different ways, the workflow isn't consistent, which is itself something worth knowing. Capture both versions side by side. The disagreement usually points to a specific handoff that has no clear owner.
Do I need a consultant or project manager to do this?
No. A whiteboard or a shared doc is enough. Consultants help when you're redesigning a process at scale. Mapping what you already do is work your own team can do in an afternoon, and should, because they're the only ones who know the unofficial steps.
Should I map all our workflows at the same time?
Start with one. Utility patent prosecution is the best first candidate for most IP practices. Trademark firms should pick trademark registration. Mapping multiple workflows in parallel dilutes attention and makes it hard to spot patterns. One map done honestly beats five done halfway.