In the world of construction projects, the cost of an error is not always measured by wasted materials or lost time. Sometimes, it is measured by lost contractual rights.
A decision that was never documented, a change implemented without formal approval, or a notice that was not submitted within the required timeframe may appear to be a minor issue during project execution. Yet, it can later develop into a dispute worth millions of riyals.
Against the backdrop of the unprecedented construction and infrastructure boom taking place across the Kingdom of Saudi Arabia, these seemingly minor contractual details have become some of the most significant challenges affecting the success and long-term sustainability of projects.
Among the dozens, and sometimes hundreds, of matters that arise on a daily basis throughout the life of a project, three recurring practices stand out. Over time, they often evolve from simple observations into complex claims involving substantial time and cost implications.
First: Continuous Design Changes — When Construction Progresses Before the Design Is Complete
In projects delivered under accelerated schedules, construction activities may commence before all designs and technical details have been fully completed.
This approach is understandable in major projects where reducing the overall delivery period is a key objective. However, it also carries contractual risks that cannot be overlooked.
A design change does not merely involve revising a drawing or replacing one material with another. It may result in the re-execution of completed works, changes to the sequence of activities, increased labour and equipment requirements, or delays to the works of other contractors.
Problems often arise when a contractor is instructed to implement a change urgently, while several fundamental questions remain unanswered:
- Was the instruction issued by a contractually authorised party?
- Was the change formally approved?
- Who will bear the associated cost?
- Has its impact on the project programme been properly assessed?
On some sites, instructions are issued during meetings or site inspections, and the contractor begins implementation in good faith to maintain progress.
However, when the works are later valued, a dispute may arise as to whether those works constitute a variation or whether they were already included within the original contractual scope.
At that point, the flexibility intended to support project delivery becomes a source of dispute.
The solution is not to prevent changes. Change is a natural feature of construction projects, particularly large and complex developments.
What is required is a clear and controlled process that begins with identifying the change, continues with assessing its technical, financial and time-related consequences, and concludes with its formal approval and documentation before implementation, or as soon as reasonably practicable where urgent site conditions require immediate action.
Second: Poor Correspondence Management — When the Facts Are Lost Between Messages
construction projects are not managed solely through drawings and programmes. They are also managed through correspondence.
Every instruction, approval, reservation, delay and site obstruction may later require a contemporaneous record demonstrating when it occurred, who was responsible, how the parties responded and what impact it had on the works.
Nevertheless, some projects continue to rely heavily on telephone calls, informal messages and conversations through applications such as WhatsApp, because they are viewed as faster and more practical for day-to-day communication.
The issue is not the use of these communication methods in itself. The problem arises when the parties rely on them without converting important decisions and instructions into formal correspondence that preserves the sequence of events and protects the parties’ contractual positions.
A site engineer may receive an instruction to carry out additional work, acknowledge it through a brief message and immediately proceed with execution.
Several months later, a team member may leave the project or the project management structure may change, leaving behind only a fragmented conversation that is difficult to connect to the technical and contractual records.
The risk becomes even more serious where the contract requires a notice to be submitted within a specified period.
If the notice is not issued on time, the affected party may find itself engaged in a dispute not about whether the event or loss actually occurred, but about whether the required contractual procedure was properly followed.
Other common failures include not documenting meetings, issuing minutes that do not accurately reflect all decisions, or failing to object to minutes containing incorrect or incomplete information.
In such cases, the right is not lost because the event did not occur, but because the contractual narrative of that event was not recorded at the appropriate time.
An effective correspondence management system should therefore clearly identify:
- The parties authorised to issue instructions.
- The approved formal communication channels.
- The required response periods.
- The numbering, filing and retention procedures for correspondence.
- The process for tracking contractual notices and related deadlines.
Documentation is not a bureaucratic exercise. It is the institutional memory of the project when personnel change and accounts of events begin to differ.
Third: The Absence of a Claims and Variations Management Plan from Day One
One of the most common misconceptions is that a claim is a file prepared at the end of the project, after delays and additional costs have accumulated and the dispute has already materialised.
In reality, a properly prepared claim does not begin when the final claim report is drafted. It begins at the moment the relevant event occurs.
Where access to a site is delayed, a design change is issued, or progress is disrupted by another party, the event should be recorded immediately.
It should then be linked to the affected activities, supported by relevant documents, daily records, photographs and resource data, and assessed on an ongoing basis.
Waiting until the end of the project often means attempting to reconstruct a story that developed over months or years using incomplete documents and the memories of employees who may no longer be working for the company.
The contractor may have incurred genuine additional costs but may be unable to separate them from its original cost base.
The programme may have been affected, but without regular updates showing the actual path of delay.
The relevant instructions may exist, but they may be scattered across emails, meeting minutes and personal conversations.
At that stage, preparing the claim becomes an exercise in searching for evidence rather than presenting an organised account of events that was properly documented and analysed when it occurred.
This is why a structured claims and variations management plan should be established from the outset of the project.
Such a plan should include:
- Standard notice templates.
- A central event and variation register.
- Clearly defined responsibilities among the site, planning, cost control and contracts teams.
- A periodic process for reviewing entitlements, risks and potential exposure.
This approach does not require the parties to adopt an adversarial position, nor does it mean turning every project event into a formal claim.
Rather, it enables management to understand the impact of decisions at an early stage and to take corrective action before the issue escalates.
Responsibility Does Not Rest with One Party Alone
It is easy to blame the contractor for weak documentation, accuse the employer of issuing excessive changes, or hold the consultant responsible for delayed approvals.
The reality, however, is more complex.
Disputes are often the result of accumulated practices across all parties: incomplete instructions, delayed responses, outdated records, and decisions made under time pressure without adequate assessment of their consequences.
Reducing disputes therefore requires a shared contractual culture, rather than a narrow focus on protecting the position of one party alone.
The employer must ensure that the scope is sufficiently clear and that decisions are made without unnecessary delay.
The consultant must manage approvals and instructions within clearly defined authority.
The contractor, for its part, must do more than simply execute the works. It must document events, maintain proper records and comply with the procedures set out in the contract.
When all parties operate within a clear and disciplined framework, the contract becomes a means of regulating the relationship rather than an early battleground for disagreement.
Contract Management Is Not Merely Paperwork
Contract management is still viewed by some as a supporting function that becomes relevant only when a problem arises.
In major projects, however, it is an integral part of engineering and project management. An engineer who understands the time and cost consequences of a change is better equipped to make sound decisions.
A project manager who actively monitors correspondence and contractual notices is more likely to identify risks before they develop into crises.
A company that effectively connects its site, planning, cost control and contracts teams is better positioned to protect its rights and manage its obligations.
Good contract management does not obstruct the project. It provides greater clarity.
Its purpose is not to manufacture claims, but to prevent unexpected consequences.
Prevention Begins with the Details
There is no single formula capable of preventing every engineering dispute.
Projects are, by their nature, exposed to change, uncertainty and differences in interpretation. However, many disputes can be reduced, controlled or resolved at an early stage where their causes are addressed in a timely manner.
A properly assessed and approved change, a documented meeting, a notice submitted within the required period, and a regularly updated project record may appear to be simple measures.
Yet, they can make a significant difference by the end of the project.
At a time when construction projects across the Kingdom are accelerating in scale, value and complexity, protecting a project requires more than high-quality design and execution.
It also requires sound decision-making, effective documentation and disciplined contract management.
A major dispute does not always begin with a major mistake.Sometimes, it begins with a small detail that no one considered important enough at the time.
