How scanning reduces programme risk
Undetected services, post-tension cables, or voids can stop a programme in its tracks. Here is how integrating scanning early reduces the risk of costly delays and scope changes.
Programme risk is the risk that the works take longer than planned. Most contractors manage it through float, sequencing and resourcing. What is less consistently managed is the programme risk that comes from not knowing what is inside a structure or beneath the ground. A live service found mid-task, an unexpected void, or a post-tensioned slab that nobody flagged can stop an activity and unravel the sequence around it. Scanning is one of the few measures that reduces this risk before it has a chance to materialise.
This post looks at how scanning, used at the right point, takes uncertainty out of the programme.
Where concealed conditions threaten the programme
Concealed conditions cause programme damage in a predictable way. A task starts on the assumption that the structure or ground is as the drawings suggest. The assumption turns out to be wrong. Work stops while the team investigates, redesigns or reroutes. The activity that stopped was probably on or near the critical path, because intrusive and groundworks tasks usually are. The delay then propagates: follow-on trades cannot start, plant sits idle, and the recovery effort competes for the same resources as the rest of the job.
The cost of the surprise itself is rarely the largest figure. The disruption to everything sequenced behind it is. That is why concealed conditions are a programme problem, not just a cost problem.
Scanning converts assumptions into known facts
Scanning replaces an assumption with a recorded fact before the assumption is tested by a drill or an excavator. Ground-penetrating radar and related techniques can locate reinforcement, post-tensioned tendons, conduits, voids and buried services, and large-scale GPR can cover significant ground areas to map services and subsurface features ahead of groundworks.
The programme value lies in the timing. A condition discovered by a scan is discovered while there is still time to design around it, reroute the work or adjust the sequence calmly. The same condition discovered by an incident is discovered with the clock running and the team under pressure. The information is the same; the programme consequence is entirely different.
Designing the surprise out before it reaches site
When scanning is carried out early enough, its findings feed back into design and planning rather than into a recovery effort. A reinforcement survey that shows congested steel where a new opening was planned lets the engineer move the opening on paper. A utility map that reveals a service crossing a proposed excavation lets the works be resequenced or the route changed before any plant is mobilised.
This is the difference between a scan used as a planning input and a scan used only as a last check. Used as a planning input, it removes the surprise from the programme entirely. Used only at the last minute, it can still prevent an incident but offers far less room to absorb whatever it finds.
Reducing the variations and claims that follow
Concealed conditions are a common source of variations and disruption claims. An unforeseen ground or structural condition typically triggers an instruction, a change in scope and a discussion about time and cost. Each of those is a programme event in its own right, consuming management attention and creating uncertainty about the completion date.
Scanning narrows the scope for this. A condition that has been surveyed and recorded is no longer unforeseen. It can be priced and programmed as part of the planned works rather than handled as a mid-job change. This matters most on phased or large-scale projects, where a single late discovery in an early phase can cast doubt over the assumptions made for every phase that follows.
Where to place scanning in the programme
The programme benefit depends heavily on timing. As a general approach:
- Before design is fixed, where new work depends on existing structure or where excavation is planned across uncertain ground — so findings can shape the design.
- Before each intrusive activity, as a routine, programmed task — so the activity is released with confidence rather than checked under pressure.
Scanning slotted in at these points produces information when it can still influence decisions. Scanning left until the day of the work can only confirm or alarm; it cannot reshape a plan that has already been committed.
A small, known task against a large, unknown one
The honest trade-off is that scanning adds a defined, modest activity to the programme. Against that, it removes an undefined and potentially large one. A scan takes a known amount of time and produces a known output. An undetected post-tensioned tendon, a struck service or an unexpected void produces a stoppage of uncertain length and a recovery effort of uncertain cost.
Programme management is largely the management of uncertainty. Scanning is one of the few tools that converts a genuine unknown into a planned, bounded task — and a planned task is one a programme can absorb.
The practical position
Treat scanning as a programme control, not only a safety measure. Identify the activities that depend on concealed conditions, place scanning early enough that its findings can still influence the plan, and use the results to design and sequence with confidence. Do that, and the structure stops being a source of programme surprises and becomes another part of the project that is known, recorded and planned for.