ZFCC工期索赔.合同管理(FIDIC+GCPCaR) - Z6

📋 概述 / Overview

本SKILL专注于国际工程项目的合同管理，涵盖从合同条款起草、索赔管理到争议预防的全流程，帮助用户预防争议、规范管理。

适用场景 / Applicable Scenarios：
- 国际工程项目投标（合同条件审核）/ International engineering project bidding (contract condition review)
- 合同条款起草和审核 / Contract clause drafting and review
- 索赔管理和策略制定 / Claim management and strategy development
- 争议预防和解决 / Dispute prevention and resolution
- 项目团队合同管理培训 / Project team contract management training

📋 目录 / Table of Contents

核心理论 / Core Theory

• 概述 / Overview
• 核心标准集成 / Core Standards Integration
• FIDIC Clause 8详解 / FIDIC Clause 8 Details

实践应用 / Practical Application

• 可执行功能 / Executable Functions
• 实践指导 / Practice Guidance
• 常见问题 / FAQ

附录 / Appendix

• 版本历史 / Version History
• 品牌说明与联系方式 / Brand Description and Contact Information

🌍 核心标准集成

本SKILL完整集成以下3大权威标准：

标准1: FIDIC Conditions of Contract (Clause 8)

来源: 国际咨询工程师联合会（FIDIC）
名称: Conditions of Contract - Clause 8 (Commencement, Delays and Suspension)
版本: 1999版 vs. 2017版对比
地位: 国际工程合同金标准
适用范围: 全球120+国家，特别是发展中国家

Clause 8 核心条款详解：

8.1 Commencement of Works（工程开工）

1999版：
- 工程师在"收到中标函后"发出开工通知
- 开工日期：收到通知后"合理时间内"（通常14-28天）

2017版：
- 工程师在"收到履约保证后"发出开工通知
- 开工日期：收到通知后"14天内"
- 变化：2017版更明确、更严格

最佳实践：
- 承包商：收到开工通知后，立即准备进场
- 工程师：在现场准备好后再发出通知
- 雇主：确保现场 access 及时提供

8.2 Time for Completion（完工时间）

定义：从开工日期到完工日期（包括所有工作和测试）

1999版 vs. 2017版：
- 相同：都定义在"合同数据"（Contract Data）
- 不同：2017版更强调"合同数据"的透明度

最佳实践：
- 投标阶段：仔细审核完工时间是否合理
- 施工阶段：定期对比实际进度和计划进度
- 索赔阶段：如果完工时间不合理，可主张"合同受挫"

8.3 Programme（进度计划）

要求：
- 承包商在"收到开工通知后"提交进度计划
- 内容包括：施工顺序、关键路径、资源计划、里程碑
- 工程师审核：在"收到后合理时间内"（通常14-28天）
- 更新：定期更新（通常每月）

1999版 vs. 2017版：
- 1999版：相对宽松
- 2017版：更严格，要求"详细进度计划"

最佳实践：
- 使用CPM软件（P6、MS Project）
- 识别关键路径和近关键路径
- 定期更新（每月），保留更新记录
- 工程师审核后，作为"approved baseline"

8.4 Extension of Time for Completion（完工延期）- 核心条款

EOT理由（FIDIC合同）：
1. 变更（Variation）
2. 合同条件中定义的"延误"（Clause 8.4）
3. 异常天气（Exceptionally adverse weather）
4. 流行病（Epidemic）
5. 当局延误（Delays by Authorities）
6. 业主风险（Employer's Risks）
7. 不可抗力（Force Majeure）

通知要求：

1999版：
- "as soon as practicable"（较宽松）
- 无明确时限（建议在14天内）
- 无详细索赔报告要求

2017版：
- "within 14 days"（严格）
- "within 84 days"提交详细索赔报告
- 必须包括：事实、延误分析、证据

工程师决定：
- 1999版：在"收到索赔报告后合理时间内"
- 2017版："within 42 days"（明确时限）

8.5 Delay Damages（误期损害赔偿费）

定义：承包商未按时完工，向雇主支付的损害赔偿费

计算：
- 合同数据中规定金额/天
- 通常：合同价格的0.05%-0.1%/天
- 上限：通常有（如10%合同价格）

1999版 vs. 2017版：
- 相同：都按合同数据计算
- 不同：2017版更强调"预先估算的损失"

最佳实践：
- 误期损害赔偿费必须是"预先估算的损失"，不能是penalty
- 如果过高，可能被认定为penalty（无效）
- 承包商可主张：误期损害赔偿费是liquidated damages，不是penalty

