How to Manage Subcontractors Across Multiple Construction Projects

A framing crew tells two different project managers they'll be on site Tuesday, because two different people asked them on two different calls and nobody compared notes. One site loses a day. This kind of conflict rarely comes from a subcontractor acting in bad faith. It comes from a general contractor running several active jobs without one place where everyone's commitments, on every project, are actually visible at once.

When the same drywall subcontractor is working three of your projects at once, it's tempting to assume they know what "the usual scope" means by now. That assumption is exactly how a contractor ends up disputing a change order because the scope was never actually written down for that specific site. Write the scope for each project separately, even when it's a repeat subcontractor, and note anything that differs from what they did on your last job together.

"The electrician is handling rough-in" is a trade-level statement. It doesn't say who confirms the rough-in passed inspection, who orders the fixtures, or who's accountable if the schedule slips. Break subcontractor work into specific tasks with one named owner each, even when that owner is the subcontractor's own foreman rather than someone on your staff. A task with no clear owner is the single most common reason work sits untouched on a busy multi-project schedule.

Most double-bookings happen because a subcontractor's commitment to one project was never checked against their commitment to another before a date got promised to a client or an inspector. Before confirming a date with a subcontractor, check what else they're already committed to on your other active projects. This only works if there's one shared schedule to check against, not three project managers each keeping their own.

Drywall can't start until electrical and plumbing rough-in both pass inspection. Painting can't start until drywall is finished and sanded. These dependencies exist on every project, but they become harder to track when the trades involved are also splitting their week across two or three other job sites. Note the dependency explicitly for each task, not just the date it's scheduled for, so a delay on one trade visibly pushes the trades waiting behind it instead of silently throwing off the schedule.

Checking progress on three sites by driving to each one, or calling each superintendent separately, doesn't scale past a handful of projects. Progress needs to be visible from one place: which tasks are done, which are in progress, and which are overdue, broken out by project and by subcontractor, so a pattern like "this trade is consistently behind on every site" is obvious instead of buried in three separate conversations.

A quick daily note from each site, what a subcontractor actually completed that day, not just what they were scheduled to do, is what lets you catch a slipping schedule in days instead of weeks. This doesn't need to be elaborate. It needs to happen every day work occurs, and it needs to be tied to the specific project and task it's about rather than living in a single group chat shared across every job.

When a subcontractor's schedule shifts on one project, it often needs to shift on another too, and the people affected need to hear about it directly rather than find out when the crew doesn't show up. Whoever learns about a schedule change first should be responsible for passing it along to every project it affects, not just the one they happen to be managing that day.

When a subcontractor doesn't finish what was committed, find out why before assuming the worst. Sometimes it's a legitimate dependency they were waiting on. Sometimes it's because they prioritized a different one of your own projects over this one, which is worth knowing, since it means your own scheduling across projects created the conflict. Document what happened and what the new target is, rather than letting an incomplete task just quietly roll into "next week" with no record of why.

A verbal agreement with a subcontractor to adjust scope, extend a deadline, or cover an extra cost is easy to forget once you're juggling several projects, and easy to dispute later if it's only in one person's memory. Write down what was decided, who agreed to it, and what happens next, even briefly, at the time it's decided rather than trying to reconstruct it weeks later.

A subcontractor who's reliable on one project and consistently late on another is a pattern worth noticing, and you can only notice it if their performance across all your projects is visible somewhere, not scattered across separate project files that nobody compares. Review subcontractor performance across your active work periodically, not just project by project, so a recurring problem gets addressed instead of being treated as a one-off every time it happens.

A short weekly review tends to catch most of this before it becomes a problem. Walk through every active project and confirm which subcontractors are scheduled for the coming week, check that none of them conflict with each other, review what's overdue from the prior week by trade, and confirm any dependency that's about to come due, like an inspection that needs to pass before the next trade can start. Fifteen minutes per project, done consistently, catches far more than an hour spent reacting to a conflict after it's already caused a delay.

The projects, people, and companies below are fictional and for illustration only. They do not describe a real ConstruDo customer or project.

A general contractor is running three active projects: a four-unit renovation on Maple Street, a small commercial buildout on Fifth Avenue, and a townhome addition on Birch Court. The same electrical subcontractor, Example Electric Inc., is booked across all three.

During the weekly review, the project manager notices Example Electric Inc. is scheduled for rough-in at Maple Street and a service upgrade at Fifth Avenue on the same Wednesday. Checking the shared schedule before the week starts catches the conflict early enough to move the Fifth Avenue work to Thursday instead, rather than discovering it when the crew doesn't show up at one of the two sites.

At the same review, the project manager also sees that drywall at Birch Court is waiting on an electrical inspection that was supposed to happen Monday and hasn't been scheduled yet. Catching that dependency during the weekly review, rather than when the drywall crew shows up with nothing to do, is what keeps a three-project schedule from quietly slipping a week at a time.