Introduction
Major construction and infrastructure projects do not always fail due to poor design, lack of funds, or the technical incompetence of the participants. They are frequently undermined by the inability of the contracting parties to exchange information, document events, make decisions, and comply with agreed procedures in a timely manner. For this reason, the contracts of the International Federation of Consulting Engineers – FIDIC – represent much more than just a set of legal rules governing risk allocation. At the same time, they serve as an operational project management system, in which notices, time limits, programmes, records, claims, and decisions are integrated into a single unified process.
Procedural discipline in FIDIC contracts means that each party must understand not only the substantive rights to which it is entitled, but also how, when, and in what form those rights are to be exercised. A Contractor may have a legitimate claim for an extension of time or additional payment, but its position can be weakened if it fails to issue the contractual notice, maintain contemporary records, or demonstrate the event’s impact on the critical path. An Employer may have grounds for a price reduction, defect rectification, or damages, yet its claim must likewise follow the prescribed contractual procedure. The Engineer, for its part, must act within its authority, consult the parties, and issue reasoned determinations within the stipulated time limits. Consequently, procedural discipline is not a secondary formality, but a prerequisite for the predictability, fairness, and efficiency of the entire contractual relationship.
The FIDIC Contract as a Project Management System
FIDIC forms were created to standardize complex construction relationships in an international environment. The Red Book is traditionally used when the Employer designs the project, the Yellow Book when the Contractor designs and builds, and the Silver Book for EPC / “turnkey” projects with a higher transfer of risk to the Contractor. Although the allocation of individual risks differs, all these forms share a common procedural logic: an event must be identified, notified, documented, evaluated, and resolved through a pre-determined chain of communication and decision-making.
The second edition of the 2017 FIDIC forms makes this logic even more pronounced. FIDIC notes that the rules on notices and other communications are more detailed, that the claims of the Employer and the Contractor are treated equally and separated from disputes, and that more developed mechanisms for dispute avoidance and verification of contractual compliance have been introduced. This brings the contract closer to an early warning system. Its purpose is not to surprise a party with the loss of a right, but to bring a problem to light while there is still an opportunity for a technical, time, or commercial solution.
Such a system only functions if the General and Special Conditions form a harmonious whole. The FIDIC Golden Principles warn that roles, rights, and obligations should not be altered in a way that undermines the fundamental nature of the chosen form; that Special Conditions must be clear; that the risk allocation should remain fair; that time limits must be reasonable; and that disputes should be referred to a Dispute Avoidance/Adjudication Board and subsequently to arbitration. Procedural discipline, therefore, begins as early as the drafting of the contract: an unclear, contradictory, or unrealistic procedure generates future disputes instead of preventing them.
Notice as the Starting Point for Rights Protection
The most recognizable expression of FIDIC procedural discipline is the notice. Contractual communication is not ordinary business correspondence. When the contract requires “Notice,” the document must be recognizable as a formal notice, addressed to the authorized recipient, delivered to the agreed address, and linked to the relevant contractual provision. Meeting minutes, a message in an informal group, or a note in a report may prove that the other party knew about the problem, but they do not always replace the formal notice that triggers the contractual mechanism.
The notice serves several functions. It enables the other party to verify the event while it is still current, take mitigation measures, change the sequence of works, preserve evidence, or plan financial consequences. At the same time, it determines the subject matter of a future claim and prevents the subsequent expansion of the factual basis. In a well-managed project, a notice is not a hostile act. It is a professional signal that an event has occurred which may affect price, time, or quality, and that it should be processed jointly.
Problems arise when a notice is perceived as a “declaration of war.” Project teams then delay formal communication to avoid disrupting business relationships, relying on verbal promises that the issue will be resolved later. When negotiations fail, the documentation trail is incomplete, deadlines have passed, and causation is difficult to prove. The opposite extreme is the hyperproduction of general and vague notices used to reserve all possible rights without a clear event and consequence. Such practice overwhelms the project with information but fails to create actual procedural clarity.
Deadlines, Time Bars, and Loss of Rights
FIDIC procedures frequently contain short and strict time limits. In the 2017 forms, the claims procedure is elaborated in particular detail: the initial notice of claim must, as a rule, be submitted within 28 days after the claimant became aware, or should have known, of the event or circumstance, followed by a fully detailed claim within a further contractual period. The purpose is not merely a formal sorting of claims. A construction project changes from day to day; after several months, it is difficult to determine which machinery was engaged, which works were on the critical path, and whether the consequence could have been mitigated.
A time bar can lead to the loss of a contractual right if the notice is not issued in a timely manner. Its application, however, is not always mechanical. Applicable law may restrict the effect of such a clause through the principles of good faith and fair dealing, the prohibition of the abuse of rights, or rules regarding waiver or the conduct of the other party. In addition, the text of the specific contract, the conduct of the Engineer, and the question of whether the recipient suffered procedural prejudice can be significant. Nevertheless, relying on the possibility that a court or arbitration will soften a strict clause represents a poor project management. The prudent strategy is to comply with the contractual deadline while simultaneously reserving all arguments derived from the applicable law.
Deadlines must bind both parties. If only the Contractor suffers the loss of rights, while the Employer can indefinitely delay its claims or decisions, the contractual balance is disrupted. For this very reason, the modern FIDIC structure seeks to establish a more symmetrical treatment of claims. Discipline is not an instrument of dominance by one party, but a joint regime of responsible and timely conduct.
The Claim as an Evidentiary and Analytical Process
A timely notice merely initiates the procedure; it does not prove the basis or the quantum of the claim. A fully detailed claim must link the contractual provision, the facts, the causal connection, and the claimed consequence. In a claim for an extension of time, it is not sufficient to state that an event lasted a certain number of days. It is necessary to demonstrate how it affected the accepted programme and the critical path, which activities were impacted, whether there was concurrent contractor delay, and what mitigation measures were taken. In a claim for additional payment, it is necessary to distinguish actual additional cost from expenses that would have been incurred in any event.
Contemporary records play a decisive role. Daily reports, the site logbook, photographs, labour and plant records, minutes, transmittal registers, programmes, orders, and financial data should be generated at the time of the event rather than only when the legal team begins preparing for a dispute. Retroactively reconstructed documentation can be useful, but it is more susceptible to challenge. A procedurally disciplined party therefore establishes a single claims register, links each event with evidence, and regularly updates its status.
Events with continuing effect present a particular challenge. In such cases, the claim is not concluded by a single submission: periodic updated reports are required, and the final claim is submitted when the consequences cease or become sufficiently ascertainable. This continuity prevents the other party from learning the full financial or time impact of a problem only at the very end of the project.
The Role of the Engineer and Decision-Making Discipline
In the Red and Yellow Books, the Engineer plays a significant role in administering the contract. They issue instructions, monitor execution, certify payments, and participate in resolving claims. When determining a claim, the Engineer is expected to consult the parties, attempt to reach an agreement an if there is no agreement make a fair and reasoned determination in accordance with the contract. Although engaged by the Employer, their function in making contractual determinations cannot be reduced to automatically endorsing the Employer’s position.
The procedural discipline of the Engineer entails maintaining a correspondence register, distinguishing instructions from non-binding comments, responding to technical submissions in a timely manner, and clearly separating certification from the final determination of rights. Delays by the Engineer can trigger a chain reaction: the Contractor cannot order equipment, the programme slips, costs arise, and a dispute then ensues over who caused the delay. Therefore, administrative efficiency is just as important as the correctness of the final decision.
The parties must also respect the limits of authority. Not every statement made by a supervisory engineer constitutes approval of additional cost, nor is every technical approval a contract variation. If the Special Conditions require a specific form or the signature of an authorised person, a contractor that acts solely on the basis of an informal discussion assumes significant risk. Conversely, an employer should not use an ambiguous internal division of authority to accept the benefit of an executed variation while subsequently refusing any liability.
Programme, Early Warning, Variations, and Payment
The programme of works in a FIDIC contract serves as the foundation for coordination, progress tracking, and delay analysis. The programme must be realistic, sufficiently detailed, and regularly updated. If the Contractor fails to display the actual sequence of works, it undermines its own claim for an extension of time. If the Employer or Engineer delays reviewing the programme without justification, the project is left without a shared timeline. Procedural discipline therefore requires that objections be substantiated, that the programme is not rejected arbitrarily, and that its eventual acceptance is not equated with a waiver of contractual rights.
Early warning complements the formal claims system. A party that identifies a potential future problem should raise it before it escalates into actual delay or cost. This approach shifts the focus from retrospective blame attribution to consequence management. Nevertheless, an early warning should not automatically be considered a substitute for a formal notice of claim unless the contract explicitly permits it.
Similar discipline applies to variations. A distinction must be made between an instruction, a request for a proposal, a technical clarification, and a formal variation. Whenever possible, the scope, method of valuation, and impact on time should be defined prior to execution. Execution without a clear paper trail invariably generates a dispute. Regarding payment, a proper statement, proof of executed quantities, certification, and the payment deadline form an interconnected process. The delay of a single step should not be obscured by informal “provisional” solutions that subsequently complicate the final account.
DAAB and Turning a Dispute into a Manageable Process
If a contracting party is dissatisfied, the dispute is referred to the Dispute Avoidance/Adjudication Board (DAAB) prior to arbitration. A standing DAAB, provided for in modern forms, can monitor the project, and assist the parties in resolving issues before a formal dispute arises. The value of such a body lies not only in rendering decisions. Members who are familiar with the contract, the site, and the history of the project can identify misunderstandings early and offer informal assistance, provided the conditions of impartiality and the consent of the parties are met.
In addition, procedure is crucial: the proper definition of the dispute, submission of the relevant file, compliance with decision-making time limits, and timely notice of dissatisfaction. DAAB decisions have contractual binding force and must be complied with, even if they may be subject to further proceedings. A party that ignores a decision because it plans to initiate arbitration undermines the system of provisional bindingness and jeopardises the project’s cash flow.
The most expensive dispute is the one that is seriously analysed for the first time only after the works are completed. The FIDIC procedural architecture seeks to gradually “cool down” a dispute: initial notice, subsequent fully detailed claim, consultations, and determination by the Engineer, the DAAB, a period for amicable settlement, and only then arbitration. Each step represents a new opportunity to resolve the matter at a lower cost and conflict level.
Consequences of Procedural Indiscipline
Procedural indiscipline produces both legal and operational consequences. Legally, a party may lose a claim, lose entitlement to an extension of time, be exposed to liquidated damages, or lose the opportunity to challenge a decision in a timely manner. Evidentiary-wise, the lack of contemporary records increases the scope for conflicting reconstructions of events. Operationally, vague instructions lead to delays, rework, and supply chain issues. Financially, disputed amounts accumulate to the point where they jeopardise the contractor’s liquidity or the employer’s budget.
Equally dangerous is selective discipline. An employer that strictly insists on the contractor’s deadlines but delays its own decisions creates an imbalance and encourages defensive administration. A contractor that issues numerous notices but fails to provide evidence and a realistic programme turns the contract into a warehouse of reserved rights. An engineer that formally manages procedures but fails to reason decisions only postpones the dispute. The essence lies not in the number of letters, but in the quality, timeliness, and mutual interconnection of information.
Procedural Discipline in the Domestic Legal and Business Environment
The application of FIDIC forms in Bosnia and Herzegovina requires linking the contract with domestic obligations, construction, administrative, labour, and tax regulations. FIDIC conditions are not legislation; they become part of the contract and apply within the limits of mandatory legal provisions. Therefore, the effect of time bars, the engineer’s authority, liquidated damages, termination, guarantees, and DAAB decisions must be verified against the applicable law.
Practice in the region often suffers from a culture of verbal orders and retroactive “paperwork sorting.” Such an approach is incompatible with the FIDIC system. Project organization must predetermine authorized persons, delivery addresses, notice templates, a deadline register, and responsibility for each step. Legal, technical, and financial teams must not function as isolated islands: a lawyer without a programme cannot prove delay, an engineer without the contract may give an unauthorized instruction, and finance without change logs cannot confirm actual cost.
The most effective model includes an initial contract workshop, an obligation matrix, a deadline calendar, standard forms, a weekly review of open notices and claims, a central document management system, and periodic compliance audits. Such a system is not bureaucratic excess. Its cost is negligible compared to the expense of a multi-million-dollar dispute based on incomplete correspondence and participants’ memories.
Conclusion
FIDIC contracts demonstrate that successful construction requires much more than technical execution. It is necessary to achieve discipline in information exchange, adherence to deadlines, record-keeping, program preparation, claim formulation, variation issuance, and decision-making. The procedure protects both parties because it enables risks to be identified, consequences to be mitigated, evidence to be preserved, and issues to be resolved before they escalate into disputes.
At the same time, the procedure must not become a trap or a means of unfair risk reallocation. Deadlines must be reasonable, Special Conditions clear, and the Engineer and DAAB functional and impartial. The Contracting Parties must act in good faith, yet they must not rely on the general obligation of cooperation as a substitute for explicit contractual steps. The most mature approach combines legal precision with project pragmatism: it formally preserves rights while simultaneously actively seeking solutions.
Therefore, the quality of a contracting party in a FIDIC project is not measured solely by whether they were “right” in the end. It is measured by the ability to warn, document, mitigate, decide, and continue execution in a timely manner. Procedural discipline transforms construction uncertainty into a manageable process. Where it exists, claims remain controlled and disputes solvable; where it is absent, even a technically successful project can end as a protracted legal and financial failure.
Author: Aleksandar Sajic
