How to manage document versions before a deed completes
The most common version-control problem in legal practice isn't saving the wrong file — it's not knowing which file is current. When a contract goes through several rounds of amendment before completion, reviewing the wrong draft is easy to do and hard to catch until it's too late.
Why it happens more often than it should
Most conveyancing matters and commercial transactions involve more than one version of the key documents. A draft contract arrives, the other side marks it up, the lender adds special conditions, and a week later there's a folder with four files named contract_v2.pdf, contract_final.pdf, and contract_final_REVISED.pdf. Without a clear rule for which one is live, the risk of reviewing an outdated text is real, not theoretical.
Solicitors and conveyancers working under time pressure are particularly exposed. When a completion date is fixed and documents are still arriving, the temptation is to press on rather than pause and confirm which version applies. That's exactly when a version-control error can go unnoticed.
How to establish which version is current
Before any document review begins, the matter file needs one document marked as the working version. This isn't a formality — it's the foundation for every check that follows.
Two approaches work reliably:
Timestamp and source. If the document arrived by email, the message date and sender are the clearest reference. For documents received through a portal or by other means, note when you received it and from whom, directly in the matter file.
Written confirmation from the instructing party. When there's genuine uncertainty about which version is final, ask for explicit confirmation. A short email saying "this is the version to proceed on" is more reliable than any file-naming convention, however carefully designed.
Once a version is marked as current, no later document should replace it without a clear note in the matter file explaining what changed and who authorised it.
Keeping the matter file unambiguous
Earlier drafts shouldn't be deleted — they can be important for understanding what changed and why. But they should be clearly separated from the document you're working from.
A practical approach: keep a single section or folder in the matter file labelled current version, containing only the live document. All earlier drafts go into a draft history folder. Anyone picking up the file mid-review — a colleague covering your desk, a supervisor checking progress — can see immediately which document applies.
If the file is entirely digital, a simple prefix convention achieves the same result: [CURRENT] for the live version, [SUPERSEDED] for everything before it. No specialist tool required, and it can be adopted by any practice immediately.
What to do when a revised version arrives close to completion
This is the most common pressure point: completion is tomorrow, and a revised contract arrives this afternoon. The important thing is not to start a new review before formally closing the previous one.
A reliable sequence:
- Pause the review of the earlier version and note in the matter file where you had got to.
- Receive the new version and verify it arrives with something to back it up — an email, a note on file, something that explains the change and who asked for it.
- Compare the new version to the previous one to identify exactly what changed. A targeted check of the amended clauses is usually sufficient, but you need to know precisely where the differences are before limiting the scope of the review.
- Mark the new version as current, move the earlier draft to history, and resume the review from the beginning for any sections affected by the changes.
If the revised version arrives so late that a complete review cannot be finished before completion, that is a matter for the fee earner or supervising solicitor to decide — not for the reviewer to absorb silently. What the reviewer should do is note clearly in the file what arrived, when, and that the review could not be completed against the final text.
The note that closes the loop
When the pre-completion review is done, the matter file should contain a short note recording which version of the document was reviewed and when the review was completed. It doesn't need to be lengthy — a single line identifying the document, the date of that version, and the date the review was finished is enough.
That note is what lets you answer, months later, if anyone asks which text was checked before the deed was signed.
If you'd like support with document review and verification in your practice, VerifyAct has tools built for that.