8.6 Suspension（暂停）

雇主暂停：
- 雇主可随时指示暂停（Clause 8.6）
- 承包商：有权索赔工期 + 费用
- 如果暂停>84天，承包商可通知终止

承包商暂停：
- 如果雇主未按时付款，承包商可暂停
- 必须提前通知（14天）
- 有权索赔工期 + 费用 + 利润

8.7 Release of Suspension（暂停解除）

工程师指示恢复：
- 工程师指示恢复施工
- 承包商：检查现场、设备、材料
- 修复暂停期间的影响

工期 + 费用索赔：
- 承包商有权索赔：工期延长 + 费用增加
- 费用包括：人员窝工、设备闲置、材料保管

标准2: GCPCaR (Guide to Construction Claims and Resolutions)

来源: 美国咨询工程师协会（ACEC）
名称: Guide to Construction Claims and Resolutions
发布: 持续更新
地位: 索赔管理最佳实践
适用范围: 国际工程项目

核心内容：
- 合同管理
- 索赔策略
- 争议预防
- 谈判技巧
- 争议解决

GCPCaR 索赔管理全流程

阶段1：合同管理与索赔避免
- 合同审核：识别风险条款
- 同期记录：建立记录系统
- 变更管理：及时 documenting 变更
- 沟通管理：书面沟通、保留证据

阶段2：索赔通知与准备
- 及时通知：符合合同时限
- 事实记录：详细记录事件
- 证据收集：同期记录、照片、邮件
- 初步分析：评估索赔价值

阶段3：索赔报告撰写
- 事实陈述：项目背景、事件描述
- 法律依据：合同依据、法律原则
- 因果关系：事件如何影响工期/成本
- 损失计算：工期延长、成本增加

阶段4：谈判与争议解决
- 谈判策略：准备谈判方案
- 争议解决：DAAB、仲裁、诉讼
- 证据准备：专家证人、技术证据
- 和解评估：成本效益分析

GCPCaR 核心原则

原则1：同期记录至关重要
- 证人的记忆往往不可靠
- 高可信度的索赔必须锚定于同期生成的文档
- 建立3层记录基石：基准计划、同期文件、进度更新

原则2：及时通知是关键
- 未按时通知 = 丧失索赔权利
- 即使合同无明确规定，也应在合理期限内通知
- 先发出通知，再补充详细分析

原则3：成本效益分析
- 争议索赔价值 > 争议解决成本？
- 否：寻求妥协或放弃
- 是：推进索赔

原则4：优先谈判和解
- 诉讼/仲裁成本高、时间长、结果不确定
- 优先寻求主动和解
- 准备充分的索赔报告支持谈判立场

原则5：专业报告至关重要
- 使文档用户友好（目录、标题、图表）
- 使文档独立（包含所有参考文件）
- 引导审阅人得出逻辑结论
- 使用证据和附加文档证明

标准3: RICS EOT (Extensions of Time) - 补充标准

来源: 英国皇家特许测量师学会（RICS）
名称: Extensions of Time (EOT)
发布: 2014年（Black Book）
地位: 工料测量师国际标准
适用范围: 英国及英联邦国家、国际工程项目（common law体系）

核心内容（作为补充）：
- 5大延期分析方法
- EOT核心原则
- 通知要求
- 加速措施

与FIDIC的关系：
- FIDIC提供合同条件框架
- RICS EOT提供EOT分析方法
- 两者互补：FIDIC（合同） + RICS（方法）

🔧 核心能力

能力1: FIDIC合同条款审核与起草

你基于FIDIC合同条件（1999版 vs. 2017版）进行合同条款审核与起草：

审核要点

1. Clause 8.3（进度计划）
   - 提交时限是否明确？
   - 更新频率是否合理？
   - 工程师审核时限是否明确？

2. Clause 8.4（EOT）
   - EOT理由是否完整？
   - 通知时限是否合理（14天 vs. 28天）？
   - 详细索赔报告时限是否明确（84天）？

3. Clause 8.5（Delay Damages）
   - 计算基础是否合理？
   - 上限是否明确？
   - 是否过高（可能被认定为penalty）？

4. Clause 20（Claims）
   - 通知时限（2017版：28天）
   - 详细索赔报告时限（2017版：84天）
   - 工程师决定时限（2017版：42天）

起草建议

1. 进度计划条款
   - 明确提交时限（如"收到开工通知后14天内"）
   - 明确更新频率（如"每月更新"）
   - 明确工程师审核时限（如"收到后14天内"）

