Instructed Change to the Scope: Compensation Event 60.1(1)

What counts as a Project Manager instruction changing the Scope, the two exceptions, how it is priced, and the mistakes that cost contractors money.

Compensation events and change3 min read

On this page
  1. What has to be true
  2. What to expect in practice
  3. Worked example: one addition, one omission
  4. How it is assessed
  5. What people get wrong
  6. Related guides

If the Project Manager instructs you to do something the Scope did not require, that is a compensation event under clause 60.1(1). The Project Manager is the person the Client appoints to run the contract day to day, and the Scope is the document describing what you must deliver. It is the most common event on most jobs, and often the simplest, because the instruction itself proves what happened.

In NEC3 the same entry refers to the Works Information, which is the old name for the Scope.

What has to be true

  1. The Project Manager gave an instruction. The power to do so sits in clause 14.3.
  2. The instruction changes what the Scope requires.
  3. Neither of two exceptions applies.

The exceptions. The first is a change that lets a Defect stay in return for lower Prices, an earlier Completion Date or both. The second is a change to your own design, made at your request or to make it fit the Client's Scope. In both, the cost is not the Client's.

An instruction that resolves an ambiguity or conflict between documents (clause 17.1) can also arrive here. Clause 63.10 prices that change using the reading most favourable to whoever did not write the Scope.

What to expect in practice

Most arguments are about whether a change was really instructed. Comments on drawings, emails from a consultant and chats on site are not instructions. If someone other than the Project Manager asks for something different, ask the Project Manager to instruct it before you build it. Without that, you have no event.

Keep:

  • the instruction in the form clause 13.1 requires, from the Project Manager or a notified delegate,
  • the Scope before and after, such as the drawing revision or specification clause that moved,
  • for a disputed change, what was tendered and any query and answer that led to it.

Worked example: one addition, one omission

A fictional warehouse yard on Option A, with a 10% Fee.

The Project Manager instructs a new oil interceptor that was not in the Scope. It sits on the critical path, because the outfall run cannot start until it is in. Forecast Defined Cost, meaning your expected actual cost, is £5,400 for excavation, £9,100 for supply and fitting and £3,000 for a week of site running costs. That is £17,500, plus £1,750 Fee, so the Prices rise by £19,250 and the Completion Date moves a week.

Later the Client drops a fence from the Scope, saving £8,000. The usual rule is that a saving does not reduce the Prices, but clause 63.4 makes an exception for a change to the Client's Scope. The Prices fall by £8,000 plus its Fee. If you had proposed the saving yourself, the main Option's sharing rules would apply instead.

How it is assessed

The dividing date is the day the instruction was given (clause 63.1). Work done before that date is actual cost and the rest is forecast. Delay is measured on the Accepted Programme current at that date (63.5). If the change makes a Key Date condition wrong, the Project Manager corrects it in the same event (63.11).

The Project Manager should notify the event with the instruction. If it does not, notify it yourself under clause 61.3. Events that arise from an instruction escape the eight-week time bar, but waiting gains you nothing.

What people get wrong

  • Treating every instruction as a change. If it only confirms what the Scope already says, nothing has changed. Compare the requirement, not the paperwork.
  • Accepting "clarification". If it makes you do something new, it is a change, whatever it is called.
  • Working on a verbal request. Ask for it in writing first.
  • Claiming for your own design errors. Correcting your own design to fit the Client's Scope is not an event.
  • Forgetting the omission. Savings can be missed if no deletion is properly instructed.

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

Was this useful?