What Clients Get Wrong Before They Send Us a Project
Five handoff gaps that can quietly cost an MEP project schedule time — and how to close them before you send us your next one.
- Many delays on an MEP project aren't caused during design; they're baked in at the handoff.
- Name a point of contact who can actually make calls, and say how fast answers can be expected.
- Reconciling real equipment early is far cheaper than reconciling it after the set is coordinated.
Many 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 schedule 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.
Many 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 can help keep an MEP project on schedule.
1. Sending Incomplete or Outdated Backgrounds
A 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 can reduce the "I thought you had that" conversations 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 adopted edition plus the local amendments and the specific energy path that jurisdiction accepts, with the utility's requirements on top. When a project arrives without those details confirmed, we either chase them or make assumptions, and assumptions are something plan reviewers can flag.
Close it: tell us the jurisdiction and anything you already know about its quirks. We'll help confirm the rest — a head start here can head 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 confirmed, or flagged as provisional, before design begins:
| Input | Why it can hold up design if missing |
|---|---|
| Current architectural backgrounds (the latest, not a superseded set) — plus the site plan and reflected ceiling plan | Equipment locations, routing, and load points get coordinated around walls that later move, and all of it has to be reworked. |
| Confirmed ceiling heights and any tight-plenum constraints | Final routing needs confirmed heights; preliminary work can proceed with documented assumptions. |
| Equipment schedules / vendor selections (or a flag for what's still provisional) | Equipment carries real loads and rough-in requirements. Late selections force changes to work that's already coordinated. |
| Utility information (available service, points of connection) | The utility's requirements apply on top of the adopted code. Without them we chase them or make assumptions. |
| A named decision-maker who can resolve coordination questions | Coordination questions have nowhere to go, and design stalls while they wait. |
| The jurisdiction (so the adopted code edition and amendments are known up front — for the energy code, the DOE state energy code portal is a quick first check) | The code is the adopted edition plus local amendments and the accepted energy path, and assumptions here are something plan reviewers can flag. |
| The scope split — what CoreX designs vs. what's by others (sprinkler and suppression, structural, civil, and low-voltage system design other than fire alarm — CoreX still provides the power and pathways for those systems) | Work falls in the gap or gets done twice. |
| The target submission / permit date | Without it there's no date to plan the design phases back from. |
None of it is complicated. But every item missing at kickoff is a question that surfaces later — often as redesign. These overlap with the owner responsibilities in standard owner-architect agreements, and having them in hand can help a set move toward permit-ready drawings with less 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 try to ask about all of it up front, at kickoff, rather than piecemeal once work is 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 can reduce avoidable stalls. A messy one means the first weeks are spent chasing missing backgrounds and unnamed decision-makers instead of designing — which is one way a project can lose time before anyone notices. The handoff isn't paperwork; it can decide 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.
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.
The best projects often start the same way: complete information, a clear point of contact, and an honest scope. Hand a project off that way to help any MEP team, ours included, reduce avoidable delays.
Have a project coming up? Schedule a scope call and we'll walk through exactly what to prepare, or see how we work.
Further 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 the MEP design team covers versus what others cover, 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 can help keep the project moving.
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 something plan reviewers can 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 tend to 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 designer with 6+ years in U.S. MEP design, contributor to 900+ projects, and an experienced third-party peer and plan reviewer.
Connect on LinkedIn →