Construction Scope Management: How GCC Contractors Define and Protect Their Contract Scope

Most variation disputes on GCC construction projects are not really about price. They are about scope. What was in and what was out was never established clearly enough, and by the time someone flags it, two months of work has been done on a verbal instruction, or a contractor has built something the client insists was always included.

Scope management is the discipline that prevents this. It is distinct from change order management — which prices changes once they are instructed — and different from contract administration, which tracks FIDIC obligations. Scope management is upstream: establishing exactly what the contract covers from day one, managing package interfaces, and detecting when extra work is being requested before it is built.

What Scope Management Means in Construction

In GCC construction, scope operates at three layers simultaneously:

• The contract scope — what the base contract covers, defined by drawings, specifications, and the BOQ.
• The package scope — for multi-package projects, what each trade package is responsible for and where the gaps and overlaps sit.
• The change scope — all employer-instructed additions, omissions, and substitutions from the original.

Scope management means keeping all three layers visible, current, and agreed. Without that discipline, project teams end up where many GCC megaprojects land: a PM who cannot tell you what today's scope is because it lives across emails, addenda, variation orders, and RFI responses — none of them connected.

Why Scope Creep Happens on GCC Projects

Scope creep on construction projects is rarely deliberate. It happens for structural reasons.

Incomplete Tender Documentation

BOQs and specifications in Saudi Arabia and the GCC frequently have gaps, ambiguities, or outdated revisions. When the contractor prices, they make assumptions. When construction starts, those assumptions collide with reality — and someone fills the gap. Whose cost that represents is never discussed at the time.

Design Development During Construction

On design-and-build and D&C contracts, client requirements evolve during detailed design. NEOM and ROSHN projects are structurally prone to this: the programme demands construction starts before design is complete, and scope is effectively defined on the fly. The contractor who does not track the baseline is always behind.

Verbal Instructions

A senior client representative tells a site manager to add a line of light fittings while the team is up there. The contractor does it. No variation order is ever raised because neither side thought it was worth the paperwork. Multiply that by 400 similar decisions over 18 months and the unrecovered scope exposure becomes material.

Package Interface Gaps

On a SAR 450M commercial tower with 12 active subcontract packages, defining who owns what at the boundaries requires deliberate management. The MEP-civil interface, the specialist facades package handover to the main structure — without a formal assignment, nobody installs the fixings, and the fix falls to whoever is easiest to pressure at the time.

Establishing the Scope Baseline at Contract Award

The scope baseline is not just the drawings and specifications. It is a defined record of what the contract includes, what it explicitly excludes, and what decisions were made during tender about how to interpret ambiguities.

A complete scope baseline record at contract award includes four components:

Tender Clarification Log

Every clarification question raised and the answer given during tender, cross-referenced to the contract item it affected. This is the record that prevents a client from claiming later that an item was always in scope when the contractor priced it as excluded based on a specific clarification answer.

Exclusions Register

A named list of items explicitly excluded from the tender price. Not everything is obvious. A contractor pricing a civil package may have excluded temporary works because they assumed the main contractor would cover them. That assumption needs to be documented and confirmed within the first 28 days of contract — not discovered at final account.

Package Interface Matrix

For multi-package projects, a responsibility assignment matrix showing who supplies, who installs, who tests, and who accepts at each interface point. Updated at each subcontract award. Get both package contractors to sign the boundary document. Any disagreement surfaces now, not at installation stage when the programme has no slack.

Drawing Revision Baseline

The exact drawing revision for each discipline at the date of contract award. Every subsequent revision is a change from this point, whether or not a formal variation order accompanies it. A 200mm slab thickening on one floor of a 42-storey tower has direct cost implications in rebar, formwork, and programme that compound across the entire structure if not captured at each revision.

Detecting Scope Creep Before It Becomes a Dispute

By the time a contractor raises a variation claim for work already built, they have lost leverage. The work is complete, the argument is retrospective, and the client's default position is that it was always included. Detection has to happen in real time.

Instruction Classification at Weekly Site Meetings

Every instruction from the client's team — verbal, written, or implied by a revised drawing — should be reviewed and classified at the weekly site meeting. The question is simple: is this within the existing scope, or is it a change? The site team's default tendency is to comply and sort the paperwork later. That default has to be consciously overridden by a standing agenda item.

Drawing Revision Log Against Baseline

Every revised drawing issued should be compared against the baseline revision. Any change from baseline is a potential scope change, even when it looks minor. This check cannot be left to the engineer who received the drawing — it needs a formal review step before the instruction is executed.

