ZFCC工期索赔.干扰分析(AACE+SCL)

ZFCC (Zenfo Forensic Claims Consultant) - The Honorable Zenfo（知府大人）的专业工程索赔咨询品牌

基于 AACE 67R-07（干扰分析）和 SCL Protocol（干扰准则），提供工期干扰分析的专业视角，覆盖生产率下降、损失生产力、干扰索赔等核心内容。

📋 目录 / Table of Contents

核心理论 / Core Theory

• 核心标准集成 / Core Standards Integration
• 干扰分析理论框架 / Disruption Analysis Theory Framework
• 核心能力 / Core Capabilities

实践应用 / Practical Application

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

附录 / Appendix

• 参考资料 / References
• 品牌说明与联系方式 / Brand Description and Contact Information

🎯 核心标准集成

本SKILL集成2大国际标准：

标准1: AACE 67R-07（干扰分析）

来源: 美国造价工程师协会（AACE International）
名称: Recommended Practice No. 67R-07 - Disruption Analysis
发布: 2007年（持续更新）
地位: 美国干扰分析标准
适用范围: 美国、国际项目（干扰分析）

核心内容：
- 干扰分析框架
- 生产率下降测量
- 损失生产力计算
- 干扰索赔证明

标准2: SCL Protocol（干扰准则）

来源: 英国工程法学会（SCL）
名称: SCL Protocol - Delay and Disruption Protocol
发布: 2002年（2017年更新）
地位: 英国干扰分析准则
适用范围: 英国、英联邦国家、国际项目（FIDIC合同）

核心内容：
- 干扰定义和分类
- 干扰证据要求
- 干扰评估方法
- 干扰索赔管理

📊 干扰分析理论框架

1. 干扰类型（AACE 67R-07）

2. 生产率下降测量（AACE 67R-07）

Measured Mile方法：

步骤1: 识别未受干扰时段（Measured Mile Period）
步骤2: 测量该时段的实际生产率
步骤3: 将此生产率应用于受干扰时段
步骤4: 计算生产率差异（损失）
步骤5: 计算费用影响

公式:
损失工时 = (预期工时 - 实际工时) × 受干扰时段工程量
损失费用 = 损失工时 × 工时费率

关键要求：
- Measured Mile时段必须可比（类似工作条件）
- 必须排除其他影响因素（天气、变更等）
- 必须有可靠的生产率数据

3. 损失生产力因素（SCL Protocol）

16个常见因素（Hudson Factors）：
1. 短工期（Short duration）
2. 现场拥挤（Congestion）
3. 缺乏材料（Material shortage）
4. 缺乏设备（Equipment shortage）
5. 设计变更（Design changes）
6. 现场指令（Site instructions）
7. 天气影响（Weather）
8. 劳动力技能不足（Lack of skill）
9. 管理不善（Poor management）
10. 图纸延误（Drawing delay）
11. 分包商干扰（Subcontractor interference）
12. 业主干扰（Employer interference）
13. 资金短缺（Cash flow problems）
14. 加班疲劳（Overtime fatigue）
15. 多语言障碍（Language barriers）
16. 安全问题（Safety issues）

4. 干扰索赔证明（SCL Protocol）

原告必须证明（11个要素）：
1. 干扰事件（由对方引起）
2. 通知（及时通知干扰事件）
3. 记录（同期记录证明干扰）
4. 生产率下降（测量生产率下降）
5. 因果关系（干扰事件 → 生产率下降）
6. 排除其他因素（天气、变更等）
7. 计算方法（合理的计算方法）
8. 支持证据（工时卡、进度报告等）
9. 专家证据（必要时）
10. ** mitigation（减轻损失措施）
11. 诚信**（诚实信用原则）

🛠️ 核心能力

能力1: 干扰事件识别

功能：识别可能导致干扰的事件

方法：
- 审查合同文件（变更条款、加速条款）
- 分析现场记录（日报、周报、会议纪要）
- 访谈项目人员（项目经理、工程师、工长）
- 对比进度计划（计划 vs. 实际）

输出：
- 干扰事件清单
- 干扰事件分类（对方责任 vs. 我方责任）
- 干扰事件时间线

能力2: 生产率下降测量

功能：测量和证明生产率下降

方法：
- Measured Mile方法（AACE推荐）
- Productivity Factor方法（SCL推荐）
- Man-Hour Analysis方法（传统方法）
- Earned Value方法（EVMS）

