A critical-path task slipped. What should I do first?
Critical-path delayVerify the current schedule logic and the delay's effect on the completion forecast. Then compare recovery options by time saved, additional cost, and risk rather than demanding overtime automatically.
What to do now
- Confirm remaining work and dependencies
- Recalculate the controlling path
- Evaluate resequencing or scope options
- Seek approval for the selected recovery plan
When to escalate
The revised finish exceeds the sponsor's agreed tolerance.
The project manager and relevant commitment owner
Example
A delayed test environment blocks integration, so the team evaluates a temporary environment against waiting for the permanent one.
Mistake to avoid
Assuming every late task needs the same urgency.
Prevent a repeat
Compare forecast versus actual results for comparable tasks, separating effort, elapsed time, waiting and scope change.
Suggested ApprovedFlow setup
- Tasks
- Timesheets
- Resources
Keep planned dates and assumptions with the affected task, compare recorded actuals, and attach the revised forecast for review. See the platform
Related cases
- How can we recover a schedule without cutting quality?Unsafe recovery choices
- Every task is on time, but the project is late. What are we missing?Missing schedule relationships
- The Product Owner is unavailable for questions. What should we establish?Product decision delay
- Our test cases cover the happy path only. What is missing?Incomplete scenario coverage