Stop Schedule Delay Cascades

Each part answers a practical question. Is the plan realistic? Do crews, materials, and equipment support it? Do people have the drawings and decisions they need? Are workers producing at the planned rate? Are trades working in the right sequence? Does the team compare actual results with the approved plan and act quickly?

Start with these indicators:

1. Actual versus baseline Compare the work completed and the dates achieved with the approved baseline schedule. The baseline is the agreed plan used for measuring change. Don’t compare today’s work only with last week’s revised forecast; that can hide drift. If concrete for Level 3 was planned to finish on May 10 but finished on May 16, record the six-day difference against the baseline.

2. Critical path Identify the current chain of activities that leads to the planned finish. Check it whenever a major activity changes. The critical path can move during construction. A delayed activity may become critical, while a previously critical activity may gain float after recovery work.

3. Float Record the available time before each activity affects the finish date. If ceiling installation has five days of float and slips three days, the project may remain safe. If fire alarm testing has zero float and slips three days, the handover date may move three days unless the team recovers that time.

4. Productivity Compare planned output with actual output. Use a unit that fits the work: square meters of blockwork per crew-day, meters of cable installed per day, or rooms completed per week. If the plan expects 40 square meters of blockwork per day and the crew delivers 28, the team needs to address the cause - not simply report a lower percentage.

5. Manpower Check whether the planned crew is available and properly assigned. A schedule that requires 12 electricians but has only seven cannot recover through better reporting alone. Record planned versus actual manpower by trade and location. This shows whether the shortage affects critical activities.

6. Material and equipment Track the items that control upcoming work, not just items already delivered. A missing pump, lift, transformer, or approved material can stop a whole sequence. Link each item to the activity it supports and its required-on-site date.

7. Drawings and information Check whether crews have the latest Issued for Construction (IFC) drawings. An IFC drawing is the approved construction version used in the field. Outdated or missing information creates rework, waiting, and incorrect installation.

8. Decisions Track requests for information and approvals. A Request for Information (RFI) asks for clarification when the available documents do not answer a construction question. Record the submission date, responsible decision-maker, required decision date, and affected activity. An unanswered RFI can become a critical path delay even when labor and materials sit ready.

9. Cash flow Check whether payment timing supports planned work. A subcontractor may reduce manpower or pause procurement when cash flow fails. This indicator belongs in schedule control because financial pressure can quickly affect resources and production.

Use a simple weekly table to connect these indicators:

| Indicator | Planned condition | Actual condition | Schedule risk | |---|---|---|---| | Critical activity | Electrical testing starts June 3 | Starts June 10 | Seven-day finish risk | | Manpower | 12 electricians | 8 available | Lower output | | Material | Switchgear on site May 28 | Delivery expected June 6 | Testing cannot start | | Drawing | IFC revision issued May 20 | Field uses older revision | Rework risk | | RFI | Answer due May 25 | Still open June 1 | Installation decision blocked |

The point isn’t to create a mountain of paperwork. It’s to connect symptoms to schedule consequences. A manpower shortage matters most when it affects a critical activity. A late drawing matters most when it blocks work with no float. This connection turns a progress meeting into an early-warning check.

Applying the Checklist to a Live Schedule

Consider a fit-out project with a planned handover on June 30. The weekly report shows 80% overall progress on June 1. That figure looks reassuring until the team checks the activities that control handover.

1. Compare the baseline with actual dates. The baseline says mechanical completion should finish May 28. Actual completion stands at 92%, with duct testing still open. The report records the remaining work instead of treating 80% as proof of health. Expected outcome: the team sees unfinished work that affects later testing.

2. Trace the critical path. The sequence runs from duct testing to ceiling closure, final electrical checks, integrated testing, and handover. Duct testing has no float. The team marks it as the immediate schedule control point. Expected outcome: the meeting focuses on the chain that controls June 30, not on easy work already completed.

