Fast-track is a nice word for a job where the drawings are chasing you down the hall. Construction starts before design is finished, packages get released in pieces, and you're pouring footings for a building whose curtain wall is still a bracketed note on a shop drawing. I've run a few of these. The weekly work plan you build on a fast-track job is a different animal from the one you build on a fully-designed project, and if you plan it the same way you'll spend every Monday morning explaining why last week fell apart.
The core problem is simple to state and brutal in practice: you are planning work against information you don't fully have yet. Everything else about fast-track scheduling flows from that one fact.
Why the normal lookahead breaks on fast-track
On a conventional job with a complete set of drawings, a six-week lookahead is comfortable. You can see the sequence, the trades line up, and the only real unknowns are weather, manpower, and the occasional surprise in the field. You commit crews to work three and four weeks out with reasonable confidence.
On fast-track, that confidence evaporates the further out you look. The work six weeks from now depends on a design package that hasn't dropped, a submittal that's still in review, or a fixture the owner hasn't picked a color for. Planning that work in detail is a waste — you'll redraw it before you ever build it.
So the first adaptation is to shorten your detailed planning horizon and lengthen your discipline about what "planned" even means. Keep the outer weeks of the lookahead deliberately coarse — placeholders and constraints, not committed crew assignments. Reserve real, day-by-day, crew-by-location detail for the near term where the design is actually locked. On most fast-track jobs a genuinely reliable weekly work plan only extends one to two weeks out. Anything beyond that is a forecast, and you should treat it like one.
Treat information as a constraint — the same as material or manpower
Every foreman knows to check for material and manpower before committing a task. On fast-track, missing information kills more weeks than missing material does, and most planning tools don't have a place to track it. Fix that. When you screen an activity for the next week's plan, run it through the full list:
- Design — is the drawing released, and is it the current revision, not the one from three ASIs ago?
- Submittals — is the shop drawing approved, or approved-as-noted with notes that actually change the work?
- Material — is it on site or confirmed to deliver before you need it?
- Manpower and equipment — do you have the crew and the lift?
- Predecessor work — is the area actually ready, inspected, and signed off?
An activity that clears every one of those is make-ready — you can commit it. An activity missing any one of them is a constraint you own until it's cleared. The discipline of only committing make-ready work is the whole game in short-interval scheduling, and on fast-track the information column is the one that trips people up. A weekly work plan full of tasks that depend on unreleased design isn't a plan; it's a wish list. This is exactly where a look-ahead tool that lets you flag and track constraints per task — LookAheadWall does this — earns its keep, because on fast-track the constraint log is the schedule.
Let the design release schedule drive the work — not the other way around
Get the design team's package release schedule and treat it as a real input, not a side conversation. Every partial release — foundations, then structure, then the envelope, then interiors by floor — is a gate that opens a chunk of buildable work. Your job is to map each release to the field work it unlocks and to keep a running countdown to the ones you're waiting on.
Then build backward. If steel needs a released structural package plus an eight-week mill lead time plus detailing and fabrication, the release date that matters isn't when you need steel on site — it's weeks earlier. On fast-track, procurement and design release are joined at the hip, and long-lead items get committed off partial or even preliminary design with a deliberate, documented risk. Switchgear, elevators, structural steel, curtain wall, generators, chillers — these get ordered before the drawings are done or they will absolutely be your bottleneck. Know your lead times cold and order to the release schedule, not the install date.
Keep a live decision log with dates that mean something
Fast-track is death by pending decision. A thousand small choices — finish schedules, fixture selections, routing calls, dimension confirmations — sit unmade, and each one quietly blocks work nobody flagged until Thursday. Keep a decision log, and make it ruthless. Every open item gets three things: what the decision is, who owns it, and the date you need the answer by to protect the schedule.
That last date is the whole point. "We need the tile selection soon" gets ignored. "We need the tile selection by the 14th or the second-floor bathrooms slip and the plumber loses his slot" gets answered. Work backward from the field need through submittal, procurement, and fabrication to find the real deadline, then escalate hard when it's missed. A late decision that costs you a crew day is worth interrupting the owner's lunch over. Say so.
Zone the building so partial releases become parallel work
The single most powerful move on fast-track is breaking the project into zones that can proceed independently, so that a partial design release actually turns into buildable work instead of sitting idle. If the east wing's interiors are released and the west wing's aren't, a zoned plan lets the east wing crews run at full speed while the west wing waits on paper.
Think in areas that can be finished out on their own — floors, wings, pours, cores. Sequence your trade flows through those zones so a crew rolls from zone to zone in a steady rhythm rather than mobilizing and demobilizing every time a package hits. This is where location-based, trade-flow planning beats a bar chart badly. When you can see each trade moving through the building zone by zone on a visual weekly plan, the gaps and collisions jump out — the drywall crew catching up to a framer who's stalled waiting on a released detail, two trades booked into the same room the same day. A bar chart hides that. A location grid shows it at a glance, which is why we built the visual look-ahead wall the way we did.
Coordinate more often, and shorten the loop with design
Weekly coordination is not enough on fast-track. The information changes too fast. Run a short daily huddle with your foremen — fifteen minutes, standing up, covering what got done yesterday, what's committed today, and what's about to be blocked. The blocks are the point. You're hunting for the constraint that's forty-eight hours from stopping a crew, while there's still time to clear it.
Just as important, tighten the loop between the field and the design team. On a normal job an RFI can take a week and nobody dies. On fast-track a week-long RFI turnaround will bury you. Push for same-day or next-day answers on field-critical questions, get the architect and key engineers reachable, and when a design conflict shows up in the field, get eyes on it that day. The projects that hold together are the ones where a superintendent can get a real answer in hours, not weeks.
Build buffers in on purpose, because the schedule has no slack of its own
Fast-track schedules are aggressive by definition — that's the whole reason to run one. That means there's almost no natural float, so you have to place buffers deliberately or the first hiccup blows through to the finish date.
Two buffers matter most. First, put a gap between when a design package is released and when you actually need to build off it — a week or two so the field has time to digest the drawings, catch the coordination problems, and get material ordered before the crew shows up. Releasing design the same week you need to install off it guarantees a scramble. Second, keep a modest feeding buffer in front of your true critical-path activities so a two-day slip in some feeder task doesn't automatically push the milestone. Don't bury the buffers where nobody can see them and don't let them get quietly consumed — protect them the way you'd protect the critical path itself, because on fast-track they are part of it.
Do not trade quality for speed — you can't afford the rework
Here's the trap. The pressure is relentless, so crews start closing walls before the rough-in inspection, skipping the pull test, moving on before the QC walk. And rework, which is annoying on a normal job, is catastrophic on fast-track. You have no float to absorb it. Tearing out a wall to fix a missed run doesn't just cost that trade a day — it cascades into every trade queued behind it in that zone.
So bake the quality steps into the weekly work plan as real activities with real durations. Frame-to-rough-in wants a day or two of buffer for cleanup and inspection — don't schedule drywall to start the morning after framing finishes. Megger the runs before you close the wall. Get the rough-in inspection signed off as a hard predecessor to cover-up, not a formality you backfill. On fast-track, the disciplined crew that inspects before it covers finishes ahead of the fast crew that has to open walls back up. Every time.
Give your subs information early and share the risk honestly
Your subcontractors are living with the same incomplete drawings you are, and they can't plan their manpower any better than you feed them. Share what you know when you know it, even when it's partial — a sub who knows a package is a week out can hold his crew instead of walking them. Surprise a sub with a released area and expect a two-week ramp before he's staffed up.
And be straight about the risk. Fast-track shifts real uncertainty onto the trades — they're pricing and manning work off incomplete design. Pretending otherwise, or writing contracts that dump all of it downstream, gets you padded bids, weak crews, and change-order warfare when the design catches up. The jobs that run well are the ones where the GC and the trades treat the incomplete information as a shared problem, coordinate around it daily, and sort out the impacts fairly. That's not soft — it's the difference between subs who flex with you and subs who lawyer up.
The short version
Fast-track scheduling isn't a different discipline, it's the same short-interval planning turned up to full volume. Shorten your committed horizon to the work that's actually released. Track information as a hard constraint, not an afterthought. Chase the design release and procurement schedules as your real drivers, keep a decision log with deadlines that bite, zone the building so partial releases become parallel work, coordinate daily, and protect your buffers and your quality steps like the schedule depends on them — because it does. Get good people who can decide in the field, give them a visual plan that shows trade flows moving through the building, and keep the loop with design short. Do that and a fast-track job stops being a fire drill and starts being a fast, controlled build. That's the whole trick: plan as fast as the job moves, and no faster than the information lets you.