How to handle last-minute changes to a contract before completion
Last-minute changes to a contract before completion are a routine part of legal practice. A client requests an amendment, the lender asks for a clause adjustment, or a drafting error surfaces the afternoon before exchange. The risk is not that changes arrive — it is integrating them without a structured re-check.
Why last-minute changes carry the highest risk
Once a contract has been reviewed and completion is close, there is a temptation to assume the document is sound and only the specific change needs attention. That logic works when the change is entirely isolated. It rarely is.
An adjustment to the purchase price affects, at minimum, the figure in the body of the contract, any deposit calculation derived from it, and potentially the financial statement the client has already approved. Correcting a party's name means checking every instance of that name across the document — the title page, the operative clauses, the execution block, and the ID the practice has on file. A change to the completion date can make existing references to notice periods and conditions inconsistent.
The problem is not the change itself. It is treating the change as if it exists in isolation when it does not.
Before drafting any amendment
The first step is to record the change before making it. This does not require a formal process — a short note in the matter file recording what is being changed, who requested it, and when is sufficient. That record matters if the amendment is later disputed or if there is a question about whether the change was agreed by all parties or made unilaterally.
The next step is to assess the scope. The practical question is: does this change touch any other piece of data already reviewed? An amendment that affects a name, a figure, a date, or a property description should be treated as potentially systemic until shown otherwise.
If the change is genuinely limited — a typographical correction that alters no substantive data — it can be made and checked in place. If the change touches data that appears more than once or that is linked to other fields, the correct approach is to re-read the relevant sections of the contract with that data in mind.
Running the post-amendment check
The post-amendment review does not need to be as wide as the original review, but it must be systematic. In practice:
1. Find every instance of the amended data. If a party's name is corrected, search the document for every instance of that name. If the price changes, look for every figure in the document that is derived from or related to that number.
2. Confirm the change is applied consistently across all instances. In longer contracts, it is common for a correction to be made in one clause and missed in another. That inconsistency survives into the executed document.
3. Cross-check the amended data against the source documents. If the change affects a party's name, go back to the ID document on the matter file. If it affects the purchase price or a property description, go back to the document that records the agreed terms or the Land Registry entry.
4. Check that adjacent text has not shifted. Word processors move text when paragraphs are inserted or deleted. A targeted correction can accidentally eliminate a closing punctuation mark, introduce a page break in the wrong place, or push an execution clause onto a new page in a way that creates ambiguity about what was signed.
What to note in the matter file
When the deed or contract is executed, the matter file should reflect that a late amendment was made and that a review followed it. A short note recording the date, what changed, and that the change was cross-checked against the relevant documents is enough.
That note has practical value. If a party later claims the contract does not reflect what was agreed, or if a discrepancy emerges with a related document, the matter file note allows you to reconstruct what changed, when it changed, and why.
When to delay completion
There is a point at which the volume or complexity of late changes makes the right decision a postponement rather than proceeding under pressure. The threshold is not fixed, but there are clear signals: when changes affect structural elements of the transaction (the parties, the property, the price, or any condition precedent); when they arrive so close to completion that a careful review is not possible; or when the changes are verbal and have not yet been incorporated into a revised draft.
Delaying completion is uncomfortable. Executing a document with an error that could have been caught is a worse outcome for everyone involved.
If you'd like support with document review and verification in your practice, VerifyAct has tools built for that.