Analysis Setup
Project Schedule Overview
Schedule Summary
Activities — Planned vs. Actual
| No. | Activity / Task | WBS / Zone | Critical | Baseline Start | Baseline Finish | Actual / Forecast Finish | Delay Status | % Complete | Status | Delay Cause | Remarks |
|---|
Delay Log & Impact Register
| No. | Delay / Event Description | Related Activity | Category | Days Impact | Critical Path | Responsibility | Status | Remarks |
|---|
About this schedule delay analysis tool
This tool builds a construction schedule delay analysis directly in the browser, for planning engineers, project managers and document controllers who need to compare the baseline programme against actual or forecast progress, flag critical-path delays, and keep a defensible record of delay causes and their impact.
Comparing planned vs. actual dates
Every activity records a baseline start and finish alongside an actual or forecast finish. The delay in days is calculated automatically, and activities still in progress are compared against the current data date so a running delay is visible before the activity is even complete.
Flagging critical activities
Marking an activity as critical separates delays that consume float from delays that flow straight through to the overall completion date. The schedule summary highlights critical delayed activities separately from ordinary delays, so attention goes where it matters most.
Logging delay causes and impact
The delay register captures each delay event with its category, the activity it relates to, the estimated days of impact, whether it affected the critical path, and who is responsible. Tracking extension of time already granted against the overall project delay shows the net, unrecovered position at a glance.
Getting data in and out
The analysis saves as a project file to reopen and update as the programme progresses, exports to CSV for further analysis or a claim file, prints directly as a PDF, and can generate a full detail report with every section written out in full for a client submission or extension of time claim. For day-to-day site recording, see the construction daily progress report.
Frequently asked questions
What is a schedule delay analysis?
A schedule delay analysis compares the planned or baseline programme against actual or forecast progress for every activity, identifies how many days each activity is ahead or behind plan, and highlights which delays sit on the critical path and are therefore likely to push back the overall completion date.
How is delay calculated for an activity?
Delay is the difference in days between an activity's baseline finish date and its actual or forecast finish date. A positive number means the activity finished or is forecast to finish later than planned; a negative number means it is ahead of schedule. For activities still in progress, the current data date is used against the baseline finish to show a running delay.
Why separate critical-path delays from other delays?
A delay on a non-critical activity may simply consume float without affecting the finish date, while a delay on a critical-path activity flows directly through to overall project completion. Flagging critical activities separately keeps attention on the delays that actually threaten the programme.
What causes are typically logged in a delay register?
Common categories include weather, design changes, material shortages, manpower shortages, equipment breakdown, client-caused delay, permits and approvals, and force majeure. Each entry records the responsible party, the estimated days of impact, and whether it affected the critical path.
Can this be used to support an extension of time (EOT) claim?
Yes. Logging baseline versus actual dates alongside a categorised delay register with responsibility and days of impact builds the contemporaneous record typically required to substantiate an EOT claim, and the tool tracks EOT already granted against the overall project delay to show the remaining, unrecovered position.
Related project management tools
Planning and reporting on the same project: