To my mind 'best practice' is providing information which appropriately describes the Employer's (or Client's) requirements. Remember that the Employer is responsible for providing the (his) Works Information (Scope) and it should be comprehensive enough to convey any particular detail, but also clear, relevant and precise. This would include any important test and inspection requirements.
When including an obligation in a contract document, think about how you would go about fulfilling it. That way you try to avoid any ambiguity or misunderstanding, which could easily lead to a dispute situation. It doesn't matter how competent a contractor is, if you have described a requirement that is ambiguous and open to interpretation then you will get just that, ambiguity !!
How important are the testing requirements? How much will they cost? Is it clear what both the Contractor and Supervisor are required to do? Get everything peer reviewed as well. I have been involved in a significant number of disputes, simply because of inconsistencies or lack of detail in the contract documentation.
When including an obligation in a contract document, think about how you would go about fulfilling it. That way you try to avoid any ambiguity or misunderstanding, which could easily lead to a dispute situation. It doesn't matter how competent a contractor is, if you have described a requirement that is ambiguous and open to interpretation then you will get just that, ambiguity !!
How important are the testing requirements? How much will they cost? Is it clear what both the Contractor and Supervisor are required to do? Get everything peer reviewed as well. I have been involved in a significant number of disputes, simply because of inconsistencies or lack of detail in the contract documentation.