Subcontract Scope of Work in GCC Construction: How to Write Package Scopes That Prevent Interface Disputes

The Interface Gap That Nobody Budgets For

When a SAR 320M mixed-use tower in Riyadh entered the fit-out phase, three separate subcontractors — civil finishes, MEP, and dry lining — each produced work orders, delivery records, and payment claims for the same corridor work. None of them were wrong, exactly. Each had a plausible reading of their contract scope. The GC absorbed the cost twice, then spent four months in a three-way commercial dispute trying to recover.

The root cause was not the subcontractors. It was a scope of work document that said "including all related works" and left every interface undefined.

This is the pattern. Interface disputes between subcontract packages are consistently among the most expensive commercial failures on GCC construction projects. They are also almost entirely preventable — the discipline that prevents them happens before the first subcontractor mobilises, not after the first dispute arises.

Why GCC Construction Has More Interface Risk Than Most Markets

Large GCC projects run dozens of subcontract packages simultaneously. A SAR 500M infrastructure project might carry 40–60 active subcontracts at peak: civil, structural, MEP (split across mechanical, electrical, plumbing, and fire), fit-out, landscaping, roads, temporary works, and specialist packages. Every point where two packages meet is a potential interface dispute.

Vision 2030 projects amplify this. NEOM's Sindalah Island, ROSHN urban developments, Aramco refinery expansions — these involve multi-GC consortia with scopes developed at tender stage by teams who won't run the execution phase. The scope definition that happens at award stage determines how much commercial pain accumulates over the following 24 months.

Four factors make GCC interface management particularly difficult:

• Scope developed under tender pressure. BOQ-based tenders often defer interface questions. "Structural steel, including connections" sounds clear until the facade contractor asks whose responsibility the bracket plates are.
• Packages awarded sequentially. Civil packages go first. MEP follows. Fit-out comes last. Each award is made against the scope definition that existed at the time. When the programme accelerates and trades overlap, the gaps appear.
• Multiple design consultants. Structural, architectural, MEP, and facade designers each produce their own drawings with different package assumptions. Coordination drawings arrive late or not at all, and subcontractors work to discipline-specific drawings until they collide in the field.
• Subcontractors under commercial pressure. A subcontractor who priced tightly at tender will claim anything their scope does not explicitly exclude. A GC who writes vague scopes hands them that leverage.

The Five Gaps That Turn Into Disputes

Every interface dispute traces back to one of five scope definition failures:

1. Connection and Fixing Responsibility

Who supplies and installs the brackets, fixings, and connections between two packages? Facade subcontractors claim the structural steel sub should have included bracket plates. The structural steel sub says the facade package starts at the bracket. The cost of the brackets is small. The delay and the dispute are not.

2. Openings, Penetrations, and Sleeves

MEP subcontractors need penetrations through floors and walls for their pipe and duct runs. Civil contractors say they need instructions before pouring. MEP says the civil sub should have allowed for openings based on the drawings. Nobody co-ordinated the drawing versions. The slab is now cast solid.

3. Temporary Works and Access

Who provides scaffolding for the facade contractor to install cladding? Is tower crane hire shared or separate? Who provides hoisting for MEP risers? These questions appear in scopes as "contractor to provide their own access equipment" — then dispute arises when trades need the same equipment in the same zone at the same time.

4. Testing, Commissioning, and Flushing

MEP sub installs pipework. Plumbing sub does sanitary fixtures. Electrical sub does power. Who is responsible for integrated testing across these systems? Who provides temporary power for commissioning? Who pays for flushing and chemical treatment of the chilled water system before handover? Unless the scope explicitly allocates this, every subcontractor points to the next.

5. Final Clean and Protection

Each subcontractor finishes their scope and leaves. Subsequent trades damage previous work. The question of who pays for protection, repairs, and final cleaning cycles through every trade from first package to last. Without explicit allocation, every subcontractor claims it is somebody else's responsibility — and they are each partially right.

What a Defensible Subcontract Scope Document Actually Contains

A scope of work that prevents disputes is not a long document. It is a precise one. The key sections are:

Scope Statement — What IS Included

Written around work outputs, not activities. "Supply, fabricate, deliver, and install all structural steel elements as shown on Drawing List A, Revision C2, including all field connections, bolts, and site welding." The drawing list and revision at award is critical — when design advances, this list becomes the baseline for change order assessment.

Exclusions List — What Is NOT Included

Every boundary decision becomes explicit. "Excluded from this scope: anchor bolts cast into concrete foundations (by civil sub); facade attachment brackets and fixings (by facade sub); crane hire for erection (by GC directly)." An exclusions list forces the GC to make conscious decisions about every gap. The gaps decided now cost nothing. The gaps discovered during execution cost multiples.

Interface Matrix Reference

Each interface point between this package and adjacent packages is tagged. Not resolved in the scope itself — but mapped to a separate interface matrix that records who is responsible for each boundary item. The scope document references the interface matrix as a contractual annex.

Drawing and Specification List

The exact documents the subcontractor is working to at time of award. Later revisions are variations — not scope creep, not silent obligation expansion.

Provisional and Prime Cost Items

