Gokbilge Engineering

Tender Practical Guides

Subcontract scope, interfaces and exclusions: build the matrix before award

A practical method for removing scope gaps between subcontractors, suppliers and the main contractor before they become variations and site delays.

Engineering analyst reviewing technical reports and schematics at a desk with a laptop showing technical charts.

The lowest subcontract price is meaningless if important interfaces are missing. Scope should be decomposed into physical work, design responsibility, procurement, temporary works, access, lifting, supports, embedded items, power and water, testing, documentation, spares, training, protection and reinstatement so every boundary has an accountable party.

A Scope–Interface–Exclusion Matrix should combine tender scope, subcontract quotation, clarifications and negotiated changes in one controlled baseline. Each exclusion must be classified as accepted, transferred to another package, retained by the main contractor or unresolved. Unresolved exclusions should never disappear into meeting minutes without a named owner and cost/programme consequence.

Particular attention is needed at discipline boundaries: civil-to-MEP penetrations, structural supports, equipment foundations, cable containment, earthing, drainage, fire stopping, controls integration and testing responsibilities frequently sit between packages. These interfaces should be priced and scheduled before award, not negotiated on site after both parties have mobilised.

The resulting matrix should feed the subcontract BOQ, responsibility schedule, programme and variation procedure. If the commercial documents and technical interface matrix do not describe the same package, the contract is not ready for signature.

Related services

Apply the guidance to a live project

These Gokbilge capabilities connect the article's subject to practical tender, commercial, engineering and project-delivery controls.