输出：
- 生产率基准（Baseline Productivity）
- 实际生产率（Actual Productivity）
- 生产率下降百分比（Productivity Loss %）
- 损失工时和费用（Lost Hours and Cost）

能力3: 干扰索赔准备

功能：准备干扰索赔文件

方法：
- 收集同期记录（工时卡、材料单、设备记录）
- 准备生产率分析（Measured Mile分析）
- 准备费用计算（损失工时 × 费率）
- 准备证据包（证据清单、证据说明）

输出：
- 干扰索赔通知（Notice of Disruption Claim）
- 干扰索赔报告（Disruption Claim Report）
- 证据包（Evidence Package）

能力4: 干扰辩护

功能：辩护对方的干扰索赔

方法：
- 质疑干扰事件（是否由我方引起）
- 质疑生产率测量（Measured Mile是否可比）
- 质疑因果关系（是否有其他因素）
- 质疑减轻措施（是否采取合理措施）

输出：
- 辩护意见（Defense Opinion）
- 反驳证据（Contrary Evidence）
- 谈判策略（Negotiation Strategy）

⚙️ 可执行功能

本SKILL提供以下可执行功能（通过脚本）：

功能1: 干扰事件识别器

脚本: disruption_identifier.py
功能:
- 输入: 项目信息、合同文件、现场记录
- 输出: 干扰事件清单、分类、时间线

功能2: 生产率下降测量器

脚本: productivity_measurer.py
功能:
- 输入: 工时数据、工程量数据、Measured Mile时段
- 输出: 生产率分析、损失计算、报告

功能3: 干扰索赔准备器

脚本: disruption_claim_preparer.py
功能:
- 输入: 干扰事件、生产率分析、费用计算
- 输出: 索赔通知、索赔报告、证据包

功能4: Measured Mile分析器

脚本: measured_mile_analyzer.py
功能:
- 输入: 进度数据、工时数据、干扰时段
- 输出: Measured Mile识别、生产率对比、损失计算

功能5: 损失生产力计算器

脚本: productivity_loss_calculator.py
功能:
- 输入: 基线生产率、实际生产率、工程量
- 输出: 损失工时、损失费用、报告

📚 实践指导

投标阶段

目标: 预防干扰风险

行动清单:
- [ ] 审核合同条件（变更条款、加速条款、干扰条款）
- [ ] 评估项目风险（拥挤、多分包商、短工期）
- [ ] 制定生产率基准（Baseline Productivity）
- [ ] 准备干扰记录程序（记录要求、责任分配）

关键提示:
- 在特殊条件中明确"干扰"定义和证明标准
- 要求"同期记录"（Contemporaneous Records）条款
- 避免"不计成本补偿"条款（No-Cost-Plus-Fee）

施工阶段

目标: 管理干扰事件，收集证据

行动清单:
- [ ] 建立生产率记录系统（每日工时、每日工程量）
- [ ] 及时通知干扰事件（合同要求的时限内）
- [ ] 收集同期记录（工时卡、材料单、设备记录、照片）
- [ ] 识别Measured Mile时段（未受干扰时段）
- [ ] 准备月度干扰报告（记录干扰影响）

关键提示:
- 同期记录是干扰索赔的生命线
- Measured Mile时段必须可比（类似工作条件）
- 及时通知是干扰索赔的前提条件

索赔阶段

目标: 准备和提交干扰索赔

行动清单:
- [ ] 准备干扰索赔通知（Notice of Disruption Claim）
- [ ] 准备干扰索赔报告（Disruption Claim Report）
- 干扰事件描述
- 生产率下降测量
- 费用计算
- 证据清单
- [ ] 准备证据包（Evidence Package）
- [ ] 提交索赔（合同要求的格式和时限）

关键提示:
- 干扰索赔必须证明因果关系（干扰事件 → 生产率下降）
- 必须排除其他影响因素（天气、变更、我方过错）
- 必须有可靠的生产率数据和计算方法

争议解决阶段

目标: 仲裁或诉讼中的干扰索赔

行动清单:
- [ ] 准备专家证人（生产率专家、延误专家）
- [ ] 准备交叉询问（质疑对方生产率测量）
- [ ] 准备可视化辅助（时间线、生产率对比图）
- [ ] 准备结案陈词（Closing Submission）

关键提示:
- 干扰索赔是事实密集型（需要大量证据）
- 专家证人的独立性和方法论是关键
- 可视化辅助（图表、时间线）帮助仲裁庭理解

❓ 常见问题

Q1: 干扰和延误有什么区别？

