Civil Engineering Project Management (4th Edition)
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
56 <strong>Civil</strong> <strong>Engineering</strong> <strong>Project</strong> <strong>Management</strong><br />
This consistency can be promoted if one person drafts all the documents or,<br />
if parts are written by others, one person carefully reads through the whole<br />
finished set of documents. An inconsistency in the documents can give rise to<br />
a major dispute under the contract, having a serious effect on its financial outcome.<br />
Some guiding principles are as follows.<br />
• The layout and grouping of subjects should be logical. These need planning<br />
out beforehand.<br />
• Requirements for each subject should be stated clearly, in logical order,<br />
and checked to see all aspects are covered.<br />
• Language and punctuation should be checked to see they cannot give rise<br />
to ambiguity.<br />
• Legal terms and phrases should not be used.<br />
• To define obligations the words ‘shall’ or ‘must’ (not ‘should’ or ‘is to’, etc.)<br />
should be used.<br />
• Quality must be precisely defined, not described as ‘best’, etc.<br />
• Brevity should be sought by keeping to essential matters.<br />
It is not easy to achieve an error-free specification. It is of considerable<br />
assistance to copy model clauses that, by use and modification over many<br />
previous contracts, have proved satisfactory in their wording. Such model<br />
clauses can be held on computer files so they are easy to reproduce and modify<br />
to make relevant to the particular project in hand. Copying whole texts<br />
from a previous specification which can result in contradictory requirements<br />
should not be adopted. Entirely new material is quite difficult to write and<br />
will almost certainly require more than one attempt to get it satisfactory.<br />
The specification has to tell the contractor precisely:<br />
• the extent of the work to be carried out;<br />
• the quality and type of materials and workmanship required;<br />
• where necessary, the methods he is required to use, or may not use, to construct<br />
the works.<br />
Under the first an informative description is given of what the contractor is to<br />
provide and all special factors, limitations, etc. applied. Under the second the<br />
detailed requirements are set out. The extent of detail adopted should relate<br />
to the quantity and importance of any particular type of work in relation to the<br />
works required. Thus the specification for concrete quality may be very extensive<br />
where much structural concrete is to be placed; but it may be quite short<br />
if concrete is only required as bedding or thrust blocks to a pipeline. A ‘tailormade’<br />
specification appropriate to the nature of the work in the contract<br />
should be the aim.<br />
Repetition of requirements should be avoided. If requirements appear in<br />
two places, ambiguity or conflict can be caused by differences of wording.<br />
Also there is a danger that a late alteration alters one statement but fails to<br />
alter its repetition elsewhere.<br />
The third of the items noted above needs careful consideration, as there may<br />
be dangers and liabilities involved in telling the contractor how to go about his