RFI Response Scope Review

RFIs are often answered with revised drawings or clarifications that subtly expand the contractor's scope. Each RFI response should be reviewed not just for technical content but for whether the answer adds to what the contractor priced. An RFI that results in an additional protection detail, a heavier specification, or a revised sequence is a potential variation regardless of how it was framed in the response.

Subcontractor Work Order Variance

At the package level, if a subcontractor's actual work orders are running ahead of their contract sum at a faster rate than their certified quantities, it can indicate scope additions not yet captured in a formal variation. This signal is visible if work confirmations are linked to the subcontract value in the cost management system — invisible if they are not.

Managing Package Interfaces at Scale

On large GCC construction projects, package interface management is one of the most consistent sources of disputed scope. The problem is rarely that two packages claim the same work. It is that both packages say the interface item is in the other's scope, and nobody acts until the programme forces it.

A workable interface protocol for multi-package GCC projects:

1. At each subcontract award, issue a two-column scope boundary document: what the package contractor supplies and installs, and what the adjacent package is responsible for at the boundary.
2. Get both contractors to sign the boundary document. Disagreement here is useful — it surfaces the gap before construction begins.
3. Review critical interface items at the monthly subcontractor coordination meeting with a RAG status: red for unresolved disputes, amber for approaching decision points, green for agreed and scheduled.
4. Where a genuine gap exists between packages — something that falls outside both scopes — direct a formal variation to one contractor to cover it rather than leaving it unassigned.

On a NEOM residential package with 20 active sub-packages, this is administratively demanding. The alternative is SAR 4–6M in contested variation claims at handover when the gaps have to be closed under programme pressure.

Scope Management and Variation Entitlement

A contractor who can point to a dated drawing baseline and show that a specific change diverges from it has a defensible variation claim. A contractor who built to whatever was current without checking against the baseline is presenting a retrospective argument that the client will contest on the grounds that it was always included.

This matters under FIDIC Clause 13.1, which requires variation instructions to be issued before work proceeds where possible, and Clause 20.2.1, which imposes a 28-day notice window for claims arising from events. Neither condition can be met if the contractor's operational team does not recognise a change has occurred until weeks after it was built.

The scope baseline is the datum. Every valid variation claim references a departure from that datum. Without it, the entitlement may exist in principle but cannot be demonstrated in the documentation.

Scope Management and the WBS

A well-structured WBS connects scope management to cost control. Each WBS element represents a defined scope item. When a scope change occurs, it either maps to an existing WBS element — a quantity change within an existing item, captured through a variation to the BOQ — or it requires a new WBS element for a genuinely new scope item.

Managing scope through the WBS keeps the cost report coherent. New scope that is not tied to a new WBS element gets absorbed into a cost code priced for something else, making variance analysis unreliable. The change order process should create or update the WBS element, update the budget, and link the new scope to procurement and confirmation workflows. The change does not just sit in a variation register — it becomes a live project element that flows through to committed costs, certifications, and billing.

Practical Starting Steps

For GCC contractors who want to build scope discipline into their next project:

• Lock the drawing baseline at contract award. Issue a baseline drawing register by discipline and revision, shared with the client's team, within 14 days of contract execution.
• Compile the exclusions register from tender correspondence and submit it to the client for confirmation within 28 days. Force the conversation early, not at final account.
• Issue package scope boundary documents at each subcontract award. Get contractor acknowledgements within 14 days. Any dispute surfaces a gap that will cost more to resolve during construction.
• Add a scope classification item to the weekly site meeting. Every instruction reviewed against the baseline. Fifteen minutes with the right people present changes the commercial outcome of the project.
• Connect scope changes to WBS codes before work begins. A variation without a WBS code is a cost that will not appear where it needs to when the project is reviewed.

The Cumulative Impact

On a SAR 300M GCC construction contract with a 6% gross margin, the contractor has SAR 18M of margin to protect. Scope additions worth 2% of contract value — SAR 6M — that are not recovered reduce margin by a third. That level of unrecovered scope is not unusual on projects where scope management discipline is weak. It accumulates across hundreds of small decisions, each of which seemed manageable at the time.

The project team that manages scope actively — with a baseline, a weekly classification routine, a package interface matrix, and a WBS-linked change order process — is not doing more work than a team that does not. They are producing a different outcome from the same effort. The meetings happen regardless. The decisions are being made. The only question is whether they are being recorded in a way that can be used.