Site acquisition is never the bottleneck you think it is. Lessons from the field on sequencing, vendor SLAs and rollout velocity.
Ask anyone who has not run a large telecom rollout what the hardest part is and they will say site acquisition. Ask anyone who has, and they will tell you the truth: acquisition is predictable. What kills timelines is everything between acquisition and integration - the unglamorous middle where surveys, approvals, materials and manpower have to arrive at the same place in the same week.
Sequence beats speed
On a recent 400-plus site programme, the single biggest gain came not from working faster but from re-sequencing the work. Clustering sites by district instead of by client priority cut crew travel time dramatically. Batching statutory approvals by jurisdiction meant one liaison visit covered fifteen sites instead of one. Velocity is a routing problem before it is an effort problem.
Geo-tagged verification changes behaviour
Our field app requires geo-tagged, time-stamped photographs at every stage - survey, civil work, installation, integration. The original purpose was evidence for the client's quality team. The unexpected benefit was behavioural: when every crew knows their work is verified in real time against location and timestamp, first-time-right rates climb and disputes about who did what, where and when simply disappear.
The quality-control loop matters just as much. Every uploaded report is reviewed by a dedicated QC team before release; execution faults go straight back to the responsible field resource with the photographic evidence attached. Rework gets assigned in hours, not at the month-end review.
Vendor SLAs need teeth and dashboards
An SLA that lives in a contract annexure disciplines no one. An SLA that lives on a shared dashboard - sites committed, sites delivered, ageing of every open item, penalty accrual to date - disciplines everyone, including us. Clients on our programmes see the same dashboard we do. That transparency is uncomfortable precisely once, and then it becomes the reason the programme stays on schedule.
Rollouts are won in the operating rhythm: the daily exception call, the weekly cluster review, the ruthless focus on the ten oldest open items. Get the rhythm right and 400 sites is arithmetic. Get it wrong and 40 sites is chaos.
Written by
Paramjeet Singh
Writing field notes on finance, tax, process and infrastructure - from the work, not about it.
