The first programme should usually be produced at the very beginning of the project before any substantive work has been carried out, see clause 31.1.

You are nevertheless correct to say the first programme, and all subsequent ones, need to show a realistic picture of the project at the time it was issued. If it does not, you are entitled not to accept it (see the first or third bullet of clause 31.3). The first programme is not required to show delays because there is no previous programme these delays can be shown against. Subsequent revised programmes are required to show delays in any event (see clause 32.1).

If the first programme is showing work that has not yet been done as already carried out, clearly that is incorrect because it is simply not practicable. As such you are entitled not to accept it for a reason stated in the contract (see  first bullet of clause 31.3).

But you must be careful not to play games. If there is weather event for wind in your contract (there is not in the standard contract) and that weather event has been exceeded, the contractor is entitled to the delay it has caused, whether or not its programme is technically wrong. That is especially so when you consider that weather events cannot be finalised until the end of the month that they incurred in.

We suggest you have a discussion with the contractor and its planner before you decide to not accept the first programme. A good project manager needs to understand there is no such thing as a perfect programme, because it is all about predicting the future, which we all know is impossible. And that is especially so at the beginning of a contract, where almost everything is yet to be carried out. For that reason, it is better to look for reasons to accept it rather than reasons not to.

This website uses cookies, so that we can provide you with the best user experience.
By continuing to use this website, you are giving consent to cookies being used.
To find out more about which cookies we use and how you can manage them, please see our Cookie Policy