The Binding Effect of DAB and DAAB Decisions Under the FIDIC Red Book

Dispute Boards are an alternative dispute-resolution mechanism composed of a panel of experts entrusted with intervening to resolve and prevent disputes on a project.¹ Unlike other dispute-resolution methods that operate only after a dispute has crystallized, this mechanism accompanies the contract from its early stages through completion.²

The Dispute Board’s continuous presence reflects a preventive and conflict-management rationale. By remaining involved in the project, its members understand the progress of the works, the technical characteristics, and the dynamics between the parties, allowing them to issue decisions within short timeframes and with greater knowledge of the dispute.³

However, because it is a purely contractual mechanism without jurisdiction of its own, one of the principal debates concerns the binding nature of its decisions.

A key feature of the FIDIC model is that decisions of the Dispute Adjudication Board (DAB), later replaced by the Dispute Avoidance/Adjudication Board (DAAB),⁴ are binding from the moment they are issued. This does not, however, mean that they are final.

Scope of the Binding Nature of Decisions

One feature distinguishing the FIDIC Red Book model is the binding nature of the decisions issued by these boards. As the mechanism evolved, the World Bank and FIDIC adopted a process under which decisions would be binding during project delivery, giving rise to the DAB.⁵

This choice was based on several considerations, including:

– The possibility of enforcing decisions through the appropriate legal channels;

– The incentive for the parties to seek an early resolution of their differences;

– The reduced risk that either party will simply disregard the panel’s determination; and

– The need for a mandatory decision on projects where approval of certain payments requires formal support.⁶

Nevertheless, there are also arguments supporting the opposite approach. For example, binding decisions may increase the cost of preparing the proceedings, encourage greater involvement by legal representatives, and limit the parties’ ability to define the resolution of the dispute themselves.⁷

Why is the decision mandatory? Because the parties are bound by the intention expressed in the contract. A DAB decision therefore takes effect on the date it is issued and remains binding until an agreement between the parties or an arbitral award provides otherwise.⁸

Clause 20.4 of the 1999 Red Book provides that a DAB decision is binding on both parties, who must comply with it immediately unless it is later revised by amicable settlement or arbitral award. Only where neither party submits a Notice of Dissatisfaction within 28 days does the decision become final and binding.⁹

This provision reflects an important distinction between a decision that is binding and one that is final and binding. A binding decision produces mandatory effects from the moment it is issued but may still be reviewed at a later stage. A final and binding decision, by contrast, is no longer subject to review and becomes conclusive between the parties.

For precisely this reason, the Contractor must continue carrying out the Works in accordance with the contract even where a claim has been referred to the DAB. The mere existence of a dispute does not entitle the Contractor to suspend the Works while awaiting the panel’s decision.¹⁰

The 2017 Red Book follows the same logic and further strengthens this obligation. Clause 21.4.3 expressly provides that both parties must promptly comply with a DAAB decision, regardless of whether either party has submitted a Notice of Dissatisfaction concerning that decision. It also specifies that the Employer is responsible for ensuring the Engineer’s compliance with the decision where applicable.¹¹

Accordingly, the sole purpose of a Notice of Dissatisfaction is to prevent the decision from becoming final, preserving the dissatisfied party’s right to refer the dispute to arbitration later. Until then, the decision remains binding and must be implemented.¹²

Consequences of Non-Compliance with Decisions

Binding decisions were not part of the earliest Dispute Board models. Initially, boards issued recommendations without mandatory force. As the mechanism developed, however, those recommendations evolved into binding decisions, transforming the process into a genuine dispute-resolution mechanism during project delivery.¹³

Nevertheless, the practical effectiveness of these decisions has been debated. Unlike arbitration, there is no specific legal instrument that generally guarantees the mandatory force and enforceability of decisions issued through this mechanism.¹⁴

DAB decisions are not equivalent to arbitral awards or court judgments. Their effectiveness therefore does not derive from jurisdictional authority, but from the parties’ contractual agreement. The parties themselves agree to refer certain disputes to this mechanism and to give binding effect to its decisions. Consequently, when a party chooses not to comply with a decision, it commits a breach of contract.¹⁵

DAB or DAAB decisions are presumed valid and produce effects unless there is a substantial or material reason to depart from them. This approach is consistent with the mechanism’s purpose: to address disputes promptly without disrupting the continuity of project delivery.¹⁶

Ultimately, the binding nature of DAB and DAAB decisions responds to the need to address disputes when they arise, rather than after the project has ended. Making these decisions binding ensures an immediate response to disputes and prevents them from delaying the Works, allowing the parties to continue performing the contract while the dispute may be reviewed later.