Construct IQ

Construction Coordination: How to Keep Trades, Office and Field in Step

By Kush Agarwal, President and CEO, YelloSKYE. Published 2026-10-23.

Executive Summary

• The Question: How do you coordinate trades, the site team and the office so that one late or out-of-sequence activity does not delay everything behind it?
• The Answer: Treat coordination as a weekly cycle: look ahead and clear constraints, hand areas between trades on recorded evidence, run meetings from facts rather than opinions, and check on site that decisions were carried out. Each step depends on everyone seeing the same current picture of the site.
• The YelloSKYE Angle: Construct IQ records each work zone by drone, 360° walk, fixed camera or laser scan, and DEX puts every capture on one dated record that trades, site managers and the office open together.

Construction coordination is the work of getting the right trade into the right area at the right time, with the drawings, materials and access it needs, and without undoing or blocking the work of anyone else. It also means keeping decisions taken in the office tied to what is actually on site. When coordination works, trades follow each other through a building in a steady rhythm. When it fails, crews stand idle, areas are handed over half-finished and finished work is opened up again.

This guide is about coordination during the build: sequencing trades, planning a few weeks ahead, managing hand-offs between trades and running coordination meetings that settle things. It shows where delays usually begin and how a shared visual record of the site, such as the one Construct IQ provides, makes each step faster and less contentious. The day-to-day running of the site (daily reports, issue logs, labour and deliveries) is covered in our companion guide to construction field management.

Three kinds of coordination on one project

The word covers several different jobs, and confusing them is one reason meetings run long without resolving much.

Design coordination is a discipline of its own. If your problem is clashes between discipline models, our guide to BIM coordination in construction explains that process in detail. The rest of this guide deals with the other two types, which carry on every day until handover.

Why delays start at the interfaces

Most activities on a programme are not difficult on their own. Delay builds up at the points where one party depends on another: a trade waiting for an area, an answer, a delivery or an inspection. Research by the McKinsey Global Institute found that large construction projects typically finish about 20 per cent later than planned. A good share of that slippage traces back to interfaces that nobody owned.

The patterns repeat from project to project:

• Trade stacking. Two or three crews are sent to the same floor at once because each was told the area was free. They work around each other slowly, or one leaves and comes back later.
• Areas released too early. The structure crew moves on, but edge protection, cleaning or a pour inspection is still outstanding. The next trade arrives and cannot start.
• Unanswered questions. A technical query sits with the designer for a week while the crew that raised it switches to lower-priority work.
• Late or wrong materials. A delivery planned for a zone that is not ready ends up stored in the way of another trade.
• Covering up before sign-off. Ceilings or drylining close over services that have not been tested or recorded, and have to be opened again.

None of these is a failure of individual skill. Each happens because the information one trade needs is held by another person, in another place, and does not arrive in time.

The coordination cycle, week by week

Coordination works best as a repeating cycle rather than a series of reactions. A practical version has four steps.

1. Look ahead and clear the way

Every week, the site team reviews the work due to start in the coming three to six weeks and asks one question of each activity: what could stop this starting on the day? The answers become a list of constraints, each with an owner and a date by which it must be cleared.

Work only goes onto the short-term plan when its constraints are clear. Lean teams formalise this with pull planning and weekly commitments, which our lean construction guide covers; the principle applies on any project, lean or not.

2. Hand areas over on evidence

The moment one trade leaves an area and the next takes it over is where most arguments start. A clean hand-off needs three things: an agreed definition of "ready" for that area, a record of its condition at the moment of release, and the receiving trade's acceptance. Without the record, damage or incomplete work found a week later becomes a dispute about who caused it.

A short walk with both foremen is still the best way to agree readiness. Capturing the zone at the same time, with a 360° walk or a fixed camera view, turns that agreement into something anyone can check later.

3. Meet to decide, not to report

A coordination meeting should resolve conflicts and assign actions. If most of the time goes on each trade describing its progress, the meeting has become a status report, and decisions are pushed to the following week. Two changes help most:

• Circulate the current site picture before the meeting. If everyone has already seen which areas moved and which did not, the meeting can start at the problems.
• Keep a decision log. Each decision gets an owner, a date and a reference to the area or drawing it affects. Next week's meeting opens with that log.

4. Check that decisions reached the site

A decision is only useful if it is built. The final step of the cycle is to confirm, on the next capture or site walk, that the agreed fix, sequence change or revised detail actually happened. This is the step most teams skip, and it is why the same problem often appears on the agenda twice.

Who coordinates what

Coordination stalls when everyone assumes someone else has raised an issue. Writing down who owns which part avoids that.

The shared site record behind good coordination

Every step of the cycle above depends on one thing: an accurate, current, agreed view of the site. Lookaheads need to know whether preceding work is finished. Hand-offs need a record of condition. Meetings need facts everyone accepts. Follow-up needs proof that a decision was built. When that view comes from memory, phone photos in chat groups and written reports, each trade brings its own version, and a lot of meeting time goes on reconciling them.

What the record should hold

• Regular, dated captures of every active area, so you can see what changed since last week and when an issue first appeared.
• Locations for everything. A query, defect or decision should point to an exact place on the site, not a vague description.
• Design comparison, so the team can see where the build differs from the drawings or model before the next trade covers it.
• One place everyone opens, with access for each role, so the trade foreman, project manager and owner are looking at the same thing.

How YelloSKYE supports it

Construct IQ combines drone flights for site-wide context, 360° walks for interiors, fixed cameras for continuous views of priority zones and laser scanning where precision matters. DEX holds every capture on one timeline. Teams tag issues directly on the site visuals with geo-referenced annotations, so a contractor sees exactly where the problem is. They compare actual progress with the planned schedule in 4D, and can be alerted when activity stops in a high-priority zone. Progress data syncs with Procore and Autodesk Construction Cloud, so coordination happens inside the systems the team already uses.

The effect shows most clearly in fit-out, where the number of trades per floor is highest. On our interior fit-out project, navigable 360° records of each floor reduced site coordination time by 70 per cent and closed snags five times faster, because queries were settled from the visual record instead of by repeated site visits. Where structural accuracy affects the trades that follow, laser scanning catches the gap early: our as-built vs BIM clash detection use case shows deviations found before services contractors arrived to install. Across several projects, the same record gives leadership a common baseline; in our portfolio monitoring use case, leadership reviewed more than ten sites in 30 minutes.

Visual records do not replace the conversation between foremen on site. They make that conversation shorter, because the facts are already settled.

Common coordination failures and how to fix them

A coordination checklist for the next four weeks

1. List every activity due to start in the next four weeks and its constraints, each with an owner and a clear-by date.
2. Agree a written definition of "ready" for each type of area hand-off.
3. Set a capture routine so every active zone has a recent, dated record before each coordination meeting.
4. Send the current site picture and progress against plan to all trades a day before the weekly meeting.
5. Start a decision log, and open every meeting by reviewing last week's entries on site evidence.
6. Make inspection and recording a hold point before any area is closed up.
7. Hold a short daily check-in for today's clashes, so the weekly meeting can look ahead.

Explore Construct IQ