Any work where quantity or scope is not yet defined should be flagged as provisional with an estimated value. This prevents a subcontractor from claiming at final account that unresolved items at award were always within their scope.

Programme Milestones

Key dates this package is responsible for: access date, material delivery dates, milestone completions, commission-ready handover. These drive the payment schedule and the back-charge trigger if they cause delays to following trades.

The Interface Matrix: Making Package Boundaries Explicit

The interface matrix is a separate document — but it should be a mandatory annex to every subcontract package. It is a table that maps every boundary point between packages to a named responsible party:

• Bracket plates for facade attachment — Structural Steel sub (supplied and installed before facade commences)
• Floor penetrations for MEP risers — Civil/Structural sub (formed at pour based on MEP drawings Issue B or later)
• Scaffolding for facade installation — Facade sub (each sub provides their own access to their working area)
• Commissioning power supply (temporary) — GC direct (from site generator; sub provides sub-distribution within their scope)
• Final clean before snag — Each sub within their package, within 48 hours of area handover to the following trade

The matrix is prepared by the GC's commercial team at the time of the first package award and updated with each subsequent award. When a gap appears — an interface nobody has been assigned — it is the GC's responsibility to resolve it before work begins in that area, not to discover it when the dispute arrives.

On large GCC projects, the interface matrix typically runs to 60–120 line items across 20+ packages. The investment to prepare it is 3–4 days of QS time. The disputes it prevents commonly represent SAR 5–15M in unresolved claims over the project lifecycle.

Managing Scope When Drawings Change

Scope documents written at award are valid as of the drawing revision at award. Design development and employer-instructed changes produce new revisions throughout construction. Three disciplines keep scope and drawings in sync:

Drawing supersession tracking. The GC's document control system records every drawing issue to every package. When a new revision changes something within a subcontractor's scope, the change must be assessed as a variation under FIDIC Clause 13.1 — instructed in writing, priced, and approved before or as the work proceeds.

Written variation instructions for scope changes. Verbal instructions to "just do it" are the single biggest driver of unrecovered variation costs in GCC construction. Under FIDIC Clause 13.1, a variation must be instructed in writing. Under Clause 20.2.1, notice must be given within 28 days of the event giving rise to the claim. A subcontractor who receives a verbal instruction to extend their scope and starts work without written confirmation has weakened their claim position significantly — and GCs who issue verbal instructions have created an unquantified obligation.

Change impact on interfaces. Design changes do not just affect the package they appear to change. An MEP coordination drawing revision might shift a duct run into a ceiling void that the dry-lining sub had assumed was clear. Every drawing revision should trigger a check against the interface matrix: does this change the boundary between any two packages?

Connecting Scope to Commercial Control

A well-written scope document does more than prevent disputes. It enables commercial control across the subcontract lifecycle:

Work confirmation alignment. Monthly work confirmations can reference the scope document to verify that what is being certified falls within the contracted scope. Items outside scope should be captured as variations — not buried in progress certificates where they are harder to isolate later.

Back-charge protection. When a subcontractor causes damage to another's work or fails to complete an interface item they are responsible for, the back-charge is grounded in a documented scope obligation. "This was your scope, you failed to complete it, here is the cost of completion" is a defensible position. "It felt like your scope" is not.

Final account discipline. A subcontractor claiming additional scope at final account is working against their own contract. A GC with a precise scope document, exclusions list, and interface matrix can close final accounts faster because the baseline is unambiguous. Contractors with structured scope documents close final accounts in 3–6 months post-completion. Contractors without them commonly carry 18–36 months of ongoing commercial claims.

Five Starting Steps for GCC Contractors

• Audit your current scope documents. Pull three recent subcontract scopes and count the phrases "including all related works," "as required," and "contractor to co-ordinate." Each one is a future dispute. Start there.
• Build a standard scope template for your five most common package types. Civil finishes, MEP mechanical, MEP electrical, fit-out, and facade typically cover 70% of dispute risk. A standard template with mandatory sections takes one week to build and pays back on the first package awarded.
• Implement the interface matrix at first package award, not last. The civil package is usually awarded first. That is when the interface matrix starts — even with one package defined. Each subsequent award adds rows. Waiting until trades start overlapping is too late.
• Require written variation instructions for every scope change. Brief your site and commercial team: verbal instructions do not exist commercially. Anything that changes a subcontractor's scope must be in writing before or at the time of instruction. This protects both parties under FIDIC Clause 13.1.
• Link scope documents to your work confirmation workflow. When certifying monthly progress, the confirming supervisor should reference the scope document. Scope creep is far easier to catch at certification stage than at final account.

The scope definition work is done before the subcontractor mobilises. It costs two to three days per major package for a thorough scope, exclusions list, and interface matrix contribution. On a SAR 300M project running 40 packages, that is roughly 80–120 days of QS time invested before concrete is poured. The return is captured in reduced variation disputes, faster final account settlement, and lower subcontractor payment claims over the following two years. For GCC contractors tendering NEOM, ROSHN, and Aramco work — where commercial process maturity is now a prequalification criterion — structured scope management is a differentiator at the bid stage before a single price is submitted.