Why the Philippines Needs Standing Dispute Boards in Infrastructure Contracts

For many years, the Philippines could plausibly believe that arbitration was enough for construction disputes. That belief was not misguided. The country had already established a specialized arbitral regime for construction through Executive Order No. 1008, and it later entrenched a broader pro-ADR policy through the ADR Act of 2004. In institutional terms, the Philippines had already accepted that technical project disputes should not be left entirely to ordinary court litigation. In legal terms, it had already embraced party autonomy and non-judicial dispute mechanisms as legitimate tools of commercial governance.^[1]

But an arbitration-centered system, however sophisticated, is still largely reactive. Arbitration functions best after a dispute has matured. By the time parties invoke it, a disagreement has usually become a claim, positions have hardened, project relationships have deteriorated, and time and cost consequences have already spread across the contract. In large infrastructure projects, this is often too late. The real commercial problem is not only how to decide disputes correctly after they crystallize, but how to stop ordinary project friction from becoming formal disputes in the first place.

That is why the Philippine conversation is shifting from dispute resolution to dispute avoidance.

A project does not normally leap from smooth performance straight into arbitration. It usually moves through stages: first, a disagreement or difference; then an issue; then a claim; and only later a dispute requiring formal adjudication. A standing dispute board changes that timeline. Instead of appearing only after conflict has fully ripened, it can intervene at earlier stages through informal assistance, advisory views, site-level engagement, and, when necessary, formal decisions. That is the deeper reason dispute boards matter. They are not simply faster mini-tribunals. They are mechanisms for interrupting escalation before the project itself absorbs irreversible damage.

This is where arbitration, for all its strengths, reveals its limits. CIAC remains indispensable. Final adjudication remains necessary. But arbitral processes do not ordinarily accompany the project while it is being performed. They do not typically attend site meetings, observe issues while they are still manageable, or provide informal guidance at the point where a commercial disagreement might still be defused. Dispute boards do.

The Philippine legal background helps explain why the country initially relied so heavily on arbitration. Executive Order No. 1008 declared a policy of encouraging the early and expeditious settlement of construction disputes and created a specialized arbitral mechanism for that sector.^[2] Republic Act No. 9285 then declared state policy to actively promote ADR as an efficient means of achieving speedy and impartial justice.^[3] Taken together, these laws established a robust architecture for resolving disputes outside the courts. Yet they were still framed mainly around the resolution of existing disputes. They did not, by themselves, solve the problem of conflict management during live project execution.

The need for a more preventive mechanism became increasingly visible as Philippine projects grew larger, longer, and more complex. This was especially true in the context of PPPs, ODA-financed works, and the state’s more aggressive infrastructure build-out. The government’s Build, Build, Build program, embodied in the Philippine Development Plan 2017–2022, reflected a scale of public works delivery in which delay and unresolved project conflict could no longer be treated as isolated legal events. They became systemic delivery risks.^[4] In that environment, relying solely on a back-end arbitral remedy is commercially and institutionally incomplete.

The earlier history of FIDIC is instructive here. One of the most important points emerging from the slides is that dispute avoidance was already present, though less fully articulated, in the 1999 FIDIC suite. The 1999 forms did not treat the Engineer merely as a claims gatekeeper; Sub-Clause 3.5 required the Engineer first to consult with each party in an effort to reach agreement before making a determination.^[5] Likewise, the 1999 regime already allowed the parties, acting jointly, to refer a matter to the dispute board for an opinion, and the dispute adjudication agreement contemplated the giving of advice or opinions when jointly requested.^[6] In other words, even the 1999 framework contained seeds of avoidance. It recognized that neutral input could be useful before full-blown adjudication.

Yet those 1999 mechanisms remained comparatively modest. They depended heavily on party initiative, were less systematically embedded, and did not yet express avoidance as the organizing objective of the board itself. The newer slides correctly show that the 2017 update did something more ambitious: it transformed dispute avoidance from a peripheral possibility into a formalized contractual function.

That transformation is visible first in terminology. The board was no longer described simply as a DAB; it became a Dispute Avoidance/Adjudication Board (DAAB). FIDIC’s official materials on the second editions of the Red, Yellow, and Silver Books explain that the 2017 revisions introduced a new sub-clause specifically to reinforce the board’s role in helping the parties with disagreements and issues before they become disputes.^[7] This was not cosmetic renaming. It was a signal that the board’s mission had changed.

The second transformation concerned timing. Under the 2017 suite, the DAAB is to be appointed from the outset of the contract across the major books, rather than being treated as something that becomes active only later in the project cycle.^[8] This point matters enormously. A board that is constituted early can conduct site visits, monitor progress, remain current on emerging disagreements, and understand the project’s commercial and technical context before conflict hardens. A board that arrives only once the parties are already in formal combat cannot perform the same avoidance function with equal credibility or effectiveness.

