Cross-trade permit-submittal framework

MEP Coordination Questions to Resolve Before a Permit Submittal

Before a multi-trade submittal moves forward, can the project team make the equipment information, trade interfaces, architectural impacts, and next decision owners visible together?

Project-team coordination framework

Organize the questions across the MEP interfaces before documents change hands.

Mechanical, electrical, plumbing, and architectural information often travel through different contacts and document views. This framework helps architects, engineers, GCs, and trade partners keep the open coordination questions connected to the people and records needed for the next project handoff.

Meridian provides independent advisory review to help organize project information and coordination questions. It is not engineering or legal advice, a code excerpt, a sealed design service, or a promise of permit approval or any other outcome.

Original MEP interface map

Put the shared coordination questions between the disciplines—not inside one trade's notes.

This visual is a question register for organizing a permit-submittal conversation. It does not provide engineering solutions, code excerpts, or a direction to proceed.

MECHANICAL

Equipment, air paths, access, and coordination references

PLUMBING

Piping routes, connections, access, and space questions

Shared interface questions

What information is current, who confirms it, and where should it appear?
What routing, clearance, access, or sequence question affects another discipline?
What architectural condition or project document needs to stay connected to the question?
Who owns the next handoff to the responsible professional, project team, or AHJ process?

ELECTRICAL

Loads, connections, pathways, and equipment coordination

ARCHITECTURAL + PROFESSIONAL INPUTS

Penetrations, chases, ceiling zones, shafts, and responsible-professional direction

Coordination question areas

A practical agenda for the team preparing a coordinated MEP submittal.

These prompts support information organization. They do not replace licensed professional judgment, engineering services, local requirements, or the AHJ's process. The AHJ and responsible licensed professionals retain final authority.

Request Plan Review Scope

Confirm equipment data and decision owners

Which equipment selections, capacities, electrical loads, connection information, and design-basis references are current? Record who can confirm each item and which project document should reflect the confirmed information.

Trace routing and clearance questions

Where do mechanical runs, electrical pathways, plumbing piping, access needs, and structural or architectural constraints intersect? Keep each routing or clearance question attached to its location, related disciplines, and next owner.

Identify architectural coordination impacts

Which penetrations, chases, ceiling zones, shafts, access locations, wall conditions, or room layouts need a coordinated project response? Identify the document views and responsible professionals connected to each question.

Maintain one action register

Use a shared record for the open question, owner, affected document, and next handoff. This keeps the team focused on what information remains unresolved without treating the register as a design direction or approval path.

Bring broader references into the conversation

When the team needs neutral preparation material before the next handoff, explore Meridian's building-code resources. Confirm project-specific requirements with the responsible professionals and the AHJ.

Open-question action register

Keep every coordination question tied to an owner, a document, and the next handoff.

Use this as a planning record for project communication. It does not determine technical solutions, code compliance, or permit outcomes.

Open question	Owner	Affected document	Next handoff
What current equipment and load information needs confirmation?	Responsible design professional or designated project contact	Equipment schedule, electrical information, related project references	Confirm the current record and route updates through project document control
Where do mechanical, electrical, plumbing, and architectural pathways intersect?	Coordinating project team and discipline contacts	Plans, sections, reflected ceiling information, coordination notes	Log the location-specific question and identify the next responsible reviewer
Which architectural conditions may be affected by the MEP interfaces?	Architectural lead and responsible professionals	Architectural plans, wall or shaft details, access information	Connect the question to the current document set and project communication path

Project-specific next step

Request an independent advisory plan-review scope for the MEP coordination questions your team is organizing.

Share the project type, location, disciplines involved, current documents, and the coordination questions that need a clear handoff. Meridian can confirm whether the requested advisory scope is a fit before asking for detailed documents.

Request Plan Review Scope

Meridian is an independent advisory service, not the Authority Having Jurisdiction. Final code interpretation and approval rest with your AHJ.