2. EOT条款
   - 明确EOT理由（参考FIDIC Clause 8.4）
   - 明确通知时限（建议28天，不要14天）
   - 明确详细索赔报告要求

3. 误期损害赔偿费条款
   - 明确计算基础（如"合同价格的0.05%/天"）
   - 明确上限（如"10%合同价格"）
   - 确保是"预先估算的损失"，不是penalty

能力2: 索赔管理与策略制定（基于GCPCaR）

你基于GCPCaR理论进行索赔管理与策略制定：

索赔管理流程

1. 合同管理与索赔避免
   - 审核合同条款（识别风险）
   - 建立同期记录系统
   - 管理变更（及时documenting）
   - 书面沟通（保留证据）

2. 索赔通知与准备
   - 及时发出通知（符合时限）
   - 详细记录事实
   - 收集证据材料
   - 初步评估索赔价值

3. 索赔报告撰写
   - 使用CEES框架（Cause, Effect, Entitlement, Substantiation）
   - 4部分结构化（事实、法律、因果、损失）
   - 使报告用户友好和独立
   - 引用同期记录和证据

4. 谈判与争议解决
   - 准备谈判策略
   - 评估和解方案
   - 准备争议解决（DAAB、仲裁）
   - 控制成本和时间

索赔策略制定

1. 评估索赔价值
   - 工期延长价值
   - 成本增加价值
   - 总部管理费和利润

2. 评估争议解决成本
   - 谈判成本
   - DAAB成本
   - 仲裁/诉讼成本

3. 制定策略
   - 索赔价值 > 成本：推进索赔
   - 索赔价值 < 成本：寻求妥协或放弃
   - 优先谈判，其次DAAB，最后仲裁

能力3: EOT申请与审核（基于RICS EOT）

你基于RICS EOT标准进行EOT申请与审核：

EOT申请流程

1. 发出通知（时限：合同规定，通常14-28天）
   - 描述事件
   - 初步评估影响
   - 保留权利

2. 提交详细EOT申请（时限：通知后28-42天）
   - 详细事件描述
   - 工期影响分析（使用CPM）
   - 证据支持
   - 申请的EOT天数

3. 跟进工程师决定（时限：合同规定，通常28-42天）
   - 如果超时未决定：发函催促
   - 如果拒绝：评估是否争议

EOT审核要点

1. 通知是否及时？
   - 检查通知日期
   - 对比合同时限

2. 延误事件是否属于EOT理由？
   - 对比合同EOT理由
   - 分析事件性质

3. 工期影响分析是否合理？
   - 检查方法（TIA、Window Analysis等）
   - 检查数据（基准、更新、实际）
   - 检查逻辑（关键路径分析）

4. 证据是否充分？
   - 同期记录
   - 事实证据
   - 技术证据

🛠️ 可执行功能

本SKILL提供以下可执行功能：

功能1：FIDIC合同条款审核

• 脚本：scripts/fidic_clause_auditor.py
• 输入：FIDIC合同文件
• 输出：合同条款审核报告
• 内容：风险条款识别、审核建议、条款对比（1999 vs. 2017）

功能2：合同条款起草

• 脚本：scripts/contract_clause_drafter.py
• 输入：项目信息、条款类型
• 输出：合同条款草案（Word格式）
• 内容：Clause 8条款、EOT条款、误期损害赔偿费条款

功能3：索赔管理流程优化

• 脚本：scripts/claim_management_optimizer.py
• 输入：项目信息、合同文件
• 输出：索赔管理流程优化建议
• 内容：同期记录系统、通知流程、报告模板

功能4：EOT申请与审核

• 脚本：scripts/eot_application_assessor.py
• 输入：EOT申请、合同文件
• 输出：EOT评估报告和决策建议
• 内容：通知合规性、分析方法、EOT天数计算

功能5：索赔报告撰写

• 脚本：scripts/generate_claim_report_structured.py
• 输入：项目信息、分析结果
• 输出：结构化索赔报告（Word格式）
• 内容：4部分结构化框架（基于Andy Hewitt CEES）

功能6：争议解决策略制定

• 脚本：scripts/dispute_resolution_strategist.py
• 输入：争议描述、索赔价值、预计成本
• 输出：争议解决策略建议
• 内容：谈判、DAAB、仲裁、诉讼的成本效益分析

功能7：同期记录评估

• 脚本：scripts/contemporaneous_record_evaluator.py
• 输入：项目文件清单
• 输出：同期记录充分性评估报告
• 内容：3层基石检查（基准计划、同期文件、进度更新）

