The NEC Scope: what it covers and what changes it

What the NEC Scope is, how a change to it becomes a compensation event, and how to avoid pricing the wrong thing.

NEC basics for newcomers3 min read

On this page
  1. Where the Scope is found
  2. Sorting what goes where
  3. Changing the Scope
  4. Example: the pump chamber lid
  5. Common problems
  6. Good housekeeping
  7. Related guides

If you are asked "is that in our price?", the answer almost always lives in the Scope. In NEC4 the Scope is the set of documents describing the work you must deliver and any limits on how you deliver it. NEC3 called it Works Information. Your core duty is to provide the works in line with it (clause 20.1), defects are measured against it, and a change to it is usually a compensation event: an event that entitles you to extra time or money.

Where the Scope is found

Two places. First, the documents that Contract Data names. Second, any instruction the Project Manager gives later. The Project Manager is the person the Client appoints to run the contract day to day. Anything in an instruction that asks for work the original documents never mentioned is treated as joining the Scope.

Sorting what goes where

Put these in the Scope:

  • drawings, specifications and standards;
  • limits such as working hours, routes in, order of work and noise;
  • what the Client will provide, and by when;
  • what must be finished by the Completion Date;
  • the rules for programmes, quality and communication.

Keep these elsewhere:

  • the edge of the site and every date or period the form asks for belong in Contract Data;
  • ground investigation results belong in the Site Information;
  • payment terms and legal changes belong in Option Z additional conditions;
  • tender queries with no agreed status should be sorted out before anyone signs.

The split matters. A payment rule hidden inside a specification may not work, and a fact placed in the Site Information is not an obligation on you.

Changing the Scope

The Project Manager does it by instruction (clause 14.3), and most such instructions are compensation events under 60.1(1). Two common exceptions: an instruction that accepts a defect, and a change to a design you produced where you asked for the change or it is needed to make the rest of the Scope fit.

Do not wait for the word "instruction" to appear. If someone with authority tells you to do something new, treat it as one and notify.

Example: the pump chamber lid

Say you are refurbishing a small pumping station. The specification calls for galvanised steel lids, but the drawing schedule shows stainless steel. You priced galvanised.

  1. As soon as either side notices the clash, tell the other (clause 17.1).
  2. The Project Manager decides stainless is wanted.
  3. When assessing, the reading that favours the party who did not supply the Scope is used (63.10). That is you, so your galvanised price stands as the starting point.
  4. Suppose galvanised was £10,000 and stainless is £16,000. Your Prices go up by £6,000, plus the Fee.

Where the muddle is in a design you supplied, the Client gets the favourable reading instead.

Common problems

  • Naming every tender paper as Scope. You import all their contradictions.
  • Woolly tests such as "to the Project Manager's satisfaction", which cannot be priced.
  • Late limits. A new restriction on working hours given by instruction is a change, so notify it.
  • Documents the Contract Data never lists. They are not Scope, however often people mention them.
  • Edition mix-ups. Check NEC3 wording has not crept into NEC4 document sets.

Good housekeeping

  1. One person reads all the Scope documents against each other before tender.
  2. Final documents are listed by title and revision in Contract Data.
  3. The work needed by the Completion Date is stated.
  4. "To include" wording that leaves the extent open is avoided.
  5. A running index records every instruction that alters the Scope.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?