Schedule Recovery: Delay Analysis and Corrective Strategies

How project managers identify, classify, and analyze schedule delays in architectural projects, and the corrective strategies available to recover lost time while managing scope, cost, and quality trade-offs.

ARE · Project Management

Overview

Every architectural project will experience schedule pressure at some point. Weather shuts down a site. A client takes three weeks to approve a color palette. The structural engineer discovers the soils report missed a layer of clay. The question isn't whether delays will happen. It's whether you can analyze them accurately and select the right recovery strategy.

Schedule recovery is the process of identifying what went wrong, measuring how much time was lost, classifying the delay by type and responsibility, and then choosing a corrective approach that gets the project back on track without blowing the budget or compromising the design. On the ARE, you need to distinguish between different delay types, understand when each recovery strategy is appropriate, and recognize the trade-offs involved.

This matters because delay claims are one of the most contentious issues in construction. Getting the analysis wrong costs money, damages relationships, and can lead to disputes that end up in arbitration. Getting it right means the project manager can protect the firm's interests, maintain the client relationship, and keep the project moving forward. The architect's role in schedule management extends far beyond drawing deadlines. It includes monitoring the total project timeline, documenting delays as they occur, and recommending recovery strategies that account for design quality, not just speed.

Essential

Schedule delays in architectural projects fall into distinct categories, and each category demands a different response. Getting this classification right is the foundation of effective schedule recovery. Classifying Delays by Responsibility Excusable delays are caused by events outside the contractor's or architect's control. Severe weather, labor strikes, unexpected site conditions, government-imposed shutdowns, and force majeure events all fall here. When an excusable delay hits, the project schedule extends, and the contractor is typically entitled to a time extension but not necessarily additional compensation. Non-excusable delays are caused by the party responsible for the work. If the contractor's crew doesn't show up, that's non-excusable. If the architect misses a deliverable deadline due to internal staffing problems, that's also non-excusable. The responsible party absorbs the schedule impact and any resulting costs. Compensable delays are excusable delays caused by the owner.

Professional

Consider a 15-story mixed-use tower project in a mid-Atlantic city. The architect's office is responsible for coordinating the design schedule across eight consultant disciplines, and the project is 14 months into a 30-month design-through-CA timeline. The project manager discovers during a monthly schedule review that the project has slipped 6 weeks behind the baseline on the critical path. The delay analysis reveals two overlapping causes. First, the owner took 5 weeks to approve the SD package instead of the contractual 3 weeks (a compensable delay of 2 weeks). Second, the mechanical engineer's DD submission was 4 weeks late due to an internal staffing transition (a non-excusable delay attributable to the consultant). The concurrent portion, where both delays were running simultaneously, lasted 2 weeks. Sorting out the concurrent period requires forensic schedule analysis.

TLDR

Delays are classified as excusable (outside anyone's control), non-excusable (caused by the responsible party), or compensable (excusable but caused by the owner, entitling time and money).
Concurrent delays overlap from multiple parties. Untangling them requires forensic analysis against the critical path.
Workarounds rearrange work sequences to recover from unexpected problems. They're the first and cheapest recovery option.
Fast-tracking overlaps sequential activities. It saves time but risks rework if later decisions change earlier work.
Crashing adds resources to shorten critical path activities. It costs money and has diminishing returns.
Crash only critical path activities, starting with the lowest cost per day of compression.
Total float = how much an activity can slip without delaying project completion. Zero float = critical path.
SPI = Earned Value / Planned Value. Below 1.0 means behind schedule.
Force majeure gets you time extensions, usually not cost recovery.
Never modify the baseline without formal documentation. Informal adjustments destroy your ability to track true performance and support delay claims.

ELI5

Think of your project schedule like a road trip GPS. You planned to drive from New York to Miami in 20 hours. You've mapped out stops, rest breaks, and a clear route. Then things happen. A bridge closes (that's like a force majeure delay). You took a wrong turn (that's a non-excusable delay; your mistake). Your friend who was supposed to meet you at a rest stop showed up 2 hours late (that's a compensable delay; their fault, and they owe you for the wasted time). Now you're behind schedule. You have three ways to catch up. First, find a detour. Instead of waiting for the bridge to reopen, take a different road. In project management, this is called a workaround. You rearrange the order of your stops to avoid the blocked route. It doesn't cost you anything extra. Second, drive and eat at the same time.

AREProject Management

Schedule Recovery: Delay Analysis and Corrective Strategies

2 min read213 words

When Projects Fall Behind: Understanding Schedule Recovery

Want to track your progress and access more study tools?

Create a free account