📖 使用方法

1. FIDIC合同条款审核

请审核本FIDIC 2017版合同的Clause 8条款，识别风险条款。

2. 合同条款起草

请起草EOT条款，适用于中东地区公路项目，合同适用FIDIC 2017版。

3. 索赔管理流程优化

请优化本项目的索赔管理流程，项目位于沙特，合同适用沙特法律。

4. EOT申请与审核

请评估本EOT申请是否符合FIDIC 2017版要求。

5. 索赔报告撰写

请生成索赔报告，包括事实陈述、法律依据、因果关系、损失计算。

6. 争议解决策略制定

请制定争议解决策略，索赔价值500万美元，预计仲裁成本100万美元。

🎯 实践指导

阶段1：投标阶段

1. 审核合同条件
   - 重点审核Clause 8（开工、工期、EOT、误期损害赔偿费）
   - 重点审核Clause 20（索赔通知、详细报告、工程师决定）
   - 识别风险条款，准备谈判方案

2. 准备合同条款建议
   - 如果合同条款不合理，准备修改建议
   - 重点：EOT通知时限（建议28天）、详细报告时限（建议56天）

阶段2：施工阶段

1. 建立同期记录系统
   - 进度记录：基准、更新、实际
   - 沟通记录：RFI、指令、变更、邮件
   - 现场记录：日志、天气、照片、劳动力、设备

2. 管理变更
   - 及时documenting变更
   - 发出变更通知
   - 记录变更对工期和成本的影响

3. 发出索赔通知
   - 及时发出（14-28天内）
   - 先发出通知，再补充详细分析
   - 在所有通信中保留索赔权利

阶段3：索赔阶段

1. 准备索赔报告
   - 使用CEES框架
   - 4部分结构化
   - 引用同期记录

2. 提交索赔报告
   - 符合合同时限
   - 书面提交
   - 保留提交证据

3. 跟进工程师决定
   - 如果在时限内未决定，发函催促
   - 如果拒绝，评估是否争议

阶段4：争议解决阶段

1. 准备谈判
   - 准备谈判方案
   - 准备充分的索赔报告
   - 评估和解方案

2. 准备DAAB/仲裁
   - 准备争议通知
   - 准备证据
   - 准备专家证人

3. 执行决定/裁决
   - 如果获胜：执行工程师决定/DAAB裁决/仲裁裁决
   - 如果失败：评估是否继续争议（仲裁/诉讼）

⚠️ 注意事项

1. 本SKILL基于FIDIC合同条件（1999版和2017版）、GCPCaR和RICS EOT进行编制。
2. 合同条款审核和索赔管理建议仅供参考，具体案件需结合合同条款、证据材料、司法实践等综合判断。
3. 建议在使用本SKILL时，咨询合同管理和索赔管理专家。
4. 本SKILL不作为法律意见，仅供学习参考使用。

📚 版本历史

• v2.2.0 (2026-07-02)：优化description、添加目录、提供完整中英对照
• v1.1.0 (2026-06-29)：理论框架优化，从RICS+EOT优化为FIDIC+GCPCaR
• v1.0.0 (2026-06-28)：初始版本，基于RICS EOT和FIDIC Clause 8编制

📖 参考文献

1. FIDIC Conditions of Contract for Construction (1999 and 2017 Editions)
2. GCPCaR: Guide to Construction Claims and Resolutions
3. RICS Extension of Time (EOT) Core Guidance (2014)
4. Andy Hewitt: Claim Notices and Reports Theory
5. SCL Delay and Disruption Protocol, 2nd Edition (2017)

ℹ️ 品牌说明与联系方式

品牌说明

ZFCC (Zenfo Forensic Claims Consultant) 是The Honorable Zenfo（知府大人）创立的独立专业品牌，专注于国际工程索赔与争议解决。

专业性保证：
- 所有内容基于权威国际标准（FIDIC、GCPCaR、RICS等）
- 结合实际工程项目经验
- 持续更新以反映最新实践

联系方式

作者：The Honorable Zenfo（知府大人）
邮箱：xzf_83@qq.com
IMA知识库：ZFCC工程索赔（评论区留言，推荐方式）

专业咨询：
- FIDIC合同管理
- 索赔通知与报告
- 合同争议预防

END of SKILL.md (Chinese Version)

> 最后更新 / Last Updated: 2026-07-02

Complete English Version

Overview

This SKILL focuses on contract management for international engineering projects, covering the whole process from contract clause drafting, claim management to dispute prevention, helping users prevent disputes and standardize management.

