Addendly

Can a contract change be approved by email?

· Redazione Addendly

Date: 8 November 2026. Author: Addendly Editorial Team. Publisher: X20 Digital Trust Services S.r.l.

Approval by email can help document a contract change, but it does not automatically satisfy every formal requirement. Before using it, establish which transaction is being amended, what the contract requires and how the process connects the decision to the document. A code received in the client's inbox does not by itself turn an approval into a qualified electronic signature.

The practical question therefore has two parts: what agreement do the parties want to reach, and what evidence will remain? This guide concerns private service and supply relationships. It does not determine validity in a particular case, cover public procurement or suggest replacing formalities required for particular transactions.

Read the amendment clauses first

Find the contract actually concluded and look for provisions on changes, communications and authorised representatives. A clause may require a signed order, a particular address or action by a designated manager. Recording a response in an app does not establish that this procedure was followed. Any uncertainty about the clause should be resolved before collecting approval.

Check the referenced attachments too. The commercial form may describe a different procedure from the specification, or the operational contact may lack spending authority. The fact that someone has coordinated the project so far is insufficient. Identify who acts for the client and on what basis, while avoiding collection of additional personal documents without a concrete need.

Understand what electronic signature means

The eIDAS Regulation distinguishes different tools. Article 25 of Regulation (EU) No 910/2014 of 23 July 2014 prevents denial of legal effect and admissibility as evidence solely because a signature is electronic or not qualified. The same article gives qualified electronic signatures an effect equivalent to handwritten signatures. The first principle does not mean every click meets every national form requirement. Source: eIDAS, Article 25.

A signature image, an email response and a process involving a code are not interchangeable descriptions. Classifying the tool requires its actual process characteristics and the provider's documentation. The commercial label “online signature” is insufficient to conclude that a signature is qualified. AgID identifies qualified services and their providers on its qualified trust services page.

Give the request a precise subject

State which contract is to be amended, which activity changes and which version is being sent. The recipient must be able to read the content before deciding. If price and timing appear in an attachment, identify it and make it accessible alongside the proposal. Avoid requesting general agreement to the project when the decision concerns one specific change.

Explain whether the amount replaces an earlier item or increases the total. State the tax basis and what the stated days mean. “Three extra days” may describe the effort required or a delay to delivery: do not leave the reader to choose an interpretation. Any points still under discussion must remain identifiable.

Keep the context without inventing certainty

Keep the version presented to the client, the sending communication and the response received. If a code is used, preserve the available process information according to the service rules, without including the secret code in a public report. System records may document a sequence; they do not automatically establish the person's authority or resolve every identity dispute.

In Italy, Article 20(1-bis) of Legislative Decree No 82 of 7 March 2005 governs the written form and evidential effect of electronic documents. Outside the cases prescribed for signatures or processes meeting specific requirements, suitability and evidential value are subject to judicial assessment considering the document's characteristics. Source: Italian Digital Administration Code, Article 20.

Do not therefore claim that a register guarantees an agreement cannot be challenged. Instead, check that exported information allows reconstruction of what was sent and the decision actually recorded. This distinction also helps when no dispute arises: a colleague must understand which proposal should guide the work.

A fictional example

An agency proposes adding two pages to an agreed website. Change A-12, version 1, states EUR 400 plus VAT and delivery on 20 November. The contact replies “fine, but just one page”. This response should not be recorded as approval of the complete proposal: it describes a different request. The agency prepares version 2 covering one page and its price, then collects a decision on that document.

If the second response comes from a different person, the file should also make that step visible. Authority still needs to be checked. The example does not decide whether a particular email concluded a contract; it shows why content and attribution of the decision must be assessed together.

When to stop the ordinary process

If a transaction requires a particular form, the contract requires a different tool or the approver's authority is unclear, the usual email process does not settle the matter. The appropriate procedure must be identified before proceeding. Even a qualified signature does not remove every additional requirement for the transaction, such as possible involvement of a public official.

Check the completed file before handing it to the team responsible for delivery. They should find the approved document without having to infer its content from an informal conversation. If the evidence remains incomplete, record the uncertainty and seek the missing information instead of replacing it with a confident status label. That practical check supports reliable project administration while leaving legal conclusions to the assessment the transaction requires.

To understand how to keep proposals, versions and decisions together, read about Addendly's features.