A:
- 延误（Delay）: 完工时间延长（Time extension）
- 干扰（Disruption）: 生产率下降（Productivity loss）

关系:
- 干扰不一定导致延误（可能通过加速弥补）
- 延误不一定由干扰引起（可能由变更、天气等引起）
- 但干扰和延误经常同时发生（并发影响）

索赔策略:
- 延误索赔 → 工期延长（EOT）
- 干扰索赔 → 费用补偿（Cost reimbursement）

Q2: Measured Mile方法最可靠吗？

A: 是的，Measured Mile方法是最可靠的方法，但要求严格：

优点:
- 基于实际数据（不是理论估算）
- 仲裁庭最易接受
- 符合因果关系证明要求

要求:
- 必须识别未受干扰时段（Measured Mile Period）
- 该时段必须可比（类似工作条件、类似工程量）
- 必须排除其他影响因素（天气、变更等）
- 必须有可靠的工时和工程量数据

如果无法识别Measured Mile时段:
- 使用Productivity Factor方法（基于行业标准）
- 使用Man-Hour Analysis方法（基于工时分析）
- 但可靠性较低，仲裁庭可能不接受

Q3: 如何证明因果关系？

A: 因果关系证明是干扰索赔的最大挑战：

必须证明:
1. 干扰事件由对方引起（对方责任）
2. 干扰事件导致生产率下降（时间上紧随）
3. 排除其他影响因素（天气、变更、我方过错）

证据:
- 同期记录（工时卡、日报、周报、会议纪要）
- 时间序列分析（干扰事件发生 → 生产率下降）
- 专家证据（生产率专家分析）
- 行业数据（类似项目的生产率数据）

关键:
- 同期记录是最重要的证据
- 时间序列证明因果关系
- 排除其他因素增强因果关系

Q4: 干扰索赔能赔多少？

A: 干扰索赔的赔偿金额取决于：

可赔费用:
- 额外工时（加班、增加人员）
- 效率低下的工时（损失工时）
- 设备闲置（效率低导致设备闲置）
- 管理费（延长管理费）
- 利润（如果合同允许）

不可赔费用:
- 我方过错导致的损失
- 未通知的干扰事件
- 未减轻的损失
- 惩罚性赔偿（除非合同约定）

典型案例:
- 损失工时: 10,000小时
- 工时费率: $50/小时
- 赔偿金额: $500,000

Q5: 对方质疑Measured Mile怎么办？

A: 对方常质疑Measured Mile的可比性：

常见质疑:
- "Measured Mile时段的工作条件不同"
- "Measured Mile时段的工程量不同"
- "有其他影响因素（天气、变更）"

应对策略:
1. 证明可比性:
- 工作条件类似（工人技能、设备、材料）
- 工程量类似（单位工程量）
- 管理方法类似（同一团队）

2. 排除其他因素:
   - 天气记录（证明无恶劣天气）
   - 变更记录（证明无重大变更）
   - 我方记录（证明我方无过错）

3. 使用多个Measured Mile时段:
   - 如果只有一个时段被质疑，使用多个时段
   - 取平均值，提高可靠性

关键:
- 详细记录Measured Mile时段的工作条件
- 专家证据支持可比性
- 多个时段提高可靠性

📖 参考资料

必读文献

1. AACE 67R-07 - Disruption Analysis
2. SCL Protocol (2017) - Delay and Disruption Protocol
3. Hudson's Building and Engineering Contracts - Chapter on Disruption
4. Keating on Construction Contracts - Chapter on Disruption

相关标准

• AACE 29R-03 - Forensic Schedule Analysis（延误分析）
• RICS EOT - Extension of Time（工期延期）
• FIDIC Clause 8 - Commencement, Delays and Suspension

在线资源

• AACE International - AACE国际标准
• SCL - 英国工程法学会
• RICS - 英国皇家特许测量师学会

ℹ️ 品牌说明与联系方式

品牌说明

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

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

联系方式

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

专业咨询：
- 干扰与生产率损失分析
- Measured Mile方法应用
- 干扰费用计算

版本: v1.1.0
最后更新: 2026-07-02
作者: The Honorable Zenfo（知府大人）
品牌: ZFCC (Zenfo Forensic Claims Consultant)

免责声明: 本SKILL提供专业指导，但不构成法律意见。具体案件请咨询当地律师。

END of SKILL.md (Chinese Version)

版本历史

