NEC4 Quality Requirements Tests and Defects

Under the NEC4 Engineering and Construction Contract (ECC), the Contractor Provides the Works in accordance with Scope. The contract requires the Contractor to manage quality throughout the work and provides procedures for testing, inspection and correction of Defects. Those responsibilities apply during design and construction and continue after Completion.

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, with the plant remaining operational during construction and connection.

Before work is covered, the Contractor needs to have arranged the required inspections and tests. On Ironbark, a failed pipeline test could hold up the connection to the existing plant. The Contractor would need to investigate and correct any Defect, repeat the test and confirm when the section would be ready. The operator’s arrangements for the connection would then need to reflect that sequence.

Quality requirements in Scope

Scope establishes the requirements against which the works are checked. For Ironbark, these would cover the pipe materials and joints, installation requirements and performance of the completed system. The test requirements should identify what is to be demonstrated and the criteria for a satisfactory result.

For a pipeline pressure test, the Contractor needs to know the required pressure, duration and permitted loss. Scope should specify those details or identify the relevant standard. The test record should allow the Supervisor to establish which section was tested, under what conditions and whether the result met the requirement.

A factory test of a pump would answer a different question from testing the installed system with its controls and connection to the existing plant. Each test needs its own criteria. During delivery, the Contractor and Supervisor need the current Scope and relevant accepted Contractor design so that their inspections reflect the requirements that apply.

The quality management system and quality plan

Clause 40.1 requires the Contractor to operate a quality management system which complies with the requirements stated in Scope. Under clause 40.2, it submits its quality policy statement and quality plan to the Project Manager for acceptance within the period stated in Contract Data. Changes to the quality plan are also submitted for acceptance.

For Ironbark, the quality plan should explain how the Contractor will control the pipeline work, including the checks before materials are installed and the records required before work is covered. Those supervising installation should be able to identify their responsibilities and the action required when a check fails.

Acceptance of the quality plan does not change the Contractor’s responsibility for the work. If it fails to comply with its quality plan, clause 40.3 allows the Project Manager to instruct it to correct that failure. The site and supplier teams need to work to the arrangements in the accepted quality plan, including any accepted changes.

Responsibilities for quality under NEC4

The Contractor remains responsible for the works, including work carried out by its Subcontractors. The Supervisor’s duties include tests and inspections, searches for Defects, notification of Defects and the Defects Certificate. The Project Manager deals with acceptance of the quality documents and any changes to Scope or commercial decisions required under the contract.

The Supervisor’s presence on Site can blur those boundaries. A discussion about a pipeline joint does not give the Supervisor a general power to change Scope, agree additional payment or change the Completion Date. Any delegation of a Project Manager or Supervisor action needs to follow the contract and be notified to the Contractor.

Where an inspection or repair requires specialist input, the Supervisor should arrange that support around the construction sequence. The arrangements should also cover absences, so that work does not reach an inspection point with nobody available to carry out the required checks.

Tests and inspections during construction

Clause 41 applies to tests and inspections required by Scope or applicable law. The testing arrangements should establish who carries out each test, who needs to attend and how the results are communicated. Notices and results must follow the contract’s communication arrangements. An inspection schedule can help organise attendance, but any separate contractual notification still needs to be issued.

On Ironbark, pipeline testing would need to fit around installation, backfilling and the connection works. The Contractor’s programme should allow for those activities and any necessary operator contribution. If a section is ready earlier or later than expected, the Contractor needs to review attendance with the people affected.

Where Scope requires Plant and Materials to be tested or inspected before delivery, clause 42.1 prevents the Contractor bringing them to the Working Areas until the Supervisor has notified the Contractor that they have passed. A supplier’s proposed dispatch date therefore needs to allow for the required test and notification.

Suppose a pressure test on one section of Ironbark’s pipeline shows a loss outside the permitted limit. The Contractor would first check the test arrangement and investigate the result. If a leaking joint is found which does not comply with Scope, there is a Defect to correct. Under clause 41.4, a test or inspection which shows a Defect is repeated after correction. Retain the original result alongside the record of the correction and repeat test.

Identifying and notifying a Defect

Clause 11.2(6) defines a Defect by reference to the contractual requirements. It includes a part of the works which does not comply with Scope, or a part designed by the Contractor which does not comply with applicable law or with the Contractor’s design accepted by the Project Manager. The notification therefore needs to identify the requirement not met.