Applicable Scenarios:
- International engineering project bidding (contract condition review)
- Contract clause drafting and review
- Claim management and strategy development
- Dispute prevention and resolution
- Project team contract management training

Table of Contents

Core Theory

• Overview
• Core Standards Integration
• FIDIC Clause 8 Details

Practical Application

• Executable Functions
• Practice Guidance
• FAQ

Appendix

• Version History
• Brand Description and Contact Information

Core Standards Integration

This SKILL completely integrates the following 3 major authoritative standards:

Standard 1: FIDIC Conditions of Contract (Clause 8)

Source: International Federation of Consulting Engineers (FIDIC)
Name: Conditions of Contract - Clause 8 (Commencement, Delays and Suspension)
Versions: 1999 edition vs. 2017 edition comparison
Status: International engineering contract gold standard
Applicable Scope: 120+ countries worldwide, especially developing countries

Clause 8 Core Provisions Details:

8.1 Commencement of Works

1999 Edition:
- Engineer issues notice of commencement "after receiving Letter of Acceptance"
- Commencement Date: "within reasonable time" after receiving notice (usually 14-28 days)

2017 Edition:
- Engineer issues notice of commencement "after receiving Performance Security"
- Commencement Date: "within 14 days" after receiving notice
- Change: 2017 edition is clearer and stricter

Best Practices:
- Contractor: Upon receiving notice of commencement, immediately prepare to mobilize
- Engineer: Issue notice only after site is ready
- Employer: Ensure site access is provided timely

8.2 Time for Completion

Definition: From Commencement Date to Completion Date (including all work and tests)

1999 vs. 2017:
- Same: Both defined in "Contract Data"
- Different: 2017 edition emphasizes "Contract Data" transparency more

Best Practices:
- Bidding stage: Carefully review if time for completion is reasonable
- Construction stage: Regularly compare actual progress vs. planned progress
- Claim stage: If time for completion is unreasonable, may argue "frustration of contract"

8.3 Programme

Requirements:
- Contractor submits programme "after receiving notice of commencement"
- Content: work sequence, critical path, resource plan, milestones
- Engineer review: "within reasonable time after receiving" (usually 14-28 days)
- Updates: Regular updates (usually monthly)

1999 vs. 2017:
- 1999 edition: Relatively lenient
- 2017 edition: Stricter, requires "detailed programme"

Best Practices:
- Use CPM software (P6, MS Project)
- Identify critical path and near-critical path
- Update regularly (monthly), retain update records
- After engineer review, use as "approved baseline"

8.4 Extension of Time for Completion - Core Clause

EOT Reasons (FIDIC Contract):
1. Variation
2. "Delay" defined in contract conditions (Clause 8.4)
3. Exceptionally adverse weather
4. Epidemic
5. Delays by Authorities
6. Employer's Risks
7. Force Majeure

Notice Requirements:

1999 Edition:
- "as soon as practicable" (relatively lenient)
- No clear time limit (recommend within 14 days)
- No detailed claim report requirement

2017 Edition:
- "within 14 days" (strict)
- Submit detailed claim report "within 84 days"
- Must include: facts, delay analysis, evidence

Engineer's Decision:
- 1999 edition: "within reasonable time after receiving claim report"
- 2017 edition: "within 42 days" (clear time limit)

8.5 Delay Damages

Definition: Damages paid by contractor to employer for failure to complete on time

Calculation:
- Amount/day specified in Contract Data
- Usually: 0.05%-0.1%/day of contract price
- Cap: Usually specified (e.g., 10% of contract price)

1999 vs. 2017:
- Same: Both calculated per Contract Data
- Different: 2017 edition emphasizes "pre-estimated loss"

Best Practices:
- Delay damages must be "pre-estimated loss", cannot be penalty
- If too high, may be deemed penalty (invalid)
- Contractor may argue: delay damages are liquidated damages, not penalty

8.6 Suspension

Employer Suspension:
- Employer may instruct suspension at any time (Clause 8.6)
- Contractor: Entitled to claim time + cost
- If suspension > 84 days, contractor may give notice of termination

Contractor Suspension:
- If employer fails to make timely payment, contractor may suspend
- Must give prior notice (14 days)
- Entitled to claim time + cost + profit

8.7 Release of Suspension

Engineer instructs resumption:
- Engineer instructs resumption of work
- Contractor: Inspect site, equipment, materials
- Remedy effects of suspension

Time + Cost Claim:
- Contractor entitled to claim: extension of time + increased cost
- Costs include: standby labor, idle equipment, storage of materials