The third transformation concerned initiative and procedure. The 2017 regime expressly contemplates the parties jointly requesting the DAAB to provide assistance or to discuss and attempt to resolve an issue or disagreement arising during contract performance. The regime also allows the DAAB itself, if it becomes aware of an issue or disagreement, to invite the parties to make such a joint request.^[9] This is a significant innovation. It means the board is not reduced to passively waiting for a formal referral. It may become an active facilitator of de-escalation, though still within the limits of party consent.

The procedural rules reinforce this role. As the slides highlight, the objectives of the DAAB procedural rules now expressly include facilitating the avoidance of disputes. Meetings and site visits are not merely administrative rituals; they are designed to keep the board informed of actual or potential issues and enable it to provide informal assistance where appropriate.^[10] Even hearing procedures reflect this logic. The 2017 materials contemplate circumstances in which a hearing may be adjourned to permit informal assistance, effectively allowing the adjudicative process to bifurcate toward possible amicable resolution rather than forcing every referred matter to continue on a purely determinative track.^[11] The result is a much more proactive and express architecture of dispute avoidance than what existed under the earlier suite.

This evolution in FIDIC matters to the Philippines because Philippine infrastructure increasingly operates within contracting environments influenced by international standard forms, PPP structures, and ODA procurement. JICA’s Dispute Board Manual is especially important in this regard. It treats the dispute board not as an optional luxury but as an integral part of sound project implementation, and it explains that under Japanese ODA practice the board is generally required from the beginning of the project regardless of size.^[12] The Manual also addresses practical concerns that have surfaced in Philippine discussions, including cost and the need to structure board expenses as part of project budgeting.^[13] In other words, the international financing context has already moved beyond the idea that arbitration alone is enough.

The Philippine policy framework has gradually begun to move in the same direction. Executive Order No. 78 requires ADR provisions in PPP, BOT, and relevant joint venture contracts involving government and private entities.^[14] More recently, the PPP Center has undertaken stakeholder consultations on draft guidelines for project dispute boards in PPP projects, signaling that dispute boards are no longer being treated merely as niche contractual experiments but as serious governance tools for infrastructure delivery.^[15] This is a meaningful development. It suggests that the Philippine state is beginning to appreciate what the FIDIC revisions made explicit: unresolved project friction should be addressed before it becomes litigation by another name.

The Philippine Construction Industry Roadmap 2020–2030 fits within this same shift. Its significance lies not simply in endorsing modern contracting language, but in linking industry development to competence in internationally accepted forms, contract administration, and dispute prevention. CIAP’s 2024 announcement on its memorandum of understanding with FIDIC expressly connects this capability-building effort to improving the quality of construction and engineering services and supporting Roadmap implementation.^[16] This is critical because the obstacles to dispute-board use in the Philippines are not purely legal. As your earlier slides noted, they include cost concerns, lack of local board professionals, limited stakeholder familiarity, and budgeting issues. Those are implementation barriers, not conceptual ones.

The comparison between ad hoc and standing boards therefore becomes decisive. An ad hoc board established only after a dispute has crystallized may still produce a binding decision, but it does little to prevent escalation. It resembles arbitration in timing, even if not in formal structure. A standing board, by contrast, is mobilized at the outset, remains involved throughout the project, and can give informal assistance before matters become claims. That is why the slides rightly emphasize that standing boards have a permanent dispute-avoidance role for the entire duration of the project. Their value lies not only in deciding disputes, but in helping the parties avoid reaching that stage at all.

This is especially compelling in the kinds of projects identified in the presentation: airports, rail, transit, bridges, dams, ports, highways, power plants, underground works, universities, and medical facilities. What these projects share is length, complexity, and risk. In such settings, the project’s success depends not just on what legal remedies exist at the end, but on whether neutral structures exist during performance to prevent routine friction from becoming paralytic conflict. The beneficiaries are not only the employer and contractor, but also the engineer, subcontractors, funding agencies, and ultimately the project itself.

The move from 1999 to 2017 is not merely a drafting update. It reflects a jurisprudence of project governance. The earlier suite acknowledged, in more limited ways, that agreement-seeking and neutral opinions could help. The later suite formalized that insight and turned dispute avoidance into an express contractual objective. It renamed the board, required its earlier constitution, empowered it to assist informally, tied site visits and meetings to awareness of potential disputes, and built procedural space for amicable resolution even after formal processes have begun. What was once implicit became explicit; what was once optional became structural.

This has direct implications for the Philippines. The country once thought arbitration was enough because it had not yet fully internalized the cost of unmanaged escalation on live projects. But once infrastructure became larger, more layered, and more dependent on continuous delivery, it became clear that arbitration, though necessary, is temporally late. It resolves the dispute after crystallization. A standing dispute board intervenes before crystallization is complete.

That is why the more accurate modern formulation is not arbitration versus dispute boards, but dispute avoidance first, adjudication second, arbitration last. The Philippines does not need to abandon arbitration. It needs to reposition it as the final safeguard within a broader project-governance model that prioritizes real-time prevention, neutral engagement, and continuity of delivery. The stronger lesson of the FIDIC evolution is not simply that dispute boards are useful. It is that successful infrastructure now depends on recognizing that the best dispute is often the one that never fully forms.