Case Study: How a Major Project Failed Because of a Lack of Review

 

Introduction

Planning is an important part of every successful project. However, planning alone is not enough. Without regular reviews and evaluations, even a well-designed project can fail. Many organizations focus heavily on launching projects but forget the importance of monitoring progress, identifying problems early, and adjusting strategies when necessary.

This case study explains how a large company project failed mainly because the management team neglected regular reviews and ignored warning signs during implementation.

Background of the Project

A retail company called BrightMart Solutions decided to launch a new digital inventory management system across all its branches. The goal of the project was to:

• Improve inventory tracking
• Reduce product shortages
• Increase operational efficiency
• Modernize company systems

The project budget was approximately $8 million, with a timeline of 12 months. Management believed the new system would improve productivity and reduce long-term costs.

At the beginning, the project appeared well-planned. The company hired a software vendor, assigned internal teams, and created a detailed implementation schedule.

However, one major weakness existed from the start: there was no strong review and evaluation process during the project execution phase.

Early Warning Signs

During the first few months, several employees reported problems:

• Staff members struggled to use the new system
• Data synchronization errors frequently occurred
• Some branches experienced delayed inventory updates
• Training sessions were incomplete and rushed

Unfortunately, these issues were treated as “temporary technical problems” rather than serious risks.

Management focused mainly on meeting deadlines instead of reviewing project quality and user feedback. Monthly review meetings were often canceled or shortened because leaders believed the project was still moving forward according to schedule.

As a result, many small problems remained unresolved.

The Lack of Proper Review

One of the biggest mistakes in the project was the absence of structured reviews. The company failed to:

• Monitor employee readiness
• Evaluate system performance properly
• Collect detailed user feedback
• Test the software thoroughly before expansion
• Reassess project risks regularly

Because no serious review process existed, management relied only on progress reports from senior project leaders. These reports focused mostly on completed tasks instead of actual project effectiveness.

The company confused “activity” with “success.”

Problems Became Bigger Over Time

As the system expanded to more branches, the technical and operational problems became worse.

Employees started creating manual workarounds because they no longer trusted the system. Inventory records became inaccurate, causing:

• Product shortages
• Overstock problems
• Delivery delays
• Customer complaints

At the same time, operational stress increased among employees because they were not properly trained.

Several branch managers requested a temporary pause for evaluation and system improvements. However, top management refused because they feared delays and additional costs.

Without review and corrective action, the problems spread across the entire organization.

Project Failure

After 14 months, the project was officially considered unsuccessful.

The company faced:

• Financial losses exceeding $12 million
• Operational disruptions across branches
• Reduced employee morale
• Customer dissatisfaction
• Damage to company reputation

Eventually, BrightMart Solutions decided to stop using parts of the new system and return to several old manual processes while searching for another solution.

An independent audit later concluded that the biggest cause of failure was not the technology itself, but poor project monitoring and lack of regular review.

Lessons Learned

This case study demonstrates several important lessons about project management:

1. Reviewing Is as Important as Planning

A good plan must be reviewed continuously. Without evaluation, teams may continue moving in the wrong direction without realizing it.

2. Small Problems Should Never Be Ignored

Minor issues often become major failures when organizations fail to respond early.

3. Feedback Matters

Employees and users often notice practical problems before management does. Their feedback should be taken seriously.

4. Progress Does Not Always Mean Success

Completing tasks and meeting deadlines does not guarantee project quality or effectiveness.

5. Flexibility Is Necessary

Successful organizations are willing to pause, reassess, and improve when needed.

Conclusion

The failure of the BrightMart Solutions project highlights the critical importance of regular review in project management. Even with strong funding, skilled teams, and clear goals, a project can collapse if leaders fail to monitor progress and respond to problems properly.

Review processes help organizations stay aware, flexible, and prepared for challenges. They allow teams to identify weaknesses early, improve strategies, and prevent costly mistakes.

In the end, reviewing a project is not a sign of weakness or delay — it is a necessary step toward long-term success.

Professional Template of Construction Claim Documents (FIDIC-Based Practice)

In construction projects, a well-prepared claim document is essential for protecting contractual rights and ensuring fair entitlement to time and cost. Under standard forms such as FIDIC, claims must be clear, structured, evidence-based, and fully compliant with contractual requirements. A poorly prepared claim often results in rejection, even if the entitlement is valid. Therefore, using a professional claim template is critical for successful contract administration.