• v1.2.0 (2026-07-02)：优化description、添加目录、提供完整中英对照
• v1.1.0 (2026-06-28)：初始版本，基于AACE 67R-07和SCL Protocol编制

Complete English Version

Overview

This SKILL provides professional guidance on construction delay disruption analysis, based on AACE 67R-07 and SCL Protocol, covering productivity loss, disrupted productivity, and disruption claims.

Role Definition

You are an expert in disruption analysis for construction projects, specialized in productivity loss measurement, disrupted productivity calculation, and disruption claim preparation based on AACE 67R-07 and SCL Protocol. You help users conduct scientific, evidence-based disruption analysis in international engineering projects.

Core Standards Integration

This SKILL integrates 2 major international standards:

Standard 1: AACE 67R-07 (Disruption Analysis)

Source: AACE International
Name: Recommended Practice No. 67R-07 - Disruption Analysis
Published: 2007 (continuously updated)
Status: US disruption analysis standard
Applicable Scope: US, international projects (disruption analysis)

Core Content:
- Disruption analysis framework
- Productivity loss measurement
- Disrupted productivity calculation
- Disruption claim proof

Standard 2: SCL Protocol (Disruption Protocol)

Source: Society of Construction Law (SCL), UK
Name: SCL Protocol - Delay and Disruption Protocol
Published: 2002 (updated 2017)
Status: UK disruption analysis protocol
Applicable Scope: UK, Commonwealth countries, international projects (FIDIC contracts)

Core Content:
- Disruption definition and classification
- Disruption evidence requirements
- Disruption assessment methods
- Disruption claim management

Disruption Analysis Theory Framework

1. Disruption Types (AACE 67R-07)

2. Productivity Loss Measurement (AACE 67R-07)

Measured Mile Method:

Step 1: Identify undisrupted period (Measured Mile Period)
Step 2: Measure actual productivity during this period
Step 3: Apply this productivity to disrupted period
Step 4: Calculate productivity difference (loss)
Step 5: Calculate cost impact

Formula:
Lost Hours = (Expected Man-Hours - Actual Man-Hours) × Disrupted Period Work Quantity
Lost Cost = Lost Hours × Man-Hour Rate

Key Requirements:
- Measured Mile period must be comparable (similar working conditions)
- Must exclude other influencing factors (weather, variation, etc.)
- Must have reliable productivity data

3. Loss of Productivity Factors (SCL Protocol)

16 Common Factors (Hudson Factors):
1. Short duration
2. Site congestion
3. Material shortage
4. Equipment shortage
5. Design changes
6. Site instructions
7. Weather
8. Lack of skill
9. Poor management
10. Drawing delay
11. Subcontractor interference
12. Employer interference
13. Cash flow problems
14. Overtime fatigue
15. Language barriers
16. Safety issues

4. Disruption Claim Proof (SCL Protocol)

Claimant Must Prove (11 elements):
1. Disruption event (caused by opponent)
2. Notice (timely notice of disruption event)
3. Records (contemporaneous records proving disruption)
4. Productivity loss (measure productivity loss)
5. Causation (disruption event → productivity loss)
6. Exclude other factors (weather, variation, etc.)
7. Calculation method (reasonable calculation method)
8. Supporting evidence (timesheet, progress report, etc.)
9. Expert evidence (if necessary)
10. Mitigation (measures to reduce loss)
11. Good faith (principle of good faith)

Core Capabilities

Capability 1: Disruption Event Identification

Function: Identify events that may cause disruption

Method:
- Review contract documents (variation clause, acceleration clause)
- Analyze site records (daily report, weekly report, meeting minutes)
- Interview project personnel (project manager, engineer, foreman)
- Compare schedule (planned vs. actual)

Output:
- Disruption event list
- Disruption event classification (opponent responsibility vs. own responsibility)
- Disruption event timeline

Capability 2: Productivity Loss Measurement

Function: Measure and prove productivity loss

Method:
- Measured Mile Method (AACE recommended)
- Productivity Factor Method (SCL recommended)
- Man-Hour Analysis Method (traditional method)
- Earned Value Method (EVMS)

Output:
- Productivity baseline (Baseline Productivity)
- Actual productivity (Actual Productivity)
- Productivity loss percentage (Productivity Loss %)
- Lost hours and cost (Lost Hours and Cost)

Capability 3: Disruption Claim Preparation

Function: Prepare disruption claim documents

Method:
- Collect contemporaneous records (timesheet, material delivery note, equipment log)
- Prepare productivity analysis (Measured Mile analysis)
- Prepare cost calculation (lost hours × rate)
- Prepare evidence package (evidence list, evidence narrative)

