What Clients Get Wrong Before They Send Us a Project
Five handoff gaps that quietly cost an MEP project weeks of schedule — and how to close them before you send us your next one.
Most delays on an MEP project aren't caused during design. They're baked in before we draw a line — in the handoff. After enough projects, and enough time reviewing other people's, you start to see the same avoidable stumbles at the start, and how much timeline they quietly cost downstream.
None of these make anyone a bad client. They're just the gaps that turn a smooth project into a bumpy one. Here are the five I see most, and how to close them before you send your next project to any MEP team.
Most MEP project delays trace to five handoff gaps: incomplete backgrounds, no named decision-maker, a fuzzy scope split, unconfirmed jurisdiction details, and late equipment selections. Closing these before a project starts is the single highest-leverage thing a client can do to keep an MEP project on schedule.
1. Sending Incomplete or Outdated Backgrounds
The most common one. We get the architectural, start coordinating around it, and then a new version lands with the walls moved. Everything downstream — equipment locations, routing, load points — now has to be reworked. Or the backgrounds are missing the info we need to even start: no ceiling heights, no reflected ceiling plan, no site plan.
Close it: send the current, coordinated backgrounds, and flag anything still in flux. If a change is coming, we'd rather wait a day for the real version than redraw around a placeholder. For a primer on what a complete set should include, see how to read MEP drawings.
2. Not Naming a Decision-Maker
Projects stall when questions have nowhere to go. We hit a coordination question — a routing conflict, an equipment choice, a code interpretation — and there's no clear person to answer it. Days pass. Momentum dies.
Close it: name a point of contact who can actually make calls, and tell us how fast we can expect answers. A project with a responsive decision-maker typically moves much faster, because coordination questions get resolved before they stall downstream design work. These are the same habits behind solid consultant coordination — see our guide on MEP coordination best practices.
3. Leaving the Scope Split Fuzzy
On a lot of projects, some scope belongs to others — the aquatics consultant's pool, the kitchen consultant's equipment package, a specialty vendor's hazardous-area work. When the line between "yours" and "theirs" isn't drawn at the start, things fall in the gap or get done twice.
Close it: confirm the scope split up front — what we're engineering, what's by others, what we coordinate around. A clear boundary at kickoff prevents the "I thought you had that" conversation at 90%. For the fuller breakdown of what's typically ours versus by others, see MEP scope: who's responsible for what.
4. Skipping the Jurisdiction Details
The code isn't just the national model code — it's the national code plus the local amendments, the utility's requirements, and the specific energy path that jurisdiction accepts. When a project arrives without those details confirmed, we either chase them or make assumptions, and assumptions are what plan reviewers flag.
Close it: tell us the jurisdiction and anything you already know about its quirks. We confirm the rest — but a head start here heads off a whole category of comments. Curious what jurisdiction gaps actually trigger at review? We cover it in why MEP sets bounce at plan check.
5. Treating Equipment Selections as an Afterthought
Owner-preferred vendors, a kitchen equipment package, medical or process equipment — these carry real loads and real rough-in requirements. When they show up late, they can force changes to work that's already coordinated.
Close it: get the equipment cut sheets and vendor preferences to us as early as you have them. Reconciling real equipment early is far cheaper than reconciling it after the set is coordinated. Long-lead equipment especially benefits from an early flag — rough-in dimensions often can't wait for a cut sheet that shows up after design development is already underway.
The MEP Project Kickoff Checklist
Whether it's a one-off project or you're just starting to outsource MEP engineering as an ongoing white-label MEP relationship, the fundamentals of a clean MEP project handoff don't change — only the paperwork around it does. We don't need a signed contract's worth of documentation at kickoff; we need the handful of items that actually determine how fast design can move. Here's what needs to be settled before design begins:
- Current architectural backgrounds (the latest, not a superseded set) — plus the site plan and reflected ceiling plan.
- Confirmed ceiling heights and any tight-plenum constraints.
- Equipment schedules / vendor selections (or a flag for what's still provisional).
- Utility information (available service, points of connection).
- A named decision-maker who can resolve coordination questions.
- The jurisdiction (so the adopted code edition and amendments are known up front).
- The scope split — what CoreX designs vs. what's by others (fire protection, structural, civil, low-voltage).
- The target submission / permit date.
None of it is complicated. But every item missing at kickoff is a question that surfaces later — usually as redesign. These are the same owner responsibilities that let a set move toward permit-ready drawings without a detour through rework. Most of it already exists in a folder somewhere before a project starts; the only real step is pulling it together ahead of the first coordination meeting instead of during it. We ask about all of it once, at kickoff — not piecemeal, and not after work is already underway.
What Happens After a Clean Handoff
Once the kickoff information is in, the early weeks of the MEP design process follow a predictable path — mapped out in our guide to MEP design phases (SD/DD/CD):
Background review (confirming we're working from the current set) → kickoff meeting (aligning scope, decision-maker, and dates) → early coordination review (spotting the obvious cross-trade and structural conflicts) → load calculations and system concepts → design development → construction documents.
The point of naming it: a clean handoff lets this run without stalls. A messy one means the first weeks are spent chasing missing backgrounds and unnamed decision-makers instead of designing — which is exactly how a project loses time before anyone notices. The handoff isn't paperwork; it's the thing that decides whether week one is design or archaeology. Get it right at the start, and the same discipline carries through construction coordination once the documents are issued.
Picture two versions of week one. In the first, backgrounds are current, the decision-maker answers a routing question within a day, and the team is running load calculations by day three. In the second, half the week goes to confirming which architectural set is actually final and waiting on a callback about a vendor selection that was supposed to be locked. Same scope, same fee, same schedule on paper — a very different week one.
For architects and GCs juggling multiple consultants, the payoff compounds. A firm that hands off cleanly to its MEP engineer is usually running the same discipline with its structural, civil, and low-voltage consultants — and the reverse tends to be true too. The handoff habit isn't MEP-specific; it's just most visible here because MEP touches nearly every other trade on the set.
Why We Ask These Questions First
If you've worked with us, you've noticed we ask a lot of questions before design starts. This is why. Our pre-design phase exists to surface exactly these gaps — the missing background, the unnamed decision-maker, the fuzzy scope split — before they become schedule problems. It's not bureaucracy; it's one of the reasons many of our projects see smoother plan reviews — fewer comments and less rework.
The best projects almost always start the same way: complete information, a clear point of contact, and an honest scope. Hand a project off that way and everything after it moves faster — with any MEP team, ours included.
Have a project coming up? Schedule a scope call and we'll walk through exactly what to prepare, or see how we work.
Related reading: MEP Design Phases (SD/DD/CD) · Why MEP Sets Bounce at Plan Check · MEP Scope: Who's Responsible for What
Common Questions
Before design starts, hand off current and coordinated architectural backgrounds — not a version that's about to change — a named point of contact who can answer coordination questions quickly, a clear split of what's engineered by you versus by others, the project's jurisdiction and any known local code quirks, and equipment cut sheets or vendor preferences as early as you have them. Closing these five gaps before kickoff is the biggest lever a client has over how fast the project moves.
At minimum, an MEP engineer needs coordinated architectural backgrounds with ceiling heights and a reflected ceiling plan, a site plan, the confirmed project jurisdiction, the scope split against any other consultants or vendors on the project, and a named decision-maker for coordination questions. Missing any of these forces the engineer to chase information or make assumptions — and assumptions are what plan reviewers flag.
Pre-design exists to surface handoff gaps — incomplete backgrounds, an unnamed decision-maker, a fuzzy scope split — before they turn into schedule problems during design or plan check. Projects that start with complete information, a clear point of contact, and an honest scope consistently move faster and clear plan check with fewer comments than projects that skip this step.
Sometimes, yes — but only if you identify exactly what's provisional and which decisions may change once the missing information arrives. Transparent, documented assumptions let design start without locking in something that later forces redesign.
Senior electrical design engineer with 6+ years designing MEP systems for 900+ U.S. projects. Experienced third-party peer reviewer and city plan reviewer.
Connect on LinkedIn →Let's Get the Handoff Right.
Bring us the backgrounds, the decision-maker, and the scope — we'll tell you if anything's missing before it costs you a week of schedule.
Schedule a Scope CallSend Us the Details