If your best lawyer went on leave tomorrow, how much of what they’re working on would the rest of the team know? Not the big, obvious stuff. The details. Where things stand, what was promised, what’s still outstanding.
Every GC will tell you their team manages its legal matters. Of course they will. But press on what “managed” means day to day, and you’ll usually find one person holding most of it in their head, a status update whenever someone happens to ask for one, maybe a spreadsheet that was accurate the day it was made and hasn’t been touched since. That’s not management. That’s memory with a law degree attached, and it holds up fine right until the person holding it is on leave, in back-to-back meetings, or gone.
I’ve had GCs tell me, half joking, that they could probably run the whole portfolio from memory if they had to. Which might even be true. But they shouldn’t have to, and most of the time they’re the only one who can.
A lot of what gets sold as matter management doesn’t really manage anything either. It’s a login screen bolted onto a spreadsheet. It’ll record a status, sure, but it won’t hold the emails, the documents, or the conversations that give that status any meaning. Some don’t even have their own document storage, so the contract’s still sitting in someone’s inbox somewhere. It doesn’t chase anything, doesn’t move anything forward. It just logs what already happened, after the fact, which isn’t really management at all.
Making matter history available
Legal work doesn’t live in silos, so I’ve never seen the point in software that pretends it does. Every task, email, document, file note, decision, and action taken on a matter should sit inside that matter, not scattered across whoever’s inbox happened to touch it that week. That’s basically the whole premise behind how we built LegalOS.
LawVu Assistant sits across all of it, and it’s easier to picture it than describe it. Someone types “open a matter for this,” and it’s open, categorized, right team already on it. “Assign this to Bob by Friday,” and it’s assigned, sitting inside the matter it belongs to. Chasing an overdue approval used to mean a Slack message and a follow up two days later. Now it’s done, and it’s sitting in the same place as everything else on that file. We call it Ask to Answer becoming Ask to Act, mostly because a request that used to get you information now gets something done.
It’s easy to talk about all this from legal’s side, but whoever’s waiting on the work has a stake in it too, and they’re usually the one left hanging longest without a system. A sales lead waiting on a contract review. An HR partner waiting on an employment matter. Neither of them cares about the legal detail, they want to know where things stand, and the only way to find that out without a system is to go interrupt a lawyer who’s in the middle of something else. Put the matter in LegalOS and they can just look for themselves.
A matter has a beginning, a middle, and an end, and usually only the beginning gets written down anywhere, and even that’s patchy. What happens in between lives wherever the lawyer working it left it, which is fine, right up until that lawyer isn’t around to ask. Say a similar dispute turns up 18 months later and lands on someone who wasn’t even at the company back then. With the record intact, they can see exactly how it played out and why. Without it, they’re starting cold, or crossing their fingers a colleague half remembers a case from a couple of years back.
I heard something close to this from a customer a while ago. Their team used to burn 15 or 20 minutes working out where to even start on a request, because the information was scattered across three or four places. These days it’s closer to two minutes, because it’s all sitting in one spot. Doesn’t sound like much on its own but multiply that across a year of requests and it’s a genuinely different amount of time back. Another customer’s contract turnaround dropped from around three weeks to under one, and when that number landed in front of their board, it got a reaction.
None of this is about replacing anyone’s judgment, by the way. It’s about not asking someone’s memory to carry things it was never built to hold. Most of the tools legal teams have had access to just digitized the same habits rather than fixing the actual system, so the memory problem never really went away. It just got a nicer interface.
Your team already manages matters, that part’s fine. The real question is what happens to all of it the next time someone goes on leave, changes roles, or leaves the company altogether. If the honest answer’s “we’d have to piece it back together,” that’s not really a people problem. That’s a system that was never quite there to begin with.
This is the second in a seven-part series looking at what sits inside a legal operating system, one capability at a time. Next up: what happens when a contract stops being a document you review and starts being data you can use.
