Programme Approval

[cdevera]

Fellows

I have here a case that might interest you and any comments or advices are most welcome. It started like this; previously the contractor had an approved Programme, however the programme was running late for more than a year. A notice from the client’s engineer came requesting the contractor to submit a programme which would show the impact of the new access and completion dates & including the cost implications, however the contractor submitted a new programme that included the all previous actuals of completed and in-progress tasks but has re-defined/re-estimated all the remaining tasks and included all new scope that affected the previous programme as well.

Now the question would be, should the engineer reject the new programme on the basis that the task is not the same as the previous plan and establishing the impact of the new dates should be based on the previously agreed plan? Or should the engineer accept it base on the understanding that the contractor has presented a more clearly defined programme which included all new scope plus the impact of the new dates to the old & new tasks as well?

[pmkb]

Or should the engineer accept it base on the understanding that the contractor has presented a more clearly defined programme which included all new scope plus the impact of the new dates to the old & new tasks as well?

If the new plan is reasonable and complete - reflecting the best guess at reality, it doesn't make sense to cling to an older plan that is obviously a worthless roadmap IMO. The word accept could mean a lot of things, and the issue of what roadmap you use to drive the project is separate from issues of responsibility (and remedy) for delays, poor initial planning, management, communication, etc.