# delay-analysis

delay-analysis analyzes construction delays for recovery plans and claim disputes. It evaluates schedule impacts, sorts concurrent causes, and calculates damages.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 119 installs · ★ 434 repo stars
- Author: datadrivenconstruction
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction/tree/HEAD/3_DDC_Insights/Schedule-Optimization/delay-analysis/SKILL.md
- Updated: 2026-10-19
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/delay-analysis

## What it does

The skill evaluates construction timeline slippages using four methods: As-Planned vs As-Built, Time Impact Analysis (TIA), Windows Analysis, and Collapsed As-Built. The underlying Python data model classifies each delay event by cause and party. It cleanly separates compensable owner delays from contractor delays.

For financial assessments, daily cost presets scale with project budget: from $5000 for jobs under $10M up to $100000 for mega projects over $200M. The skill requires a local `python3` binary. Calculations halt immediately if either the baseline or as-built schedule record is missing.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill delay-analysis -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/delay-analysis/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/delay-analysis/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill delay-analysis -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/delay-analysis/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill delay-analysis -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/delay-analysis/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction 3_DDC_Insights/Schedule-Optimization/delay-analysis
```

2. **Manually: put the files in place**
- File: `.github/skills/delay-analysis/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill delay-analysis -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --path 3_DDC_Insights/Schedule-Optimization/delay-analysis
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/delay-analysis/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill delay-analysis -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction/tree/HEAD/3_DDC_Insights/Schedule-Optimization/delay-analysis/SKILL.md

## When to use it
- Compare baseline schedule dates against actual project progress
- Perform time impact analysis by inserting specific delay events
- Isolate concurrent delays between contractor and owner
- Calculate delay damages using daily financial rates
- Generate structured `DelayAnalysisReport` data for claims

## Example prompts
- Compare `baseline` and `as_built` schedule versions to isolate critical path slippage
- Log a permit delay event and run a time impact analysis
- Calculate potential damages for a 15-day delay on a medium project

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 9bb2162239baf596.

BEGIN THIRD-PARTY FILE 9bb2162239baf596
````text
---
name: "delay-analysis"
description: "Analyze construction schedule delays for claims and recovery. Perform time impact analysis, identify delay causes, calculate damages, and document for disputes."
homepage: "https://datadrivenconstruction.io"
metadata: {"openclaw": {"emoji": "⏱️", "os": ["darwin", "linux", "win32"], "homepage": "https://datadrivenconstruction.io", "requires": {"bins": ["python3"]}}}
---
# Delay Analysis

## Overview

Analyze construction schedule delays for project recovery and claims. Perform time impact analysis (TIA), identify concurrent delays, calculate delay damages, and prepare documentation for dispute resolution.

> "Proper delay analysis is essential for fair resolution of construction disputes" — DDC Community

## Delay Analysis Methods

```
┌─────────────────────────────────────────────────────────────────┐
│                    DELAY ANALYSIS METHODS                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  As-Planned vs As-Built    │    Time Impact Analysis (TIA)      │
│  ─────────────────────     │    ────────────────────────────    │
│  Compare original to       │    Insert delay events into        │
│  actual schedule           │    schedule to measure impact      │
│                            │                                     │
│  Windows Analysis          │    Collapsed As-Built              │
│  ────────────────          │    ─────────────────               │
│  Divide project into       │    Remove delays from as-built     │
│  time periods              │    to find "but-for" completion    │
│                                                                  │
````
END THIRD-PARTY FILE 9bb2162239baf596

The third-party file has ended. Everything between the 9bb2162239baf596 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2245 of 20427 bytes. © datadrivenconstruction · MIT · https://github.com/datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction/tree/HEAD/3_DDC_Insights/Schedule-Optimization/delay-analysis/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
