Somewhere on your firm’s system there’s a folder named Production 3. Inside it: several hundred, perhaps even a thousand, PDFs with names like SCAN_004528.pdf. Everyone meant to organize it after discovery closed. Then motions came due, depositions got scheduled, and the team started working around the pile instead of in it.
Meanwhile, the actual case – who said what, which exhibits matter, where the strategy conversation stands – isn’t in that folder at all. It’s scattered:
- The dep outline is a Word doc – somewhere. There are four versions.
- The “which exhibits matter” conversation is spread across a 47-message email thread.
- The chronology is current only in the head of one paralegal or associate, who is also the only person who can find anything.
This workflow is so common that most teams don’t see it as a problem anymore. It’s just how litigation works.
It doesn’t have to be. None of this feels like a crisis on any given workday – it costs an hour here, an afternoon there, and then a scramble the week before mediation, or arbitration or, even worse, trial. Most of what breaks does so early and quietly. You don’t know it’s a problem until tensions are high and you have a looming deadline. The fix is a handful of habits and processes established at the start.
Decide the folder structure before the documents arrive.
A folder structure is really an org chart for your case. It should mirror how the team thinks about the matter.
There’s no single right folder structure, but a workable one might look something like:
- Pleadings
- Motions and Briefs
- Discovery
- Expert Testimony
- Correspondence
- Key Documents & Facts
- Attorney Notes
Each folder can hold sections or subfolders – Discovery might include depositions by the deponent’s name. The process should work the same anywhere within the structure. A few rules that hold up:
- Build it on day one. A clear folder structure invites sorting. A pile just keeps growing.
- Keep it shallow. Two levels, maybe three. If finding a document requires six clicks, people will stop searching and start emailing.
- Name folders according to contents. Not for who dropped the files there.
The test: an associate joins the case in month nine. Can they find the key deposition exhibit without asking anyone? If yes, your structure works. If they have to ask the paralegal – or worse, the first chair – the filing system isn’t working.
Agree on file names the whole team can read.
Every team says they’ll get to naming conventions and clear folder structures. Almost nobody does, which is how you end up with SCAN_004528.pdf sitting next to FINAL_v3_USE THIS ONE.docx.
The convention itself matters less than everyone using the same one. Pick an order – date, document type, party, subject – and hold to it. The specifics will be yours; the consistency is the point.
Then run two tests:
- The scan test. Can someone skim the file list and know what each document is without opening it?
- The search test. When a team member searches six months from now, what will they actually type? A witness name? A date? The subject of the dispute? If the likely search terms aren’t in the file name, the document is effectively lost.
One honest caveat: no software fixes lazy naming. I’ve had a lawyer in a demo put it perfectly – any system “depends on somebody having clean, tidy file naming hygiene.” True. It’s a habit, and it’s on the team. The good news is it takes about two weeks of discipline before it stops feeling like discipline.
Stop making case decisions in email.
Here’s the most expensive habit in litigation collaboration: making decisions in email.
The document lives in one place. The three-week back and forth about what it means lives in another – an inbox (which hopefully has been filed properly and not deleted). When the case goes quiet for two months (they always do) and the team comes back, nobody remembers where the discussion landed. So someone digs through old threads, forwards the wrong version, and the argument happens again.
The alternative is simple: comment and discuss next to the documents, inside the workspace, in the folder where the work is happening.
- The strategy debate about an exhibit sits with the exhibit.
- When the team returns, it’s clear where the discussion left off – who said what, what was decided, what’s still open.
- A new associate onboards by reviewing the workspace, not by asking someone to forward six months of email.
Your inbox is where case knowledge goes to disappear. Stop putting it there.
Link documents – don’t re-attach them.
Every time a document gets emailed, downloaded, and re-uploaded, you’ve created a twin – or worse, a quadruplet. For an exhibit, that means a copy of the same document sitting in three folders, and nobody certain they’re all looking at the same one. For a working document – a timeline, a case narrative – it means versions, and the question “is this the current one?” starts eating your meetings. Different problems, same cause: the document has more than one home.
The better practice: every document gets one home, and everywhere else it’s needed, it’s linked, not copied.
Think about a deposition outline. Question 14 references a key exhibit. If the exhibit is linked right there, whoever picks up the outline has the exhibit one click away. If it’s not, they go hunting – and the hunt happens again for every person, every time. Link it once, and the question and its evidence travel together for the life of the case.
Establish one source of truth.
Much of the above can be done with the tools you already have. A shared workspace, a disciplined team, and consistent naming conventions will take you a long way.
But I’ve watched teams try to hold these habits together with willpower, so I built them into Moxx. The Workbook is organized as folders that behave like paper folders – customizable, draggable, structured the way your team thinks. It won’t let you upload a document without designating a folder (that’s on purpose – no file dumps). Comments, tasks, and outlines sit in a drawer right beside the documents they’re about. And every document lives in one master place, linked wherever it’s needed, so “which version?” stops being a question anyone asks.
None of it is complicated. It’s the discipline above, built in – so your team doesn’t have to remember to have it.
Less time hunting. More time on strategy. That’s the case that wins.
The Moxx Workbook: customizable folders, named and arranged the way your team works.