Standard 2: GCPCaR (Guide to Construction Claims and Resolutions)

Source: American Council of Engineering Companies (ACEC)
Name: Guide to Construction Claims and Resolutions
Published: Continuously updated
Status: Best practice for claim management
Applicable Scope: International engineering projects

Core Content:
- Contract management
- Claim strategy
- Dispute prevention
- Negotiation skills
- Dispute resolution

GCPCaR Claim Management Process

Stage 1: Contract Management and Claim Avoidance
- Contract review: Identify risk clauses
- Contemporaneous records: Establish record system
- Change management: Timely documenting changes
- Communication management: Written communication, preserve evidence

Stage 2: Claim Notice and Preparation
- Timely notice: Comply with contract time limits
- Fact records: Detailed event records
- Evidence collection: Contemporaneous records, photos, emails
- Preliminary analysis: Assess claim value

Stage 3: Claim Report Writing
- Fact statement: Project background, event description
- Legal basis: Contract basis, legal principles
- Causation: How event affected time/cost
- Loss calculation: Time extension, cost increase

Stage 4: Negotiation and Dispute Resolution
- Negotiation strategy: Prepare negotiation plan
- Dispute resolution: DAAB, arbitration, litigation
- Evidence preparation: Expert witness, technical evidence
- Settlement evaluation: Cost-benefit analysis

GCPCaR Core Principles

Principle 1: Contemporaneous Records are Crucial
- Witness memory is often unreliable
- High-credibility claims must be anchored to contemporaneously generated documents
- Establish 3-layer record foundation: baseline programme, contemporaneous documents, progress updates

Principle 2: Timely Notice is Key
- Failure to give timely notice = loss of claim right
- Even if contract doesn't expressly require, notice should be given within reasonable time
- Give notice first, then supplement with detailed analysis

Principle 3: Cost-Benefit Analysis
- Dispute claim value > dispute resolution cost?
- No: Seek compromise or abandon
- Yes: Proceed with claim

Principle 4: Prioritize Negotiation and Settlement
- Litigation/arbitration is costly, time-consuming, uncertain
- Prioritize proactive settlement
- Well-prepared claim report supports negotiation position

Principle 5: Professional Report is Crucial
- Make document user-friendly (table of contents, headings, charts)
- Make document self-contained (include all reference documents)
- Guide reviewer to logical conclusion
- Use evidence and supporting documents to prove

Standard 3: RICS EOT (Extensions of Time) - Supplementary Standard

Source: Royal Institution of Chartered Surveyors (RICS)
Name: Extensions of Time (EOT)
Published: 2014 (Black Book)
Status: International standard for quantity surveyors
Applicable Scope: UK and Commonwealth countries, international engineering projects (common law system)

Core Content (as supplement):
- 5 major EOT analysis methods
- EOT core principles
- Notice requirements
- Acceleration measures

Relationship with FIDIC:
- FIDIC provides contract condition framework
- RICS EOT provides EOT analysis methods
- Complementary: FIDIC (contract) + RICS (method)

Core Capabilities

Capability 1: FIDIC Contract Clause Review and Drafting

You conduct contract clause review and drafting based on FIDIC contract conditions (1999 vs. 2017 edition):

Review Key Points

1. Clause 8.3 (Programme)
   - Is submission time limit clear?
   - Is update frequency reasonable?
   - Is engineer review time limit clear?

2. Clause 8.4 (EOT)
   - Are EOT reasons complete?
   - Is notice time limit reasonable (14 days vs. 28 days)?
   - Is detailed claim report time limit clear (84 days)?

3. Clause 8.5 (Delay Damages)
   - Is calculation basis reasonable?
   - Is cap clearly specified?
   - Is it too high (may be deemed penalty)?

4. Clause 20 (Claims)
   - Notice time limit (2017 edition: 28 days)
   - Detailed claim report time limit (2017 edition: 84 days)
   - Engineer decision time limit (2017 edition: 42 days)

Drafting Recommendations

1. Programme Clause
   - Clearly specify submission time limit (e.g., "within 14 days after receiving notice of commencement")
   - Clearly specify update frequency (e.g., "update monthly")
   - Clearly specify engineer review time limit (e.g., "within 14 days after receiving")

2. EOT Clause
   - Clearly specify EOT reasons (refer to FIDIC Clause 8.4)
   - Clearly specify notice time limit (recommend 28 days, not 14 days)
   - Clearly specify detailed claim report requirements

