Every superintendent has sat through the coordination meeting that goes nowhere. Fifteen foremen crammed into the trailer, half of them on their phones, somebody reading last week's printed schedule that was already wrong by Tuesday, and forty-five minutes gone before anyone talks about the actual conflict between the mechanical rough-in and the drywall crew that's about to blow up Friday. You leave with a page of notes nobody reads and the same problems you walked in with.
The meeting isn't the problem. The way most of us run it is. A good weekly coordination meeting is one of the highest-leverage hours on the whole job — it's where you catch the collisions before they cost you. The trick is treating it like a working session, not a status report, and using the tools you have so the room is arguing about the right things. Here's how to actually run one that's worth the trades' time.
The meeting is not for status — it's for commitments and constraints
If your coordination meeting is mostly people going around the table saying what they did last week, you're wasting everyone. Status is something people should be able to read before they walk in. The meeting exists to do two things a report can't: lock down what each trade will actually complete in the next week or two, and surface the things standing in the way of the work after that.
This is the core idea behind the Last Planner System and short-interval scheduling, and it's worth internalizing whether or not you use that vocabulary. You're working two horizons at once. The near horizon — call it the weekly work plan — is a set of firm commitments: "By Thursday, my crew has the west corridor ceiling grid in." The middle horizon — the three-to-six-week look-ahead — is where you hunt constraints so those future commitments are makeable when they come due. Keep those two conversations separate in the meeting. When you blur them, you get vague promises about work that isn't ready and hand-waving about work that is.
Do the work before the meeting starts
The single biggest lever on meeting quality is preparation, and most of it isn't yours to do alone. Send the current look-ahead out at least 24 hours ahead — a full day, not an hour, because a foreman who's on another job that afternoon needs a real window to look at his line and flag a problem. If people are seeing the schedule for the first time when they sit down, you've already lost the meeting to catch-up.
Ask every trade to come with three things: what they'll finish this week, what's blocking anything in the next month, and what they need from another trade to hit their dates. That last one is where the money is. Most jobsite conflicts aren't a surprise — they're a request nobody made in time. The electrician who needs the wall to stay open one more day, the plumber who's waiting on the sleeve layout, the framer who can't close up until inspection signs off. Get those on the table before the meeting and the meeting becomes about solving them instead of discovering them.
This is exactly the kind of legwork scheduling software should carry for you. A tool like LookAheadWall can push the current plan to every sub automatically so nobody's working off a stale PDF, and the trades can look at their own activities on their phone before they ever get to the trailer. When the distribution is automatic, you stop being the bottleneck and the plan everyone shows up with is actually the current one.
Run it off one live screen, not fifteen printouts
Put the schedule up on a screen everyone can see and drive it from there. The moment you're all looking at the same live plan instead of arguing over whose printout is right, the tone changes. When a sub raises a concern about the third floor east, filter the view to the third floor east so the whole room is looking at the same corridor. Location-based, visual schedules earn their keep here — a conflict between two trades in the same room is obvious when you can see both bars stacked on the same area, and nearly invisible in a list of activity codes.
A couple of practical habits make this land:
- Zoom to the fight, not the whole job. Nobody needs to stare at the sixteen-month bar chart during a weekly meeting. Filter down to the week or two you're committing to and the areas in play.
- Let people follow along on their own devices. A foreman who can pull the same view on his phone is a foreman who'll actually check his dates on site the next morning instead of remembering them wrong.
- Show trade flow, not just individual bars. The value of a look-ahead is seeing the handoffs — framing to rough-in, rough-in to inspection, inspection to insulation and close-up. When the sequence is visible, the whole room understands why one trade's slip pushes three others.
Spend your time on the constraints, not the ready work
Here's a discipline that will change your meetings: don't discuss activities that are ready to go. If the work is unconstrained, the crew's on site, and the predecessor is done — there's nothing to talk about. Move on. Spend the room's attention on the activities in the next few weeks that are not ready.
Walk the look-ahead and for each upcoming activity ask the boring, powerful question: is anything in the way of this being started and finished on time? The usual suspects, and they're the same job after job:
- Missing information — an unanswered RFI, a coordination drawing that hasn't come back, a detail nobody's resolved.
- Submittals and long-lead material — the fixtures that are still four weeks out, the switchgear that shows a ship date after your install date.
- Prerequisite work — the predecessor trade that has to finish, or at least clear the area, before this crew can move in.
- Inspections and approvals — the rough-in sign-off you need before anyone closes a wall.
- Access, equipment, and manpower — the hoist window, the lift that's double-booked, the crew that's short three men this week.
Every constraint you name gets a person and a date attached to it — not "someone should check on the fixtures" but "Mike calls the supplier by Wednesday and reports the ship date." That's the whole game. A constraint without an owner and a deadline is just a complaint. Capture those assignments where they won't get lost; a shared plan that carries the constraint list from one meeting to the next means nothing quietly falls off the table. When you clear a constraint two weeks early instead of discovering it the morning the crew shows up, you've turned a would-be delay into a non-event.
Get real commitments from the people who do the work
The near-term activities — the ones you're planning to start this coming week — need a firm yes from the person who'll actually run the crew. Not the PM in the office, not the sub's estimator. The foreman. Commitments made by the people who control the labor are the ones that hold, because they're built on what that person actually knows about his crew and his other jobs.
There's a quiet social mechanic worth using here: when a foreman says "yes, west stair done by Thursday" out loud, in front of the other trades he's handing off to, he means it more than a checkbox he clicked alone. Peer commitment is real. Your job is to make the ask specific and answerable — "Can you complete the grid in the east corridor by end of day Thursday, yes or no?" — and then hold the whole room to that same standard.
Measure what you promised versus what you did
The only way planning gets more reliable is if you look back honestly. Start the next meeting by checking the previous week's commitments: what got done as planned, and what didn't. The simple metric here is percent plan complete — of the activities a trade committed to, how many actually finished. You're not doing it to shame anybody. You're doing it to find the pattern.
When a trade blows commitments week after week, the number tells you before your gut does, and the useful part is the why. If commitments keep failing because of missing information, your constraint-hunting is too shallow. If they fail because trades keep overcommitting, your planning is optimistic and you need to squeeze the estimates. A reliable job usually runs somewhere in the high numbers on plan completion; a job constantly hovering around half is telling you the plan is fiction and the field is improvising. Tracking it over a few weeks turns a fuzzy feeling into a fixable problem.
Buffers, handoffs, and the collisions to watch for
A few hard-won specifics worth building into how you sequence the look-ahead, because these are the handoffs that go wrong most:
- Leave a buffer between framing and rough-in. A day or two between "frame complete" and the trades starting rough-in gives you room for cleanup, layout, and the framing inspection. Butt them back-to-back and one slow inspector stalls three trades.
- Never schedule close-up on top of rough-in inspection. The wall stays open until the electrical, plumbing, and mechanical rough-ins are signed off. Sequence insulation and drywall to start after that sign-off, with a little slack — the amount of rework caused by closing a wall the inspector then makes you reopen is staggering, and it's entirely avoidable.
- Test before you cover. Megger the electrical runs, pressure-test the plumbing, and confirm the mechanical before anything gets buried behind board. Finding a bad run after the drywall's up and taped is the expensive way to learn this.
- Coordinate the ceiling before anyone's in it. Duct, sprinkler main, plumbing, cable tray, and light fixtures all fight for the same plenum. That fight belongs on a coordination drawing weeks out, not in the field with two foremen and a tape measure.
- Watch shared resources. One hoist, one crane, one tower — when three trades all need it Tuesday morning, that's a conflict the schedule should surface days ahead so you can sequence the picks instead of refereeing a standoff.
When you can see these handoffs laid out on a location-based plan, the collisions announce themselves. When they live only in people's heads, they announce themselves the hard way — on site, with crews standing around.
Close the loop before the next meeting
The meeting's worth ends the moment its decisions get lost. Before people leave, everyone should be clear on what they committed to and what they owe. Get the updated plan back out to the field the same day — including to the sub who couldn't make it — so the whole crew is working off the outcome, not their memory of the room. Automated reminders on the constraint assignments keep the open items visible until they're actually closed, which is the difference between a follow-up system and a stack of forgotten notes.
Run this way and the coordination meeting stops being the hour everybody dreads. It becomes the hour where you find next month's problems while they're still cheap to fix. The software — a shared, current, visual look-ahead that everyone can see and drive — isn't what makes the meeting good. But it takes the busywork off your plate so the room can spend its time where it belongs: on the handoffs, the constraints, and the commitments that actually move the job.