CCM Certified Contract Manager Questions and Answers

Under the FIDIC Red Book (1999), the Tender Documents typically include:

The Bill of Quantities (Option B), which provides detailed quantities for priced items and forms a basis for tender pricing.

The Specifications (Option E), which define the technical requirements for the Works.

The Schedule of Guarantees (Option A) is usually provided later, during contract formation, not as part of tender documents.

Employer’s Requirements (Option C) are more commonly referenced in design-build contracts such as the Yellow Book, not the Red Book which is traditionally a design-bid-build contract.

Schedule of Baselines (Option D) is not a standard tender document in FIDIC Red Book contracts.

Under the FIDIC Silver Book 1999, Sub-Clause 3.1 [The Employer’s Representative] provides that the Employer may appoint an Employer’s Representative to act on his behalf. This reflects the optional nature of this role in EPC/Turnkey contracts, where the Employer typically has a more limited involvement compared to Red Book arrangements.

Option B is correct because the contract explicitly allows (but does not mandate) such an appointment. The Employer’s Representative can carry out duties and exercise authority as delegated by the Employer.

Option A is incorrect because while neither the Employer’s Representative nor any other party can unilaterally amend the Contract, this statement is misleading and not specific to the role defined in the Silver Book.

Option C is incorrect because the appointment is not mandatory; the Employer may choose not to appoint a Representative.

Option D is incorrect because the Employer does not need the Contractor’s agreement to appoint an Employer’s Representative. The appointment is at the Employer’s discretion, although it must be notified to the Contractor.

This reflects a key feature of the Silver Book: greater Employer control and flexibility, with fewer administrative layers compared to contracts involving an independent Engineer.

Under Sub-Clause 8.3 of the FIDIC Red and Yellow Books 2017, the revised programme must reflect:

The planned sequence and timing of works including recognized holidays (Option A) to ensure realistic scheduling.

The actual progress to date, delays, and impacts on subsequent activities (Option B) so that stakeholders can manage resources and risks effectively.

Option C (remedial work) is typically not part of the main programme but may be in a separate defect rectification schedule.

Option D is too narrow; the programme should include all activities, not only undelivered materials.

Under FIDIC contracts:

Profit is usually allowed on claims arising from Employer-caused delays, instructions, or breaches that directly affect the Contractor’s performance or costs (Options A, B, C, and E).

Option D relates to delays caused by third parties (authorities). Typically, delays caused by relevant authorities (e.g., permit or approval delays) are treated differently, and profit is not generally recoverable on these claims as they are considered neutral or force majeure-type delays. The Contractor may receive an extension of time and reimbursement of direct costs but not profit.

Thus, Option D is the claim event where profit is not allowed.

The Commencement Date is a critical contractual milestone that triggers contractual obligations including the start of time for completion. For clarity and enforceability, it must be specified clearly in contract documents forming part of the formal contract. The Contract Agreement (Option B) and the Particular Conditions (Option C) are the standard places to unambiguously specify the Commencement Date.

Minutes of meetings (Option A) or emails (Option D), while useful for informal communication, do not have the legal certainty or binding contractual effect unless expressly incorporated into the contract documents. Therefore, specifying the Commencement Date solely in meeting minutes or emails is not advised for clarity and risk mitigation.

Under the FIDIC Red and Yellow Books 1999 editions, the Engineer acts as the Employer ' s representative with authority delegated under the contract. When an instruction requires the Employer’s prior approval, it is primarily the Engineer’s responsibility to obtain that approval before issuing the instruction to the Contractor.

The Contractor is not contractually required to verify whether the Engineer has obtained the Employer’s approval. The Contractor is generally entitled to rely on the Engineer’s instructions as valid and binding unless there is clear evidence to the contrary.

This principle avoids placing an undue administrative burden on the Contractor and maintains the hierarchical contract administration structure, where the Engineer is the primary point of contact and decision-maker.

