The point where work gets scattered
A file called ‘final’ can be edited several times. Without stable versions, neither party can readily tell which scope, price or dates they saw when they made a decision. This guide addresses review and recordkeeping, not the legal effect of an amendment.
Preserve the earlier original and its context
Keep the earlier signed original in the form you received it, including the associated signing information available through your existing process. Use a working copy for edits. A screenshot, a pasted signature image or a summary of the old terms is not the same review object as the complete earlier document.
Record the title, date and version label, plus any attachments that were part of the review. Avoid renaming several different files to the same ‘final’ label. If the earlier file is missing, obtain the actual record through the process you used before making claims about what it contains. Do not reconstruct it from memory and describe the reconstruction as the original.
Describe the proposed changes in plain language
Prepare an identifiable new version or other change document appropriate to your existing agreement process. Explain the changed deliverables, responsibilities, price, dates and attachments. Show unchanged context where the reader needs it to understand the revision. A change summary helps navigation, but the complete proposed terms still need to be available for inspection.
Sample review note: ‘Please review Project Agreement v3 dated 4 August alongside v2. The proposed changes add a sixth page, increase the total by $300 and move the delivery date to 22 August. The new page uses the existing review process. Scope attachment A is updated; the other listed attachments are unchanged.’ Check that the documents actually match that summary.
- Current signed version remains available.
- Proposed version and changed attachments are identifiable.
- The change summary matches the complete proposed text.
Request review without assuming consent
Give the intended reviewers the actual changed terms and enough context to ask questions. Use the document review and consent process suitable for the engagement. If the identity or authority of the reviewer is uncertain, resolve it before treating a response as the decision. A reply about scheduling is not necessarily a response to the revised price.
Sample wording: ‘Please check the complete v3 terms and let me know if the added page, revised total and new date reflect our discussion. We will follow our usual agreement process once questions are resolved. I have not started the additional page.’ Do not copy earlier consent into a new file or describe silence as approval of the revision.
State the working version after the decision
Once the relevant review is complete, tell the people doing the work which version and accepted changes to use. Update the production checklist and related payment references to reflect the actual decision. Retain the earlier version and the new record so a later question can be traced without erasing the sequence.
If the client declines or asks another question, keep the proposal open and clarify the effect on current work. If the documents conflict, pause the affected decision and seek appropriate qualified help rather than improvising a legal conclusion. Version labels and careful records make review clearer; they do not establish universal enforceability, replace needed advice or determine the rights of either party.
Keep the context with the conversation
Messages can help prepare a change summary from the versions and context you choose. Inspect the full originals through your existing document process and keep the actual review decision. Return to the client conversation with the current version identified. Review any revised payment or appointment separately and inspect its confirmed result before reporting it complete.
Understand your Twin · See Business access and metered AI usage