On major construction projects, much of the physical work may be delivered through subcontractors. Yet the Employer normally looks to the main Contractor for the result.
That creates the central subcontract-management problem:
the Contractor must translate its upstream obligations into workable downstream obligations without creating gaps, contradictions or procedures that the supply chain cannot practically perform.
A “back-to-back” sentence alone does not achieve that.
Effective subcontract management begins before award and continues through final account, defects and release of security.
1. Start with an upstream-to-downstream obligation matrix
Before drafting or negotiating the subcontract, identify main-contract obligations relevant to the package.
Typical areas include:
- scope and performance requirements;
- design responsibility;
- programme and milestones;
- access;
- permits;
- health and safety;
- quality;
- testing and commissioning;
- reporting;
- notices;
- variations;
- records;
- insurance;
- intellectual property;
- confidentiality;
- claims cooperation;
- defects;
- handover; and
- dispute support.
For each main-contract obligation, decide whether it should be:
- fully flowed down;
- adapted to the subcontract scope;
- retained by the Contractor;
- shared through an interface; or
- expressly excluded.
This is more reliable than incorporating the entire main contract by a general reference.
2. Make the scope boundary measurable
Subcontract disputes often begin at interfaces, not in headline scope descriptions.
Define:
- inclusions;
- exclusions;
- quantities where applicable;
- design deliverables;
- temporary works;
- materials supplied by each party;
- free-issue equipment;
- unloading/storage;
- testing;
- commissioning;
- utilities;
- access;
- lifting;
- scaffolding;
- survey;
- permits;
- protection of completed work;
- as-builts and O&M manuals; and
- demobilisation.
Use drawings, responsibility matrices and interface schedules where words alone are insufficient.
The test is practical: if two adjacent subcontractors read their packages separately, is there a clear owner for every interface?
3. Align document hierarchy
A subcontract often contains many documents:
- agreement;
- special conditions;
- general conditions;
- scope;
- specifications;
- drawings;
- price schedule;
- programme;
- main-contract extracts;
- clarifications;
- method/interface documents.
Establish priority.
Otherwise a detailed scope exclusion can conflict with a general flow-down obligation, leaving the parties to argue which controls.
4. Flow down time obligations intelligently
The Contractor needs enough time to manage the subcontractor’s output before its own upstream deadline.
Build realistic allowance for:
- review;
- correction;
- integration;
- testing;
- handover; and
- Contractor submission to the Employer/Engineer.
Do not simply copy the main contract’s deadline into the subcontract. If the Contractor has 28 days to notify upstream and gives the subcontractor the same 28 days downstream, there is no management buffer.
FIDIC’s Golden Principles state that contractual time periods should be of reasonable duration. The same commercial logic applies in supply-chain design: downstream periods must be workable and should protect the Contractor’s upstream position.
5. Make the programme contractual and package-specific
A subcontract programme should show more than a final completion date.
Control:
- commencement;
- access dates;
- design/submittal dates;
- procurement;
- interfaces;
- key milestones;
- testing;
- sectional/work-package completion;
- handover;
- float treatment where relevant;
- update frequency;
- recovery requirements; and
- required schedule format/data.
The main Contractor should be able to integrate the subcontractor’s programme into the master schedule and identify critical interface slippage early.
6. Create a two-way notice system
The subcontractor must notify the Contractor early enough for the Contractor to protect its own main-contract rights.
The subcontract should define:
- notice triggers;
- recipient;
- form;
- timing;
- initial content;
- continuing updates;
- detailed particulars; and
- consequences of non-compliance.
But notice obligations should also work in the other direction. The Contractor may need to notify the subcontractor of:
- upstream instructions;
- access changes;
- acceleration;
- non-compliance;
- delay;
- backcharges;
- defects; and
- Employer allegations.
Maintain linked upstream and downstream notice registers so the same event can be traced across both contracts.
7. Control change before work is buried
Subcontract changes can quickly become difficult to value because the work is field-driven and records are distributed.
A robust process should define:
- who can instruct a change;
- when the subcontractor must notify;
- quotation format;
- valuation rules;
- programme-impact submission;
- authority to proceed;
- cost-record requirements;
- interim valuation if price is not agreed; and
- final Change Order/amendment.
Site staff should know that technical authority and commercial authority are not necessarily the same.
8. Align payment with measurable achievement
A payment mechanism should be auditable.
Define:
- valuation date;
- required supporting records;
- measurement rules or milestone evidence;
- certification period;
- invoice requirements;
- retention;
- advance recovery;
- materials on/off site;
- set-off;
- taxes;
- final account; and
- release conditions.
Avoid payment milestones that are not objectively measurable or that depend on an upstream event the subcontractor cannot observe.
Where upstream certification affects downstream payment, the risk allocation should be expressly drafted and legally reviewed for the relevant jurisdiction.
9. Control securities and insurance as live obligations
At award, verify:
- performance security;
- advance-payment security;
- parent-company guarantee where required;
- insurance certificates;
- limits;
- deductibles;
- policy period;
- insured parties;
- professional indemnity for design; and
- expiry/renewal dates.
Then operate a tickler calendar.
A security that expired unnoticed is not a paperwork issue; it is lost risk protection.
10. Manage design and interface responsibility
For design subcontracts, define:
- design criteria;
- applicable standards;
- design life;
- review procedure;
- status codes;
- reliance on Contractor/Employer information;
- BIM/model responsibilities;
- interfaces;
- checking;
- professional indemnity;
- intellectual property;
- as-built design; and
- effect of review/approval.
A Contractor review should not accidentally transfer design responsibility unless the contract intentionally says so.
11. Require records before a claim exists
The subcontractor’s records may later be needed for a main-contract claim.
Specify and monitor:
- daily reports;
- labour;
- equipment;
- quantities;
- progress photos;
- programme updates;
- procurement status;
- inspection/testing;
- instructions;
- delay events;
- cost records; and
- change records.
The Contractor should not first request detailed evidence two years later when preparing an upstream claim.
12. Link subcontractor claims to the main contract—but do not confuse them
A downstream event may also form part of an upstream claim, but the two entitlements are not automatically identical.
Test separately:
- subcontract entitlement;
- main-contract entitlement;
- notice compliance under each;
- causation;
- programme effect;
- recoverable cost; and
- contractual risk allocation.
Where the subcontractor’s cooperation is needed for an upstream claim, define obligations to provide records, personnel and technical support.
13. Manage performance through a governance rhythm
A strong subcontract is not self-administering.
Hold structured reviews covering:
- safety;
- quality;
- design;
- programme;
- procurement;
- access/interfaces;
- notices;
- changes;
- payment;
- resources;
- risk;
- open actions; and
- forecast completion.
Use one action register with owners and dates.
Commercial issues should be visible before they become positions in a formal claim.
14. Close-out is a process, not a final payment
Begin close-out before physical completion.
Track:
- punch list;
- tests;
- as-built drawings;
- O&M manuals;
- training;
- spare parts;
- warranties;
- defects;
- final quantities;
- change closure;
- final account;
- release/waiver documents where applicable;
- return/reduction of security;
- retention release;
- insurance tail;
- demobilisation; and
- document archive.
Do not release leverage before required deliverables are complete.
FIDIC publishes dedicated Conditions of Subcontract for Construction (2011) and for Plant and Design (2019), reflecting the fact that subcontracting needs its own coherent contract structure rather than an informal copy of the main contract.
A lifecycle subcontract control model
A practical model has five gates:
Gate 1 – Pre-award: scope, interfaces, flow-down, due diligence, price, programme.
Gate 2 – Mobilisation: securities, insurance, programme, reporting, document systems, responsibilities.
Gate 3 – Performance: progress, design, quality, notices, change, payment, records.
Gate 4 – Claims/final account: entitlement, evidence, upstream/downstream alignment, settlement.
Gate 5 – Close-out: handover, defects, final documents, release of retention/security, archive.
The central principle
Subcontract management is not mainly about transferring risk to another company.
It is about ensuring that the work package, commercial mechanism and project controls remain aligned with the main contract from award to close-out.
When that alignment is designed early, the Contractor gains something more valuable than a strong set of remedies: fewer interface gaps, earlier warnings, cleaner records and a supply chain that is easier to manage.
REFERENCES & FURTHER READING