Modern FIDIC projects operate within increasingly sophisticated contractual environments. Contracts are more detailed, notice regimes more formal, claims procedures more structured, approval routes more controlled — and project teams have greater access to commercial and legal advice than ever before.
Yet decisions are not necessarily being made earlier. Responsibilities are not necessarily clearer. Disputes are not necessarily being prevented.
On some projects, governance no longer asks first: what decision does the project need now? It asks: what position will be easiest to defend later?
That distinction matters. Legal discipline is essential in complex projects, but when every technical and commercial decision is shaped primarily around future dispute risk, governance can become slower, more defensive and less capable of resolving issues while they are still manageable. The contract remains strong. The project may not.
WHAT OVER-LEGALISATION ACTUALLY MEANS
Over-legalisation does not mean that lawyers are too involved. Complex projects need legal expertise — clear contracts, enforceable procedures, disciplined notices and credible dispute mechanisms that can prevent ambiguity and protect parties from decisions whose consequences haven’t been properly understood.
The problem begins when legal defensibility becomes the dominant measure of a project decision: an Engineer’s technical assessment delayed while every contractual implication is reviewed, an instruction passing through multiple layers of approval before it can be issued, a notice drafted primarily to protect a future claim rather than to resolve the issue now, a determination shaped more by surviving scrutiny months later than by reaching a timely, balanced decision today.
Each step may be reasonable in isolation. Collectively, they can move a project from active contract administration into permanent pre-dispute positioning.
The contract is no longer being used primarily to govern delivery. It is being used to prepare the record of a disagreement that everyone increasingly expects to happen.
MORE PROCEDURE DOES NOT AUTOMATICALLY MEAN MORE CONTROL
FIDIC governance relies on structure — defined authority, contractual notice requirements, supported claims, recorded decisions, respected timeframes. These disciplines are necessary. But process is not the same as control.
A project may have detailed approval matrices, extensive notice registers, formal claims procedures, legal review of significant communications, carefully drafted correspondence and an established Dispute Board — and still remain unable to resolve routine issues promptly. The existence of procedure doesn’t guarantee that someone is willing and authorised to make a decision.
In weak governance environments, procedure can become a substitute for ownership: a matter is referred upward, then sideways, then to commercial review, then to legal review, then back to the Engineer for further substantiation. Execution continues, cost accumulates and positions harden while the project stays administratively active but operationally undecided.
A well-documented delay in decision-making remains a delay in decision-making.
WHEN LEGAL PROTECTION BEGINS TO REPLACE GOVERNANCE
Legal input exists to support sound decision-making — clarifying the contractual framework, identifying exposure, helping participants understand the consequences of their options. It begins to displace governance when the project becomes more concerned with avoiding responsibility than with making the decision itself.
A technical conclusion isn’t issued because the organisation wants absolute certainty about its downstream commercial effect. A reasonable interim decision is avoided because it might later read as an admission. A notice becomes longer and less operationally useful because every sentence is written for a future tribunal rather than the people who need to resolve the issue today. A mechanism meant to support timely administration becomes the reason administration slows down.
The project starts optimising for the dispute it may face tomorrow rather than the delivery problem it faces today. That may produce stronger documentation. It does not necessarily produce stronger governance.
THE ENGINEER AT THE CENTRE OF THE TENSION
The Engineer’s role sits directly at the intersection of technical judgement, contractual procedure and commercial consequence. That assessment may affect time, cost, entitlement and responsibility — so decisions that appear technical can attract extensive commercial and legal scrutiny. That scrutiny isn’t inherently inappropriate.
The difficulty arises when the Engineer remains responsible for administering the contract but no longer has practical authority to act without multiple layers of confirmation — expected to assess the facts, administer notices, monitor progress, evaluate variations, consider programme impact and issue determinations, while the ability to formalise those conclusions depends on approvals held elsewhere.
The Engineer carries visible responsibility. Practical decision-making authority is distributed across the Employer, commercial management, legal advisers and internal governance structures — and execution continues while those functions align.
On some projects, the Engineer is no longer administering the contract with legal support. The contract is being interpreted primarily through legal risk, with the Engineer left to implement the result.
That is not an argument against legal involvement. It is an argument for preserving the distinction between legal advice, commercial governance, contractual administration and independent technical judgement. When those functions support one another, governance becomes stronger. When one begins to replace the others, the project loses balance.
WHY THIS HAPPENS
Over-legalisation is rarely caused by one profession or one decision. It usually develops because the project organisation has lost confidence in its own ability to manage uncertainty.
Fear of precedent — a decision on one issue may influence later claims or interpretations, so teams hesitate to resolve matters without understanding every consequence. Fragmented authority — the person closest to the facts may not have authority to accept cost, time or contractual consequences. Weak contemporary records — where records are incomplete, teams become reluctant to decide because the factual basis may later be challenged. Previous disputes — organisations that have experienced significant claims often respond by adding control layers and legal review. Governance by escalation — instead of defining who decides what, organisations escalate whenever an issue becomes sensitive. Defensive project culture — participants are rewarded for avoiding personal exposure rather than reaching timely, balanced decisions.
Each response is understandable. Together, they can create a project in which everyone is involved and no one fully owns the decision.
THE EFFECT ON LIVE PROJECT DELIVERY
When governance becomes excessively defensive, the first consequence isn’t necessarily a formal dispute. It’s operational drift.
Instructions remain provisional. Variations remain acknowledged but unvalued. Responsibilities remain discussed but unallocated. Delay events remain technically recognised but contractually unresolved. The project continues because execution teams absorb the uncertainty — one party performs work while reserving its rights, another allows execution while reserving its position, the Engineer records the issue but waits for confirmation, commercial teams maintain unresolved-item registers, legal advisers protect the language used in correspondence.
Movement continues. Control weakens. By the time the matter reaches a Dispute Board, adjudication or arbitration, the dispute mechanism isn’t the cause of the governance failure — it’s the place where the accumulated consequences finally become visible.
FORMAL DISPUTE PROCEDURES ARE DOWNSTREAM
Dispute Boards are an important part of the FIDIC structure, providing a defined route for resolving disagreements the parties and project administration have been unable to settle. But they are downstream of the real governance point.
By the time a matter reaches formal dispute resolution, the instruction has already been given or withheld, the work has already been performed, the delay has already occurred, the notice period has already run, the records have already been created or missed, and the parties’ commercial positions have already hardened.
The Dispute Board doesn’t usually determine whether governance worked. It reveals where governance stopped working earlier. A project that relies on formal dispute mechanisms as its principal decision route isn’t demonstrating strong contractual governance — it’s demonstrating that earlier governance mechanisms were unable to produce an accepted outcome.
Dispute procedures should remain a safeguard. They should not become the normal operating system of the project.
GOVERNANCE SHOULD REDUCE CONFLICT — NOT INSTITUTIONALISE IT
The purpose of governance is not to create more process. It is to improve the quality, timing and traceability of decisions.
Effective governance makes risks visible before they crystallise, defines who has authority to decide, connects technical assessment with contractual consequence, allows provisional positions where full certainty isn’t yet possible, preserves rights without making every communication adversarial, escalates issues before delay and cost become entrenched, and maintains a common record while the parties still have room to agree.
Legal mechanisms support this structure — they help ensure decisions are made within the contractual framework and that consequences are understood. But governance becomes weaker when legal review is used to compensate for unclear authority, poor records or reluctance to make decisions.
Legal discipline should strengthen project judgement. It should not replace it.
WHAT BALANCED FIDIC GOVERNANCE LOOKS LIKE
Balanced governance doesn’t return the project to informal decision-making, and it doesn’t ask the Engineer to act without contractual discipline or commercial awareness. It creates a structure in which engineering judgement, commercial management and legal advice operate at the right level and the right time — through clearly defined delegated authority, approval thresholds proportionate to the decision, early coordination between technical, commercial and legal functions, notice procedures that preserve positions without preventing discussion, decision routes that distinguish consultation from approval, contemporaneous records created before an issue becomes contested, interim assessments where final certainty isn’t yet available, escalation based on consequence and urgency rather than organisational habit, and Dispute Boards used as safeguards rather than routine substitutes for project decisions.
The objective is not to eliminate legal risk. It is to prevent legal risk from becoming the organising principle of everyday delivery.
THE REAL QUESTION
Perhaps FIDIC governance hasn’t become over-legalised because lawyers became too involved. Perhaps it has become over-legalised because project organisations stopped making timely decisions and increasingly relied on contractual procedure to compensate for weak governance. Legal mechanisms then become dominant not because they were designed to run the project, but because earlier mechanisms failed to do so.
The question is not whether projects need strong legal discipline. They do. The question is whether that discipline is supporting engineering judgement and commercial decision-making — or gradually replacing them. Because a project governed primarily around the dispute it may face tomorrow is no longer fully governing the delivery problems it faces today.
THE PRINCIPLE
Contracts became more sophisticated. But sophistication should be measured by more than the quality of the drafting or the strength of the dispute mechanism — it should be measured by whether the governance structure helps the project decide earlier, allocate responsibility clearly, preserve technical judgement, manage commercial consequences and prevent manageable issues from becoming formal disputes.
A contract may be legally robust and still operate within weak project governance. A project may be procedurally compliant and still remain unable to make timely decisions.
Governance succeeds when legal discipline, commercial management and engineering judgement reinforce one another. It fails when procedure becomes the place where unresolved responsibility is allowed to hide.
How ACC TRUST can support
ACC TRUST supports Employers, contractors and project organisations in strengthening the connection between technical decision-making, contractual administration and commercial governance under FIDIC and other complex contract structures.
Support relevant to the issues examined in this article includes reviewing governance structures, delegated authority and approval routes; assessing the operational effect of Particular Conditions and internal procedures; clarifying the roles of the Employer, Engineer, Contractor and commercial teams; establishing notice, instruction, variation and decision-management processes; identifying issues delayed by fragmented or unclear authority; connecting technical assessments with programme, cost and contractual position; reviewing unresolved matters before they develop into formal claims or disputes; supporting early commercial assessment and dispute-avoidance strategy; and strengthening project reporting so that open decisions, responsibility and contractual exposure remain visible.
ACC TRUST provides commercial and contractual governance support and works alongside technical and legal advisers where specialist engineering or legal interpretation is required.
For support with FIDIC governance, contract administration, decision structures or unresolved commercial exposure:
Explore ACC TRUST services:
→ https://acctrust.ro/en/services
Discuss a specific project:
→ office@acctrust.ro
About ACC Trust Insights
ACC Trust Insights is the knowledge centre for Commercial & Contract Governance, Project Delivery and Risk Management in complex projects. The platform examines where technical execution, contractual administration, legal structure and commercial position intersect — and where project exposure often develops before it becomes visible through conventional reporting or formal dispute.
Each article draws on practice across construction, infrastructure and energy environments, translating recurring project patterns into practical governance principles for Employers, contractors, consultants, lenders and project leaders.
Explore ACC Trust Insights:
→ https://insights.acctrust.ro
ACC TRUST
Commercial & Contractual Governance Advisory
Property · Infrastructure · Energy
office@acctrust.ro