How Can a Company Avoid Paying for Work That Has Not Been Delivered as Agreed?
A company entered into a contract with a contractor to construct a residential tower for a total contract price of SAR 2 million. The parties agreed that half of the contract price—SAR 1 million—would be paid upfront upon signing, while the remaining SAR 1 million would be paid once the building was completed and handed over.
After receiving the advance payment, however, the contractor stopped work entirely after completing only 30% of the project. The company was forced to engage another contractor at additional cost and suffered financial losses because part of the amount already paid related to work that had never been completed.
From a contractual perspective, the company’s exposure arose largely because the payment structure was not adequately tied to actual progress and acceptance of the completed work. A more protective structure would have divided the contract price into milestone payments linked to defined stages of completion and formal acceptance.
Given the significance of this issue, this article examines how companies can reduce this type of exposure, using construction contracts as an example of contracts performed in stages.
What Is the Scope of Work in a Contract?
The scope of work identifies and describes, with sufficient precision and completeness, the tasks, works and deliverables that the performing party is required to complete. It also sets out the timetable for the different stages of performance, the period allocated to each stage, the specifications that must be satisfied and the applicable delivery dates.
In a construction contract, for example, the scope of work may include:
- The tasks and works the contractor is required to perform.
- The approved drawings and materials to be used.
- The final deliverable and its technical specifications, together with the specifications applicable to the partial deliverables produced at each stage.
- The project schedule, including the overall completion period, the duration of each stage, and the dates for completing and delivering the relevant milestone.
The scope of work therefore depends on several interconnected elements and should be defined comprehensively and precisely in the contract.
A poorly defined scope can expose the company to payments for incomplete or non-compliant work and may also create disputes over whether a particular milestone has actually been completed.
Setting Acceptance Criteria for the Work
Acceptance criteria should establish clear and measurable conditions for each stage of performance. These may include the required specifications, the inspection or testing procedure, the person or entity authorised to approve the work, the period for raising comments, the process for remedying defects, and the document evidencing acceptance.
Where appropriate, payment for each stage should be made conditional upon completion of the inspection process and issuance of written acceptance, rather than upon delivery alone.
Saudi Arabia’s Civil Transactions Law links payment for certain work with inspection and acceptance. Article 469(2) provides that where the work consists of several parts, or where remuneration is calculated on a unit basis, the contractor must be paid in proportion to the work completed after it has been inspected and accepted.
The parties may also identify the entity responsible for inspection. This may be the company’s internal technical team or an independent third party, such as an accredited engineering consultancy.
For example, a construction contract may provide that a particular stage will not be accepted until it has been inspected by an independent engineering consultant, confirmed as compliant with the agreed specifications, and documented through a written acceptance certificate to which the corresponding payment is linked.
When Is Delivery Considered Accepted?
Accepted delivery refers to delivery that discharges the performing party from its obligation to deliver the relevant work.
Article 475 of the Civil Transactions Law provides that a construction contract ends upon completion of the agreed work. For the work to be regarded as completed, the company must have approved and accepted it and taken delivery in accordance with the applicable contractual arrangement.
An important distinction should nevertheless be made here.
Discharge at this stage relates to the contractor’s delivery obligation. Other obligations may continue after handover, including obligations relating to latent defects and structural defects in buildings and construction works, including those governed by the mandatory insurance regime for latent defects, which applies for ten years, or for any longer period agreed between the parties where applicable.
The position differs depending on whether the contract itself specifies the procedure for acceptance.
Where the Contract Specifies an Acceptance Procedure
Contracts commonly identify a procedure that must be followed before completed work is treated as accepted.
This may involve issuing a handover or acceptance report signed by the company after inspection and approval of the work.
The legal effect of such a document depends on its content rather than its title. A handover report may relate to preliminary, conditional or final acceptance, and each may have a different contractual effect.
- Preliminary acceptance: This takes place after the contractor has completed the relevant work and the company takes delivery for inspection and verification against the agreed drawings and technical specifications. The warranty period may begin from this point, while the contractor remains subject to its continuing warranty obligations.
- Conditional acceptance: This occurs where the company accepts the work subject to reservations, typically because non-material apparent defects remain outstanding. The contractor is required to remedy those defects within an agreed period. Until that occurs, the acceptance does not necessarily discharge the contractor from its remaining obligations, including completion of the delivery process itself.
- Final acceptance: This ordinarily occurs after the applicable warranty period has expired and the relevant requirements for final handover have been satisfied. Its legal effect depends on the contract and the applicable law.
The contract may instead require an acceptance certificate or another specified document. Where the parties have expressly agreed that acceptance occurs only upon completion of a particular procedure, delivery should be assessed by reference to that procedure.
Where the Contract Does Not Specify an Acceptance Procedure
If the parties have not agreed on how completed work is to be accepted, the nature of the work and the applicable custom may become relevant.
Certain types of work require technical testing before acceptance, while others may be capable of acceptance following a visual inspection or another process recognised for that type of work.
For this reason, the contract should preferably specify the acceptance procedure expressly rather than leave the question to potentially uncertain customary practices that may not reflect the company’s expectations or the needs of the project.
Does Silence Amount to Acceptance of Delivery?
As a general rule, silence does not amount to acceptance.
Article 37 of the Civil Transactions Law addresses the legal significance of silence in contracts. It provides, in substance, that silence by the person to whom an offer is made does not constitute acceptance unless the parties have agreed otherwise or circumstances indicate acceptance. It also addresses certain situations involving previous dealings between the parties or an offer made solely for the benefit of the recipient.
Applied to the acceptance of delivered work, the position may be considered as follows.
General Rule: Silence Does Not Constitute Acceptance
If a contractor completes the work and places it at the company’s disposal, the company’s failure to respond does not, by itself, necessarily amount to acceptance.
Where the contract establishes a specific acceptance procedure, acceptance should ordinarily be documented through that procedure rather than inferred simply from silence.
There may, however, be circumstances indicating otherwise, including:
- Where the contract expressly provides that the company’s silence for a specified period will constitute acceptance.
- Where there is clear conduct indicating acceptance, such as the company taking over and using the completed work without objection in circumstances supporting that conclusion.
Circumstances in Which Silence May Be Treated as Acceptance
Article 37 also recognises circumstances in which silence may carry the effect of acceptance.
This may arise, for example:
- Where previous dealings between the parties establish a course of conduct under which silence has been treated as acceptance in relation to similar performance.
- Where the relevant performance or offer is made solely for the benefit of the recipient, subject to the conditions governing the application of the provision.
There is also a separate issue where the contractor formally calls upon the company to take delivery.
Under Article 468 of the Civil Transactions Law, where the person who has completed the work requests the other party to take delivery and the latter fails to do so within the relevant period, legal consequences may arise from that failure.
Accordingly, a company should not assume that simply remaining silent will always preserve its position. The contract should clearly define the period for inspection, the procedure for raising objections and the circumstances in which acceptance will be deemed to have occurred.
How Should Payments Be Linked to Project Milestones?
Linking payments to actual milestones is one of the most important contractual mechanisms for reducing the risk that a company pays for work that has not been completed or accepted.
A milestone-based payment structure can be organised as follows:
- Divide the work into clearly defined consecutive stages. Each stage should specify the relevant deliverable, its commencement and completion dates, and the payment due upon acceptance of that stage.
- Allocate the contract price across those stages so that each payment reasonably corresponds to the value of the work completed and accepted. This reduces the risk of paying for work that has not yet been performed. Depending on the circumstances and the contract, the contractor may nevertheless be entitled to payment for a completed and accepted portion of the work where that portion can be independently delivered and used.
- Make satisfaction of the agreed acceptance criteria a condition to payment. The payment should therefore become due upon completion and acceptance of the relevant milestone, rather than merely because a particular date has passed.
- Provide a clear mechanism for rejected work. This may include allowing the contractor a defined period to remedy the defects or establishing other contractual consequences, including termination where the contract permits it.
This structure reflects the principle that payment should follow performance of the corresponding contractual obligation rather than the mere passage of time.
If the relevant work has not been completed in accordance with the agreed standards, the contractor should not automatically become entitled to payment for the uncompleted or unaccepted portion. This does not necessarily prevent payment for any part that has been properly completed and accepted, subject to the contract and the circumstances of performance.
For the company, the objective is straightforward: the amount paid at any stage should remain aligned as closely as possible with the value of work that has actually been completed and accepted.
Protecting the Company Starts With the Contract
Reducing the risk of paying for undelivered work begins with the contract itself.
A clearly defined scope of work, measurable acceptance criteria, a documented acceptance process and milestone-based payments can substantially improve the company’s contractual position when work is performed in stages.
The contract should therefore be structured around the commercial reality of the project: what must be delivered, how completion will be verified, who has authority to accept it, and when payment becomes due.
Where a company is entering into a material project or staged-performance contract, reviewing these mechanisms during contract drafting can help align payment obligations with actual performance and reduce avoidable contractual exposure.
Frequently Asked Questions About Scope of Work and Acceptance Criteria
How Should Acceptance Criteria Be Drafted in a Contract?
The contract should identify the required specifications, the inspection and testing procedure, the person or entity authorised to accept the work, the period for raising comments, the process for remedying defects and the document that formally records acceptance.
What Can a Project Owner Do If a Contractor Stops Work After Receiving an Advance Payment?
Contractual protection is generally stronger where payments are linked to completed and accepted milestones rather than where a substantial amount is paid upfront without being tied to specific deliverables.
What Happens If the Completed Work Does Not Meet the Agreed Specifications?
The contract should establish a clear mechanism for dealing with rejected work, such as giving the contractor a defined period to remedy the defects or applying other contractual consequences in accordance with the agreement.
How Can a Company Link Payments to Project Milestones?
The project can be divided into clearly defined stages, with each stage assigned a specific deliverable, timetable, acceptance criteria and corresponding payment. The payment then becomes due only once the milestone has been completed, inspected and accepted.
What Is the Difference Between Preliminary, Conditional and Final Acceptance?
Preliminary acceptance takes place after completion of the work for inspection and verification. Conditional acceptance occurs where the company accepts the work subject to outstanding defects or reservations that must be remedied. Final acceptance takes place once the applicable contractual requirements, including any relevant warranty-stage requirements, have been satisfied.
Does a Company’s Silence Regarding Delivered Work Amount to Acceptance?
As a general rule, silence does not by itself amount to acceptance. However, the contract, the parties’ previous dealings, their conduct and specific statutory provisions may affect the result in particular circumstances.
Does Delivery of the Work Automatically Mean That It Has Been Accepted?
Not necessarily. Acceptance depends on the procedure agreed in the contract and may require inspection, testing and the issuance of a handover report or acceptance certificate.
Can a Company Withhold a Payment If a Milestone Does Not Meet the Acceptance Criteria?
Where the contract makes payment conditional upon completion and acceptance of the relevant milestone, the passage of time or physical delivery alone should not be sufficient to trigger payment for work that has not satisfied the agreed acceptance requirements.
How Can a Company Avoid Paying for Work That Has Not Been Completed or Accepted?
The contract should clearly define the scope and deliverables for each stage, establish measurable acceptance criteria, link each payment to completion and formal acceptance of the relevant milestone, and set out a clear procedure for rejected or non-compliant work.


