Outsourcing MEP design works. Consultancies use it to absorb workload peaks without hiring, contractors use it for shop drawings and as-builts, and developers use it to get calculation-backed packages at a fraction of in-house cost. MEP work travels unusually well between offices: it is calculation- and drawing-intensive, the deliverables are standardised, and the codes are written down.
When it goes wrong, it almost never goes wrong at the engineering. It goes wrong at the handover — a scope that was never written down, a deliverable list both sides imagined differently, a code assumption nobody checked. After three decades of sitting on the receiving end of these handovers, this is the checklist we wish every client ran before sending a project to any external team, ourselves included.
The 10-Point Checklist
- Put the scope in writing — including what is excluded. "MEP design" can mean anything from a heat-load summary to a full authority-submission package. Name the disciplines (HVAC, electrical, plumbing, fire), the stage (concept, detailed design, shop drawings, as-builts), and — just as important — what is not included. Most outsourcing disputes are two reasonable people holding two different unwritten scopes.
- List the deliverables one by one. Not "drawings and calculations" — a list: load calculations per space, single-line diagrams, ductwork and piping layouts, equipment schedules, specifications, cable schedules. If you cannot list it, you cannot review it, and you will not receive it.
- Name the codes and the market. A package designed to the wrong reference is rework, not a discount. State the governing codes and the authority the package must satisfy — and where two frameworks could apply, decide the design basis up front, exactly as we described in ASHRAE vs CIBSE. A competent partner will ask this question before you do; treat silence on codes as a warning.
- Agree software, versions and formats before work starts. AutoCAD or Revit, which release, native files or exports, and — on BIM projects — the level of development each model element must reach and who owns clash detection. A Revit 2024 model delivered to a Revit 2022 office is a deliverable you cannot open.
- Prepare the input package properly. The quality of MEP output is capped by the quality of architectural input. A complete, current drawing set, the client brief, any survey data, and a named contact for queries. Sending "the latest architecture" twice a week mid-design costs more than any outsourcing saves.
- Fix review gates, not just a deadline. One final deadline invites one final surprise. Break the engagement into stages — concept sign-off, mid-design review, pre-issue check — so course corrections happen while they are cheap. Good remote teams want these gates as much as you do.
- Agree the revision policy in advance. Comments from your internal review: included. Changes because the architecture moved: variation. Authority comments: usually included for the submitted package. Whatever the split, write it down before the first drawing is issued — this is the single most common friction point in outsourced design.
- Check the timeline against the time zones. Offshore time zones are a feature if you plan them — queries sent at your close of business are answered by your morning — and a bug if you don't, because "one quick clarification" can cost a day per round trip. Agree the overlap window and the response time for queries.
- Settle confidentiality and ownership. An NDA covering the project information, and a contract that assigns the deliverables and calculation files to you on payment. Also agree whether the work may be named in the partner's portfolio. None of this is exotic — it simply needs to exist before drawings do.
- Start with a pilot, and price the real thing properly. One building, one floor, one discipline — a small paid pilot tells you more about a partner than any brochure. On pricing: fixed fees suit defined packages and make outsourcing predictable; hourly rates suit open-ended support. Be suspicious of quotes produced without seeing drawings — a serious estimate follows the input package, not the phone call.
Outsourced MEP fails at handovers, not at engineering. A written scope, an itemised deliverables list, a named code basis and staged reviews prevent almost every horror story — and any partner who resists those four things has told you what you need to know.
Red Flags Worth Trusting
- A quote produced before anyone looked at your drawings
- No questions about codes, authority, or market on the first call
- Reluctance to share a comparable past deliverable or take a paid pilot
- "Unlimited revisions" — which in practice means the scope was never defined
- No named engineer responsible for your project
How We Run It
This checklist is also a fair description of our own intake process. When a consultancy or contractor sends us a project for outsourced MEP drafting and design, the first thing they receive is a scope-and-deliverables sheet against their input package — with the code basis stated, the review gates proposed, and a fixed fee and timeline within 24 hours. The design and drawing services pages show what the packages contain, and our free load calculator is an honest sample of how we like numbers presented: assumptions visible, basis stated.
Conclusion
Outsourcing MEP design is not a leap of faith — it is a procurement exercise, and it rewards the same discipline as any other: define what you are buying, stage how you will check it, and agree what happens when things change. Run the ten points above and the worst outcome you are likely to face is a partner who answered them so well you stop thinking of it as outsourcing at all.