3. Delay Damages Clause
   - Clearly specify calculation basis (e.g., "0.05%/day of contract price")
   - Clearly specify cap (e.g., "10% of contract price")
   - Ensure it is "pre-estimated loss", not penalty

Capability 2: Claim Management and Strategy Development (Based on GCPCaR)

You conduct claim management and strategy development based on GCPCaR theory:

Claim Management Process

1. Contract Management and Claim Avoidance
   - Review contract clauses (identify risks)
   - Establish contemporaneous record system
   - Manage changes (timely documenting)
   - Written communication (preserve evidence)

2. Claim Notice and Preparation
   - Give timely notice (comply with time limits)
   - Record facts in detail
   - Collect evidence materials
   - Preliminary assessment of claim value

3. Claim Report Writing
   - Use CEES framework (Cause, Effect, Entitlement, Substantiation)
   - 4-part structured (facts, law, causation, loss)
   - Make report user-friendly and self-contained
   - Cite contemporaneous records and evidence

4. Negotiation and Dispute Resolution
   - Prepare negotiation strategy
   - Evaluate settlement options
   - Prepare for dispute resolution (DAAB, arbitration)
   - Control cost and time

Claim Strategy Development

1. Assess Claim Value
   - Time extension value
   - Cost increase value
   - Head office overhead and profit

2. Assess Dispute Resolution Cost
   - Negotiation cost
   - DAAB cost
   - Arbitration/litigation cost

3. Develop Strategy
   - Claim value > cost: Proceed with claim
   - Claim value < cost: Seek compromise or abandon
   - Prioritize negotiation, then DAAB, last arbitration

Capability 3: EOT Application and Assessment (Based on RICS EOT)

You conduct EOT application and assessment based on RICS EOT standard:

EOT Application Process

1. Give Notice (time limit: contract specifies, usually 14-28 days)
   - Describe event
   - Preliminary assessment of impact
   - Reserve rights

2. Submit Detailed EOT Application (time limit: 28-42 days after notice)
   - Detailed event description
   - Time impact analysis (use CPM)
   - Evidence support
   - EOT days claimed

3. Follow Up Engineer's Decision (time limit: contract specifies, usually 28-42 days)
   - If no decision within time limit: Send letter to urge
   - If rejected: Assess whether to dispute

EOT Assessment Key Points

1. Is notice timely?
   - Check notice date
   - Compare with contract time limit

2. Is delay event an EOT reason?
   - Compare with contract EOT reasons
   - Analyze nature of event

3. Is time impact analysis reasonable?
   - Check method (TIA, Window Analysis, etc.)
   - Check data (baseline, updates, actual)
   - Check logic (critical path analysis)

4. Is evidence sufficient?
   - Contemporaneous records
   - Factual evidence
   - Technical evidence

Executable Functions

This SKILL provides the following executable functions:

Function 1: FIDIC Contract Clause Review

• Script: scripts/fidic_clause_auditor.py
• Input: FIDIC contract document
• Output: Contract clause review report
• Content: Risk clause identification, review recommendations, clause comparison (1999 vs. 2017)

Function 2: Contract Clause Drafting

• Script: scripts/contract_clause_drafter.py
• Input: Project information, clause type
• Output: Contract clause draft (Word format)
• Content: Clause 8 clauses, EOT clauses, delay damages clauses

Function 3: Claim Management Process Optimization

• Script: scripts/claim_management_optimizer.py
• Input: Project information, contract document
• Output: Claim management process optimization recommendations
• Content: Contemporaneous record system, notice process, report template

Function 4: EOT Application and Assessment

• Script: scripts/eot_application_assessor.py
• Input: EOT application, contract document
• Output: EOT assessment report and decision recommendation
• Content: Notice compliance, analysis method, EOT days calculation

Function 5: Claim Report Writing

• Script: scripts/generate_claim_report_structured.py
• Input: Project information, analysis results
• Output: Structured claim report (Word format)
• Content: 4-part structured framework (based on Andy Hewitt CEES)

Function 6: Dispute Resolution Strategy Development

• Script: scripts/dispute_resolution_strategist.py
• Input: Dispute description, claim value, estimated cost
• Output: Dispute resolution strategy recommendation
• Content: Cost-benefit analysis of negotiation, DAAB, arbitration, litigation

Function 7: Contemporaneous Record Evaluation

• Script: scripts/contemporaneous_record_evaluator.py
• Input: Project document list
• Output: Contemporaneous record sufficiency assessment report
• Content: 3-layer foundation check (baseline programme, contemporaneous documents, progress updates)

Usage Methods

1. FIDIC Contract Clause Review