A professional construction claim document typically begins with a cover letter or formal notice of claim, which briefly identifies the project, contract number, and nature of the claim. This section clearly states that the submission is made under the relevant contract clause and provides a summary of the relief sought, such as Extension of Time (EOT), additional payment, or both.

The next section is the executive summary of the claim, which provides a concise overview of the dispute. This includes the cause of the claim, key events, impact on the project, and the final entitlement requested. This section allows the Engineer or adjudicator to quickly understand the essence of the claim before reviewing detailed analysis.

Following this, the claim must include a background and project description, which outlines the scope of work, contract conditions, project timeline, and key contractual milestones. This section sets the context for the claim and helps establish the baseline against which delays or changes are assessed.

The next important section is the description of the event or entitlement basis, where the Contractor explains the specific event triggering the claim. This may include variations, delays, unforeseen site conditions, or Employer instructions. The description must be factual, chronological, and supported by records such as instructions, correspondence, or site reports.

A critical part of the claim document is the contractual entitlement analysis, where relevant FIDIC clauses are referenced. This section explains why the Contractor is entitled to additional time or cost under the contract. It must clearly link the event to specific clauses such as variation provisions, delay events, or claim procedures.

The claim must also include a delay analysis section (for EOT claims). This is one of the most important technical parts of the document. It demonstrates how the event impacted the critical path using methods such as impacted as-planned, time impact analysis, or as-built comparison. This section proves causation between the event and project delay.

For cost-related claims, a quantum (cost) analysis section is required. This includes detailed breakdowns of direct and indirect costs, labor, equipment, overheads, and any additional expenses incurred. Supporting invoices, records, and cost calculations must be attached for verification.

The claim document must also include a supporting evidence section, which contains all relevant documents such as site instructions, correspondence, daily reports, meeting minutes, photographs, progress reports, and contractual notices. Proper indexing and referencing of evidence is essential for clarity and credibility.

Finally, the document ends with a conclusion and formal request, summarizing the entitlement and clearly stating the relief sought. This is followed by a declaration confirming that the information provided is true, accurate, and submitted in accordance with the contract.

In conclusion, a professional construction claim document is not just a narrative but a structured contractual argument supported by evidence and analysis. A well-prepared template ensures clarity, improves credibility, and significantly increases the likelihood of successful claim approval under FIDIC and other standard construction contracts.

How to Start Analysis as an Adjudicator in Construction Disputes

In construction adjudication, the quality of a decision depends heavily on how the adjudicator begins the analysis process. Unlike arbitration or litigation, adjudication is time-bound, document-heavy, and requires rapid but structured reasoning. A well-organised analytical approach is essential to ensure fairness, clarity, and contractual correctness within a short decision-making period.

The first step for an adjudicator is to understand the dispute clearly and define the issues. This involves carefully reviewing the Notice of Adjudication and the Referral Notice to identify exactly what is being claimed, what is being disputed, and what relief is being sought. At this stage, the adjudicator should separate the key issues from background information to avoid being overwhelmed by unnecessary details.

Once the issues are identified, the adjudicator must review the contractual framework. This means carefully examining the contract clauses that govern the dispute, such as payment provisions, variation clauses, Extension of Time (EOT) provisions, notice requirements, and dispute resolution procedures. Understanding the contract is critical because adjudication decisions must be based on contractual rights rather than general fairness alone.

The next step is to establish the chronology of events. Construction disputes are highly dependent on timing, so the adjudicator should reconstruct a clear timeline using correspondence, site instructions, progress reports, and meeting minutes. This helps to determine causation, sequence of events, and whether contractual time limits—such as notice periods—were complied with.

After establishing the timeline, the adjudicator should move to evaluate the evidence submitted by both parties. This includes technical documents, payment records, delay analyses, drawings, and witness statements. The adjudicator must assess the reliability, relevance, and consistency of the evidence rather than simply accepting submissions at face value.

A key part of the analysis is determining causation and contractual entitlement. The adjudicator must assess whether the claimed event actually caused the alleged impact, such as delay or additional cost. For example, in an EOT claim, it must be proven that the event affected the critical path and was not concurrent with other delays caused by the Contractor.

The adjudicator should then apply the contract to the facts, ensuring that all decisions are grounded in contractual provisions. This includes checking compliance with notice requirements, claim procedures, and any time-bar provisions. Even a valid claim may fail if procedural requirements were not followed.