In FIDIC Yellow Book (1999), the Contractor is responsible for scrutinizing the Employer ' s Requirements per Sub-Clause 5.1 and must notify any discrepancies or errors. However, passing this obligation to a Subcontractor, and requiring the Subcontractor to indemnify the Contractor for errors or defects arising from the Employer ' s Requirements or the Contractor ' s design, unfairly shifts risk and liability to the Subcontractor. The Subcontractor is likely not in a position to fully review or control the Employer’s Requirements or the overall Contractor’s design. This exposes the Subcontractor to excessive risk, beyond their scope and capacity.

Advice C highlights that the Subcontractor becomes vulnerable to claims for design defects outside their control. This misallocation of risk is generally not recommended and can be challenged during contract negotiation. Good contract management practice and risk allocation principles (FIDIC Contract Manager Study Guide, Module on Claims and Dispute Resolution) support this position.

While Options A, B, and D propose different approaches, only C correctly identifies the fundamental contractual and risk management issue that should prevent the Subcontractor from entering the contract as is.

According to the FIDIC 2017 editions (Red, Yellow, and Silver Books), when the Contractor submits a revised programme, the Engineer or Employer has a limited time (typically 14 days) to review and raise any Notice of Non-Compliance if the programme does not meet contract requirements (Sub-Clause 8.3 or equivalent). If no notice is issued within this period, the Engineer or Employer is deemed to have no objection to the revised programme.

This does not imply formal approval or consent, but the programme can be used for the execution and administration of the works in the absence of objections. This avoids unnecessary delay due to inaction.

Option D is correct as it captures this deemed “no objection” position.

Option B is incorrect as “deemed consent” is stronger than FIDIC provisions state; it is more correct to say “no objection”.

Option A is incorrect since the Contractor does not have to remind the Engineer or Employer for consent within this period.

Option C is incorrect because the Contractor may proceed if no non-compliance is notified.

Option B is correct: BIM is indeed a digital data technology applicable throughout the project lifecycle.

Option D is correct: Use of BIM requires careful consideration of contract clauses and appropriate adjustments in Particular Conditions.

Option A is incorrect; the 1999 edition does not mandate BIM use.

Option C is false; BIM improves quality, accuracy, delivery times, and cost efficiency.

Under FIDIC Yellow Book 1999, Sub-Clause 5.2 [Contractor’s Documents] requires the Contractor to submit design documents to the Engineer for review. Importantly, the responsibility for planning and coordinating these submissions lies with the Contractor.

The Contractor must ensure that the programme (Clause 8.3) allows sufficient time for the Engineer’s review process, including any resubmissions that may be required if documents are not approved initially. This reflects the design responsibility placed on the Contractor in the Yellow Book, where the Contractor controls both design and execution.

The Engineer’s role is to review and respond within the time stated in the Contract, but the Engineer is not responsible for integrating this review time into the overall project schedule. Similarly, the Employer has no direct role in managing this timing.

From a contract management perspective, failure by the Contractor to allow adequate review time may lead to delays for which the Contractor bears responsibility, as such delays would not typically qualify for Extension of Time unless caused by the Engineer exceeding prescribed review periods.

Thus, proper programming and coordination of document submissions is a key Contractor obligation, making Option A correct.

Under FIDIC Red Book 1999, Sub-Clause 12.3 [Evaluation] governs how the Engineer determines the value of work done. Sub-Clause 12.3(a) sets out conditions under which existing rates and prices in the Contract should be used for valuation, even if the quantity of work changes. It includes criteria such as similarity of work, similar conditions, and that the rate is appropriate.

However, the statement in the question is incorrect because it implies that all four criteria must be satisfied simultaneously before a new rate can be applied. In reality, FIDIC does not require all criteria to be strictly fulfilled in a cumulative manner. Instead, the Engineer exercises professional judgment to determine whether existing rates are appropriate. If they are not appropriate—due to significant changes in quantity, conditions, or nature of work—then new rates or prices may be determined.