Please review Clause 8 of this FIDIC 2017 edition contract and identify risk clauses.

2. Contract Clause Drafting

Please draft EOT clause, applicable to highway project in Middle East, contract governed by FIDIC 2017 edition.

3. Claim Management Process Optimization

Please optimize the claim management process for this project, located in Saudi Arabia, contract governed by Saudi law.

4. EOT Application and Assessment

Please assess whether this EOT application complies with FIDIC 2017 edition requirements.

5. Claim Report Writing

Please generate claim report, including fact statement, legal basis, causation, loss calculation.

6. Dispute Resolution Strategy Development

Please develop dispute resolution strategy, claim value USD 5 million, estimated arbitration cost USD 1 million.

Practice Guidance

Stage 1: Bidding Stage

1. Review Contract Conditions
   - Focus on Clause 8 (commencement, time for completion, EOT, delay damages)
   - Focus on Clause 20 (claim notice, detailed report, engineer decision)
   - Identify risk clauses, prepare negotiation plan

2. Prepare Contract Clause Recommendations
   - If contract clauses are unreasonable, prepare amendment recommendations
   - Focus: EOT notice time limit (recommend 28 days), detailed report time limit (recommend 56 days)

Stage 2: Construction Stage

1. Establish Contemporaneous Record System
   - Progress records: baseline, updates, actual
   - Communication records: RFI, instructions, variations, emails
   - Site records: log, weather, photos, labor, equipment

2. Manage Changes
   - Timely documenting changes
   - Give change notices
   - Record impact of changes on time and cost

3. Give Claim Notices
   - Give timely (within 14-28 days)
   - Give notice first, then supplement with detailed analysis
   - Reserve rights in all communications

Stage 3: Claim Stage

1. Prepare Claim Report
   - Use CEES framework
   - 4-part structured
   - Cite contemporaneous records

2. Submit Claim Report
   - Comply with contract time limits
   - Submit in writing
   - Preserve evidence of submission

3. Follow Up Engineer's Decision
   - If no decision within time limit, send letter to urge
   - If rejected, assess whether to dispute

Stage 4: Dispute Resolution Stage

1. Prepare for Negotiation
   - Prepare negotiation plan
   - Prepare sufficient claim report
   - Evaluate settlement options

2. Prepare for DAAB/Arbitration
   - Prepare notice of dispute
   - Prepare evidence
   - Prepare expert witness

3. Execute Decision/Award
   - If win: Execute engineer decision/DAAB award/arbitral award
   - If lose: Assess whether to continue dispute (arbitration/litigation)

Important Notes

1. This SKILL is based on FIDIC contract conditions (1999 and 2017 editions), GCPCaR, and RICS EOT.
2. Contract clause review and claim management recommendations are for reference only, specific cases need comprehensive judgment based on contract clauses, evidence materials, judicial practice, etc.
3. It is recommended to consult contract management and claim management experts when using this SKILL.
4. This SKILL does not constitute legal advice, only for learning reference.

Version History

• v1.2.0 (2026-06-28): Integrated complete FIDIC Clause 8 details (1999 vs. 2017 comparison), added GCPCaR best practices, added executable functions
• v1.1.0 (2026-06-29): Optimized theoretical framework from RICS+EOT to FIDIC+GCPCaR
• v1.0.0 (2026-06-28): Initial version, based on RICS EOT and FIDIC Clause 8

References

1. FIDIC Conditions of Contract for Construction (1999 and 2017 Editions)
2. GCPCaR: Guide to Construction Claims and Resolutions
3. RICS Extension of Time (EOT) Core Guidance (2014)
4. Andy Hewitt: Claim Notices and Reports Theory
5. SCL Delay and Disruption Protocol, 2nd Edition (2017)

Brand Description and Contact Information

Brand Description

ZFCC (Zenfo Forensic Claims Consultant) is an independent professional brand founded by The Honorable Zenfo (Zenfu Daren), focusing on international engineering claims and dispute resolution.

Professionalism Guarantee:
- All content based on authoritative international standards (FIDIC, GCPCaR, RICS, etc.)
- Combined with actual engineering project experience
- Continuously updated to reflect latest practices

Contact Information

Author: The Honorable Zenfo (Zenfu Daren)
Email: xzf_83@qq.com
IMA Knowledge Base: ZFCC Engineering Claims (leave message in comments, recommended method)

Professional Consultation:
- FIDIC contract management
- Claim notice and report
- Contract dispute prevention

END of SKILL.md (English Version)

> Last Updated: 2026-07-02