Is the FIDIC Engineer the Employer's agent or a neutral decision-maker?

The clearest answer is: both descriptions can be correct, but not at the same moment and not for the same function. Under the 2017 Red and Yellow Books, the Engineer is appointed by the Employer and is generally deemed to act for the Employer when carrying out the ordinary contract-administration functions assigned by the contract. But when the Engineer moves into the Clause 3.7 process to encourage agreement or make a determination, the contract expressly changes the required posture: the Engineer is to act neutrally between the Parties and make a fair determination taking account of the relevant circumstances. Treating the Engineer as either a completely independent arbitrator or simply the Employer's messenger misses this functional distinction.

The ordinary Engineer role is broad and very operational. Depending on the form and project, it includes programme review, measurement, payment certification, instructions, variation administration, inspection and testing, notices to correct, Taking-Over Certificates and the Performance Certificate. These are not ceremonial functions. A late programme review, an unclear instruction, an undocumented variation position or an incomplete testing record can alter the commercial and schedule position of the project. The 2017 forms deliberately place more emphasis on active and timely contract management, which means the Employer must resource the Engineer role as a real project-control function rather than a signature authority.

Clause 3.7 is where the distinction becomes most important. The Engineer first consults with the Parties in an effort to reach agreement. If agreement is not achieved within the contractual period, the Engineer proceeds to a fair determination. In the 2017 Red and Yellow Books, the consultation and determination steps are governed by defined time limits, commonly described as up to 42 days for the agreement stage followed by up to a further 42 days for determination unless the contract provides or the parties agree otherwise. This turns claim handling into a managed process with deadlines for the Engineer as well as the claiming party.

Neutral does not mean detached from the project. The Engineer may have spent months reviewing the programme, issuing certificates, attending site meetings and administering instructions before the same subject reaches determination. The contractual safeguard is that, in the determination function, the Engineer is not to act as the Employer's advocate. The analysis should be traceable to the contract, contemporaneous records, programme logic, technical cause and effect, valuation evidence and the circumstances that matter to the entitlement. This is one reason why weak project records damage both sides: the Engineer cannot make a robust fair determination from opinions alone.

The Engineer's determination is also not something the parties can ignore while deciding what to do later. Under the 2017 process, a determination is binding unless and until it is revised through the contract's dispute mechanisms, and a party that is dissatisfied must pay close attention to the Notice of Dissatisfaction deadline. The 2017 forms use a 28-day NOD period after receipt of the determination; failure to preserve dissatisfaction can cause the relevant agreement or determination to become final and conclusive under the contract. This is why a contract-management calendar must track not only claim notices but Engineer decisions and the deadlines that follow them.

Can the Employer restrict the Engineer? For many ordinary powers, the Particular Conditions may identify situations in which Employer consent is required. But the determination function is deliberately protected. FIDIC's structure and Golden Principles are intended to preserve the roles that make the contract work, and restrictions that prevent the Engineer from exercising the required professional judgment can undermine the administration model. Owners should therefore distinguish governance from interference: it is legitimate to define authority, reporting and escalation, but not to turn a contractual determination into a pre-approved Employer position while still presenting it as the Engineer's neutral assessment.

The Silver Book needs separate treatment because it does not use the same Engineer role. The Employer or Employer's Representative performs the corresponding administration functions under that form. That is another reason not to transfer Red/Yellow Book assumptions casually into an EPC/turnkey contract. Gokbilge Engineering supports FIDIC-based projects from the project-management and engineering side by establishing authority matrices, correspondence protocols, decision registers, programme controls, change workflows and technical substantiation that allow the contract administrator — Engineer, Employer's Representative or project team — to make decisions from controlled evidence. Legal independence, conflicts and governing-law duties should be addressed with qualified legal counsel.

This article explains FIDIC contract administration from an engineering and project-delivery perspective. It is not legal advice. The signed contract, Particular Conditions, applicable law and the exact FIDIC edition/reprint always govern the project.