Finally, the adjudicator must form a reasoned conclusion and decision. The analysis should lead logically to a clear outcome that addresses each disputed issue. The decision must be structured, concise, and supported by references to both facts and contractual clauses.

In conclusion, starting analysis as an adjudicator requires a disciplined and structured approach: identifying issues, reviewing the contract, establishing chronology, evaluating evidence, assessing causation, and applying contractual provisions. This method ensures that even within the strict time limits of adjudication, decisions remain fair, logical, and contractually sound.

Key Notices Required During FIDIC Contract Implementation (and Their Time Limits)

In FIDIC construction contracts, the issuance of timely notices is a fundamental requirement that directly affects a party’s contractual rights. Many entitlements such as Extension of Time (EOT), additional payment, or compensation depend on strict compliance with notice provisions. Failure to issue notices within the required time limits can result in the loss of claims, even if the underlying event is valid. Below are the key notices commonly required under FIDIC contracts, presented in paragraph form with clear bullet points for ease of reference.

---

⏱️ Notice of Claim (EOT or Additional Payment)

The Notice of Claim is one of the most critical notices under FIDIC, typically related to Extension of Time or additional cost claims. It must be issued promptly after the Contractor becomes aware of the event giving rise to the claim.

• Must be submitted within 28 days of awareness of the event
• Applies to EOT claims, additional payment, or compensation events
• Failure to notify within time may result in loss of entitlement

---

🧾 Fully Detailed Claim Submission

After submitting the initial notice, the Contractor must provide a complete and substantiated claim with full supporting documentation.

• Typically due within 42 days (FIDIC 1999) or 84 days (FIDIC 2017)
• Must include delay analysis, cost breakdown, and supporting evidence
• Required for Engineer’s evaluation and determination

---

🏗️ Notice of Variation or Instruction Impact

When an Engineer’s instruction affects cost, time, or scope, the Contractor should issue a notice highlighting the impact.

• Must be issued without delay / as soon as practicable
• Used to notify potential time and cost consequences
• Important for preserving rights to valuation and EOT

---

⚠️ Notice of Unforeseeable Physical Conditions

If unexpected site conditions are encountered, such as unsuitable ground or hidden obstructions, a formal notice is required.

• Must be given within 28 days of encountering the condition
• Supports claims for additional cost and/or EOT
• Common in excavation, foundation, and earthworks

---

⛔ Notice of Delay Affecting Completion

When an event is likely to delay project completion, the Contractor must inform the Engineer promptly.

• Must be issued within 28 days of awareness of delay event
• Supports Extension of Time claims
• Helps establish causation and critical path impact

---

🔧 Notice of Suspension of Works

If the Contractor suspends work due to Employer default (such as non-payment), proper notice must be issued.

• Usually required within 21–28 days depending on contract conditions
• Must state reasons for suspension
• Protects rights to claim delay and cost consequences

---

🛑 Notice of Termination

Termination under FIDIC requires strict compliance with notice procedures and specified waiting periods.

• Typically 14 to 28 days notice period, depending on default type
• Must clearly state contractual grounds for termination
• Non-compliance may invalidate termination action

---

📌 Conclusion

In FIDIC contracts, notices are not merely administrative formalities but essential legal requirements that protect contractual rights. Proper and timely issuance of notices ensures that claims for time and cost are valid and enforceable. Effective contract management therefore depends heavily on disciplined notice administration, accurate documentation, and strict adherence to contractual time limits.

Major Contract Manager Mistakes in FIDIC Projects

In FIDIC-based construction projects, the Contract Manager plays a critical role in ensuring that contractual rights, obligations, claims, and risks are properly managed. However, many project disputes and financial losses are not caused by the contract itself, but by poor contract management practices on site. Understanding the common mistakes is essential for successful project delivery and dispute avoidance.

One of the most common mistakes is the failure to issue timely contractual notices. FIDIC contracts require strict compliance with notice provisions for claims such as delays, variations, and unforeseen conditions. Many Contract Managers fail to submit notices within the required time limits, assuming that verbal communication or informal emails are sufficient. This often results in loss of entitlement to Extension of Time (EOT) or additional payment, even when the claim is valid.

Another major mistake is the poor management of Extension of Time (EOT) claims. Contract Managers often fail to properly demonstrate causation between delay events and the project’s critical path. Without a structured delay analysis and supporting documentation, EOT claims are frequently rejected or significantly reduced.

