Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Substantiating Delays in a Project

2 replies [Last post]
Nilesh Jain
User offline. Last seen 3 years 23 weeks ago. Offline
Joined: 22 Jan 2020
Posts: 16
Groups: None

Hello Everyone,

I'm doing scheduling for four years and slowly pulled into claim analysis and schedule auditing. Therefore, I have limited knowledge and your expert opinion would be appreciated.

I'm working on a project with 12,000 and doing schedule audit every month. Every update, the contractor is trying to compress the critical path by reducing the activity duration or by overlapping them. The reason given for every update is 'According to the Pull Planning Session,' and the contractor is just trying to maintain the contractual finish date on the schedule. However, I know that they are behind schedule and eventually, the Owner would be in trouble. 

My question is, what is the best practice I should adopt to make sure the Owner is protected, and if we ever go for a claim, the owner has a stronger case against the contractor?

Thanks for your time and looking forward to hearing from you.

Regards,

Nilesh Jain

Replies

Stephen Devaux
User offline. Last seen 18 weeks 2 days ago. Offline
Joined: 23 Mar 2005
Posts: 667

Wow! Indeed, a really good question!

And a really, really good answer from Patrick!

Fraternally in project management,

Steve the Bajan

Patrick Weaver
User offline. Last seen 5 days 15 hours ago. Offline
Joined: 18 Jan 2001
Posts: 373
Groups: None

Hi Nilesh,

Your question is really good!

What not to do:  Don't get involved in 'helping' the contractor plan its work. If you do you will accept some responsibility.

What to do:

1. Make sure payments accurately reflect work actually accomplished.

2. As far as possible make sure all of the client inputs are delivered in accord with the original program requirements. If these are delivered later than this the contractor can claim 'pacing' if the deliveries actually cause a delay the contractor can claim the delivery was the overriding cause of the delay and seek EOTs with costs.

3. Keep really accurate records of everything done on a daily basis. Date stamped photographs help. Signed records are good. Make sure the progress information is shared with the contractor (no surprises).

4. Expect lots of claims from the contractor and gear up early. 

5. Don't assume the contractors Head Office knows what is going on.  Regular requests to the head office to explain schedule slippages each month (eg, contract issued last month was for 1000cu.m. only achieved was 700cu.m - please explain) will put pressure on the site to perform. Focus these on one or two key metrics only.

It may help to get expert advice early (but this tends to be expensive).

Some free resources that mey help are avaiable at: https://mosaicprojects.com.au/PMKI-TPI-080.php