Furthermore, Sub-Clause 12.3 provides flexibility and refers to Clause 13 [Variations and Adjustments] where necessary. The valuation process is not rigidly conditional upon all criteria being met but rather guided by fairness and reasonableness.

Therefore, the statement is false because it misinterprets the application of the criteria as absolute and cumulative, whereas FIDIC allows discretion and does not impose such a strict requirement.

Under FIDIC Red Book 1999, the Performance Security (or Performance Guarantee) is held to ensure the Contractor’s performance during the defects liability period. The security is typically released only after the Employer issues the Performance Certificate, which confirms the completion of defects liability obligations and that the Contractor has fulfilled the contract.

The contract commonly specifies a fixed period (often 21 days) within which the Employer must return the Performance Security after issuance of the Performance Certificate (Option D). The Taking-Over Certificate (Options A and C) marks substantial completion but does not end the Contractor’s obligations for defects.

Option B is correct: A Variation is a formal change to the Works instructed by the Engineer via a Notice (Sub-Clause 3.5). This includes changes to design or execution such as slopes on a road.

Option A is a proposal, not yet a Variation. Positive interest does not constitute a Variation.

Option C is partially correct but depends on formal instruction after proposal acceptance; the question specifies the Engineer instructs the Variation, but since it was a request for proposal first, the Variation instruction comes later. Without explicit instruction, this is not yet a Variation.

Option D is invalid as verbal instruction plus a Notice denying cost claims does not constitute a proper Variation.

Option B is correct: Deleting critical dispute resolution Sub-Clauses 20.2 - 20.4 contradicts the Golden Principles by undermining fair dispute handling.

Option D is correct: Extending payment release to 180 days violates timely payment principles and fairness in cash flow management.

Option A is generally acceptable as the Contractor often assumes responsibility for nominated subcontractors.

Option C is acceptable in some jurisdictions and contracts to provide finality but can be debated.

Y is not correct. The Contractor’s obligation to commence works depends on the Commencement Date notification as per the contract. If the Employer requests commencement on the 14th day after signing, and the contract allows or the Engineer has not yet notified otherwise, the Contractor should comply unless formally instructed otherwise.

Delaying work beyond the contractual or Employer’s instruction without valid cause may be considered breach of contract and could lead to claims against the Contractor.

Both claims are valid under the Silver Book principles:

The error in the Employer ' s Requirements (typo in NTS-PW-01) leads to entitlement for additional piling costs.

The unforeseen hydrological data causing additional flood protection works qualify as unforeseeable physical conditions entitling the Contractor to compensation.

Hence, Option D is correct — the Contractor is entitled to both claims.

Under the FIDIC Red Book (both 1999 and 2017 editions), the Employer is responsible for the design of the Works. This design is primarily communicated to the Contractor through key technical documents included in the Contract.

Option B (Specifications) is correct because Specifications define the technical requirements, standards, materials, workmanship, and performance criteria. They are a core component of the design documentation and directly guide how the Works are to be executed.

Option A (Bill of Quantities) is also correct. While primarily used for measurement and payment, the Bill of Quantities is derived from the design and reflects the quantified scope of the Works. It is intrinsically linked to the design and provides a structured breakdown of the elements required to construct the Works.

Option C is incorrect because the Breakdown of Lump-Sum is relevant to lump-sum contracts (e.g., Silver Book), not the Red Book’s remeasurement approach.

Option D is incorrect as the Schedule of Subcontractors relates to execution planning, not design.

Option E is incorrect because the Contract Agreement is a legal document formalizing the contract, not a design document.

Thus, in Red Book contracts, the design basis is fundamentally established through the Specifications and the Bill of Quantities, supported typically by Drawings (though not listed here).

Option C does NOT, on its own, provide grounds for termination. The Contractor’s request for evidence of financial arrangement, without further contractual breach, is insufficient to terminate.

