NEC4 Scope and Project Requirements

Define the work, interfaces and project requirements in proportion to the project.

On this page

The NEC4 Engineering and Construction Contract (ECC) provides the procedures for managing a project. It is the Scope that tells the Contractor what this project requires: the works to be provided, the constraints on carrying them out and any other information required by the contract.

That distinction matters at tender and throughout delivery. Detailed procedures are of little help if the parties have different understandings of the work itself. The first test is whether the requirements can be understood, planned and priced by the people who will carry them out.

Start with the work to be delivered

A tender pack can contain hundreds of pages and still leave the Contractor unable to establish who designs an interface, when an existing asset can be shut down or what completion looks like. More documentation does not necessarily produce a clearer requirement.

Preparing the Scope requires input from the people who understand the asset, its operation and the proposed construction.

Make the requirements capable of being priced

Consider a pumping-station upgrade. A requirement to maintain service throughout construction may be straightforward to write but expensive to deliver. Tenderers need to understand the permitted outages, operating capacity, isolation arrangements and any restrictions on temporary works. The operator needs to confirm that those arrangements are achievable.

Identify what is fixed and where the Contractor has a choice. If the Client requires a particular construction sequence, state it. If the requirement is continuous service and the method is for the Contractor to develop, describe the performance required without inadvertently prescribing a different method elsewhere in the pack.

Read the drawings, specifications and operational requirements together. Ask a planner and estimator who were not involved in preparing them to explain how they would deliver and price the work. Their questions are a useful test of what still needs attention.

Allocate design and interface responsibilities

The Scope should identify the parts of the works the Contractor is to design. A collection of drawings marked with different design statuses is a poor substitute for a clear allocation of responsibility.

For each significant interface, identify the information to be supplied, who supplies it and what the receiving designer must do with it. A mechanical package may depend on structural loads, electrical capacity and control-system requirements from three different sources. Assigning the package to one designer does not resolve those dependencies.

Set out the required design submissions and allow for their preparation and review in the delivery plan. The separate article on NEC4 acceptance explains why the review process does not transfer the Contractor’s design responsibility to the Project Manager.

Specify administration that serves the project

Every additional report needs someone to prepare it and someone to use it. Before requiring a weekly dashboard, a monthly progress report and a separate safety report, identify the decision each one supports. Information already available in the programme or commercial requirements of the contract should not have to be restated in the Scope solely to fit another template.

For a modest refurbishment, a short schedule of forthcoming isolations and decisions may be more useful than a reporting pack developed for a major infrastructure programme. Requirements still need to satisfy the contract, but the supporting detail should reflect the work, its risks and the people managing it.

Include necessary technical and management requirements in the Scope. Do not use it to conceal changes to payment rights, liability or the conditions of contract. Those are separate drafting decisions, discussed in the article on NEC4 amendments.

Check that completion can be demonstrated

Mechanical completion may mean the installation is finished and ready for commissioning. Operational completion may require the installed system to be tested and shown to perform as intended. If the project uses both stages, the Scope should define the work, tests and records required for each, and state what must be done before Completion under the ECC.

For the pumping station, a factory test may establish that a pump performs to specification without demonstrating that the installed system operates with the existing controls. The Scope should distinguish those checks and identify any Client contribution, such as operator attendance or access to an operating system.

Control the issued requirements

Before tender, reconcile the document list and revisions. Remove superseded requirements and resolve conflicts while the people who prepared the pack are available. Record which assumptions have been resolved and which matters still need a decision.

During delivery, distinguish an explanation of an existing requirement from a change to it. A revised drawing should come with a clear account of what has changed and the appropriate contractual communication. Informal technical agreement should not leave the site team guessing which version it is required to build.

This article is intended to provide general commentary and insights on construction, commercial and dispute resolution matters. It is not legal, contractual or professional advice and should not be relied upon as such. Specific advice should always be sought in relation to individual projects and circumstances.

Related training

NEC4 contract drafting training examines how the project documents describe the work and support its delivery.

Further reading

All articles
NEC4 · Decisions

NEC4 Acceptance: Design, Programmes and Quotations

Read article
NEC4 · Project management

NEC4: Integrating Early Warning with Project Risk Management

Read article
Australia · AS contracts

AS 4000:2025: Practical Implications for Project Teams

Read article