How to document a contract change before sending it to the client
Draft date: 8 November 2026. Author: Addendly Editorial Team.
To document a change, prepare a proposal that connects it to the original contract and clearly identifies the version submitted to the client. Describe the work affected, quantify the financial impact and explain how delivery will change. Then keep the proposal together with the decision you receive. A general message of approval, separated from the document it concerns, leaves a practical question unanswered: which change was accepted?
This guide concerns the organisation of records for a private contractual relationship. It provides practical criteria, rather than a contract template suitable for every situation. Before sending a proposal, check the contract terms, the authority of the person approving it and any applicable requirements concerning form. The process described does not replace the procedure required for public procurement or transactions subject to particular formalities.
Start with the document you are changing
Retrieve the contract and the attachments that were actually agreed. Record their reference and date, then identify the part affected by the request. If other changes have already been approved, the comparison must start from the position resulting from those changes as well. Using only the original quotation can bring back activities that were removed or count a cost twice.
Distinguish the client's request from the proposal you prepare in response. The request might be a sentence spoken during a meeting; the proposal should explain what you are willing to deliver and on what terms. Keeping both makes it possible to trace the origin of the change without attributing details to the first conversation that were only settled later.
Describe a difference that can be checked
Assign a number to the change and a version to the document. State what was previously planned and what is now proposed, avoiding expressions such as “update as agreed”. If the change concerns an attachment, identify the file and its revision. A photograph or screenshot may explain the context, but should not be the only place where an essential condition appears.
Make the boundaries of the proposal explicit as well. A change to a software function may require migration work that is not included in the stated price; replacing a material may leave installation unchanged. Readers should be able to identify what is being added or replaced without reconstructing earlier conversations. If something remains undecided, mark it as open instead of presenting the document as ready for final acceptance.
Separate the cost of the change from the project total
Show the value of the change with the correct sign: a reduction should not look like an additional charge. Specify the VAT treatment and make clear whether the price covers all costs envisaged for that change. If the amount depends on quantities that are not yet known, describe the calculation method and the conditions for later confirmation. An estimate and an agreed price are different pieces of information.
Show the project total before the proposal separately from the total that would result if it were approved. Do not include a pending change in the summary as though it had already been accepted. Also check that the amounts being compared use the same tax basis. A VAT-inclusive total next to a VAT-exclusive change, without an explanation, can make even a correct calculation difficult to understand.
For timing, state the current delivery date and the proposed date, explaining what the additional days mean. If the schedule depends on materials arriving or the client providing information, describe that dependency. Do not turn a conditional date into a firm promise merely because the form requires a date field.
Connect approval to the version sent
Before sending the document, check the recipient and the capacity in which they are acting. Control of an email account does not, by itself, establish that someone can change a contract on behalf of an organisation. Authority must be checked in the context of the particular relationship and applicable rules; a list of commercial contacts is no substitute.
Send a stable version and record the reference used in the approval request. If you change the price during negotiations, prepare a new version and request a decision on that version. Do not reuse a response relating to the previous document. A rejection or a request for clarification should also remain connected to the correct proposal, so that anyone returning to the file can understand why the activity did not proceed.
A fictional example
A supplier is developing a portal for EUR 8,000, excluding VAT. The client asks for an additional data export. Proposal V-04, version 1, describes the fields to be exported, states a price of EUR 600 excluding VAT and moves delivery back by two working days. The proposed total becomes EUR 8,600 on the same tax basis, assuming no other changes.
During the discussion, the client also requests a date filter. The supplier prepares version 2 with the new description and a price of EUR 750. The first proposal remains in the file as superseded. The decision must refer to version 2: keeping only an “OK” received before the filter was added would not clarify which work had been agreed. The example illustrates a method for organising records without determining the legal effects of an actual response.
Keeping the records and understanding electronic signatures
Archive the version sent, the attachments it refers to and the decision, together with the relevant time records. Check that an authorised colleague can reconstruct the sequence without accessing your personal inbox. Before closing the project, test document export and check that the attachments are readable. The retention period should reflect the actual obligations and needs associated with the relationship.
Article 25 of the eIDAS Regulation distinguishes the effects of electronic signatures: a signature is not denied legal effect solely because it is electronic or not qualified; a qualified signature has the equivalent legal effect of a handwritten signature. This does not make every approval using a code a qualified signature. Source: Regulation (EU) No 910/2014 of 23 July 2014, Article 25, consolidated text.
In Italy, Article 20(1-bis) of Legislative Decree No 82 of 7 March 2005 governs electronic documents. Outside the specifically defined cases, suitability for satisfying a written-form requirement and evidential value depend on judicial assessment of the document's characteristics. It is therefore inappropriate to promise that an email code will suffice for every transaction. Source: Italian Digital Administration Code, Article 20.
To see how to record changes and collect a client's decision, read about Addendly's features.