If Ironbark’s operator wants an additional valve for convenience, the first question is whether Scope already requires it. Where the installed arrangement complies with the contract, the operator’s preference for another valve does not make it defective. Adding the valve would require the appropriate Project Manager instruction to change Scope.

Under clause 43.2, the Contractor and Supervisor notify each other of Defects as soon as they become aware of them, until the defects date. The Contractor must notify Defects it identifies without waiting for the Supervisor to find them. Clause 43.1 also allows the Supervisor to instruct a search for a Defect, separately from the scheduled tests and inspections.

For the leaking joint, the notification should identify the location, the observed condition and the requirement not met, supported by the test result. “Poor workmanship” alone would leave the Contractor uncertain about what correction was required. An internal non-conformance report may help record the investigation, but it does not remove the obligation to notify the Defect.

Correcting Defects and recording the result

Clause 44.1 requires the Contractor to correct a Defect whether or not the Supervisor has notified it. On Ironbark, the leaking joint would need to be repaired and the required test repeated to establish compliance. The correction record should include that result, rather than simply record that a repair crew attended.

The obligation to correct a Defect and the treatment of its cost are separate questions. Whether the repair cost is included in Defined Cost depends on the main option and the applicable cost and Disallowed Cost provisions; the correction obligation alone does not decide payment.

Keep the correction record linked to the notification, showing the work carried out and the evidence that it meets the requirement. The Supervisor’s list should distinguish proposed repairs from those completed and checked. Although the contract does not provide a general procedure for the Supervisor to accept every corrected Defect, the Supervisor needs that information to maintain its record and issue the Defects Certificate.

The defect correction period is the time allowed for correcting a notified Defect. Under clause 44.2, it starts at Completion for Defects notified before Completion and at notification for those notified afterwards. For a part of the works taken over by the Client, clause 44.4 delays the start until the necessary access and use have been provided. The defects date is the deadline for notifying Defects and instructing searches. It is not a common deadline for completing every repair.

If a repair is needed after Ironbark’s pipeline has been connected, the Contractor may need an isolation and operator attendance before it can carry out the work. The access arrangements and applicable correction period need to be recorded, with the repair coordinated around the operating plant.

Accepting a Defect or leaving it uncorrected

Clause 45 provides a process for the Project Manager and Contractor to agree a change to Scope so that a Defect does not have to be corrected, with a reduction in the Prices, an earlier Completion Date or both. An informal discussion with the Supervisor does not change the requirement.

On Ironbark, the Project Manager would need to consider any proposal to retain non-compliant work against the utility’s operating requirements and applicable legal obligations. Offering a deduction would not, by itself, allow the Contractor to leave the leaking joint in place. The obligation to correct remains unless the requirement is changed through the contractual process.

Where a notified Defect has not been corrected when required, clause 46 provides for the Project Manager to assess the amount the Contractor pays. The basis of that assessment differs depending on whether the Client has allowed access to correct the Defect.

Completion and the Defects Certificate

The Project Manager certifies Completion against the contractual definition. The Contractor must have done the work Scope requires by the Completion Date and corrected notified Defects which would prevent the Client using the works or Others doing their work. Each outstanding item needs to be assessed against those requirements.

If Scope does not state the work to be done by the Completion Date, Completion occurs when the Contractor has done all the work necessary for the Client to use the works and for Others to do their work. The contractual fallback matters where the documents have not defined the required Completion work.

For Ironbark, installing the pipeline would not achieve Completion if system tests required for Completion remained outstanding. A notified Defect which does not prevent Completion would remain on the correction record afterwards. Calling an item “minor” does not establish whether it prevents the Client using the works or Others doing their work.

Completion and take over are different events. The Project Manager certifies Completion against the contractual definition; take over concerns the Client taking over the works or a part of them under clause 35. The team should record each separately rather than assume that an operational handover or use of the works proves Completion.

The Supervisor issues the Defects Certificate at the time required by clause 44.3. It lists Defects notified by the Supervisor before the defects date which the Contractor has not corrected, or states that there are none. It is not a warranty that the works contain no undiscovered Defects, and its issue does not remove the Client’s rights concerning Defects the Supervisor has not found or notified.

When Ironbark’s operator takes responsibility for running the new system, the records should show which sections have been tested, the repairs carried out and any work still outstanding. Keeping those records current allows the operator to arrange future access and maintenance with an understanding of the installed system and its test history.