Under the NEC4 Engineering and Construction Contract (ECC), Site Information describes the Site and its surroundings. It helps the Contractor understand the conditions in which the works will be carried out and forms part of the contractual basis for assessing physical conditions encountered during construction.
Its usefulness depends on what the records actually establish. A drawing showing an approximate service route may help a tenderer plan the work, but it leaves different questions from a survey confirming the pipe’s position and depth. Those limitations matter when pricing the work and when deciding how to excavate safely around an operating asset.
The fictional Ironbark Recycled Water Scheme, introduced in NEC4 Explained, provides an example. A regional Australian water utility is procuring a pipeline, pumping station and balancing tank under ECC Option C. The scheme will supply recycled water from an existing treatment plant to an industrial estate. The plant must remain in operation while the new works are constructed and connected.
What belongs in NEC4 Site Information
Site Information is defined by both its content and how it is identified in the contract. Under clause 11.2(18), it describes the Site and its surroundings and is contained in the documents identified in Contract Data. The Client identifies those documents in Contract Data part one. A report’s presence in a tender folder or data room is not, by itself, enough to establish its contractual status.
The appropriate material depends on the project. For Ironbark, it could include borehole logs along the pipeline route, groundwater observations, topographical surveys and records of existing services. Work around the treatment plant may also require foundation drawings, contamination records or information about buried structures.
When compiling the documents, the Client should gather the relevant physical conditions information it holds, including records retained by its operations team. A report commissioned years earlier may still contain useful findings. The people who operate the plant may know of alterations which never reached the main drawing register. That information needs to be examined before deciding what to issue.
Site Information and Scope
Records of Ironbark’s existing treatment plant pipework would describe conditions in which the Contractor will work. Requirements to maintain treatment operations, obtain approval for an outage or verify service locations before excavation would tell the Contractor what it must do. Those requirements belong in Scope.
For example, a service drawing may indicate where an existing main is thought to run. If the Client requires the Contractor to expose and survey it before designing the new connection, Scope should state that requirement. Including the drawing alone does not explain the investigation the Contractor is to carry out.
One drawing can contain both existing asset records and requirements for new work. The documents need to make those functions clear so that the team can distinguish information about a condition from an obligation to investigate or construct something. Requirements for investigation or new work belong in Scope.
Reading investigation reports and service records
Borehole logs record findings at particular locations and depths. They do not establish continuous conditions between the boreholes. Groundwater observations also need to be read with an understanding of when and how they were taken. An interpretative report can help explain the findings, but its assumptions should be understood alongside the underlying records.
Suppose Ironbark’s ground investigations cover sections of the pipeline route but do not extend to the treatment plant connection. The tender team needs to recognise that gap when considering its methods and allowances. The delivery team needs the same understanding when planning excavation at the connection.
Service records require similar care. A route taken from historic drawings has a different evidential value from a position confirmed by exposure and survey. The source, date and stated qualifications should remain available to the people using the record. Removing them from a drawing can make approximate information appear more certain than it is.
Site Information cannot describe every condition throughout a site. Its limitations should nevertheless be apparent to a reader. A missing investigation and a completed investigation which found nothing are different things, even if neither gives the tenderer a definitive answer about what lies below ground.
Identifying the contractual documents
A document schedule should identify each report or drawing by title, reference, date and revision. Broad references to a changing data room can leave the parties uncertain about which records formed the contract. Tender clarifications and replacement documents need to be carried through into the final set.
The review involves more than choosing the latest revision of every file. An older investigation report may remain relevant even where a later service plan corrects the position of a pipe. For Ironbark, the team would need to explain that relationship rather than discard useful investigation records simply because another document had been superseded.
Conflicting records should be reconciled before tender where possible. Where a difference cannot be resolved, the documents should make the uncertainty visible. Leaving two plans showing different service positions without explanation makes it harder to price the work and plan the investigation.
Clause 60.3 also has a specific rule for ambiguity or inconsistency within Site Information, including information referred to in it. For the physical conditions assessment, the Contractor is assumed to have taken account of the conditions more favourable to doing the work. This is not a general order of precedence for all the contract documents.
Site Information and physical conditions
The physical conditions provisions described here are those of the June 2017 ECC incorporating the January 2023 amendments, without project amendments affecting them. The provisions in the signed contract must be checked.
Clause 60.1(12) concerns physical conditions encountered within the Site, excluding weather conditions. The test is whether an experienced contractor would have judged, at the Contract Date, that the conditions had such a small chance of occurring that it would have been unreasonable to allow for them.
That requires more than a comparison between a report and the conditions found. The question concerns what an experienced contractor would reasonably have allowed for, rather than simply what the particular Contractor expected or included in its tender.
Under clause 60.2, the Contractor is assumed to have taken account of:
- the Site Information;
- publicly available information referred to in the Site Information;
- information obtainable from a visual inspection of the Site; and
- other information which an experienced contractor could reasonably be expected to have or obtain.
The public information category is specifically tied to material referred to in Site Information. Other information may still be relevant under the final category, depending on what an experienced contractor could reasonably have been expected to know or obtain.
If Ironbark’s excavation encounters material different from that recorded in the boreholes, the team would need to examine the investigation coverage and the other relevant information. The difference alone would not establish a compensation event. Equally, the absence of a condition from Site Information would not settle whether the Contractor should have allowed for it.
Where clause 60.1(12) applies, the assessment concerns the difference between the conditions encountered and those for which it would have been reasonable to allow. It does not bring every cost of working at that location into the compensation event. Ironbark’s use of Option C does not change this test or make every unexpected cost a compensation event.
Report qualifications and disclaimers also need to be read carefully. A statement that service positions are approximate may explain the limits of a record. A restriction on reliance needs to be considered in the context of the whole contract. Neither should be treated as a shorthand answer to who carries all physical conditions risk.
Unexpected conditions on Ironbark
Suppose controlled exposure at Ironbark’s treatment plant connection reveals the existing main at a shallower depth than the team expected. It obstructs the proposed connection arrangement. The service records showed an approximate route, but no verified depth.
The first task is to protect the live asset and establish what has been found. The team should record the location and level, retain photographs and survey information, and consider how the connection can proceed safely. The findings can then be compared with the contractual records and the other information relevant to the physical conditions test.
There may not yet be enough information to decide whether this is a compensation event. An early warning is still required as soon as the Contractor or Project Manager becomes aware of a matter which could have one of the effects listed in clause 15.1. These include increasing the Prices, delaying Completion or meeting a Key Date, or impairing the performance of the works in use. On Ironbark, the process could be used to examine further investigation, alternative connection arrangements and the effect on the operating plant.
If the Contractor believes the event is a compensation event and the Project Manager has not notified it, the Contractor must give the separate notification required by clause 61.3. An early warning does not replace that notice or suspend its time limit while investigations continue. The same problem can require both an early warning and a compensation event notification.
The facts given here are insufficient to determine entitlement. The team can continue reducing the effects while that question is examined. New investigation results should be circulated and retained without silently replacing the original contractual Site Information.
Preparing Site Information before tender
I would ask the people preparing Ironbark’s tender documents to work through the proposed excavations with the investigation team and plant operator. They should be able to explain what information is available at each location, where it came from and what remains uncertain. That review may identify a need for further investigation or for clearer requirements in Scope.
A planner or estimator who was not involved in compiling the records can then test whether the information is usable. If they cannot identify the agreed documents or understand why two records differ, tenderers are likely to face the same problem. Resolving those questions before issue gives the parties a clearer basis for planning and pricing the work.
This forms part of the wider preparation for using NEC4 in Australia. Our NEC4 ECC Contract Drafting course also examines how Site Information, Scope and Contract Data work together. On Ironbark, the aim would be a set of records which the construction team can retrieve, understand and use without having to reconstruct what was issued at tender.