A further critical error is the misinterpretation of variations. Many Contract Managers assume that all Engineer instructions automatically qualify as variations. In reality, only instructions that change the scope of works are considered variations under FIDIC. This misunderstanding leads to incorrect claims and disputes with the Engineer or Employer.

Weak record keeping and documentation control is also a frequent problem. Proper contract management requires detailed records of site instructions, daily progress reports, correspondence, test results, and meeting minutes. Without strong documentation, it becomes very difficult to support claims or defend against disputes.

Another common mistake is the lack of proactive contract administration. Many Contract Managers focus heavily on site execution while neglecting contractual monitoring. This reactive approach often leads to missed deadlines for notices, claims, and approvals, weakening the Contractor’s contractual position.

Additionally, there is often a misunderstanding of the role of the Engineer and contract procedures. Contract Managers sometimes expect immediate approval or compensation without following formal procedures outlined in FIDIC. This leads to frustration, disputes, and breakdown in communication between parties.

Finally, poor risk management and commercial awareness is a significant issue. Many Contract Managers fail to properly assess contractual risks related to site conditions, productivity assumptions, or design changes, resulting in unplanned cost overruns and claims disputes.

In conclusion, most major issues in FIDIC projects are not due to the contract itself, but due to contract management failures on site. A successful Contract Manager must be proactive, disciplined, and highly aware of contractual procedures, particularly in relation to notices, variations, EOT claims, documentation, and risk management. Strong contract administration is ultimately the key to protecting both time and cost in complex construction projects.

The Pathway of a Notice of Adjudication in Construction Contracts

In construction projects, disputes can arise at any stage due to payment issues, variations, delays, or quality disagreements. To resolve these disputes quickly and avoid disrupting ongoing works, many contracts such as FIDIC, NEC, and other standard forms provide a mechanism called adjudication. The process begins with a key step known as the Notice of Adjudication, which formally triggers the dispute resolution procedure.

The Notice of Adjudication is a written document issued by one party (the referring party) to the other party, clearly stating that a dispute has arisen and is being referred to adjudication. This notice marks the official starting point of the adjudication process. It typically includes details such as the nature of the dispute, the issues in contention, the contractual basis of the claim, and the remedy or relief sought. The purpose of this notice is to ensure that both parties are fully aware that a formal dispute resolution process has begun.

Once the Notice of Adjudication is issued, the next step is the appointment of an adjudicator. Depending on the contract, the adjudicator may be jointly agreed upon by the parties or appointed by a nominating body specified in the contract. The adjudicator must be independent and impartial, with suitable technical and contractual expertise relevant to the construction dispute.

After the adjudicator is appointed, the referring party submits a detailed Referral Notice or claim submission. This document expands on the initial notice and includes all supporting evidence such as contracts, correspondence, site records, drawings, payment certificates, and delay analysis if applicable. The responding party is then given an opportunity to submit its response and supporting documents within a defined timeframe.

The adjudicator reviews the submissions from both parties, may request additional information, and can conduct site visits or meetings if necessary. The process is intentionally fast-paced, typically lasting around 28 to 42 days, depending on the contract provisions. This ensures that disputes do not delay construction progress for extended periods.

Finally, the adjudicator issues a written decision, which is usually binding on an interim basis. This means that both parties must comply with the decision immediately, even if one party disagrees and intends to challenge it later through arbitration or litigation. The objective is to maintain cash flow and allow the project to continue without interruption.

In conclusion, the pathway of a Notice of Adjudication is a structured and time-bound process that begins with formal notification of a dispute and progresses through adjudicator appointment, evidence submission, review, and finally a binding decision. This mechanism plays a crucial role in modern construction contracts by ensuring disputes are resolved quickly, efficiently, and without halting project execution.

Dispute Cases in FIDIC Contracts: Common Issues and Relevant Clauses

Disputes are a normal part of construction projects, and FIDIC contracts are specifically designed with structured mechanisms to manage and resolve them. In FIDIC-based projects, disputes do not only refer to court cases; they include any disagreement between the Employer and Contractor regarding rights, obligations, payments, time, or performance under the contract.

In practice, disputes in FIDIC contracts often arise from several common situations. One of the most frequent is payment disputes, where the Contractor disagrees with the Engineer’s valuation of completed work or rejection of claims for variations. Another common issue is Extension of Time (EOT) claims, where the Contractor argues that delays caused by variations, late instructions, or unforeseen conditions entitle them to additional time. Disputes also frequently occur in relation to variations, especially when there is disagreement on whether an instruction constitutes a variation and how it should be valued. In addition, quality and defect disputes, particularly regarding non-conforming works or rejection of materials, are also common in construction projects. Finally, disputes may arise from termination or suspension of works, where one party believes the contract has been wrongly suspended or terminated.

