Why law firms still track matters in spreadsheets
Spreadsheet matter tracking persists in legal ops for rational reasons. Here is what actually breaks, and when a case record is worth the switch.
Walk into almost any legal ops function and ask to see how matters are tracked. A surprising number of the time, the answer is a spreadsheet. Not a neglected one. A good one, color-coded, with conditional formatting and a tab per practice area and a column for next action. Someone maintains it carefully. They are a little defensive about it, and they should be, because it works better than the systems they were told to replace it with.
This post is not an argument that those teams are doing it wrong. It is an argument about what the spreadsheet quietly cannot do, when that gap turns into a problem, and how to tell whether you are anywhere near that line.
The spreadsheet is a rational choice, right up until it isn’t
It helps to start by being honest about why spreadsheet matter tracking is so durable. The teams that use it are not behind. They evaluated the alternatives and the alternatives lost.
The heavyweight enterprise case platforms want a six-figure contract and a six-month implementation before anyone tracks a single matter. The generic CRMs are built around contacts and deals, so a matter becomes a contact record bent into a shape it was never meant to hold. The project tools track tasks beautifully and have no concept of a case, a respondent, or a privileged document. Against all of that, a spreadsheet is free, it is instant, it bends to whatever the team needs this week, and everyone already knows how to use it.
So the spreadsheet survives because it is the only option that respects the team’s time. That is a real point in its favor, and any honest case for moving off it has to concede that first.
The trouble is that a spreadsheet is a record of states, not a record of actions. It tells you where a matter is right now. It does not tell you how it got there, who moved it, or when. For a lot of work, that distinction never matters. For matter tracking in a firm or a legal ops team, it is the entire job, and it stays invisible until the day someone asks.
What actually breaks
The failure is rarely dramatic. The spreadsheet does not crash. It just turns out to have been missing something all along, and you find out at the worst possible time.
The audit trail has to be reconstructed, because it was never recorded. When a regulator, an auditor, or opposing counsel asks who accessed a matter, what changed, and when, the spreadsheet has no answer. Version history might show that a cell changed last Tuesday. It will not show who changed it, why, or what it said before. So someone spends a week reconstructing the trail from email threads and memory, and the reconstructed version is exactly the kind of after-the-fact narrative that invites more scrutiny, not less. A real audit trail is valuable precisely because nobody decided to start keeping it. It already exists when the question arrives.
The documents live somewhere else, all of them. The matter facts are in the spreadsheet. The signed engagement letter is in a signing tool. The evidence is in a shared drive. The compiled exhibit set was Bates-numbered by hand in a PDF editor and emailed around. Four systems, no connective tissue, and a chain of custody that exists only in the head of whoever last touched the file. The moment that person is on leave, the matter is harder to defend than it should be.
Sensitive fields are visible to everyone or to no one. A spreadsheet shares at the file level. Either a colleague can open the matter tracker and see the complainant’s name, the respondent’s history, and the working notes, or they cannot open it at all. There is no way to let an analyst update a status without also showing them the identity of the person under investigation. Field-level and row-level security are not features a spreadsheet can approximate. For confidential matters, that is not a limitation, it is a liability.
None of these are exotic edge cases. They are the ordinary obligations of legal work. The spreadsheet handles the visible part of the job, the part where a matter moves from intake to closed, and silently drops the part that a record is supposed to carry.
It comes down to what your work is judged by
There is a test that cuts through it. Ask what happens when someone external reviews your matters.
If the honest answer is “nothing much, we track them for our own coordination,” then the spreadsheet is probably fine and a case management system would be overhead you would resent. Plenty of internal tracking is exactly this, and it does not need a system of record.
But if the answer is “an auditor could ask, a regulator could request, a matter could end up in front of a judge, an internal investigation could be challenged,” then the spreadsheet is carrying a weight it was never built to hold. The work is being judged by the record it leaves, and the record is the one thing the spreadsheet does not actually keep.
That reframing matters because it separates the teams who genuinely need to move from the teams who are being sold a migration they do not need. The trigger is not company size or matter volume. It is whether the record is the deliverable.
When the migration is finally worth it
For years, the math did not work. If the only way off the spreadsheet was a six-figure platform and a half-year project, then most teams were right to stay put. The cure cost more than the disease, and the disease was usually survivable.
What changed is the floor. Matter tracking software that keeps the audit trail, the documents, the signature workflow, and the security model inside one case record no longer requires an enterprise budget or an implementation partner. That is the only reason the calculation flips. A team can stand up real legal matter management without betting a quarter of work on getting it live.
The point worth holding onto is structural, not promotional. A defensible matter record needs three things a spreadsheet cannot give it. First, an audit trail that records every action with attribution, by default. Second, document workflow that keeps everything attached to the matter itself: the engagement letter, the signed envelope with its routing history and signer identity, the version history, and the Bates-numbered export. Third, field-level and row-level security so the right people see the right things. When those are native, the record is a byproduct of doing the work. When they are not, the record is a second job you do later, under deadline, from scattered sources.
This is the gap Avikto is built to close. Attribution, field-level and row-level security, an inline document and signature workflow, and configurable audit-log retention are how the system behaves by default, with CJIS-aligned security practices at the Professional tier rather than as an enterprise upsell. Professional is $499 per month with unlimited users, which is roughly what a mid-size team already spends on the PDF licenses it uses to Bates-number exhibits by hand. The difference is that the trail comes with it.
If your matters live in a spreadsheet today, the useful next step is not a feature comparison you will never check against. Take one matter type, the one most likely to be reviewed by someone outside your team, and walk through what its record would look like in a system designed around it.