Managing 100+ Subcontracts Without Losing Control - Blog
Managing 100+ Subcontracts Without Losing Control

April 15, 2026

Managing 100+ Subcontracts Without Losing Control

Ahmed ElazabAhmed Elazab

A procurement director at a SAR 800M mixed-use development in Riyadh recently described managing subcontracts like "running 120 simultaneous projects that nobody can see into." He had the contracts. He had the payment schedules. What he didn't have was any visibility into what was happening between signing and final account settlement — and by the time problems surfaced, they were already disputes.

If your business is running 50, 80, or 120+ active subcontracts across multiple projects, you already know that the tools most GCs use — spreadsheets, isolated accounting entries, email chains — weren't designed for this volume. The breakdown isn't a people problem. It's a systems problem.

Where Control Breaks Down at Scale

Subcontract management looks manageable with 10 or 15 trades. Each PM knows their subs, tracks progress manually, and handles disputes one at a time. Scale that to 100+ subcontracts across a portfolio and the same approach produces three predictable failures.

Quantity Drift Goes Undetected

Subcontractors complete work. Site engineers approve quantities on paper. Those quantities move slowly — or inconsistently — into the billing system. By the time accounts reconciles the actual work done against what was approved, the gap between confirmed quantities and claimed quantities can be weeks old. In high-volume environments, that drift accumulates into disputes worth SAR 500K–2M per project.

Retention and Holdback Visibility Collapses

A standard GCC subcontract withholds 5% retention, often split between practical completion and defects liability release. That's easy to track for one sub. For 120, each with different contract values, different milestone dates, and potentially different retention percentages, the only way to keep it accurate is automation. Without it, GCs either over-retain (damaging relationships) or under-retain (losing leverage).

Payment Certification Becomes a Bottleneck

The payment certification process — work confirmation → measurement → certification → payment — has anywhere from 3 to 7 approval steps depending on the sub's risk tier. When those steps live in email, approvals stall. Subs start calling. PMs start chasing. Accounts start issuing payments without complete certification just to clear the backlog. That's where over-billing happens.

What You Actually Need to Track Per Subcontract

A structured subcontract management system tracks these dimensions continuously — not just at payment certification time:

  • Contract value and approved variations — The live contract sum including all approved change orders, so every stakeholder sees the same number.
  • Cumulative certified value — What has been formally certified to date, against which future claims are measured.
  • Uncertified work in progress — Quantities approved at site level but not yet formally certified. This is the figure that finance and procurement most often disagree on.
  • Retention balance — Withheld to date, with automated tracking of release triggers tied to practical completion and defects certificate milestones.
  • Exposure to uncertified claims — Subcontractor claims submitted but not assessed. These are contingent liabilities your cost reports should flag.
  • Performance flags — HSE incidents, RFI response times, NCRs linked to this sub's scope. Financial and operational data in one view.

Most accounting systems give you the first two. Structured subcontract management gives you all six — and flags when any of them moves outside tolerance.

Connecting Contracts to Confirmations to Payments

The fundamental design principle for managing subcontracts at scale is: no payment without a confirmation chain. Here is what that looks like in practice:

  1. Work order issued against the subcontract, scoped to a WBS activity and BOQ line item.
  2. Site supervisor confirms quantities digitally at the work face — not via email, not on paper passed to the office on Friday afternoon.
  3. PM or quantity surveyor reviews the confirmation against the approved scope, flags any discrepancy before it goes to billing.
  4. Payment certification generated automatically from confirmed quantities, applying the correct retention percentage and any set-off amounts.
  5. Accounts issues payment against the certified amount — no manual re-entry, no reconciliation step.

This chain makes the entire billing history auditable. For FIDIC-based contracts, that audit trail is the difference between a resolved dispute and an arbitration claim.

Early Warning Systems That Actually Work

The most valuable feature in high-volume subcontract management isn't reporting — it's the alert before the report is needed. Configurable thresholds can flag:

  • Subcontract approaching contract ceiling: At 85% of the approved contract sum with no variation approved, the system alerts the commercial team — not after the sub overruns.
  • Certification overdue: If a work confirmation has been sitting unapproved for more than 7 days, escalate to the PM and commercial director.
  • Retention release triggered: When a practical completion milestone is reached, automatic notification to accounts that retention is eligible for partial release — instead of the sub having to chase it.
  • Uncertified claims aging: Claims older than 30 days without a response are flagged to avoid FIDIC notice lapses and protect the GC's contractual position.

These alerts don't replace judgment — they replace the administrative burden of scanning 120 lines of a spreadsheet every week looking for the one that's about to go wrong.

Portfolio-Level Visibility Without Losing Project Detail

For a GC running SAR 1.2B across 6 active projects, the commercial director needs two views simultaneously: the portfolio (where are we exposed?) and the project (what specifically is driving that exposure?).

A structured system surfaces both without requiring someone to compile a weekly report. The portfolio dashboard shows total subcontract value, cumulative certified across all projects, retention held, and outstanding claims. Drill into any project and you see the same data at the subcontract level — with the ability to pull the original contract, the confirmation history, and the variation log in the same click.

That's the difference between managing subcontracts and having visibility over them. One is administrative effort. The other is commercial control.

Where to Start If You're Managing Volume Today

If you're at scale but haven't yet structured the workflow, these are the highest-leverage first steps:

  • Standardize your subcontract tiers. Not all subs need the same workflow depth. A specialist MEP subcontractor with a SAR 15M scope needs different oversight than a labor-only cleaning contract. Match the process to the risk.
  • Close the confirmation gap first. The biggest source of quantity disputes is the lag between physical completion and recorded confirmation. If your site supervisors are still on paper, that's the first thing to fix — not the reporting layer.
  • Get retention dates into the system. Map every subcontract's retention milestones into a structured register. This alone prevents the most common source of subcontractor friction in GCC construction.
  • Connect HSE to commercial. If a subcontractor has three NCRs in a month, that should trigger a review of their payment certification. Performance data and commercial data belong together.

The Bottom Line

At 100+ subcontracts, the challenge isn't managing any single subcontract — it's maintaining visibility and control across all of them simultaneously. That requires structure, not harder work. The GCs operating at this scale without disputes consuming their commercial teams have one thing in common: every subcontract moves through the same consistent workflow, and every deviation gets flagged before it becomes a claim.

The data exists on every project. The question is whether it's connected and accessible — or scattered across email threads, paper confirmations, and outdated spreadsheet tabs that nobody fully trusts.

Did you enjoy reading this blog? Share it

Ready to find out more?