Running one job is a full-time fight. Running four at once is a different animal entirely, and the thing that kills you isn't any single project — it's the seams between them. The framing crew you promised to Site A is stuck finishing punch at Site C. The lift you scheduled for two buildings can only be in one place Tuesday morning. Nobody's lying to you; everybody's just optimizing for their own site, and the sum of all those local decisions is a mess only you can see. This is the real work of multi-site scheduling: managing the resources that float between projects, and making the priority calls nobody at the site level is positioned to make.
Here's how experienced multi-site supers actually keep the plates spinning.
Why Multi-Site Is a Different Problem, Not Just More of the Same
On a single job, your crews and equipment are captive. You know where the excavator is because there's only one place it can be. The moment you're running concurrent projects, three problems show up that don't exist on a solo job:
- Resource competition. The same specialty crews, the same equipment, and sometimes the same foreman serve more than one site. Demand for them peaks on different days, and those peaks overlap.
- Priority ambiguity. When two sites both need the crane Wednesday, someone has to decide who wins — and if that rule isn't written down before the conflict, it gets decided by whoever yells loudest.
- Blind spots. Each site super has deep visibility into their own job and near-zero visibility into everyone else's. The person who needs the full picture — you — is often working off three separate spreadsheets and a group text.
Notice that none of these are about any one schedule being wrong. They're coordination problems. That's why throwing a better single-project scheduling tool at each site individually doesn't fix multi-site — you need the layer that sits above the sites.
Build the Rolling Look-Ahead at the Portfolio Level
The discipline that saves you is the same one that works on a single job — a rolling three-to-six-week look-ahead — but you run it once across all sites instead of once per site. The goal is a single view where you can scan the next few weeks and spot the collisions before they happen.
Practically, that means every site's weekly work plan feeds up into one aggregate demand picture. When you can see that Sites B and D both spike their crane hours in Week 3, you've found your conflict while it's still a planning problem and not a Tuesday-morning phone call. This is exactly where look-ahead scheduling software earns its keep across a portfolio: LookAheadWall lets each superintendent build their location-based weekly plan on their own board, while you see the combined resource load across every project without re-keying anything. The whole point is to surface the overlap early, when moving a task two days costs nothing.
A rule of thumb worth adopting: any resource that serves more than one site should be planned at least three weeks out, not one. Single-site tasks can float on a one-week horizon because you can absorb the churn locally. Shared resources can't — a same-week crew reassignment between sites almost always means somebody eats a day of standby.
Manage Shared Crews Like a Dispatcher, Not a Hoarder
The most common multi-site failure is site supers treating shared crews as "theirs." A super holds the tile crew an extra two days "just in case," and the other site sits idle waiting. Multiplied across a portfolio, that hoarding instinct is enormously expensive.
Run shared crews like a dispatcher runs trucks:
- One availability calendar per shared crew, visible to everyone. If the drywall crew is committed to Site A Monday through Thursday, every other super should be able to see that they're not available until Friday — without asking.
- Commit windows, not open-ended assignments. "You have the crew Monday to Wednesday" forces the receiving super to plan tightly. "You have the crew until you're done" invites the exact hoarding you're trying to kill.
- Plan the handoff, including travel. A crew leaving Site A at 3:30 and driving forty-five minutes across town is not starting productive work at Site B until the next morning. Build that half-day of transition into the plan instead of pretending it's free.
One practical trick: stagger your shared crews' rotations so they hit each site on a predictable cadence — the electricians are at Site A Mondays and Tuesdays, Site B Wednesdays, and so on. A predictable rotation is worth a little theoretical inefficiency because everyone can plan around it. Constant ad-hoc reassignment feels flexible but burns hours in travel and re-mobilization every single move.
Coordinate Equipment Around Move Time, Not Just Use Time
Equipment is where the schedule and the checkbook meet. Every super wants the lift, the compactor, or the man-basket on their site "for the week," and the sum of those wants is a machine that's never anywhere long enough to earn its transport cost.
The number people forget is the move, not the use. A lowboy, a permit, a couple of hours of load-and-secure, and travel — a piece of shared equipment often costs the better part of a day every time it changes sites, before it lifts a thing. So:
- Batch the work. If a site needs a piece for two half-days a week apart, it's frequently cheaper to do both jobs in one visit than to move the machine twice.
- Sequence around the equipment, not the other way around. When a resource is genuinely scarce, let its route drive the site schedules for that week. Reordering a couple of tasks at each site to keep the crane moving in a clean loop beats letting every site pull it independently.
- Keep one honest location log. "Where's the lift right now" should never require three phone calls. When your scheduling board shows equipment position and its committed moves alongside the crew plans, the conflicts jump out on their own.
Write the Priority Rules Down Before You Need Them
This is the piece almost everyone skips, and it's the one that separates a calm multi-site operation from a daily brawl. You will have weeks where two sites need the same thing and only one can have it. Decide the tie-breakers in advance, in writing, so the call is already made when the pressure hits.
Good priority frameworks usually rank on a short, honest list:
- Contractual exposure. The job with liquidated damages ticking or a hard inspection date wins over the job with float.
- Critical path. A resource that unblocks a chain of follow-on trades beats one feeding a task with slack behind it. Losing a day on the critical path loses a day on the whole job; losing a day on a task with three days of float costs nothing.
- Cost of the delay. Idling a ten-man crew is more expensive than shifting a two-man punch task.
Write it as a simple document your supers have seen and agreed to. Then when the conflict comes, you're not negotiating relationships in real time — you're applying a rule everyone already accepted. And define the escalation path just as clearly: which conflicts a super can resolve peer-to-peer, and which ones come to you. Most should get settled between supers who trust the framework. The ones that hit your desk should be genuine exceptions, not the daily default.
Run a Real Cross-Site Coordination Rhythm
Visibility in software doesn't replace the conversation — it makes the conversation short. Hold a standing weekly cross-site look-ahead review, thirty minutes, all supers, cameras on if they're remote. The agenda writes itself off the aggregated look-ahead:
- Where do shared resources collide in the next three weeks?
- Which commitments from last week got kept, and which slipped? Track your plan-percent-complete per site and watch the trend — a site whose PPC keeps sliding is usually the one quietly hoarding shared crews or missing prerequisite work that jams up everyone downstream.
- What does each super need from another site next week, and is it committed or just hoped for?
Keep it disciplined. This is not a status meeting where everyone recites what they did — it's a negotiation about the shared pool for the weeks ahead. The moment it turns into a report-out, you've lost the value.
Standardize the Process So Your People Can Move
The quiet superpower of running every site on the same scheduling process and the same board is mobility. When a super gets pulled from one job to cover another, they don't waste a week learning a new system — the weekly work plan looks the same, the trade-flow sequences are built the same way, the look-ahead reads the same. Same for a foreman who floats. Consistency across sites turns your whole staff into a resource you can redeploy, which on a multi-site operation is exactly the flexibility you're short on.
Standardization also gives you honest benchmarking. When every project logs its commitments and completions the same way, "Site C is always behind" stops being a gut feeling and becomes a number you can act on. You can see whether it's a staffing problem, a priority problem, or a super who's over-promising — and you can only see that when the data's consistent enough to compare.
The Bottom Line
Multi-site scheduling isn't harder single-site scheduling. It's a coordination discipline layered on top: plan shared resources three weeks out, dispatch crews on committed windows instead of open-ended holds, sequence around scarce equipment, and — above all — decide your priority rules before the conflict, not during it. The software's job is to give you one honest picture across every project so the collisions surface early and the weekly conversation stays short. Get that picture, hold the rhythm, and the seams between your jobs stop being the thing that beats you.