3. Check productivity against the remaining scope. The plan requires testing 10 zones in five working days, or two zones per day. The team completed three zones in three days - one zone per day. At that rate, seven remaining zones need seven more days, not four. Expected outcome: the forecast shows a three-day slip unless the team changes the production rate.

4. Check manpower and equipment. The plan calls for two testing crews and one access lift. One crew remains assigned to another area, and the lift has a maintenance hold until June 3. The team assigns the second crew to the critical zones and arranges a replacement lift. Expected outcome: the planned two-zone daily rate becomes possible again.

5. Check information and decisions. Two zones still lack an approved IFC detail for access panels. An RFI submitted May 27 remains unanswered. The project lead sets a decision deadline of June 2 and identifies the exact zones affected. Expected outcome: the decision has an owner and a date, rather than sitting as an invisible delay.

6. Recalculate float and finish impact. After the equipment and crew changes, testing returns to two zones per day. The open RFI remains the main risk. If the answer arrives June 2, the team protects the June 30 handover. If it arrives June 5, integrated testing loses three days and the finish date moves unless the team adds a recovery shift or resequences work.

7. Report the schedule impact, not just the delay duration. The weekly report states: “Duct testing is three days behind its activity plan, has zero float, and threatens integrated testing. Recovery requires the second crew, replacement lift, and RFI answer by June 2.” Expected outcome: managers can make decisions before the delay spreads.

Use this short review each week:

Quick checklist

• Compare actual dates and quantities with the approved baseline. - Identify the current critical path. - Record float for activities near the finish. - Measure output per crew-day or another clear unit. - Compare planned and actual manpower by trade. - Confirm materials and equipment against required-on-site dates. - Verify that crews use current IFC drawings. - List open RFIs and approvals with decision deadlines. - Check whether cash flow could reduce resources. - State the likely finish-date impact and the recovery action.

If the team completes this review consistently, the 80% figure becomes one piece of evidence rather than the verdict. That shift matters. A project can be busy, visibly productive, and still moving away from its finish date.

Mistakes That Hide Critical Path Drift

Mistaking overall progress for schedule health

A single percentage blends easy work with finish-controlling work. It can rise while a critical activity loses its float.

Do this: Break progress into work packages, then highlight activities on or near the critical path. Report both completion and finish-date effect.

Not this: “The project is 80% complete, so the schedule is healthy.”

A better statement says, “Overall progress is 80%, but the zero-float testing sequence is three days late and needs recovery.”

Treating every delay as equal

A delayed activity with 10 days of float may not affect handover. A two-day delay on a zero-float activity may affect handover immediately.

Do this: Record the activity’s float and trace its links to the final milestone.

Not this: Add every late activity together and call the total the project delay.

That approach exaggerates some problems and misses the one that controls the finish.

Updating the forecast until it matches reality

Teams sometimes replace the baseline with a later forecast after work slips. The report then appears close to plan because it compares actual results with a plan that already absorbed the delay.

Do this: Keep the approved baseline visible. Show the current forecast beside it, with the reason for every major change.

Not this: Compare actual progress only with last week’s revised dates.

The baseline shows the original commitment. The forecast shows the likely outcome. You need both to see drift and manage it.

Ignoring information, decisions, or cash flow

A crew can stand ready with tools and materials yet remain unable to work because a drawing or approval is missing. Likewise, a subcontractor may cut manpower when payment delays strain cash flow.

Do this: Link every open drawing, RFI, approval, and payment concern to the affected activity and required decision date.

Not this: List them in a separate log with no schedule connection.

Schedule health becomes useful when it reveals cause and consequence. The real question isn’t “How much work is complete?” It’s “Which unfinished condition can move the finish date, and what must change before it does?” That question turns progress reporting into schedule control - and gives the team a chance to stop a small drift before it becomes a cascade.

End of chapter one. 4 more chapters and about 8,657 words in the full book.