Failure Blueprint (Story no.6) — Waiving project requirements

In case you don’t know this story is part of a serial of stories, you can visit previous stories through the links below

1| How to fail in a construction project

2| How to fail in a construction project

3| How to fail in a construction project

4| How to fail in a construction project

5| How to fail in a construction project

Now let’s continue

7- Final negotiation and waived requirements

Usually directly before signing the contract each party will try to get a bite from the agreed terms and conditions,

Owner will try to increase contractor’s obligations and the contractor will try to reduce his obligations

If this happened there will be two scenarios, Either the contractor will get what he is trying to get, then the site team will suffer with him in this obligations which was waived without assigning another party to do it, whether waiving the specs of a description in BOQ which usually what happens as an offer from the contractor to reduce the costs and the procurement or even engineering may accept it considering that this waiving is small compared to the contract but in fact they will stuck executing this item even through a variation to the contractor or by another contractor who will price it higher than the original contractor.

The second scenario which the client gets what he try to get, then the execution team of the contractor will stuck executing such works which wasn’t originally budgeted in the pricing stage, and they will try by all mean find a work around this issue which will not be in favor of the project.

In fact in both situation the proper documentation is the key factor of preventing all of risks which may occur at a later stage of the project