Litigation document management: organizing the active case file

Every matter accumulates documents; a litigated matter accumulates a record. That isn't a rhetorical distinction. In a transactional matter the documents are instruments and drafts, they're almost entirely generated by the parties, and the file's job ends when the deal closes and the closing binder is assembled. In a litigated matter, a large share of the documents arrive from outside your control — the other side's filings, the court's orders, productions from opposing counsel, subpoena returns. Their dates, versions, and provenance are themselves potentially at issue.

Most firms notice this the way you notice a load-bearing wall: only when something cracks. A matter runs on the firm's standard template through the pre-suit phase perfectly well. Then a complaint gets filed, and within a few months the Documents area holds four files whose names all contain some form of the word final, two copies of the same production set at different stages of redaction, and an exhibit nobody can trace back to the Bates range it came from. Nothing went wrong procedurally. The organizing scheme simply stopped matching the shape of what it was holding.

The fix is unglamorous and mostly free: decide the litigation-specific structure and conventions before the first production set lands, rather than after. Strip the phrase of its software connotation and that decision set is what litigation document management actually consists of: the branches a litigated matter needs, how to name a document based on the state it's in, how to version drafts against a filing deadline, how Bates ranges and exhibit numbers relate to filenames, and where a general document system genuinely stops being enough. Each of those is a decision a firm makes once and reuses on every case.

One framing note before the specifics: the conventions below are operational rather than jurisdictional, so where a rule, a scheduling order, or a standing order says something different, that governs and the convention bends. Check those before adopting anything here firm-wide.

Outside litigation, a filename that carries date, type, and a short description is enough. Inside litigation it isn't, because the same document exists in several states and the states are what people are actually asking about. A motion drafted on Tuesday, filed on Thursday, and served on Thursday afternoon is one document in three conditions. Only one of them — the accepted, stamped filing — is the operative version of the record.

Put the docket number first on anything that has one. A leading docket entry number makes the pleadings folder sort itself into the same order the court sees, which turns the folder listing into a usable chronology at no cost. Where the docket number isn't yet known — a document being drafted, or a state system that assigns numbers differently — a leading ISO date does the same job and stays sortable. The general pattern is covered in the naming conventions guide; the litigation-specific addition is the status token.

Make the status a token, not a tone. The word FINAL isn't a status. It's an aspiration, and it's why a matter ends up with four files claiming it. A small closed vocabulary works far better — a document is a draft, an as-filed copy, a served copy, or a received copy, and the token appears in the same position in every filename. 0042 - 2026-04-15 - MSJ Opposition - FILED.pdf and 0042 - 2026-04-15 - MSJ Opposition - POS.pdf answer the two questions people actually ask, in a document list, without opening anything.

Keep the stamped copy the operative one. Electronic filing systems generally return a copy bearing the filing stamp or header the system applies, and that returned copy — not the PDF you uploaded — is what should be promoted to the court-file branch. It isn't the same file you submitted; depending on the system it may also carry an added cover or notice page. A year later, the stamped version is the one that answers questions. Pulling those returned copies back down out of federal and state portals is its own workflow, walked through in the court documents guide and, for the federal system specifically, the PACER and ECF guide.

One caution on renaming: the convention is worth applying to documents your firm creates and to documents you download, but be deliberate about renaming a file that arrived as part of a production. Production filenames frequently encode Bates ranges or map to entries in a load file, and renaming them quietly breaks that correspondence. The rule most teams land on is that anything inside a production set keeps the name it was delivered with. The firm's convention applies to the folder around it.

The single most common structural mistake in a litigation matter file is treating a Bates range or an exhibit number as though it were a filename. They aren't names. They're coordinates in two separate addressing systems that both point at the same underlying documents, and a folder tree can only express one hierarchy at a time.

Bates numbers address pages within a production. They're assigned upstream — in a PDF tool for smaller matters, in a review platform for larger ones — and applied at the moment a production is prepared. So a document produced in two different productions can carry two different ranges. The organizing consequence is simple: the production set is the unit of filing, kept intact exactly as delivered, and the Bates range identifies material within it. What that filing workflow looks like in practice, including load files and privilege log handling, is covered in the discovery documents guide.

Exhibit numbers address documents within a proceeding — a deposition, a motion, a hearing, a trial — and the same document routinely picks up several over the life of a case. Because both systems point at the same documents from different directions, the thing that reconciles them is not a folder but an index: one spreadsheet per matter mapping each document to its Bates range, every exhibit designation it has carried, the witness or filing it was used with, and where the file lives. It's a modest artifact that quietly becomes the most-used document in the matter.

Trial binders are a view, not a new copy. When trial approaches, the exhibit list gets built from the index and the binder — physical or electronic — gets assembled from documents that already exist in the matter. Copy everything fresh into a Trial folder instead and you end up with two divergent versions of an exhibit, one with a sticker and one without. Assemble from the index, keep the assembled set as its own record once it is final, and let the index remain the thing that says which underlying documents it was built from.

Numbering conventions themselves vary more than people expect. Deposition exhibits are often numbered sequentially across an entire case by agreement among counsel, so that exhibit 47 means the same document in every deposition; trial exhibit ranges are commonly allocated by party in the court's pretrial order. Neither is universal. Read the scheduling order and any standing order before the first deposition rather than renumbering afterward.