To manage these disputes, FIDIC provides a clear dispute resolution framework. The key mechanism is the Dispute Avoidance/Adjudication Board (DAAB) or previously the Dispute Adjudication Board (DAB), depending on the contract edition. This mechanism is outlined primarily in Clause 21 of the FIDIC Red Book 2017, which governs dispute resolution procedures. The process typically begins with a formal notice of dispute, followed by referral to the DAAB for a decision. The DAAB’s decision is binding on an interim basis, meaning it must be complied with immediately, even if one party intends to escalate the dispute further.

If either party is dissatisfied with the DAAB decision, the dispute may be referred to arbitration, as provided under Sub-Clause 21.6 (Arbitration) in the FIDIC Red Book 2017. Arbitration is the final step in the FIDIC dispute resolution ladder and results in a legally binding and enforceable award. In older versions of FIDIC (such as the 1999 Red Book), dispute procedures are found under Clause 20, which also covers the DAB process and arbitration referral.

Other relevant clauses often linked to disputes include Clause 3 (The Engineer’s role and authority), which governs instructions and determinations; Clause 13 (Variations and Adjustments), which is frequently the source of scope and payment disputes; and Clause 8 (Commencement, Delays, and Suspension), which is closely connected to EOT claims and delay disputes.

In conclusion, disputes in FIDIC contracts are not unusual but are anticipated and structured within the contract framework. With mechanisms such as the DAAB, adjudication, and arbitration, FIDIC provides a clear pathway for resolving conflicts efficiently. The most critical clauses related to disputes are Clause 21 in the 2017 edition (or Clause 20 in the 1999 edition), along with supporting clauses on Engineer’s instructions, variations, and delays. This structured system helps ensure that disputes are managed in a fair, timely, and contractually controlled manner without unnecessarily stopping construction progress.

The Role of an Adjudicator in Construction Disputes

In the construction industry, disputes are almost inevitable due to the complexity of contracts, fast-track project delivery, and multiple stakeholders involved. To avoid lengthy interruptions to ongoing works, many standard contracts such as FIDIC and NEC include adjudication as a fast dispute resolution mechanism. At the center of this process is the adjudicator, an independent professional appointed to make a quick, binding decision on disputes between contracting parties.

The primary role of an adjudicator is to act as a neutral decision-maker who resolves disputes in a fair, impartial, and timely manner. Unlike a judge in a court of law, the adjudicator’s objective is not to provide a final legal judgment but to deliver a temporary binding decision that allows the project to continue without delay. This is especially important in construction, where unresolved disputes can quickly disrupt cash flow, delay progress, and increase project costs.

An adjudicator reviews the evidence submitted by both parties, which may include contracts, correspondence, site records, payment certificates, and technical reports. Based on this information, the adjudicator assesses the facts, interprets the contract, and determines the most appropriate outcome in accordance with the contract provisions. The process is typically fast, often completed within a few weeks, and is designed to be less formal than arbitration or litigation.

Another key responsibility of the adjudicator is to ensure procedural fairness. This means both parties must have a reasonable opportunity to present their case and respond to the other party’s submissions. While the process is streamlined, the adjudicator must still act in accordance with principles of natural justice and remain independent from the project stakeholders.

The adjudicator also plays an important role in maintaining project continuity. By providing quick decisions on disputes such as payment issues, variations, or delay claims, the adjudicator helps prevent work stoppages and preserves the progress of construction activities. Although the decision is binding on an interim basis, it can later be reviewed through arbitration or litigation if either party is dissatisfied.

In addition, the adjudicator is expected to possess strong technical and contractual knowledge, particularly in construction law, engineering principles, and contract administration. This expertise allows the adjudicator to understand complex technical disputes, such as those involving structural design, concrete quality, delays, or variations.

In conclusion, the adjudicator plays a crucial role in construction dispute resolution by delivering fast, impartial, and practical decisions that keep projects moving forward. While not a final authority like a court or arbitral tribunal, the adjudicator ensures that disputes do not halt construction progress, making the role an essential part of modern construction contract management.

