How to Manage Multiple Versions of a Pleading

There are few worse moments in litigation than discovering that the draft served on the other side was not the version counsel approved. It happens more easily than lawyers like to admit: a partner marks up a copy, someone works on a different one, filenames multiply, and under deadline pressure the wrong file goes out. A pleading passes through many hands and many revisions, and the discipline that keeps the right one authoritative is not about clever software. It is about knowing, at every moment, which version is the real one and who said so.

Let status carry the version, not the timestamp

The most common failure is treating the most recently modified file as the current one. Modification time tells you what was touched last, not what was approved. Instead, make status explicit in the filename or the matter record, using a small fixed vocabulary: working, for review, approved, filed, served. A document labelled "approved" should mean a named person approved it, on a known date, not that someone opened it this morning to fix a typo.

Keep one authoritative copy and make it obvious

At any point there should be exactly one version that counts, and it should be impossible to mistake for the others. Everyone on the matter needs to know where it lives and how it is marked. The earlier drafts do not get deleted, but they get demoted clearly, so that a colleague under pressure reaches for the right file by default rather than by luck. Ambiguity about which copy is authoritative is the gap through which the wrong draft escapes.

Record who changed what, and who approved it

A pleading's history is part of its reliability. For every substantive change, you want to be able to say who made it and on whose instruction, and for every approval, who gave it and when. This matters when a client asks why a paragraph was pleaded a particular way, and it matters even more if the pleading is later challenged. Keep the trail light but real:

• who drafted each substantive version
• who reviewed and approved it, with the date
• what changed between the approved version and the filed one

Compare the filed copy against the approved one

Approval and filing are two different events, and the gap between them is where errors hide. Before treating a matter as settled, compare what was actually filed or served against the version that was approved, and do it including the annexures and schedules, which are the parts most likely to drift out of sync. If the two differ, you want to find out from your own comparison, not from opposing counsel pointing it out in open court.

Archive the history without cluttering the present

Prior versions are evidence of process and should be retained, but they should not compete with the current copy for attention. Move superseded drafts into a clearly marked history, leaving the working area holding only what is live. A drafting workspace that tracks versions and status alongside the matter, such as Juniorlawyer, makes this separation natural, because the approved and filed copies stay flagged while the earlier drafts remain available without getting underfoot.

Managed this way, version control stops being a source of anxiety and becomes quiet infrastructure. The right pleading is always identifiable, its approval is always traceable, and the moment of filing is a deliberate act rather than a gamble on which file happened to be open. That certainty is worth far more than the small effort of labelling drafts honestly as they move through the process.