How to manage subcontractor scanning on a large project

On a large, multi-phase project, scanning is almost always subcontracted. It is a specialist activity, it is intermittent, and it does not justify an in-house resource. Subcontracting it is the right decision. The problem is that a subcontracted, intermittent, specialist task is also one of the easiest things on a project to manage badly — under-scoped at procurement, squeezed under cost pressure, and quietly left with gaps that nobody notices until intrusive work hits something it should not have.

This post sets out how a principal contractor or engineer should manage subcontracted scanning so the coverage is complete and consistent across a long programme.

Why scanning is vulnerable to de-scoping

Scanning is vulnerable for structural reasons, not because anyone decides it is unimportant. Its cost is visible and its benefit is invisible — a successful scan produces a quiet day, while the cost of skipping one only appears later, as someone else’s incident. On a phased project the works are split into packages, and a task that runs across all of them can fall between every package, owned by none.

When budgets are reviewed, a line that has “produced nothing” is an obvious candidate for trimming. The trim is rarely a clear decision to stop scanning; it is a gradual narrowing — fewer attendances, smaller areas, scanning only where someone specifically asks. The coverage erodes without anyone choosing it.

Define the scope as deliverables, not days

The first control is procurement. A scanning subcontract written as a number of days is impossible to manage, because nobody can later tell whether the right things were scanned. A subcontract written around deliverables can be managed.

A defined scope should answer: which elements and areas are to be scanned, before which activities, to what level of detail, and producing what record. Tie scanning to the activities it protects — every drilling, coring or cutting operation, every excavation in a given zone — rather than to a fixed quantity of attendances. When the scope is expressed as “scanning will precede these works and produce these records”, a missing scan becomes a visible non-conformance rather than an invisible saving.

Give scanning a single owner across the whole programme

On a phased project, scanning needs one owner for the duration, not a different owner per phase. That owner — typically the principal contractor’s design or temporary works manager — is responsible for the scanning scope across every package, for engaging the subcontractor consistently, and for checking that coverage does not lapse at the joins between phases.

The phase boundaries are where gaps appear. A package finishes, a new one starts, the new team assumes scanning was handled, and a stretch of work proceeds with no scan. A single owner with a programme-wide view is the person who catches that. Without one, scanning is everyone’s assumption and no one’s responsibility.

Tie scanning to the permit system

The most reliable control is procedural: make it impossible to start intrusive work without a scan. A permit-to-drill or permit-to-excavate system that will not be issued until a current scan record exists turns scanning from an optional good practice into a gateway.

This works because it does not depend on memory or goodwill. The site team cannot proceed without the permit, and the permit cannot be issued without the record. It also produces an audit trail — each permit references a scan, so coverage can be checked at any point by comparing permits issued against scans recorded. A mismatch is then an immediate, visible question rather than a buried gap.

Manage consistency, not just presence

Across a long programme it is not enough that scanning happened; it must have happened consistently. Different surveyors, different equipment and different reporting formats produce records that are hard to compare and hard to integrate. On a project running over many months, that inconsistency accumulates.

Manage it by setting expectations at procurement and holding to them:

• A consistent reporting format and deliverable for every phase.
• Records referenced to the project coordinate system so they overlay the project drawings.
• A known location in the document control system for scan records.
• Continuity of personnel where practical, so the subcontractor’s team knows the structure.

Consistency is what allows the body of scan data to function as a coherent project record rather than a stack of unrelated reports.

Watch the cost-pressure moments

Scanning is most at risk at predictable points: value-engineering exercises, mid-project budget reviews, and the procurement of later phases against an overspend in earlier ones. The owner of the scanning scope should be alert at these moments and able to state plainly what is being given up if scanning is reduced.

The argument is not that scanning must never change. It is that any reduction should be a conscious, recorded decision made by someone who understands the exposure — not a quiet trim made by someone looking only at a cost line. A decision to narrow scanning, taken with the risk understood and written down, is legitimate. A gap that nobody chose is not.

The practical position

Subcontracting scanning is correct; managing it loosely is the mistake. Scope it as deliverables tied to the activities it protects, give it one owner for the whole programme, gate intrusive work behind a permit that requires a scan record, and insist on consistency of format and reference throughout. Manage it that way and a long, phased project ends with complete, comparable coverage — and no quiet gaps waiting for a drill to find them.