Options A, B, and D are valid grounds for termination under FIDIC Yellow Book 2017 due to prolonged suspension, non-payment beyond allowed period, or failure to comply with binding determinations.

Options A and B are correct: Both the Red and Yellow Books require the Engineer to certify payments before the Employer pays the Contractor.

Option C (Silver Book) typically places the risk on the Contractor and often provides for payment without Engineer certification, reflecting the turnkey nature of the contract.

FIDIC Golden Principle 2 (GP2) emphasizes that Particular Conditions must be drafted clearly, precisely, and without ambiguity, ensuring that any modification to the General Conditions is transparent and easily understood.

Option D directly reflects this requirement. It highlights that any changes to the General Conditions must be explicitly referenced to the relevant Sub-Clauses and must clearly indicate the nature of the modification (addition, replacement, omission, etc.). This approach ensures traceability, avoids confusion, and preserves the contractual clarity essential for proper administration and dispute avoidance.

Options A, B, and C all contradict the Golden Principles by promoting ambiguity or informal modification practices. Allowing inconsistent clarifications, relying on implicit amendments, or incorporating changes via emails without properly integrating them into the Particular Conditions undermines contractual certainty and increases the risk of disputes.

From a contract management perspective, clear drafting of Particular Conditions is critical to maintaining the integrity of FIDIC contracts, ensuring that all Parties have a shared and precise understanding of their rights and obligations.

Thus, Option D best reflects the intent and application of FIDIC Golden Principle 2.

Under FIDIC Red Book 1999, advance payment is intended to assist the Contractor in financing the mobilization and early works costs before the Contractor begins receiving regular payments for work performed (Option A). It is not a payment for work already completed, so Option B is incorrect.

The General Conditions provide that the advance payment is usually made in a lump sum or agreed instalments and that the Employer makes the payment in advance (Option C is partially true but generally it can be one or multiple instalments, depending on contract terms).

Importantly, the advance payment must be repaid by the Contractor through deductions from subsequent interim payments (Option D), ensuring the Employer recovers the advanced funds as the work progresses.

Option B is correct. Under FIDIC contracts, the Contractor must provide proof of how the Provisional Sum has been expended when requested by the Engineer. This ensures transparency and proper use of funds allocated as Provisional Sums.

Option A is incorrect; Provisional Sums are often used based on instructions from the Engineer or Employer.

Option C is incorrect because Provisional Sums are precisely intended to be used, in whole or in part, according to Engineer’s or Employer’s instructions.

Under the FIDIC Silver Book 1999, the priority of documents is defined in the Appendix to the Contract Agreement and reflected in Sub-Clause 1.5 [Priority of Documents]. This hierarchy determines which document prevails in case of discrepancies or inconsistencies.

The correct order begins with the Contract Agreement, which forms the legal foundation of the contract. It is followed by the Conditions of Contract (General and Particular Conditions), which define rights, obligations, and risk allocation.

Next in priority are Addenda, which include clarifications and modifications issued during the tender stage. These are crucial because they may amend earlier tender documents and must take precedence over them.

After Addenda come the Employer’s Requirements, which define the technical scope, specifications, and performance criteria of the project. Finally, the Contractor’s Tender is ranked last, as it reflects the Contractor’s offer based on all preceding documents.

This hierarchy ensures consistency and clarity, especially in EPC/Turnkey projects where design responsibility lies with the Contractor but is guided by the Employer’s Requirements. Proper understanding of document priority is essential for resolving ambiguities and managing contractual risks effectively.

This statement is true. Under FIDIC Silver Book 1999, Sub-Clause 8.6, the Employer can instruct the Contractor to submit a revised programme to meet the contractual Time for Completion. If, after such instruction, the revised programme still shows the Works will not complete on time, the Employer may claim additional costs (such as delay damages or compensation) due to continued delay.

