Importance of Schedule Update Review

I have been involved in planning and scheduling for many years and have found that a proper review is one of the elements of an update that is neglected, forgotten or just simply ignored.

During this paper I will attempt to explain why I believe it is the most important part of a schedule update and:

  • highlight what are key elements that need to be reviewed,

  • whom is responsible for performing the schedule update review and

  • possible actions that need to be taken.

In this paper I use the term programme and schedule interchangeably given the definition from different contract suites.

I have seen all too often programmes submitted without a proper review being performed. So, the question may be, why does one need to do a schedule update review when the project team members supposedly have given accurate input to the update and can substantiate the progress? The answer is very simple, the updated programme is your record of what has happened in the past period, what works are to be performed in the upcoming period, and most importantly, what is driving the project to completion and who is responsible for the delays, should there be any. So, if you simply submit the programme without reviewing the critical path/s, either to sectional completion dates or project completion dates, it suggests that you are satisfied:

  1. That the future activities and logical relationships that form those critical path/s are realistic and credible, and

  2. With underlying causes that may be driving those path/s, may it be induced by the owner or yourself.

If no update review is performed, you could be submitting a programme that indicates that you are the reason for delay when in fact it could be due to something as simple as incorrect logic between activities that have created this incorrect picture, or you simply forgot to include an owner delay event that impacts the programme. Also, it is just as important for the owner to perform a similar review to satisfy himself that the programme is true and reflective of the current status, the future intent and who is responsible for driving the project’s completion dates. It is in both party’s best interest to resolve and agree to all dates and statuses so as to reduce ambiguity and potential future conflicts.

Once the programme has been updated with the current period progress it is deemed to be the contractor’s contemporaneous record. This is a record that will most definitely be used in a dispute situation to prove (demonstrate) or challenge (repudiate) entitlement to EOT, and prolongation if applicable.

So, what is it that needs to be reviewed to ensure that the programme to be submitted is acceptable to both the owner and the contractor?

Critical Path or Longest Path to Completion

I personally think that reviewing the credibility of the critical path/s, or longest path to completion, is of utmost importance and possibly the most important check to perform. Reason being that, once the programme is submitted to the owner it gets filed by both parties as your contemporaneous record, and as I mentioned earlier this is a record that will most certainly be used in the event of disputes relating to an extension of time claim.

So, if the programme indicates that in a specific period you are the cause for the delay to the project completion, or sectional completion, then it will be recorded as such, and similarly if the delay is due to the owner it will be recorded as such. If you are responsible for the delay, then you are obligated to mitigate the delay and recover where possible. If you don’t analyse these paths you could submit a programme that indicates that you are the cause of delay when in fact it may not be.

Additionally, it may be that the situation on the ground has changed thereby no longer making the logical path/s to completion realistic or credible, therefore requiring a schedule change that may result in completely different critical or longest path/s and completion dates.


All changes, may it be due to instructions by the owner or your own, need to be in the programme. I have seen all too often project managers not wanting to put own delay events into the programme because the client must not see that they are underperforming or had to perform rework due to their own fault. Changes made to activities, logic changes, calendar changes, resource changes all need to be documented, and reasons provided.

Remaining Units

If schedules have been resource loaded, and I am an advocate for this practise, it is of utmost importance to ensure that the remaining labour or non-labour units are correctly updated in the programme. Similar to the best practise of updating activity remaining durations rather than purely activity percent completes, remaining units must be representative of those quantities or effort that are required to complete the outstanding portion of activities. If this is not done it may result in activity duration overruns following on from understating the remaining resource quantities or effort.

Programme Quality

After all the activities have been updated and the programme has been statused, there are several common checks that need to be performed to ensure that the programme conforms to that which is required for a quality programme. Some of these checks can be done by using the software to perform these checks, if the software has the functionality, else it will have to be performed manually or outside of the software. The DCMA 14-Point check is a good check to subject your programmes to, and if followed, can ensure that your programme meets the minimum requirements of a quality programme.

What must be checked as a minimum are the following:

  • Open ended activities, i.e. activities without driving predecessors or successors

  • Remaining work in the past, i.e. earlier than the status date

  • Actual dates in the future, i.e. later than the status date

  • Activities with external early and late dates, i.e. activities that have relationships with activities in other projects

  • Activities with constraints


"AACE’s 53R-06 Schedule Update Review – As Applied in Engineering, Procurement, and Construction" (click here for a sample of the document), provides for good structured means to perform schedule update reviews and I recommend that all who are involved with programme updates, and that includes the project manager to get a copy of this document.

Is your schedule credible? In claim and EOT situations, your project schedule is the first legal document to be assessed. You would not want it to be found lacking or deemed "not credible"!

If you're not sure whether it is, and not sure what to look for, let Profactaplan do a "Schedule Quality Audit" for you. Read more about it here.

#ProjectPlanning #ConstructionProject #ProjectSchedule #ProjectProgramme #ScheduleUpdate


© Professional and Proactive Planning Services


Tel: 082 777 1376


PO Box 123, Darling, 7345, South Africa