Every superintendent I've ever respected had one thing in common: they could tell you, off the top of their head, which subs were going to show up Monday and which ones were going to leave them hanging. That instinct comes from years of watching foremen not answer their phones on a rainy Friday. The good news is that the right software can turn a lot of that gut feel into something you can point to, share, and hold people to. The bad news is that most crews buy a tool, use ten percent of it, and wonder why nothing changed.
This is a working guide to actually running your subs through software instead of just storing their phone numbers in it. If you're a superintendent or a lead foreman coordinating five to fifteen trades on a job, this is for you.
Stop treating the software as an address book
Here's the trap almost everyone falls into. You roll out a subcontractor management platform, you load in every foreman's cell, every PM's email, and every insurance cert, and then you keep running the job exactly the way you always did: texts, phone calls, and a whiteboard in the trailer. The software becomes a filing cabinet nobody opens.
The point of putting your subs in a system isn't storage. It's that every commitment, every schedule change, and every open issue lives in one place that everybody can see. When the drywall foreman says he never got the word that the framing inspection slipped a day, you want to be able to show him the exact notification, timestamped, that went to his phone. That single capability — a shared record of who was told what and when — is worth more than every other feature combined, because it changes how people behave. People keep their word differently when they know it's written down.
Build the schedule the trades actually work from
A master CPM schedule is a contract document. It is not a work plan. No electrician has ever pulled up a 1,400-line Primavera file to figure out what room to be in Tuesday morning. The tool your subs live in day to day should be your look-ahead — the two-, three-, or four-week window that says, in plain terms, who is doing what work, in what area, on what day.
This is where short-interval scheduling earns its keep. A weekly work plan that shows location, trade, and duration is something a foreman can look at for fifteen seconds and know exactly what you need from his crew. When that plan is location-based — first floor east wing, level 3 corridor, units 201 through 210 — you stop having the argument where two trades show up in the same room and one of them stands around for four hours. Visual, area-driven look-ahead scheduling is precisely what LookAheadWall was built for, and it's the layer where trade coordination actually happens, not the master schedule.
The rule of thumb: distribute your look-ahead the same day and time every week. Thursday afternoon for the following two weeks works well — it gives foremen the weekend to line up manpower and material. Consistency matters more than the specific day. When subs know the plan drops every Thursday at two, they start planning around it instead of waiting for you to chase them.
Track commitments, not just tasks
The single most valuable thing you can do in any of these systems is capture commitments and then check whether they were kept. This is the heart of the Last Planner approach, and it's dead simple: at your weekly coordination meeting, each foreman commits to specific work he'll complete that week. You write it down. Next week, you check what got done.
The number that comes out of that — percent of commitments completed — is the most honest metric on your job. Not because the percentage itself is magic, but because the misses tell you why. When you track reasons for non-completion over a few weeks, patterns jump out: it's almost never the trade being lazy. It's material that didn't show, a prior trade that ran long, an RFI that never got answered, a missing inspection. You're not building a case to beat up your subs. You're finding the constraints that are actually slowing the job, most of which are upstream of the guy who missed his commitment.
A foreman who commits to nine tasks and finishes eight is more valuable to you than one who vaguely agrees to "get to the third floor" and delivers nothing measurable. Push for specific, countable commitments. "Rough-in units 201 through 206" beats "keep working on the third floor" every time.
Make constraints the meeting, not the schedule
Here's a shift that separates the superintendents who finish on time from the ones who are always explaining why they didn't. Your coordination meeting shouldn't be a status report where everyone says what they did last week. It should be a constraint-clearing session focused on the next two to three weeks.
Before a task can go on the look-ahead as "ready," it should be clear of the usual constraints. I keep a mental checklist and I recommend you build the same into whatever system you run:
- Prior work complete — is the predecessor trade actually done in that area, or just mostly done?
- Material on site — not "ordered," not "on the truck." On site, staged, in the right zone.
- Information clear — no open RFI, no pending submittal, current drawings in hand.
- Access — can the crew physically get to the work, with the equipment they need?
- Manpower — does the sub have the bodies, or is he splitting his crew across three jobs?
- Inspection sequencing — is the required inspection lined up so it doesn't become a two-day hold?
Anything that fails that check is a constraint, and constraints get an owner and a due date. That's what your software should be tracking loudly. A task with an open constraint has no business being promised to a foreman as ready work — that's how you burn trust and manpower at the same time.
Sequencing and the buffers that keep you honest
Coordination software won't save you if the underlying trade flow is wrong. You have to know the sequence cold, and you have to build in buffer where the handoffs are fragile. A few I'd never schedule without breathing room:
- Frame to rough-in: give yourself a day or two after framing before the rough-in trades pile in. Somebody has to clean up, the framing inspection has to pass, and you want the walls signed off before anyone bores through a stud in the wrong spot.
- Rough-in to cover: plumbing, electrical, low-voltage, and HVAC all have to be in and inspected before insulation and drywall. Sequence them so they're not fighting for the same bay, and megger the electrical runs and pressure-test the plumbing before the wall closes. Reopening a finished wall is the most expensive four hours on any job.
- MEP overhead before ceiling grid: get the overhead rough coordinated and inspected before the ceiling trades start, or you'll be cutting tile to chase a duct that moved.
- Finishes: paint before flooring in most cases, and hold your final trades — hardware, trim-out, fixtures — off the wet trades until things are truly dry and cured, not just dry to the touch.
When you connect these handoffs visually as trade flows in your look-ahead, the software does something a spreadsheet can't: when one trade slips, you can see immediately which downstream trades need to be renotified. That renotification — telling the drywall crew their Monday just became a Wednesday, the same day you find out — is the difference between a controlled slip and a truck full of hangers showing up to a room that isn't ready.
Documentation is your quiet insurance policy
Nobody gets into this trade because they love paperwork. But the superintendent who documents is the one who wins the argument in the trailer six months later. Log delays, log the reasons commitments got missed, log when access wasn't available and whose fault it was. You're not building a grudge file. You're building the record that protects the schedule and, when it comes to it, backs up a change order or a delay claim.
The trick is to make documentation a byproduct of the work you're already doing, not a separate chore. If your commitment tracking and your issue log live in the same system as your look-ahead, the record writes itself as you run your weekly cycle. That's the whole game — capture it in the flow of the meeting, not in a separate report you'll never actually fill out.
Feed the field, not just the office
One last thing that trips up a lot of otherwise good rollouts: the schedule lives on a laptop in the trailer, and the crew leaders never see it. A plan a foreman can't pull up on his phone in the parking lot at 6:45 a.m. isn't a plan he's going to follow. Whatever system you use, the field has to be able to see the current week's work plan on a phone, without calling you. A mobile view for crew leaders closes that gap — it's why LookAheadWall pairs the planning side with a companion app so the guy running the crew sees the same look-ahead you built, not a two-week-old printout.
Where to actually start
If you're standing up a coordination process from scratch, don't try to use every feature in month one. Do these three things and you'll be ahead of most jobs in the country:
- Publish a location-based look-ahead every week, same day, same time, to every trade.
- Capture specific commitments at your weekly meeting and review completion — with reasons — the following week.
- Track constraints with an owner and a due date, and refuse to promise work that isn't constraint-free.
Everything else — RFI logs, submittal tracking, performance history, change-order impacts — is worth building in once that core loop is humming. But the loop is the thing. Software doesn't coordinate trades. A superintendent running a disciplined weekly cycle coordinates trades, and good software makes that cycle faster, more visible, and impossible to fake your way through. Get the loop right and the tool starts paying you back within a couple of weeks. Skip it, and you've bought yourself a very expensive address book.