Thus, the Employer’s right to claim additional costs is contingent on the revised programme not enabling timely completion.

Option A best describes the Time for Completion as the Contractor’s fundamental obligation to complete the entire Works within the contractual Time for Completion, calculated from the Commencement Date.

Options B, C, and D incorrectly limit the scope to " most " of the Works or confuse the reference date.

The Time for Completion sets the critical timeline for contract performance and triggering of delay damages or extensions.

Option B is correct: Notices are compulsory when required and must reference the relevant Sub-Clause to be valid.

Option D is correct: Notices are formal written communications and must comply with the contract’s prescribed procedures.

Option A is incorrect; notices are often mandatory, not merely recommended.

Option C is incorrect; notices are obligations for all Contract Participants, not just the Engineer.

Under FIDIC Red Book 1999, the Engineer plays a key role in determining claims submitted by the Contractor (Clause 20). If the Engineer fails to make a determination within the prescribed time, the Parties may be unable to resolve the dispute and thus the matter may proceed to dispute resolution mechanisms.

Option B is correct because if the Engineer does not decide, the claim remains unsettled, and the Parties are left to resolve the dispute, often via Dispute Adjudication Board or arbitration.

Option A is incorrect; claims must comply with notice requirements to be valid.

Option C is incorrect because the Engineer may request further particulars but is not obligated to give a final decision on quantum immediately.

Option D is incorrect as the Engineer, not the Employer’s Representative, first responds to claims.

Option E is incorrect since the Engineer’s decision is not final and binding if disputed; it may be challenged.

Option B is correct: The Contractor must obtain approval from the Engineer/Employer before making design changes.

Option C is correct: The Contractor can submit Value Engineering proposals to improve efficiency or reduce costs.

Option A is incorrect; unilateral changes are not allowed.

Option D is incorrect; Value Engineering can be proposed even after initial submission.

Under both FIDIC Red and Yellow Books (1999 and 2017 editions), the Engineer is defined as the person appointed by the Employer to carry out duties assigned under the Contract (Clause 3). However, FIDIC does not prescribe any specific qualification, such as requiring the Engineer to have a formal technical education.

The contract focuses on the role and functions of the Engineer rather than formal credentials. The Engineer is expected to act as a professional administrator of the contract, performing duties such as issuing instructions, certifying payments, making determinations, and acting neutrally when required (especially under FIDIC 2017, Clause 3.7). While in practice Engineers are typically qualified professionals (often engineers by training), this is a matter of industry practice, not a contractual requirement.

FIDIC intentionally avoids prescribing qualifications to allow flexibility for the Employer in appointing a suitable representative with the necessary competence and experience for the specific project. The emphasis is on capability and impartiality, rather than formal academic credentials.

Therefore, the statement is false because FIDIC contracts do not mandate that the Engineer must have received technical education

Under FIDIC 1999 Conditions of Contract, retention money is addressed primarily in Sub-Clause 14.9 [Payment of Retention Money]. The release of retention is typically split into two halves: the first half upon issuance of the Taking-Over Certificate, and the second half after the Defects Notification Period (DNP) has expired and all outstanding work has been completed.

However, the contract provides a safeguard for the Employer (and Engineer administering the contract) where there are outstanding defects or incomplete obligations. In the Red Book, Clause 11 [Defects Liability] governs the Contractor’s obligation to remedy defects during the DNP. Similarly, in the Yellow and Silver Books, Clause 12 [Tests after Completion] may require additional works or compliance activities after completion.

If there are works still to be executed or defects yet to be remedied, the Engineer is entitled to withhold an amount equivalent to the estimated cost of completing such works from the retention money due for release. This ensures the Employer is financially protected in case the Contractor fails to fulfill post-completion obligations.

Therefore, the statement is correct, as it accurately reflects the contractual mechanism allowing withholding of retention corresponding to outstanding liabilities under the relevant clauses.

