Variation or New Scope? A Practical Contract Management Test

On a busy construction project, the phrase “this is extra work” is often used before anyone has established what the contract actually requires.

The commercial question is more precise:

Has the required work changed the Contractor’s contractual obligations, or is the work already included in the original scope?

The answer controls entitlement to additional time and money. It can also determine whether the team should issue a notice, submit a proposal, proceed under an instruction, or simply perform an existing obligation.

The following test is designed for practical contract management. The exact contractual result depends on the signed agreement.

Test 1: What is the contractual baseline scope?

Do not start with the latest drawing. Start with the contract.

Identify the documents that define the obligation:

• Agreement;
• General and Particular Conditions;
• Employer’s Requirements or Scope;
• specifications;
• tender drawings;
• schedules;
• accepted proposal;
• bills or price schedules;
• clarifications;
• exclusions;
• interface matrices; and
• incorporated addenda.

Then apply the document hierarchy.

A change can only be measured against an established baseline. If the baseline itself is ambiguous, the first issue may be contract interpretation rather than valuation.

Test 2: What exactly changed?

Define the delta.

Examples include:

• additional quantity;
• different quality or performance standard;
• altered alignment or location;
• changed sequence;
• different method imposed by instruction;
• new testing requirement;
• additional interface;
• omitted work;
• change in design criteria; or
• acceleration/resequencing.

Avoid saying merely “the drawing changed.” A revised drawing can correct an error without changing scope, develop an already-required design, or introduce a genuine new obligation.

Compare the before and after requirements in a change matrix.

Test 3: Is the requirement already captured by a broad obligation?

Many contracts include obligations such as completing all work necessary for performance, coordinating interfaces, correcting defects or carrying out Contractor design.

A broad clause does not automatically make every later requirement free of charge. Equally, a Contractor cannot convert ordinary completion of its existing obligation into a Variation simply because the work is more difficult than expected.

Ask:

• Was the requirement reasonably identifiable from the original documents?
• Is it necessary to achieve an expressly defined performance obligation?
• Does it result from a Contractor design development within its existing responsibility?
• Is it rectification of non-compliant work?
• Is it a response to the Contractor’s own means and methods?
• Or has the Employer/Engineer introduced a materially different requirement?

This is where technical and contractual review must work together.

Test 4: Who issued the instruction—and did they have authority?

A genuine change in project direction may still create an administration problem if it was communicated by someone without contractual authority.

Check:

• who can instruct a Variation;
• whether delegation is permitted;
• required form of instruction;
• confirmation procedure for oral instructions;
• whether the Engineer/Project Manager can instruct the change directly;
• whether Employer staff can do so; and
• whether the Contractor must notify if it considers an instruction to be a Variation.

A workshop comment, design-review remark or site request should not automatically become authorised extra work.

Test 5: Which contractual change mechanism applies?

Under FIDIC, Variations are generally administered through Clause 13, subject to edition and Particular Conditions. The 2017 suite distinguishes more clearly between instructed Variations and proposals requested from the Contractor.

Under NEC4, the commercial mechanism is different. A Project Manager’s instruction changing the Scope will ordinarily be considered through the compensation-event process, subject to the contract and the exceptions in Clause 60.

This matters because the required sequence—notification, quotation, assessment and implementation—can be different even where the physical change is the same.

Test 6: What is the time effect?

A Variation is not only a quantity-surveying exercise.

Assess:

• procurement lead time;
• design duration;
• approvals;
• access;
• construction sequence;
• critical-path effect;
• additional testing;
• commissioning;
• rework;
• productivity;
• interfaces; and
• mitigation options.

A change with a small direct cost can have a significant schedule consequence. Conversely, expensive additional work may be executed within available float and have no effect on completion.

Time and cost should be assessed together but proved separately.

Test 7: How should the change be valued?

Follow the contract’s valuation hierarchy.

Potential approaches include:

• existing applicable rates;
• adjusted rates;
• new rates;
• lump-sum quotation;
• cost plus agreed mark-up;
• daywork/force account; or
• defined-cost assessment under NEC.

Do not wait until the work is complete to decide how records should be kept.

If valuation is unresolved, create a dedicated cost code and capture:

• labour by trade and hours;
• equipment type and hours;
• materials;
• subcontract invoices;
• quantities;
• production achieved;
• supervision;
• dates;
• instructions; and
• contemporaneous approval/sign-off where the contract provides for it.

A practical seven-question decision tree

When new work appears, ask:

1. What document defines the original obligation?
2. What is different from that obligation?
3. Is the difference already covered by design, coordination, compliance or rectification duties?
4. Who required the difference, and did they have authority?
5. Which contractual change mechanism applies?
6. What time and cost consequences arise?
7. What notice, quotation and records are required now?

If the team cannot answer Question 1, it is too early to confidently answer “Variation” or “included.”

Common mistakes

Pricing before defining scope. This turns the debate into a negotiation over money before entitlement is established.

Treating every revised drawing as a Variation. Revisions can be design development or correction within existing responsibility.

Proceeding without notice. Even a valid change can become procedurally difficult if the required notification or quotation is late.

Ignoring deleted scope. Omissions and substitutions also need contractual treatment and valuation.

No cost segregation. Additional work mixed into normal project codes becomes hard to quantify.

No programme assessment. The team later claims delay without having recorded how the change affected the contemporaneous plan.

The best change record is created before the argument

A disciplined project maintains a change register from the moment a potential delta appears.

Each entry should contain the baseline requirement, new requirement, instruction, authority, contractual position, notice, status, cost code, schedule effect and current valuation.

That turns “variation or new scope?” from a late-project debate into a controlled project decision.