The Hidden Coordination Risks of Schedule Compression

Compressed Schedules Don't Squeeze All Tasks Equally

You're 10 days into a project when the owner announces they need to accelerate completion by three weeks. The schedule gets compressed. Superintendent moves trades up, extends shifts, brings in more crews. But here's what actually happens: structural and MEP coordination, the tasks that were already on the critical path and hardest to compress, compress less than everything around them. They don't scale with concurrent crews. Meanwhile, submittals and drawing reviews—the work that depends on coordination decisions—get front-loaded into a tight window before construction starts. The A/E team who was planning to review drawings over four weeks now has two. Submittals that were scheduled to arrive after design coordination is complete now arrive before. And the coordination work itself doesn't change; it just gets compressed into a space where it wasn't meant to fit.

The result is predictable: critical coordination decisions get made with incomplete information, or worse, made again incorrectly midway through construction when field conditions reveal what drawings didn't. Shortcuts that seemed reasonable at preconstruction become expensive rework. Schedule delays actually increase because the coordination breakdown forces you to stop crews and solve problems in the field.

The Coordination Work That Can't Be Compressed

Some coordination tasks are inherently sequential and can't be parallelized. A general contractor can't framing and MEP coordination happens when all MEP trades have designed their systems and submitted them for review. You can't approve a submittal before it arrives. You can't resolve a clash before it's identified. These aren't time-wasters; they're dependencies.

When you compress the schedule, you're usually pushing hard on the construction phase—moving the start date earlier, stacking crews, extending hours. But preconstruction has hard task dependencies that don't move. Design coordination, submittal approval, and drawing review all have a minimum duration based on the number of decisions that need approval and the number of approvers involved. Trying to force MEP coordination into two weeks when it structurally requires four weeks doesn't make it faster; it makes it wrong.

The sneaky part: the schedule looks compressed, so everyone assumes coordination is on track. But the A/E team is doing cursory reviews instead of detailed coordination. The GC is marking submittals approved without waiting for all sign-offs. The subs are starting layout work before the coordination approval is final, betting they won't have to rework. And then mid-construction, when those bets lose, everyone acts surprised.

Shortcuts That Backfire

"We'll do full coordination review during construction." Worst decision you can make. Field coordination is expensive—you're paying trades to stand around while MEP is rerouted, you're delaying concrete pours while sprinkler mains move, you're burning schedule float you don't have. Issues that cost $500 to fix on a drawing cost $8,000–$15,000 to fix in the field. And if the issue is discovered after a system is partially installed, costs spike further. Preconstruction coordination is mandatory, not optional.

"We'll approve submittals with a comment: 'Pending coordination review.'" Submittals marked approved but pending something are approved-in-limbo. The sub assumes they can start manufacturing or procurement. Then coordination review finds a problem and the submittal gets rejected, but the sub is already two weeks into production. Submittals should only be marked approved when they're truly approved. Use a "Pending Coordination" status until review is complete.

"The structural engineer will coordinate with MEP." Vague coordination assignments don't work, especially when the schedule is tight. Structural says, "MEP didn't send us their plans." MEP says, "Structural never asked." By the time it's resolved, two weeks are gone. Coordination needs to be explicitly assigned—not vague suggestions. The GC or architect should name the MEP coordinator and the structural coordinator and put them on a coordination schedule that includes specific deliverables and milestones.

"We'll skip the preconstruction meeting and go straight to construction." The preconstruction meeting is where coordination expectations get established. Who approves what? By when? How are clashes escalated? If you skip this meeting to save time, you've guaranteed miscommunication. The meeting actually saves time downstream because everyone knows the process.

Protecting Coordination When Time Is Tight

If compression is unavoidable, protect coordination explicitly. Don't let it be the task that gets squeezed because it has no cranes or concrete.

1. Front-load coordination into early preconstruction. Begin MEP coordination and submittal review before the construction phase starts, not during. Allocate real time—not the leftover hours after faster tasks are done. Give the A/E team the design documents early and ask them to start coordination immediately, in parallel with detailed design if necessary.

2. Use AI-assisted drawing and submittal review. Tools that automatically flag coordination issues, spec discrepancies, and missing information compress the review cycle. Instead of an architect spending a day reading through a submittal, AI flags potential issues in 20 minutes. The architect focuses on judgment calls, not baseline compliance checking. This doesn't change what gets reviewed—it changes how fast. Submittal review tools and clash detection are designed for exactly this.

3. Establish a coordination hot-line. When compression is serious, designate a single person (usually the GC) who coordinates between all MEP trades and the design team. This person has authority to make decisions and escalate problems immediately. Don't let coordination drift across multiple emails.

4. Run a preconstruction coordination workshop. Don't just review the schedule; walk through known coordination risks. Above-ceiling conflicts, trades that need to cross each other, subcontractor sequencing issues. Identify the top 5–10 areas that could cause problems and establish coordination solutions in advance. This is the place to solve coordination problems before they hit the field.

The Takeaway

Schedule compression is real and sometimes unavoidable. But coordination work can't be compressed as aggressively as construction work. Coordination is a precondition for efficient construction, not an optional prep task. Teams that protect coordination time when the schedule compresses actually recover the lost time faster, because they don't spend the acceleration budget on field rework. If compression is on the table, the first conversation should be: "What coordination activities are non-negotiable and how do we protect them?" Everything else is negotiable.