In the FIDIC Silver Book (1999 and 2017 editions), which is tailored for EPC/Turnkey contracts, the Employer is responsible for notifying the Contractor of the Commencement Date (Sub-Clause 8.1). Unlike other FIDIC contracts where the Engineer might notify commencement, the Silver Book places more responsibility on the Employer due to the nature of the contract where the Contractor is largely responsible for design and execution with fewer Engineer roles.

The Employer’s formal notification of the Commencement Date signals the official start of the Contractor’s obligations and triggers timelines under the contract.

The Engineer or Resident Engineer typically does not issue such notice in the Silver Book framework.

Option A is correct: “Notice” is a defined term under FIDIC 2017 Red Book; “Other Communications” is a separate category, also defined but distinct.

Option D is correct: Notices, Notices of Dissatisfaction, and Certificates require delivery to all Parties and the Engineer, whereas other communications may not have such strict requirements.

Option B is incorrect as there are contractual differences.

Option C is partially correct but “Other Communications” and “Notice” are distinct terms, so A is more precise.

Under the FIDIC Red Book 2017, Clause 21 establishes a standing Dispute Avoidance/Adjudication Board (DAAB) as a default requirement. This is a major evolution from the 1999 edition, where a Dispute Adjudication Board (DAB) could be ad hoc. Therefore, Option C is correct, as the General Conditions clearly provide for a standing DAAB appointed at the outset of the Contract.

Option D is also correct. The appointment procedure for DAAB members requires mutual agreement between the Parties. Even if one Party nominates a member, that nomination must be accepted by the other Party to ensure neutrality, independence, and confidence in the dispute resolution process.

Option A is incorrect because amicable settlement (Clause 21.5) is required after a DAAB decision and before arbitration, not before referring a matter to the DAAB.

Option B is incorrect because DAAB decisions are binding immediately (whether or not final), unless and until revised by arbitration. They are not dependent on prior confirmation by arbitration to be binding.

Option E is incorrect because failure to give a Notice of Dissatisfaction (NoD) relates to a DAAB decision becoming final and binding—not an Engineer’s determination. The statement incorrectly mixes procedural steps.

These provisions reflect FIDIC’s structured multi-tier dispute resolution system, promoting early resolution through DAAB before escalation to arbitration.

The Contractor may submit Value Engineering proposals to improve efficiency or reduce costs; however, it is not an absolute contractual obligation to submit such proposals. Also, the preparation of these proposals is generally at the Contractor’s own cost initially. If the proposal is accepted and results in a Variation, then adjustments to the Contract Price may occur, potentially reimbursing the Contractor.

Thus, both statements are false.

Under FIDIC Red Book 2017, Clause 1.3 [Communications] provides strict and structured requirements governing Notices and other forms of communication. The distinction between a “Notice” and “other communication” is critical because Notices often trigger contractual rights, obligations, and time bars.

Option A is correct because Clause 1.3 expressly requires that a communication intended to be a Notice must be clearly identified as such. This ensures that both Parties understand the formal and legal significance of the communication, particularly where time-sensitive provisions (such as claims under Clause 20) are involved.

Option C is also correct. Clause 1.3 differentiates between Notices and other communications. Where a communication is not a Notice, it should still be clearly identified as another form of communication and, where appropriate, include references to the relevant contractual provision. This promotes clarity, traceability, and proper contract administration.

Option B is incorrect because communications must generally be sent to the addresses stated in the Contract Data unless formally changed by notice. Delivering to an alternative address without proper notification may render the communication invalid.

Option D is incorrect because communications are not limited to the Contractor’s Representative; they must be sent to the designated addresses of the respective Parties as defined in the Contract Data.

Overall, Clause 1.3 reinforces disciplined communication management, which is a cornerstone of effective FIDIC contract administration.

Under the FIDIC Silver Book 1999, Clause 9 governs Tests on Completion, while Clause 12.4 addresses Tests after Completion. These provisions define performance verification before and after Taking-Over.

