Every task is on time, but the project is late. What are we missing?
Missing schedule relationshipsIndividual task dates can look healthy while handoffs, integration, and dependencies push the finish date. Reconstruct the end-to-end delivery path rather than judging progress from isolated tasks.
What to do now
- Trace the final deliverable backward
- Add missing handoffs and approvals
- Check dependency logic and calendars
- Recalculate the completion forecast
When to escalate
The integrated forecast exceeds the agreed delivery tolerance.
The project manager and relevant commitment owner
Example
Development finishes on Friday, but integration cannot start until a shared environment is available the following week.
Mistake to avoid
Averaging task status colors to determine the project finish date.
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
- Should we add more people to finish a late task faster?Unproven schedule compression
- A task finished early, but nobody used the time gained. Why?Unmanaged schedule opportunity
- The procurement process will finish after the required start date. What can we do?Procurement lead-time mismatch
- How can we forecast staffing before every task is known?Early capacity uncertainty