An airport terminal is the only building I've worked on where you can pour a beautiful slab, hang thousands of feet of duct, and still miss your opening date because someone forgot to schedule the badging office three months out. Terminals punish crews that treat them like a big office building. The structure is often the easy part. What eats schedules is everything wrapped around the structure: an operating airfield you can't touch, a baggage system that runs the length of the building and dictates the concrete, a federal agency that owns your security screening layout, and a commissioning-and-readiness gauntlet at the end that most trades have never seen before.
Look-ahead scheduling — the disciplined habit of pulling the next three to six weeks into a weekly work plan and actually committing to it — is how you keep this kind of job from turning into daily firefighting. Below is how the pieces really fit together, and where the usual sequencing bites you.
Why a Terminal Isn't Just a Big Building
Three things make terminal work different from ordinary commercial construction, and every one of them changes how you plan.
First, you are almost always building next to, above, or inside a live airport. Cranes have height restrictions tied to the flight paths. Deliveries route through security. Any work that touches an active concourse happens on the airport's clock, not yours, and often at night. Second, the baggage handling system (BHS) is a building-length machine that has to be coordinated with structure, not fit in afterward. Third, the finish and turnover phase is longer and more formal than anything a private developer runs — there's integrated systems testing, a commissioning authority, and an operational readiness process the airport controls.
Put those together and you get a job where the critical path lives in the interfaces between trades and agencies, not inside any single trade's scope. That's exactly the situation a rolling look-ahead is built for: it forces you to look at the handoffs, not just the durations.
Sequence the Baggage System First, Then Frame Around It
The single most common terminal scheduling mistake is treating baggage handling as a late MEP-adjacent scope. It isn't. A checked-bag inspection system and its conveyor lines drive the depth of the bag-well slab, the location and size of housekeeping pads, dozens of floor and wall penetrations, and the routing of power and controls. If the BHS designer's steel-support layout lands after your slab is poured, you are coring and patching — or worse, ripping out.
Practical sequence that works:
- Get the BHS steel support and floor-loading drawings approved before the bag-hall slab-on-grade design is locked. Treat the BHS shop drawings as a structural predecessor, not a follow-on.
- Set embeds, sleeves, and housekeeping pads with the slab pour. Chasing these later in a bag hall full of conveyor steel is miserable and slow.
- Sequence conveyor steel erection so it doesn't block your overhead MEP mains. In a tall bag hall you want the big mechanical and electrical runs in before the conveyor structure boxes you out of the ceiling.
- Protect a clear delivery and staging path for conveyor sections. They come in long, awkward pieces and can't thread through a finished corridor.
Build a 6-week look-ahead specifically around the BHS install and you'll catch the collisions on paper. The trades that get burned by baggage systems are the ones who never saw the conveyor routing until it showed up on a truck.
Plan Security and Badging as a Long-Lead Item
TSA and the airport's security office aren't subs you can push. Their screening-equipment footprints, sightline requirements, and secured/sterile-area boundaries are fixed constraints you build to. Two things routinely blindside first-time terminal teams:
Badging has a lead time that has nothing to do with your schedule. Every worker who sets foot airside typically needs a background check and a security badge, and that process can run weeks. Start it late and you've got framers standing at a gate they can't pass. Put badging enrollment on your look-ahead as a hard predecessor to any airside activity, and track it like a submittal — because that's effectively what it is.
Screening equipment coordination is its own mini-project. The screening lanes and checked-bag machines have power, data, structural, and clearance requirements set by the equipment provider and the agency. Rough those in wrong and you're demoing finished walls. A weekly work plan that names the screening-area rough-in as its own tracked activity — with the equipment cut sheets in hand — keeps this from becoming a punch-list disaster.
Phasing Around a Live Airport
If you're renovating or expanding an operating terminal, phasing is the schedule. You'll be handed a sequence of construction phases with temporary walls, temporary passenger routing, and hard dates when a concourse or gate has to go back into service. Miss a re-opening date and you're not just late — you may be blocking gates the airline is counting on.
A few hard-won rules for live-airport work:
- Assume your most productive hours are gone. Loud, dusty, and disruptive work migrates to overnight shifts when passenger traffic drops. Plan crew size and productivity around a night shift, not a day one.
- Temporary partitions, exit paths, and dust barriers are on the critical path, not overhead. The airport won't let you start behind a wall until the barrier and egress are inspected and signed off.
- Deliveries route through security and often through occupied space. Build extra time into every material handling activity — a load that would take an hour in an open jobsite can take a shift when it has to be escorted airside.
- Utility tie-ins to live systems are scheduled shutdowns with the airport, coordinated weeks ahead. There is no "we'll just cut it over Tuesday."
This is where short-interval scheduling really earns its keep. The three-week window is close enough to commit crews and confirm the night-shift access, the badging, and the barrier inspections — while still leaving room to react when a phase slips. Trade-flow planning helps you see how work moves through each phase zone so a single delayed barrier doesn't quietly stall four trades behind it.
MEP and Special Systems: The Real Complexity
Terminal MEP isn't just bigger — it's denser and more integrated. On top of standard mechanical, electrical, and plumbing you're carrying flight information display systems, public address and mass notification, access control, CCTV, the BHS controls network, common-use passenger processing systems, and gate/apron systems feeding the jet bridges. Many of these are owner- or airline-furnished, which means your schedule depends on deliveries and integrators you don't control.
The coordination gotchas that recur:
- Overhead congestion is severe. Run the MEP coordination and clash detection early and hold it. The ceiling plenum in a terminal is a knife fight — mechanical mains, cable tray, fire protection, and the low-voltage cabling for a dozen special systems all want the same space.
- Owner-furnished equipment has its own clock. Jet bridges, screening machines, display hardware — put every one on the look-ahead with its delivery and vendor-install window, and treat a slipped delivery like the schedule hit it is.
- Low-voltage cabling is death by a thousand cuts. The special systems each pull cable through the same pathways. Sequence pathway (tray, conduit, J-hooks) as a coordinated package before individual vendors show up, or they'll trip over each other.
- Close-the-wall discipline matters. In-wall rough-in for card readers, panels, and device boxes has to be right before drywall. A missed box in a terminal wall isn't a quick fix — it may be in a secured area you can no longer freely access.
Don't Underestimate the Turnover: IST, Commissioning, and ORAT
Here's the part that sinks schedules built by people who've only done private work: the gap between "construction complete" and "open to passengers" is long, formal, and sequential. You typically move through integrated systems testing (proving that separate systems talk to each other — that a fire alarm actually releases the right doors and stops the right conveyors), then commissioning of the mechanical and life-safety systems by a commissioning authority, and finally Operational Readiness and Airport Transfer (ORAT) — trial operations where the airport runs volunteers through the building as if it were a real travel day to shake out the bugs.
What this means for your look-ahead:
- Systems have to come online in a dependency order. You can't test the BHS controls integration until power, network, and conveyor mechanical are all done in that zone. Sequence completion by system-testing readiness, not by trade convenience.
- Build in reticence time. Integrated testing always finds problems — that's the point. Leave a genuine buffer between "testing starts" and "ORAT starts," because you'll be chasing punch and re-testing. A week or two of float here is not padding; it's realism.
- ORAT trials are owner-run and dated. They're a fixed downstream milestone. Everything in your final look-ahead phases backward from the first trial, not forward from where the drywall crew happens to be.
- Commissioning needs stable conditions. You can't commission mechanical systems in a building that's still full of construction dust and open ceilings. Substantial completion of the enclosure and permanent-power availability are real predecessors.
Making the Look-Ahead Actually Work on This Kind of Job
None of this is theory — it's the difference between a terminal that opens on its announced date and one that quietly slips a quarter. The habit that holds it together is the weekly work plan: every week, the supers and foremen commit to what they'll finish in the next several days, and you measure what actually got done against what was promised. On a terminal, that plan has to speak the language of interfaces — badging cleared, barrier inspected, BHS steel released, screening cut sheets in hand, integration zone ready to test — not just "hang drywall on level 2."
A location-based look-ahead tool like LookAheadWall helps here because a terminal is naturally organized by zone and phase: bag hall, ticketing, concourse, gates, secured versus sterile. Planning by location, connecting trade-flow sequences so you can see how a delayed barrier or a late owner-furnished delivery ripples into the crews downstream, and sharing that plan out to every sub — including the crew leaders carrying it on the mobile app at the gate — keeps a very complicated building legible. The software doesn't build the terminal. But it makes the handoffs visible early enough that you can do something about them, which on a job this interconnected is most of the battle.
Get the baggage system into the structural conversation early, treat badging and screening as long-lead items, respect the live-airport phasing, and plan the turnover backward from the first ORAT trial. Do those four things and run a disciplined weekly plan around them, and the terminal that felt impossible starts to look like just another sequence of well-managed handoffs.