Option A is correct. Under Sub-Clause 9.4 [Failure to Pass Tests on Completion], if the Works fail the Tests on Completion, the Employer has several options, including accepting the Works subject to a reduction in the Contract Price. This reflects the commercial flexibility within FIDIC, allowing completion despite minor deficiencies, with financial adjustment.

Option D is also correct. Under Sub-Clause 12.4 [Failure to Pass Tests after Completion], if the Works fail post-completion performance tests, the Contractor may be required to pay performance damages. Once these damages are paid, the Works may be deemed to have satisfied the required performance levels. This mechanism ensures that operational deficiencies are compensated financially rather than requiring physical rectification in all cases.

Option B is incorrect because both Tests on Completion and Tests after Completion can coexist within the same contract; they serve different purposes (pre-taking-over vs post-taking-over performance verification).

Option C is incorrect because Tests after Completion are generally carried out by or under the responsibility of the Contractor, not solely the Employer, although the Employer may witness them.

These provisions demonstrate FIDIC’s structured approach to quality assurance and risk allocation across different project stages.

Under FIDIC Red Book 1999, Sub-Clause 17.3 defines Employer’s Risks, which include war, hostilities, rebellion, revolution, insurrection, or military/usurped power. The scenario clearly falls within “insurrection,” making it an Employer’s Risk. Consequently, under Sub-Clause 17.4, the Contractor is entitled to both Extension of Time (EOT) and Cost if such risks affect execution of the Works.

At this stage, the Engineer must acknowledge that the event qualifies as an Employer’s Risk and that entitlement in principle exists. However, the exact quantum of delay and Cost cannot yet be determined because the situation is ongoing. FIDIC practice allows for such claims to be assessed after the effects are known. Importantly, the Contractor has already provided notice, satisfying Sub-Clause 20.1 requirements.

Option B is incorrect because entitlement is not conditional upon the end of the event; only quantification is deferred. Option C is wrong because foreseeability does not negate Employer’s Risks explicitly listed in Sub-Clause 17.3. Option D misapplies Sub-Clause 2.1, which relates to access to the Site, not political violence or insurrection.

Therefore, Option A correctly reflects FIDIC principles: recognition of entitlement with later assessment of time and cost.

FIDIC’s Golden Principles (GPs) guide good contract management and administration. Golden Principle 1 (GP1) emphasizes “Clear communication and documentation” to avoid misunderstandings and disputes. It specifically promotes thorough documentation of all agreements and clarifications reached during the tender process. The use of a memorandum of understanding or similar record ensures transparency and mutual understanding. Furthermore, the formal award of the contract by a signed letter of acceptance aligns with the principle of clear and formal contract formation.

GP1 ensures that all key matters, changes, and agreements are properly documented during the tender phase and contract award to form an unambiguous contractual basis.

GP2 and GP3 relate more to ongoing contract administration, risk management, and dispute resolution rather than the contract formation process.

GPA (Golden Principle A) is not a standard FIDIC term associated with contract formation or tender stage documentation.

Therefore, the described process aligns best with Golden Principle 1 (GP1).

According to the FIDIC Red Book 1999, Sub-Clause 14.10 – Application for Final Payment Certificate and related procedures allow the Contractor to submit the Final Statement, which includes the final account of all sums due.

If after submission the Contractor identifies errors or omissions in the Final Statement, the Contractor is generally entitled to submit corrections or adjustments to that statement before the issuance of the Final Payment Certificate. This ensures that the final account accurately reflects all amounts due.

The Engineer reviews the Final Statement and may seek clarifications or adjustments. The contract typically allows the Contractor to correct or revise the Final Statement as part of this review process.

However, once the Final Payment Certificate is issued and accepted by the parties, it becomes more difficult for the Contractor to amend the Final Statement without formal agreement or dispute resolution.

Hence, prior to certification, the Contractor can correct the Final Statement.