Working with structural engineers — a guide for contractors

Most non-trivial UK construction work involves a contractor and a structural engineer working alongside each other. When they coordinate well, surveying and NDT work flows smoothly into engineering analysis and back into construction. When they coordinate badly, surveys are commissioned to the wrong specification, engineering decisions are made on inadequate data, and re-work appears late in the programme. Here is how to make the coordination work.

What the engineer is trying to do

A structural engineer’s job on an existing-fabric project is, in summary:

• Build an analytical model of the structure.
• Calibrate that model against measured data.
• Run analysis under design loads.
• Produce a defensible assessment, design, or strengthening scheme.

For each of these steps, they need data. Some of it comes from drawings, some from inspection, and most of the rest from surveying and NDT. A defensible engineering output rests on data that is appropriate, sufficient, and well-organised.

What you, as contractor, are trying to do

For a contractor on an existing-fabric project, the priorities are usually:

• Deliver the construction works on programme and budget.
• Manage risk on tight commercial terms.
• Avoid surprises during construction.
• Produce defensible records of the work for handover.

Many of these depend on the same data the engineer needs. The two roles align more often than they conflict — but the alignment has to be intentional.

Where coordination breaks down

Common failure modes:

The contractor commissions the survey alone. The brief reflects the contractor’s needs (pre-drill clearance, basic mapping) without the engineering inputs. The data does not feed the engineer’s analysis cleanly.

The engineer specifies the survey in isolation. The brief reflects the engineering needs but ignores access constraints, site programme, or commercial reality. The surveyor cannot deliver to the brief.

The two parties never speak before the survey. The surveyor does what they can with the brief they are given. The deliverable disappoints both parties.

Sample density is wrong for the question. The contractor wanted broad coverage; the engineer wanted statistical confidence on critical elements. The compromise satisfies neither.

Coordinate systems mismatch. The CAD output cannot be cleanly overlaid on the engineer’s analytical model.

These are all avoidable with a short coordination conversation before the survey is commissioned.

What that conversation should cover

A useful pre-survey coordination conversation covers:

• The engineering brief: what assessment or design is the data feeding?
• The data the engineer needs: geometry, reinforcement, cover, strength, durability?
• The sample density: enough for statistical confidence on critical elements.
• The coordinate system: what does the engineer’s model use?
• The deliverable formats: what does the engineer ingest?
• The site programme: what access is available, when?
• The commercial structure: who is paying for what, and how is variation handled?

Half an hour with the contractor, the engineer, and the surveyor on the same call usually settles all of these. The cost is small; the value is significant.

Roles in the engagement

A clean engagement has clear roles:

• The contractor is the commercial party, runs the site, and manages access.
• The engineer specifies the data needed and interprets the data into engineering output.
• The surveyor captures the data, in line with the agreed brief and method.

Confusion of roles — particularly the surveyor being asked to make engineering judgements they are not qualified to make — produces poor outcomes. A surveyor who is asked “is this safe to drill through” should mark up the reflectors and let the engineer make the call. A surveyor who is asked “is this slab strong enough” should produce calibrated strength data and let the engineer make the call.

What the engineer needs to know about the survey

A useful contractor-side discipline is to share with the engineer:

• The surveyor’s qualifications and method.
• The calibration record.
• Any limitations the surveyor flagged.
• The on-site findings as the surveyor saw them.

Engineers who only see the formal deliverable miss the colour around it — the surveyor’s intuition about anomalies, the conversation about limitations, the small details that don’t make it into the report. A short briefing call after the survey, with the surveyor and the engineer, captures these.

Where surveys feed engineering most directly

The most common touchpoints:

Reinforcement layout for capacity calculation. Engineers cannot calculate capacity without reinforcement detail. GPR plus ferro provides it.

Cover for durability assessment. The cover survey informs the engineer’s durability calculation directly.

In-situ strength for capacity calculation. Calibrated NDT and core testing provide the strength input.

Geometry for analytical model. LiDAR provides the geometry the analytical model is built on.

Defect characterisation for residual capacity. Distress mapping and quantification feeds the engineer’s residual capacity assessment.

For each, the engineer should be involved in the brief — not just the receiver of the deliverable.

Practical advice

For a contractor commissioning surveying or NDT in coordination with a structural engineer:

1. Get the engineer in the room (or on the call) before the survey is briefed.
2. Lock the brief between contractor, engineer, and surveyor.
3. Insist on integrated deliverables.
4. Brief the engineer on the survey findings as the surveyor saw them.
5. Plan follow-up as a possible part of the campaign — surveys sometimes reveal more questions.

The goal is one coordinated dataset that supports both the engineer’s analysis and the contractor’s construction. Done well, the engagement is calm, predictable, and produces defensible work. Done badly, it produces re-work for everyone.