Running one job is a full-time fight. Running three or four at once is a different animal entirely. The trailer stops being a place you sit and becomes a place you drive past on the way to the next fire. You lose the thing that made you good at one job — the ability to walk the deck every morning and feel what's off before anyone tells you. Spread across sites, you're always a day behind on at least two of them, and you find out about the problem when it's already cost you.
Field management software gets sold as the fix for this, and most of the pitch is vague. Let's talk about what actually breaks when you go multi-site, and what a tool has to do to earn its keep.
Why Multi-Site Is Harder Than "More Of The Same"
The naive assumption is that four jobs are just four times the work of one. They're not. The real cost is context-switching and shared resources. When you leave Site A to go handle a delivery problem at Site C, Site A doesn't freeze — the tile setter still shows up, the inspector still comes, the GC still calls asking why the elevator sub isn't there. You come back to two new problems you didn't see start.
The other multiplier is contention. Your best finish carpenter, the manlift, the concrete pump, the one inspector who covers your whole region — these get fought over across jobs. A delay on one site quietly steals a resource another site was counting on next week, and nobody connects the two events until the second job slips. That invisible coupling between jobs is the thing that eats multi-site operations alive, and it's exactly what a portfolio-level view is supposed to surface.
The One View That Actually Matters
Forget the executive dashboard with the pretty pie charts for a second. The view that saves you is an exception view: one screen, all jobs, showing only what's off plan. Not "here's the status of everything" — you don't have time to read status on four jobs every morning. You need "here are the six things across all four jobs that are behind, blocked, or about to blow an inspection window."
Good look-ahead scheduling software builds this out of the weekly work plans your teams are already maintaining. If each site runs a real three-week or four-week look-ahead — tasks by location, with predecessors and constraints marked — the system already knows what's supposed to happen this week versus what got committed and what didn't. Roll that up and the exceptions fall out automatically. Commitments made and not met (your PPC, percent plan complete) is the single most honest early-warning number in the business, and it's the same metric whether you're looking at one job or twelve.
If your "portfolio view" is a spreadsheet somebody updates on Fridays, it's already lying to you by Monday. The whole point is that the roll-up is a byproduct of the field actually maintaining its plan, not a separate reporting chore someone has to remember to do.
Shared Crews And The Travel Tax Nobody Budgets
Here's a mistake I've watched cost real money: scheduling the same crew on two jobs the same week as if they teleport. A crew that finishes at Site A at 2:00 doesn't start at Site B at 2:15. There's load-out, drive time, badge-in, and the twenty minutes of standing around figuring out where to start. Realistically you lose a half to a full day every time a crew hops sites mid-week.
When you plan crews across projects, protect the moves. A few rules of thumb that hold up:
- Don't split a single crew across two sites in the same day unless the sites are genuinely close and the work is truly independent. Whole-day or whole-week assignments beat fractional ones almost every time.
- Build in a travel buffer as an actual scheduled item, not a hope. If the manlift and the crew both leave Site A Thursday, Site B doesn't get productive work out of them until Friday afternoon.
- Watch the same trade being promised to two jobs by two different people. This is the classic multi-site double-book, and it only shows up if both jobs' plans live in one system where the conflict is visible.
A shared crew that's silently overcommitted is worse than a short crew, because at least a short crew you can plan around. The overcommitted one shows up looking fine on paper right up until the week it doesn't show up at all.
Equipment: Know Where It Is And Who Has It Next
Big-ticket equipment — pumps, lifts, generators, trench boxes — is where multi-site coordination pays for itself fastest. The failure mode is boring and expensive: the lift you needed Monday is still sitting on the job that finished with it, nobody scheduled the move, and now your steel guys are standing around at $80-plus an hour waiting on a machine that's forty minutes away.
What you want is dead simple to describe and surprisingly rare in practice: every shared piece of equipment shows its current location and its next committed need. When the four-week look-ahead on Site B calls for the pump in week two, and Site A shows it released in week one, the handoff is obvious. When Site A's pour slips a week, you want the conflict to light up now, while you can still rent a second unit or resequence, not the morning both crews need it.
Track the move itself as a task with a duration. "Relocate manlift A→C" is real work with a real cost. If it's invisible on the schedule, it'll happen late.
Covering Sites You Can't Stand On
The hardest part of multi-site supervision is that your instincts were built on presence, and now you're absent most of the time. You can't fix that entirely, but you can change what "checking in" means. Instead of calling each foreman to ask how it's going — which gets you an optimistic guess — have each site maintain its own weekly work plan and daily commitments. Then your morning isn't four phone calls, it's one screen: what did each site commit to yesterday, what got done, and what's the reason for anything that didn't.
That last part — the reason — is gold. When a foreman logs why a task missed (material late, prerequisite not done, inspection failed, crew pulled to another job), you start seeing patterns across the whole portfolio. If "prerequisite not complete" keeps showing up, you've got a sequencing or trade-flow problem, not a manpower problem, and throwing more bodies at it won't help. A mobile companion app matters here for a specific reason: the foreman who's actually holding the tools will update a plan from his phone in the field. He will not walk back to a trailer and open a laptop. LookAheadWall's crew-leader app exists for exactly that gap — the plan gets updated by the person who knows the truth, at the moment he knows it.
Trade Flow Is Where Multi-Site Discipline Lives Or Dies
On a single job, an experienced super carries the sequence in his head — who has to finish before the next trade can start, where the crews chase each other through the building. Frame, then rough-in with a day or two of buffer for cleanup and inspection, then insulation once the rough inspections pass, then board. Megger the runs and pressure-test before anything closes a wall, because opening it back up after board is the kind of mistake that shows up in a lessons-learned meeting.
You cannot hold four jobs' worth of that sequence in your head. This is the honest case for building trade flows into the plan rather than trusting memory. When the sequence is explicit — this location's rough-in feeds that location's inspection feeds that location's cover-up — the schedule enforces the logic even when you're on another site and can't eyeball it. And when one predecessor slips, you see the downstream trades that just lost their start dates instead of finding out when three subs show up to a wall that isn't ready.
Standardize The Process, Not The Jobs
Every job is different, but the way you plan them shouldn't be. When each site invents its own format, its own task names, its own idea of "done," the roll-up is garbage and you can't compare anything. Push one planning rhythm across all sites: same look-ahead horizon, tasks organized by location, the same weekly commitment-and-review cadence. Then a number like percent plan complete means the same thing on Site A as it does on Site D, and comparing them actually tells you something — like which superintendent is making commitments he can keep and which one is optimistic every single week.
Comparison is a management tool, not a scoreboard for beating people up. If one job consistently hits 85% PPC and another sits at 55%, the low one isn't necessarily run worse — it might be starved of a resource, or stuck behind a design issue, or fighting a sub the other job doesn't touch. The comparison tells you where to point your attention. That's the entire value of seeing all your jobs in one place: it directs a limited amount of your time to the jobs that need it most this week.
A Short Checklist Before You Take On The Next Job
Adding a site to your plate isn't just adding a location. Before you say yes to the fourth job, be honest about the shared machinery underneath:
- Resource contention: Which crews and equipment does this new job share with your existing ones, and where are the collision weeks?
- Coverage math: How many days a week can you physically be on each site, and what's the plan for the days you're not?
- One system, one format: Is the new job going to plan the same way as the others, so the roll-up stays honest?
- Field-updatable plans: Can the person doing the work update the plan without walking back to a trailer?
- Exception surfacing: Will problems on this job reach you the day they start, or the week they've already cost you?
None of this is about a piece of software being magic. Multi-site management is fundamentally about seeing the coupling between jobs before it bites you — the shared lift, the double-booked crew, the slipped predecessor that quietly wrecks next week two sites over. A good look-ahead system earns its place by making that coupling visible and keeping every job's plan in one honest, current view. The tool doesn't run the jobs. You still do. It just stops you from finding out about the problem a week too late, which, when you're covering four sites, is most of the battle.