Output:
- Disruption claim notice (Notice of Disruption Claim)
- Disruption claim report (Disruption Claim Report)
- Evidence package (Evidence Package)

Capability 4: Disruption Defense

Function: Defend against opponent's disruption claim

Method:
- Challenge disruption event (whether caused by us)
- Challenge productivity measurement (whether Measured Mile is comparable)
- Challenge causation (whether there are other factors)
- Challenge mitigation measures (whether took reasonable measures)

Output:
- Defense opinion (Defense Opinion)
- Contrary evidence (Contrary Evidence)
- Negotiation strategy (Negotiation Strategy)

Executable Functions

This SKILL provides following executable functions (via scripts):

Function 1: Disruption Event Identifier

Script: disruption_identifier.py
Function:
- Input: project info, contract documents, site records
- Output: disruption event list, classification, timeline

Function 2: Productivity Measurer

Script: productivity_measurer.py
Function:
- Input: man-hour data, work quantity data, Measured Mile period
- Output: productivity analysis, loss calculation, report

Function 3: Disruption Claim Preparer

Script: disruption_claim_preparer.py
Function:
- Input: disruption event, productivity analysis, cost calculation
- Output: claim notice, claim report, evidence package

Function 4: Measured Mile Analyzer

Script: measured_mile_analyzer.py
Function:
- Input: schedule data, man-hour data, disruption period
- Output: Measured Mile identification, productivity comparison, loss calculation

Function 5: Productivity Loss Calculator

Script: productivity_loss_calculator.py
Function:
- Input: baseline productivity, actual productivity, work quantity
- Output: lost hours, lost cost, report

Practice Guidance

Bidding Stage

Goal: Prevent disruption risks

Action List:
- [ ] Review contract conditions (variation clause, acceleration clause, disruption clause)
- [ ] Assess project risks (congestion, multiple subcontractors, short duration)
- [ ] Establish productivity baseline (Baseline Productivity)
- [ ] Prepare disruption recording procedure (recording requirement, responsibility allocation)

Key Tips:
- Clearly define "disruption" definition and proof standard in special conditions
- Require "contemporaneous records" clause
- Avoid "no-cost-plus-fee" clause

Construction Stage

Goal: Manage disruption events, collect evidence

Action List:
- [ ] Establish productivity recording system (daily man-hours, daily work quantity)
- [ ] Timely notify disruption events (within contract required time limit)
- [ ] Collect contemporaneous records (timesheet, material delivery note, equipment log, photos)
- [ ] Identify Measured Mile period (undisrupted period)
- [ ] Prepare monthly disruption report (record disruption impact)

Key Tips:
- Contemporaneous records are lifeline of disruption claim
- Measured Mile period must be comparable (similar working conditions)
- Timely notice is prerequisite of disruption claim

Claim Stage

Goal: Prepare and submit disruption claim

Action List:
- [ ] Prepare disruption claim notice (Notice of Disruption Claim)
- [ ] Prepare disruption claim report (Disruption Claim Report)
- Disruption event description
- Productivity loss measurement
- Cost calculation
- Evidence list
- [ ] Prepare evidence package (Evidence Package)
- [ ] Submit claim (contract required format and time limit)

Key Tips:
- Disruption claim must prove causation (disruption event → productivity loss)
- Must exclude other influencing factors (weather, variation, own fault)
- Must have reliable productivity data and calculation method

Dispute Resolution Stage

Goal: Disruption claim in arbitration or litigation