Variations under FIDIC Red Book: How Instructions Become Variations & How Extension of Time (EOT) Claims Are Assessed

In FIDIC Red Book construction contracts, the Engineer has the authority to issue instructions to the Contractor for the execution of the Works. However, not every instruction automatically becomes a variation. An instruction is considered a variation only when it results in a change to the original scope of works defined in the contract. This may include changes to design, quantities, quality, sequence, or method of construction. If an instruction merely clarifies existing requirements or enforces compliance with the contract documents, it is not treated as a variation. On the other hand, if it introduces additional work or alters the original contractual obligations in a way that affects cost or time, it becomes a variation and may lead to adjustments in both contract price and completion time.

An Extension of Time (EOT) under FIDIC is a contractual entitlement that allows the Contractor to extend the completion date when delays occur due to events beyond their control. Variations are one of the most common causes of EOT claims, particularly when they affect the critical path of the project. However, the Contractor must demonstrate that the variation actually caused delay to the overall completion of the Works, not just to individual activities. Simply receiving a variation instruction does not automatically entitle the Contractor to additional time; the impact on project progress must be clearly proven.

Several key aspects affect the success of an EOT claim under FIDIC. First, strict compliance with contractual notice requirements is essential, as failure to notify the Engineer within the required timeframe may weaken or even invalidate the claim. Second, the Contractor must establish clear causation, showing that the delay event directly impacted the critical path of the project. Third, proper documentation is critical, including site instructions, progress records, correspondence, and delay analysis reports. The Engineer will then assess whether the delay is excusable under the contract and whether an extension is justified. Other factors such as concurrent delays and the Contractor’s obligation to mitigate delay impacts may also influence the final decision.

In conclusion, under FIDIC Red Book contracts, an instruction becomes a variation when it changes the original scope of works, and such variations often form the basis for Extension of Time claims. However, entitlement to EOT depends on strict contractual compliance, clear evidence of delay impact, and proper documentation. Understanding this relationship is essential for effective contract management and successful project delivery.

FIDIC Red Book Explained: How Site Instructions Turn into Contract Variations

In a FIDIC Red Book construction contract, instructions issued by the Engineer play a central role in project administration and site execution. However, not every instruction automatically becomes a variation. Understanding how an instruction is transformed into a variation—and what factors influence this process—is essential for both the Employer and the Contractor in managing cost, time, and contractual obligations.

Under the FIDIC Red Book, a variation is generally defined as a change to the original scope of works as described in the contract. This may include changes to quantities, quality, design, sequence, or timing of the works. The Engineer has the authority to issue instructions to the Contractor, but only certain instructions qualify as variations under the contract. Typically, when an instruction alters the original scope, introduces additional work, or changes the execution conditions, it is considered a variation.

For an instruction to become a variation, it must first clearly deviate from the contractual scope or specifications. If the instruction merely clarifies existing requirements or enforces compliance with the contract, it is not treated as a variation. However, if the instruction requires additional work, redesign, change in materials, or modification of construction methods beyond what was originally specified, it becomes a variation and is subject to valuation and potential adjustment of the contract price and/or completion time.

Several key aspects can influence whether an instruction is classified as a variation. The first is the contractual wording and scope definition, which sets the baseline for what is included in the original contract. A poorly defined scope often leads to disputes over whether an instruction constitutes a variation. The second is the Engineer’s interpretation and authority, as the Engineer determines whether the instruction changes the scope or simply enforces compliance. The third is the method of execution, since changes in construction methodology or sequencing can sometimes be argued as variations if they significantly affect cost or time.

Another important factor is the timing of the instruction. Instructions issued after construction has started may have a greater likelihood of being treated as variations, especially if they disrupt planned sequences or require rework. The cost and time impact also play a critical role, as variations typically entitle the Contractor to additional payment and/or extension of time, provided proper notice and claims procedures are followed under the contract.

Additionally, the documentation and communication process is crucial. Under FIDIC conditions, the Contractor is required to promptly notify the Engineer if an instruction is believed to constitute a variation. Failure to follow notification procedures may affect entitlement to additional payment or time extension, even if the instruction technically qualifies as a variation.

In conclusion, under the FIDIC Red Book, an instruction becomes a variation when it changes the original contractual scope of works, and this determination depends on several factors including contract wording, Engineer’s interpretation, timing, execution impact, and proper contractual notification. Clear understanding and proper administration of variations are essential to maintaining fairness, avoiding disputes, and ensuring successful project delivery.