MEP coordination in preconstruction: assign the interfaces before comparing trade prices

MEP coordination can reveal responsibilities beyond one trade’s drawings. Review supports, openings, controls, access, testing and complete package coverage.

Guide3 min read

Published

Construction scaffolding interior

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.

Book a demo
On this page
  1. Locate the project’s coordination requirements
  2. Build an interface list that can be assigned
  3. Compare the proposal’s boundary with the intended package
  4. Preserve unresolved design and scope questions separately
  5. Keep the package and estimate connected as coordination develops

MEP coordination addresses how mechanical, electrical and plumbing systems fit and function together within the project. In preconstruction, the GC also needs to determine which packages carry the work created at those interfaces. A coordinated layout does not by itself prove that supports, openings, controls, access or testing have been assigned and priced.

The responsible designers and coordination team resolve the technical arrangement. The estimator's review asks whether the issued requirements and assumptions are represented in the trade scopes and proposals.

Locate the project’s coordination requirements

Read the issued drawings, specifications, design responsibilities and coordination deliverables. Identify which information is contractual, which is a working model and which questions remain open.

AIA's BIM contract-document discussion makes document status a deliberate contract question. Do not assume every model view carries the same authority as the issued contract set.

Build an interface list that can be assigned

For each important interface, record the initiating system, required related work, responsible package and source. An illustrative equipment installation can affect structural supports, power, controls, penetrations, firestopping, access and commissioning. Verify which of those obligations the actual package requires.

The HVAC scope guide and electrical-exclusion review provide more detailed trade examples. Do not merge every interface into one generic “coordination included” note.

Compare the proposal’s boundary with the intended package

Read qualifications about wiring, controls, openings, sleeves, testing and work by others. Follow the requirement into the other proposals before deciding the exclusion is covered elsewhere.

The firestopping guide demonstrates why an interface can remain unowned even when every major trade has submitted a price. A section reference and a bidder acknowledgment are useful inputs, not completed responsibility decisions.

Preserve unresolved design and scope questions separately

Identify which questions require a technical answer and which require a procurement or package assignment. State what the estimate carries while each remains unresolved, who approves that basis and which answer triggers another review.

Do not price an invented technical solution merely to close an administrative checklist. Conversely, do not let a pending design question erase a known obligation from the review.

Keep the package and estimate connected as coordination develops

Piper's Scope Generation helps organize requirements into reviewable trade scope, and Bid Leveling compares proposals against that reference. Both build on the same project understanding and preserve source-linked findings.

The project team still resolves technical coordination and approves responsibility boundaries. When those decisions change, reopen the affected proposal and carry instead of updating the model alone.

For South Brooklyn Marine Terminal review, identify the exact port or electrical contract and its handover points rather than assuming the whole offshore-wind program is one package.

The coordinated system also has to be started, tested and handed over. Use a building commissioning responsibility matrix to assign trade attendance and retests.

ShareLinkedInX

Where this fits in Piper

Scope Generation

Turn drawings, specifications, addenda, and company standards into source-backed trade scopes.

Bid Leveling

Compare subcontractor bids against the intended scope so the low number does not hide an expensive gap.

Related reading

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

See Piper on your project

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.