The Subcontractor Paradox
Outside-plant (OSP) subcontractors are the backbone of any national FTTH rollout — they do the trenching, the duct installation, the cable pulling, and the splicing that physically connects homes to the network. They are also the biggest source of quality risk, schedule risk, and cost overrun on the programme. The paradox is simple: you cannot do the work without them, and you cannot fully control the work when you rely on them.
I have managed OSP subcontractor relationships at every scale — from single-city deployments with two or three local contractors to national programmes with dozens of subcontractors across multiple regions. The patterns of failure are remarkably consistent, and they all stem from the same root cause: a mismatch between the programme's expectations and the subcontractor's incentives.
What Breaks First: Quality
The first thing that breaks at scale is quality. A subcontractor who delivers excellent work on a single site with ten technicians will struggle to maintain that quality when they are asked to deliver across twenty sites with two hundred technicians. The reason is not that the subcontractor does not care about quality — it is that their quality control systems do not scale.
On a single site, the subcontractor's project manager can personally inspect every trench, every splice, every duct installation. At twenty sites, the project manager is spread too thin. The foremen who replace them at site level may not have the same standards, or the same understanding of what "good" looks like. Without a standardized quality framework — clear acceptance criteria, mandatory inspections, photographic evidence — quality degrades predictably as volume increases.
The solution is not to inspect more — it is to standardize more. When every trench has the same depth specification, every splice has the same test requirement, and every duct installation has the same acceptance checklist, quality becomes a function of process rather than individual skill. The subcontractor's foremen do not need to be experts; they need to follow the process. And the programme team can audit the process rather than inspecting every meter of trench.
What Breaks Second: Schedule
The second failure mode is schedule degradation. Subcontractors are optimistic by nature — they want to win the work, so they quote aggressive timelines. When reality sets in — weather delays, permit delays, material shortages, technician turnover — the timeline slips. At small scale, the slip is manageable: you negotiate, you adjust, you absorb. At large scale, the slip cascades.
The cascade happens because subcontractors are often interdependent. Contractor A does the trenching, Contractor B does the cable pulling, Contractor C does the splicing. If Contractor A slips by a week, Contractors B and C are both delayed — but they will still charge for the mobilization time they spent waiting. The programme absorbs not just the schedule slip but the cost of idle resources across multiple subcontractors.
The control mechanism that prevents this cascade is a shared master schedule with contractual handover points. Contractor A does not simply "finish trenching" — they finish trenching to a defined acceptance standard, at which point the work package is formally handed over to Contractor B. The handover is a milestone with a date, an acceptance sign-off, and a financial implication. When the handover is late, the schedule impact is visible immediately, and the commercial conversation about who pays for the delay can happen based on facts rather than opinions.
What Breaks Third: Commercial Discipline
The third failure mode is commercial discipline breakdown. Subcontractor contracts are typically based on unit rates — price per meter of trench, price per splice, price per meter of cable. This seems straightforward, but at scale, the measurement of quantities becomes a battleground. Did the subcontractor trench 500 meters or 520? Were the 20 extra meters authorized variation or scope creep? Were the splices that failed testing included in the count or excluded?
The solution is a measurement system that is transparent and agreed upon by both parties. In the STC programme, we implemented a system where every work package had a digital measurement — GPS-tracked trench lengths, splice test records with unique identifiers, cable pull logs with start and end points. The subcontractor and the programme team saw the same numbers, at the same time, from the same system. Disputes about quantities dropped dramatically — not because the system was perfect, but because both parties trusted it.
Contract Structures That Work
The contract structure itself is a critical control mechanism. I have worked with three basic models, and each has its place.
The first is the unit-rate contract — the subcontractor is paid a fixed rate per unit of work completed. This is the most common model for OSP work, and it works well when the scope is well-defined and the quantities can be measured accurately. The risk is that the subcontractor is incentivized to maximize quantity, not quality — more meters of trench means more money, even if some of those meters are poorly executed. The mitigation is a quality holdback: a percentage of payment is retained until the quality inspection passes.
The second is the lump-sum contract — the subcontractor is paid a fixed amount for completing a defined scope of work. This shifts the risk of quantity variation to the subcontractor, which can be beneficial when the scope is uncertain. The risk is that the subcontractor will cut corners to protect their margin if the scope turns out to be larger than expected. The mitigation is the same quality framework — acceptance criteria must be met regardless of the subcontractor's cost situation.
The third is the target-cost contract — the subcontractor is reimbursed for actual costs plus a fee, with a shared savings mechanism if the work is completed below target. This is the most collaborative model, and it works well with subcontractors you have a long-term relationship with. The risk is that it requires a high level of trust and transparency — the subcontractor must open their books, and the programme team must be willing to share risk.
The Performance Management Loop
Regardless of contract type, every subcontractor needs a performance management loop. This is not an annual review — it is a monthly cycle of measurement, feedback, and action. The monthly performance report covers four dimensions: schedule adherence (planned versus actual), quality performance (pass rates, defect counts), commercial discipline (quantity disputes, change order volume), and safety record.
The performance report is shared with the subcontractor — not as a weapon, but as a tool for improvement. When a subcontractor sees that their quality pass rate is 85% while the programme average is 95%, that is actionable information. When they see that their schedule variance is the worst in the programme, they know they need to change something. The conversation is not "you are performing badly" — it is "here is the data, here is where you stand, what support do you need to improve?"
When to Change Subcontractors
One of the hardest decisions in subcontractor management is knowing when to change a subcontractor. The default response to underperformance is often to give the subcontractor another chance — and sometimes that is the right call, especially if the underperformance is driven by factors outside their control. But when the same subcontractor underperforms month after month, despite support and clear feedback, the decision to replace them must be made.
The cost of changing a subcontractor is high — mobilization of a new team, knowledge transfer, schedule disruption. But the cost of keeping an underperforming subcontractor is often higher — the drag on the programme's overall performance, the impact on other subcontractors who are performing well, and the message it sends about the programme's standards. The decision should be data-driven, transparent, and timely. When the performance data justifies it, the change should be made cleanly and quickly, with a clear handover plan that minimizes disruption to the programme.