Extra work: how to prepare a proposal with clear prices and timing
Date: 8 November 2026. Author: Addendly Editorial Team. Publisher: X20 Digital Trust Services S.r.l.
To present extra work, compare the request with the current contract, describe the difference and separate the additional price from the project total. Then state the effect on delivery and collect a decision on the exact proposed version. Do not treat additional work as approved merely because it was discussed in a meeting or added to an activity list.
This guide provides an organisational method for private service and supply relationships. It does not determine when an activity creates entitlement to additional payment. That depends on the contract, the nature of the work and applicable rules. Public procurement and procedures requiring specific formalities are outside its scope.
Check whether the request actually changes the assignment
Before calculating a price, retrieve the agreed scope: the accepted quotation, contract and referenced attachments. Compare the new request with what was already included. Correcting a defect should not automatically be presented as a new feature; equally, a requirement arising later may be a genuine addition. If the boundary is disputed, describe the point requiring clarification before turning it into a financial item.
Record the request with its date and project reference. Recording who made it may help, but a request alone does not establish authority to commit the client. The technical contact may explain a requirement without being authorised to approve spending. Check the contractual procedure and distinguish those discussing the content from those making the decision.
Describe the activity so it can be compared
A clear proposal shows the starting position and the proposed result. Instead of “report integration”, state which report will be added, what data it contains and the delivery format. Where a technical attachment is needed, give it a stable name and version. Avoid references to files called only “latest” or “final”: those names become ambiguous after another revision.
Also clarify relevant exclusions. If the client requests a monthly export, do not leave it implicit that historical data migration and user training will be included. There is no need to multiply exclusions: select those that could affect the decision or price. For each unresolved point, identify the missing information.
Show the calculation and its conditions
If the price is fixed, state the change amount and its tax treatment. If it depends on quantities or hours, describe the measurement units and counting method. Explain whether it is an estimate requiring confirmation. A number without these details may look like a final price even when the supplier intended only an approximate indication.
Present the current total separately from the proposed total. A EUR 500 change to a EUR 6,000 project produces EUR 6,500 only if there are no other changes and the figures use the same tax basis. A summary should distinguish approved changes from pending proposals. If a new proposal replaces an earlier one, do not add both.
Explain the effect on the schedule
State the agreed date and proposed new date. Clarify whether days are working days and which dependencies prevent a definite date. The arrival of materials or availability of client data may affect scheduling. The days needed to perform the work do not always equal the delivery delay, particularly when other activities continue in parallel.
If the change can be performed without moving delivery, make that visible. If choosing between alternatives affects the timetable, present them before approval. Do not promise to absorb a delay to make the price more attractive when operational capacity has not been checked. The document should reflect a plan the delivery team can actually use.
A fictional example
A maintenance company has an assignment worth EUR 3,000 plus VAT to replace several components. The client requests additional work on a second installation. Proposal E-07 describes that installation, states EUR 450 plus VAT and identifies one additional working day, with proposed delivery on 18 November. The proposed total is EUR 3,450 plus VAT.
During verification, the company discovers that a part must be ordered. It updates the proposal before the final sending, separating the working day from the wait for materials. The client can then assess price and schedule without discovering the dependency after deciding. This example is invented and does not assess a real company's entitlement to payment.
Connect the decision and preserve the file
Archive the version sent together with attachments and the actual response. A request for a discount or clarification should not be recorded as complete approval. When a material condition changes, prepare a new version and collect a decision referring to it. Superseded versions help reconstruct negotiations but should not be confused with the current operational plan.
An electronic signature does not remove the transaction's formal requirements. Article 25 of Regulation (EU) No 910/2014 of 23 July 2014 distinguishes non-discrimination against electronic signatures from the equivalence of qualified signatures to handwritten signatures. Source: eIDAS, Article 25. For electronic documents in Italy, Article 20 of Legislative Decree No 82 of 7 March 2005 also matters. An email code alone does not guarantee compliance with every required form.
Before closing the proposal, check that the person responsible for delivery can distinguish a pending extra from work already authorised. This final administrative check helps keep the working schedule consistent with the evidence in the file. Where a decision is missing, record that gap rather than interpreting silence as an agreed change.
To see how to collect changes, versions and decisions in one register, read about Addendly.