An MEP coordination review connects equipment identity, service requirements, routes, openings, levels, controls, and access with architectural and structural information. Use PDF review to find document questions; use the appropriate models, calculations, and professional review to resolve geometry and engineering requirements.
Agree on the inputs and coordination boundary
Start with the current mechanical, electrical, and plumbing drawings, plus the architectural and structural information for the areas under review. Include fire-protection documents, controls sequences, equipment specifications, and manufacturer information where they affect the chosen scope. Record missing inputs before reviewing.
Choose a manageable unit of work: a plant room, roof equipment group, repeated unit type, or a congested corridor. State which systems and locations are included. That boundary makes it easier to tell the difference between a completed check and an area that nobody reviewed.
Decide who coordinates the response when several disciplines are involved. A penetration question may need both the service designer and structural engineer. Assigning it to “MEP” without identifying the required structural decision leaves the interface unresolved. On mass timber floors, these openings are cut in the factory; see MEP penetrations in CLT floors.
Twelve checks across the source documents
For each item, identify the same equipment or location in the source pair, compare the stated information, and record what the responsible designer needs to decide. The CSV adds space for project references, ownership, status, the response, and closure evidence.
| Review area | Open these sources together | Question to resolve |
|---|---|---|
| Equipment identity | Floor plan tag, equipment schedule, system diagram | Do all sources describe the same unit, quantity, and duty? |
| Power connection | Mechanical schedule, electrical equipment connection data | Are the stated supply characteristics and connection responsibilities reconciled? |
| Controls sequence | Controls diagram, operating sequence, equipment specification | Does each described sensor, interlock, and operating mode have a consistent reference? |
| Drainage interface | Equipment detail, plumbing plan, discharge notes | Is the required drain destination described and connected to the correct system? |
| Floor level | Mechanical/plumbing location, structural plan and datum notes | Are elevations comparable, or is one a finish level and another a structural level? |
| Penetration request | Services route or pit, structural opening detail | Is the opening or recess required by the service addressed by structural information? |
| Ceiling zone | Ceiling plan, duct/pipe routes, building section | Is enough vertical information supplied to investigate the congested zone? |
| Service access | Equipment layout, access panel, manufacturer service information | Does the package describe a usable maintenance approach and the space it needs? |
| Replacement route | Equipment dimensions, doors, hatches, route plans | Has the team identified how the selected equipment reaches or leaves its location? |
| Roof arrangement | Intake/exhaust locations, equipment classification, project criteria | Are separation questions assessed using the actual systems and applicable criteria? |
| Support boundary | Equipment support notes, structural details, trade scope | Who designs and supplies the support, and where is the receiving structure addressed? |
| Protective assembly | Rated assembly plans, service penetrations, project details | Does the penetration condition have a relevant protection detail and a responsible reviewer? |
These are review prompts, not default sizing or clearance requirements. Use the actual design criteria, equipment data, adopted requirements, and engineering analysis for the project. If the package does not establish them, record the information needed rather than substituting a generic value.
Trace an equipment tag through its connections
Choose one equipment tag and write down where it appears. Follow the floor plan to its schedule row, then to the system diagram, controls description, specification, and connection information. Confirm the quantity and function before comparing electrical, hydraulic, or mechanical characteristics.
Build a short dependency list: what supplies the unit, what leaves it, what controls it, what supports it, and what space people need to access it. An isolated equipment schedule rarely answers all five questions. Investigate a missing link without assuming that the other discipline omitted it; the information may be supplied on a separate detail or deferred package.
The published equipment-consistency example concerns requirements that did not align across plans, diagrams, schedules, and specifications. It illustrates why a tag-level review can be useful even when no obvious drawing overlap is visible.
Separate document gaps from geometric clashes
A missing opening reference is a document question. A clash between modeled objects is a geometric question. They may describe related problems, but they require different evidence. A two-dimensional route crossing a beam on plan does not establish their relative elevation or prove an actual intersection.
Autodesk’s Model Coordination documentation describes clash detection using uploaded 3D models. A PDF review can complement that process by investigating schedules, notes, references, and specification requirements that a geometric check may not address. For what a coordinated model adds and where model-only review falls short, see 3D model-based plan review.
When the drawings do not establish whether an installation fits, ask for a relevant section, coordinated model view, or dimensioned detail. Do not infer a verified clearance from a screenshot. Record the unresolved geometry and route it to the team responsible for coordination.
Example: the service needs a structural interface
Groundbook’s mixed-use review included a potential missing-opening issue: a sump shown in mechanical/plumbing information was not represented in the corresponding structural slab or footing area reviewed. The next step was to confirm whether another structural detail addressed it and, if necessary, obtain the intended opening arrangement.
The sample finding is a prompt to reconcile the two disciplines. It does not establish an approved opening size or authorize a site alteration. The service requirements and structural implications need to be resolved together.
For closure, check both sides: the services location and the receiving structural information. If the equipment moves instead, inspect the connections, access, and affected architectural layout. A response is complete only when the documented resolution can be followed through its dependencies.
Use the checklist in a review meeting
Bring the unresolved rows, their source pairs, and the decisions needed. Group duplicate comments about the same root requirement, while retaining affected locations. Agree on an owner and a decision date tied to the next submission, procurement, or construction dependency.
After the meeting, record the response reference and the documents expected to change. Backcheck the updated package before closing each item. Keep an accepted design decision separate from proof that the drawings were revised to express it.
Groundbook supports a source-linked coordination review across the PDF set. Review its potential findings with the responsible engineers, then use your project’s established decision and document-control process to resolve them.