Action List:
- [ ] Prepare expert witness (productivity expert, delay expert)
- [ ] Prepare cross-examination (challenge opponent's productivity measurement)
- [ ] Prepare visual aids (timeline, productivity comparison chart)
- [ ] Prepare closing submission

Key Tips:
- Disruption claim is fact-intensive (requires large amount of evidence)
- Expert witness's independence and methodology are key
- Visual aids (charts, timeline) help arbitral tribunal understand

FAQ

Q1: What is the difference between disruption and delay?

A:
- Delay: Completion time extension (Time extension)
- Disruption: Productivity loss (Productivity loss)

Relationship:
- Disruption does not necessarily cause delay (may be compensated by acceleration)
- Delay is not necessarily caused by disruption (may be caused by variation, weather, etc.)
- But disruption and delay often occur simultaneously (concurrent impact)

Claim Strategy:
- Delay claim → Time extension (EOT)
- Disruption claim → Cost reimbursement (Cost reimbursement)

Q2: Is Measured Mile method most reliable?

A: Yes, Measured Mile method is most reliable method, but requirements are strict:

Advantages:
- Based on actual data (not theoretical estimate)
- Arbitral tribunal most easily accepts
- Complies with causation proof requirement

Requirements:
- Must identify undisrupted period (Measured Mile Period)
- This period must be comparable (similar working conditions, similar work quantity)
- Must exclude other influencing factors (weather, variation, etc.)
- Must have reliable man-hour and work quantity data

If cannot identify Measured Mile period:
- Use Productivity Factor Method (based on industry standard)
- Use Man-Hour Analysis Method (based on man-hour analysis)
- But reliability is lower, arbitral tribunal may not accept

Q3: How to prove causation?

A: Causation proof is biggest challenge of disruption claim:

Must Prove:
1. Disruption event caused by opponent (opponent responsibility)
2. Disruption event led to productivity loss (timely following)
3. Exclude other influencing factors (weather, variation, own fault)

Evidence:
- Contemporaneous records (timesheet, daily report, weekly report, meeting minutes)
- Time series analysis (disruption event occurrence → productivity loss)
- Expert evidence (productivity expert analysis)
- Industry data (productivity data of similar projects)

Key:
- Contemporaneous records are most important evidence
- Time series proves causation
- Excluding other factors strengthens causation

Q4: How much can disruption claim recover?

A: Disruption claim compensation amount depends on:

Claimable Costs:
- Additional man-hours (overtime, increased staff)
- Inefficient man-hours (lost hours)
- Equipment idle (inefficiency causes equipment idle)
- Overhead (extended overhead)
- Profit (if contract allows)

Non-claimable Costs:
- Loss caused by own fault
- Unnoticed disruption event
- Loss not mitigated
- Punitive damages (unless contract agreed)

Typical Case:
- Lost hours: 10,000 hours
- Man-hour rate: $50/hour
- Compensation amount: $500,000

Q5: What if opponent challenges Measured Mile?

A: Opponent often challenges Measured Mile's comparability:

Common Challenges:
- "Working conditions in Measured Mile period are different"
- "Work quantity in Measured Mile period is different"
- "There are other influencing factors (weather, variation)"

Response Strategy:
1. Prove comparability:
- Similar working conditions (worker skill, equipment, materials)
- Similar work quantity (unit work quantity)
- Similar management method (same team)

2. Exclude other factors:
   - Weather records (prove no bad weather)
   - Variation records (prove no major variation)
   - Own records (prove no own fault)

3. Use multiple Measured Mile periods:
   - If one period is challenged, use multiple periods
   - Take average, improve reliability

Key:
- Detailed records of working conditions in Measured Mile period
- Expert evidence supports comparability
- Multiple periods improve reliability

References

Must-Read Literature

1. AACE 67R-07 - Disruption Analysis
2. SCL Protocol (2017) - Delay and Disruption Protocol
3. Hudson's Building and Engineering Contracts - Chapter on Disruption
4. Keating on Construction Contracts - Chapter on Disruption

Related Standards

• AACE 29R-03 - Forensic Schedule Analysis (delay analysis)
• RICS EOT - Extension of Time (schedule extension)
• FIDIC Clause 8 - Commencement, Delays and Suspension

Online Resources

• AACE International - AACE international standards
• SCL - Society of Construction Law
• RICS - Royal Institution of Chartered Surveyors

ℹ️ Brand Description and Contact Information

Brand Description

ZFCC (Zenfo Forensic Claims Consultant) is an independent professional brand founded by The Honorable Zenfo (知府大人), specialized in international engineering claims and dispute resolution.

Professionalism Guarantee:
- All content based on authoritative international standards (AACE 67R-07, SCL Protocol, etc.)
- Combined with actual engineering project experience
- Continuously updated to reflect latest practice

Contact Information

Author: The Honorable Zenfo (知府大人)
Email: xzf_83@qq.com
IMA Knowledge Base: ZFCC Engineering Claims (comment area message, recommended method)

Professional Consultation:
- Disruption and productivity loss analysis
- Measured Mile method application
- Disruption cost calculation

Version: v1.1.0
Last Updated: 2026-07-02
Author: The Honorable Zenfo (知府大人)
Brand: ZFCC (Zenfo Forensic Claims Consultant)

Disclaimer: This SKILL provides professional guidance, but does not constitute legal opinion. For specific cases, please consult local lawyer.

END of SKILL.md (English Version)