Manage Client Expectations
Make sure the contract reflects the client’s expectations. If you find differences early in the project you should tell the client. If you find them late in the project, you …
Make sure the contract reflects the client’s expectations. If you find differences early in the project you should tell the client. If you find them late in the project, you …
Check and confirm geotechnical reports that are supplied to you in a contract. The client may supply reports that are old or inaccurate. Specify in the contract that you are …
You must learn to say no to some requests from clients If change requests from the client will make the design unsafe or unusable, you should refuse to change it. …
Keep a careful watch on external dependencies. External things such as deliveries, contracts, and approvals that could delay your project if late. They may not be your direct responsibility and …
When reading a large specification, to avoid inducing sleep, scan it by key words. If possible, when given a specification by a client, get the it in electronic form. This …
For contracts longer than 12 months, you should have a clause to allow unknown technologies to be added. Particularly for high tech and IT projects. Part way through a long …
A contract is a risk allocation and control device. Remember the importance of the contract.
A contract can list project deliverables without making the requirements clear. Agree on the detail, formats, deadlines and acceptance criteria early, and make documentation requirements easy to find in tenders and contracts. A clear deliverables list helps prevent rework, missing information and difficult project closeouts.
Finishing the work is not the same as delivering it. Check the payment milestone, submit the required package and keep the evidence before invoicing your client.
If a partly completed project is put on hold (deferred project) by the client, when it is restarted it should be treated as a new project. This includes reviewing and …