Here's a number that should keep you up at night: on most commercial and multi-family jobs, subs perform 80 to 90 percent of the physical work. You, the GC, mostly move people, information, and materials into position so the trades can do their thing. Which means your project doesn't succeed because you built it well. It succeeds because you coordinated the eleven companies who built it well, and got them to hand off cleanly to each other 400 times without tripping over one another.
That's the whole game. And it's why "coordination" gets talked about like a soft skill when it's actually the hardest, most failure-prone part of the job. Software helps, but only if you understand what you're actually trying to fix. Let's talk about where sub coordination really breaks down on site, and how the right tools plug those specific holes — instead of just giving you another dashboard nobody opens.
Coordination fails at the handoff, not in the plan
Walk any job that's behind and you'll almost never find that a single trade was slow. What you'll find is a broken chain of handoffs. The framers finished the demising walls but left the top track shy of the deck in three spots, so the drywall hanger can't close up, so the taper's crew shows up to a floor they can't touch and goes home. Nobody was "late." The handoff was dirty, and the delay rippled three trades downstream before anyone noticed.
This is the thing to internalize: your schedule is a chain of promises between trades. The electrician's rough-in is a promise to the inspector and the drywall crew. The drywaller's finished, primed wall is a promise to the painter and the millwork installer. When one link is late or sloppy, everyone downstream eats it, and the guy who caused it is usually long gone.
Good coordination software matters here because it makes the handoffs visible — who hands off to whom, when, and in what location. A visual, location-based look-ahead like the wall LookAheadWall is built around shows trade-flow sequences as connected lines, not just a list of bars. When you can see that plumbing top-out feeds framing inspection feeds insulation feeds drywall in the same corridor, you can spot the pileup before it happens instead of explaining it afterward.
Share the near-term, not the whole Gantt
The classic mistake is handing a subcontractor the full CPM schedule — 1,400 activities, six months out — and calling it "schedule visibility." No foreman reads that. He reads it once, sees his work is on there somewhere in April, and never opens it again.
What a sub's crew leader actually needs is the three-week window: what am I doing this week, what's coming next week, and what do I need to have staged and manned for the week after. That's the entire value of short-interval scheduling. The look-ahead is deliberately small enough that a foreman will glance at it from his truck and adjust his crew count for Monday.
So when you're evaluating whether software is helping sub coordination, ask a simple question: can a sub see only the near-term work that's theirs, on their phone, without a login they'll forget? If sharing a weekly work plan takes more than one tap for the person receiving it, it won't get used. This is exactly why a mobile companion app for crew leaders matters — the office builds the plan; the field just needs to see their slice of it.
Make-ready: the constraint log is where projects are actually won
If I could teach one habit to every young super, it's this: run a make-ready process on every activity before it hits the weekly work plan. Before you commit a task to next week, you check it against the constraints that would keep it from being done:
- Design — are the drawings released and RFIs answered for this area?
- Materials — is it on site, or at least confirmed with a delivery date that clears the start?
- Prior work — is the preceding trade actually complete and inspected, not "basically done"?
- Labor & equipment — does the sub have the manpower and the lift/hoist window booked?
- Permits & inspections — is the sign-off in hand so you're not closing a wall you'll have to open?
An activity only earns a spot on the committed weekly plan when every constraint is clear. This is the heart of the Last Planner System, and it's the single biggest lever on reliability. Teams that track constraints religiously routinely push their planned-work completion from the industry-typical 50-something percent up toward the 80s. The math is brutal and simple: if only half your promised tasks finish each week, half your handoffs are dirty, and your whole downstream chain is guessing.
Software's job here is to be the constraint log that doesn't get lost. Tie each constraint to an activity and an owner and a need-by date, and the make-ready becomes a living to-do list you clear in the coordination meeting instead of a conversation everyone forgets by Thursday.
Run the weekly coordination meeting off the plan, not off memory
The best sub-coordination tool ever invented is a 45-minute meeting every week where the foremen make commitments to each other's faces. Software supports it; it doesn't replace it. A meeting that works looks like this:
- Review last week: which committed tasks got done? For each miss, one honest root cause — no blame, just the reason, because the reason is data.
- Walk the next week location by location, trade by trade, confirming the handoffs. "Electrical, you're clear of corridor C by Wednesday? Drywall, you're manned to start Thursday?"
- Surface constraints on the week two to three weeks out, and assign someone to clear each one before it becomes this week's problem.
- Get verbal commitments. A foreman saying "yes, I'll be done" in front of his peers is worth ten emails.
When the plan is shared and visual, the meeting stops being a status-reciting slog and becomes an actual negotiation of handoffs. That's the difference between a coordination meeting and a complaint session.
The trade-flow gotchas that actually bite
Twenty years of watching the same collisions, here are the ones worth writing on the trailer wall:
- Overhead MEP has to dance, not queue. Duct, plumbing, sprinkler, and conduit all fight for the same ceiling space. Sequence them — big duct first, then gravity plumbing, then sprinkler main, then conduit that can weave around — or you'll be paying to move ductwork that "got there first."
- Never let drywall bury an inspection. Framing, rough electrical, rough plumbing, and low-voltage all need sign-off before you close the wall. Build a real buffer between rough-in and cover — a day or two for cleanup and the inspector's schedule — because inspectors don't come when you snap your fingers, and reopening a wall is the most demoralizing rework there is.
- Megger the runs before you close the wall. Same principle everywhere: test what you can't get back to. Pressure-test the pipe, ring out the cable, hydro the sprinkler branch while it's still exposed.
- Protect finished floors from the trades that come after. Sequence flooring late, or protect it hard, because the punch-list painters and the door hardware guys will absolutely trash a green-labeled floor if you let them.
- Watch the two-trade squeeze in tight areas. A mechanical room or a small unit bathroom can physically hold two crews for about a day before they start standing in each other's light. Stagger them.
None of these are in a manual. They're in the scar tissue. But a look-ahead that shows trade flows by location lets you catch the collision on the screen Monday instead of in the corridor Thursday.
Documents and RFIs: the quiet delay machine
A sub working off an outdated detail is a rework bill waiting to be written. The coordination win isn't "we have a document platform" — it's that when a drawing gets revised, the affected trades actually know before they build to the old version. Set it up so revisions push to the people in that area, and so a foreman can pull the current sheet on his phone standing at the work, not by driving back to the trailer.
Same discipline on RFIs. An unanswered RFI is a constraint by another name. Route it, put a name and a due date on it, and — critically — connect it back to the activity it's blocking on the look-ahead. That way an RFI that's been sitting eight days doesn't just live in an inbox; it shows up as a red flag on the wall next to the task it's going to sink.
Measure reliability, not just percent complete
Percent complete tells you where you are. It doesn't tell you whether you can trust anybody. The metric that actually predicts your future is Percent Plan Complete — of the tasks a trade committed to this week, what fraction did they actually finish? A sub who hits 90 percent PPC week after week is one you can build a schedule around. One bouncing around 40 percent is quietly making your plan fiction, no matter how busy their crew looks.
Track PPC by trade over time and you get an honest picture of who's reliable, and the root-cause notes tell you why the misses happen — late material, missing manpower, waiting on the prior trade. That's the difference between "the plumber is a problem" and "the plumber keeps getting caught behind late framing inspections," which are two completely different conversations with two completely different fixes.
The point of all of it
Strip away the feature lists and sub coordination comes down to a few plain habits: share only the near-term work, in a form the field will actually look at; clear constraints before you commit a task; run a real weekly meeting where trades make promises to each other; keep documents current where the work happens; and measure whether people keep those promises. Software that's built around a visual, location-based look-ahead makes those habits easier to keep — LookAheadWall exists for exactly this. But the tool only matters because the habits do.
The best-run job I ever walked wasn't the one with the fanciest software. It was the one where every foreman knew, on Monday, exactly who he was handing off to on Friday and what "done" meant to that guy. Get the handoffs clean and the schedule mostly takes care of itself. Everything above is just how you make the handoffs clean.