Question 1 of 4

Question 1 (25 marks)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

Approach. Lay the site investigation out as a sequential flow chart from the owner's initial brief through to construction verification, with the two non-technical threads the question explicitly asks for — the client/contractor relationship and the contract — drawn as external inputs entering the chart at the two points where they actually govern the sequence: scope/budget definition, and hand-off into construction.

The process runs in two logically distinct phases that the chart makes explicit. The pre-contract phase (Client Brief → Desk Study → Site Reconnaissance → Scope & Budget → Tender & Contract Award) is where the client's terms of reference are translated into a technically defensible scope of work: the desk study and reconnaissance establish what ground conditions are plausible so that the scope and budget put out to tender are realistic, rather than a generic boilerplate specification. This is also where the client/contractor relationship is formalized — the client (or their prime consultant) issues the tender, contractors (drilling subcontractors, laboratories) submit bids against the defined scope, and the contract that is awarded fixes the standard of care, the payment basis (unit-rate vs. lump-sum, important because ground conditions are inherently uncertain before drilling starts), access and safety obligations, and who owns liability for a differing-site-conditions claim. The technical execution phase (Field Exploration → Sampling & In-Situ Testing → Lab Testing & Interpretation → GI Report → Design/Peer Review → Construction Monitoring) is where the contracted drilling and testing actually happen, the results are interpreted into design parameters, and the whole package is checked, first by an independent peer reviewer before it goes into the design, and again in the field during construction.

The inter-relations that make this a genuine feedback process, not a one-way pipeline, are drawn explicitly on the chart. The client review arrow into the GI Report reflects that the client (or their representative) must accept the interpreted ground model and its residual risk before it is used for design — a report is a recommendation, not an unqualified fact, until the client signs off on it. The differing-conditions arrow running from Construction Monitoring back into the GI Report is the most important loop on the chart: when the ground actually exposed during construction disagrees with the investigation's interpretation, that disagreement must be fed back into the report/design basis (triggering a design change, additional targeted investigation, or a formal differing-site-conditions claim under the contract) rather than being resolved informally in the field. Without this loop explicitly drawn and understood by all parties, a genuine ground-condition surprise becomes a dispute about who should have known, rather than a managed technical and contractual process.