All insights
Coordination3 min read

One project, many technical boundaries

The quality of delivery depends on how civil, structural, utility, and building decisions meet.

NIKA Pro-Ing

Editorial illustration of concrete structure and coordinated building services in an unfinished building
AI-generated editorial illustration

Construction brings different disciplines into the same physical space. Each may have its own drawings, sequence and responsibilities, but the finished result has to work as one. Coordination begins by making the points of connection visible and agreeing who will resolve them.

Start where one scope meets another

Interfaces are the places where one part of the project depends on another. A service route may need an opening in a structural element. An external drainage connection may depend on the building level. A finished ceiling may need room for equipment and access. Recording these dependencies creates a more useful discussion than reviewing each package as if it stood alone.

Make responsibility explicit

For each open issue, establish who provides the information, who reviews it and who is authorised to accept the solution. These roles may belong to different people. A short record of the issue, the responsible parties and the decision date helps prevent a question from being passed between teams without resolution. It also makes the effect on the programme easier to discuss.

Coordinate the sequence as well as the drawing

A solution can fit on a drawing and still be difficult to deliver in the planned order. Teams need to consider access, temporary conditions, inspections and the work that will become hidden later. Reviewing the sequence together helps identify decisions that cannot wait until installation. Changes should return to the relevant designers and responsible parties rather than being improvised in isolation on site.

Keep one clear record of the decision

Once an issue is resolved, the people doing the work need the current information. Record what changed, which drawings or instructions are affected and what remains open. A meeting is useful when it produces decisions that others can follow. Consistent revision control and a concise action list help turn coordination from a recurring conversation into a practical part of delivery.

Questions to take into the next conversation

  • Where does this package depend on another team or discipline?
  • Who must review and accept the proposed solution?
  • Has the agreed decision reached everyone affected by it?

Further reading

RIBA — Plan of Work
A technical question

Start with the problem in front of you.

If the question is connected to a live construction or infrastructure requirement, bring us the context and we can discuss the next practical step.

Discuss a project