Fast-track work is the only job where you can be behind on day one and it isn't your fault. Design and construction run at the same time, so you're pouring footings off a foundation package while the architect is still fighting the owner over curtain wall details three floors up. The drawings you need next month don't exist yet, and everyone above you is treating the compressed schedule as a promise you already made.
I've run enough of these to know the projects that go sideways aren't the ones with the hardest design. They're the ones where nobody kept the two clocks — design release and field readiness — synced up. Coordinating subs on a fast-track job is a scheduling problem before it's a software problem, but the right tool makes the scheduling problem visible early enough to do something about it. Here's what actually matters when you're building while the design is still being drawn.
Schedule the design, not just the field work
On a conventional job you plan around when a crew can start. On fast-track you plan around when the drawings that crew needs will hit the field — and that date is a constraint just as hard as a concrete cure or a long-lead delivery. The single biggest mistake I see is treating the design release schedule as somebody else's problem living in a separate spreadsheet.
Pull it into your look-ahead. Every activity in your three- and six-week window should be tied to a specific issued-for-construction package, and every package that isn't in your hands yet should show up as a constraint with an owner and a needed-by date. When you build your weekly work plan, you're really answering two questions per line: is the crew available, and is the design that governs their work released? If either answer is no, that activity isn't ready — it's a wish.
A practical rule: back the design need-by date up from the field start by your lead time to review and detail. If a sub needs shop drawings approved before they fabricate, and fab is four weeks, then the IFC package that feeds those shops has to land at least five to six weeks before you want steel on site. Miss that math and you'll be idling a crew you already mobilized.
Overlap on purpose — and coordinate the overlap harder
Fast-track buys speed by overlapping activities that a traditional CPM schedule would run in series. That's the whole point. It's also where jobs get chaotic, because now you've got framers, MEP rough-in, and a fireproofing crew all wanting the same slab on the same shift.
The way to survive overlap is to plan it in space, not just in time. Break the floor into zones and hand out zones, not the whole level. Location-based planning is what keeps two trades off each other's backs — plumber in zone A while the framer works zone C, then they rotate. This is exactly where a visual, location-based look-ahead earns its keep over a bar chart: you can see the collision before it happens because two trades are literally sitting in the same cell of the same area on the same day. A Gantt line never shows you that.
When you're stacking trades, watch three things:
- Vertical conflicts. Overhead MEP and anyone working below them don't share a zone. Somebody's getting a wrench dropped on them otherwise.
- Inspection gates buried inside the overlap. You can't close a wall until rough-in is signed off. If drywall is chasing electrical too tight, one failed inspection stalls the whole sequence.
- Cure and dry times nobody buffered. Fresh slab, self-leveler, fireproofing — they all need time you can't compress, no matter how fast-track the job is.
Long-lead procurement runs the whole show
On most fast-track jobs the schedule isn't driven by how fast the crews work. It's driven by switchgear, air handlers, generators, elevators, and custom glazing — the stuff with a lead time measured in months, ordered off a design that isn't finished. You commit to that gear based on a preliminary package and pray the final design doesn't move the connection points.
Track procurement inside the same look-ahead your crews live in, not off to the side in a log the field never opens. Every long-lead item should carry a release date, a fabrication window, a ship date, and a required-on-site date, and the on-site date should tie directly to the field activity that consumes it. When switchgear slips two weeks, the whole electrical sequence should visibly move so you're renegotiating the plan on paper before the truck is late, not after.
The honest version of this: on fast-track, submittals and procurement are your real critical path more often than the field is. If you only obsess over one thing, obsess over the long-lead log.
Make RFIs and decisions move in hours
A traditional job can absorb a two-week RFI turnaround. Fast-track can't — a crew is standing on the thing you asked about. When you build with incomplete design, you generate more questions and you need them answered faster, which is a brutal combination if your process is email and hope.
Two habits help. First, look ahead far enough to ask early. A lot of "emergency" RFIs are questions you could have seen coming three weeks out if you'd read the upcoming package against the field conditions. The whole value of a rolling look-ahead is that it surfaces the constraint while there's still time to resolve it calmly. Second, put a name and a clock on every open decision. "Pending design" is not a status. "Owner to confirm finish by Thursday or we sequence around it" is.
And pre-plan your fallback. For any activity that depends on a design answer you might not get in time, know your alternate sequence before you need it — what you'll build instead so you're not sending a crew home. On fast-track, the super who always has a Plan B is the one who hits the date.
Version control isn't glamorous, but it'll save the job
When drawings reissue every couple of weeks, the most expensive thing that can happen on your site is a crew building off a superseded sheet. I've watched a mason lay half a wall off a revision that got voided nine days earlier because the current set never made it to his hands. That's rework nobody budgeted, on a schedule with no slack.
Everybody in the field needs to be pulling from one current source, with old versions archived but clearly retired. If your foremen are working off PDFs someone emailed last month, you don't have version control, you have a rumor mill. The tools worth using make the current package the only easy thing to open, and tie the sheet a crew is working from to the activity on the schedule — so "which revision governs this work" has one answer, not five.
Coordinate more often, but keep the plan the source of truth
Weekly planning is the baseline. During the hot stretch of a fast-track job, the real coordination cadence is daily — a short huddle to confirm what's ready today, what got released overnight, and what just fell out. Information that was true at 7 a.m. can be dead by lunch when design is still moving.
The trap is letting all that live in text threads and hallway conversations. Every change still has to land back on the plan, or the plan quietly becomes fiction and everyone starts trusting their own memory instead. This is where a shared, real-time look-ahead that the whole team — including crew leaders on their phones — sees the same version of does the heavy lifting. When a package releases or a delivery slips, you update the plan once and the field sees it, instead of playing telephone with fifteen subs.
A tool like LookAheadWall is built around exactly that loop: a visual weekly work plan tied to trade-flow sequences, shared with the subs, updated as conditions change. On fast-track that loop just runs faster and matters more.
Don't let compression eat quality or safety
Schedule pressure has a way of turning inspections into the thing that "we'll catch on the next one." That's how you get a failed rough-in that costs you a week you didn't have, or worse. Put your quality holds and inspection windows on the plan as real activities with real durations — not as afterthoughts you squeeze between trades. If drywall is scheduled to start the same morning the inspector is supposed to sign off rough-in, you've built a failure into the plan and you just can't see it yet.
Same with the buffers everyone wants to delete when they're behind. Frame-to-rough-in usually wants a day or two for cleanup and inspection. Megger the runs before you close the wall. Those aren't slack you can cash in under pressure — they're the difference between fast and reckless.
Plan for change instead of being surprised by it
Fast-track generates change orders. That's not a failure of the process, it's the process — you started building before the design was done, so of course things move. The mature version of managing it is to expect a baseline rate of change and carry contingency for it, in both dollars and schedule float, rather than treating every revision as a fire.
Watch the trend. If your change volume is climbing week over week in a particular area, that's a design coordination problem telling you where the next batch of RFIs and rework is coming from. A super who's tracking that pattern can get ahead of it. One who's just processing changes as they land is always a step behind.
None of this makes fast-track easy. But the difference between a fast-track job that lands and one that turns into a claim usually comes down to one discipline: keeping the design clock, the procurement clock, and the field clock visible on the same plan, and re-planning honestly every week as reality shifts under you. Do that well, and the compressed schedule stops being a threat you're reacting to and becomes something you can actually steer.