How Does MEP Coordination Prevent Construction Change Orders?

MEP coordination is what ensures that every mechanical, electrical, and plumbing system within a building design has a defined space, clear pathways, and documented requirements before construction begins. Technology is a scope that must be coordinated alongside MEP work – because when technology systems aren’t dealt with during the design phase, they often become the primary driver of technology-related change orders.

TL;DR

  •  MEP coordination gives every mechanical, electrical, and plumbing system a defined space, pathway, and set of requirements before construction, and technology is a separate scope that has to be coordinated alongside it.
  • Most technology-related change orders trace back to three root causes: missing or incomplete technology scope in the construction documents, conduit and pathway conflicts, and undersized or improperly specified equipment rooms.
  • Coordinating technology scope during design development, rather than after construction documents are issued, resolves these conflicts on the drawings instead of in the field.
  • A dedicated technology consultant produces the Division 27 and Division 28 drawings and specifications that an MEP engineer's contract does not cover, so contractors can price the full scope accurately. 

 

Construction documents are complete, contractors can price the work accurately, and the field crews aren't discovering coordination gaps that should have been resolved on a drawing. In this blog, we'll break down where technology change orders come from, how coordinating technology with the MEP design prevents them, and why the timing of that coordination matters for commercial building projects.

Where Do Technology Change Orders Actually Come From?

Technology-related change orders on commercial building projects almost always trace back to the same small set of root causes. Understanding what they are makes it easy to see why coordinating the technology scope alongside MEP design prevents them.

The most common change order is a missing or incomplete technology scope in the construction documents. When the technology scope isn't defined during design – when there are no Division 27 drawings, no AV specifications, no access control design – contractors at bid are working with incomplete information. They scope conservatively, include allowances for unknowns, and look to the RFI process to resolve gaps. Every one of those unknowns is a potential change order.

The second most common cause is conduit and pathway conflicts. When conduit routes are specified without knowing what they will carry, they end up the wrong size, in the wrong location, or in conflict with mechanical or structural elements. Resolving those conflicts in the field, whether that means rerouting conduit, relocating equipment, or cutting new wall penetrations, generates change orders that proper coordination during design development would have prevented.

The third is undersized or improperly specified equipment rooms. Telecommunications rooms and equipment rooms sized without technology input routinely end up too small, inadequately cooled, or missing dedicated circuits. Correcting those conditions in the field is expensive – it may require relocating walls, upgrading HVAC, or adding electrical panels.

A change order is almost always a design problem that got caught late.

How MEP Coordination Prevents Change Orders

Coordinating technology scope alongside the MEP design addresses each of these root causes directly. The technology consultant is a specialized design professional who works alongside the MEP engineer, and the two work together with the architect to establish what the building's technology systems require and ensure those requirements are reflected in the construction documents.

Conduit and pathway conflicts get resolved through coordination drawings that show the exact conduit routes each technology system requires, including sizes, locations, termination points, and sleeve requirements through the structure. Those routes are coordinated with the MEP engineer's power and mechanical drawings during design development, which resolves conflicts on paper before they become field problems.

Equipment room sizing is handled by establishing the space, power, and cooling requirements for telecommunications rooms and the main equipment room during schematic design. Those requirements are incorporated into the architectural floor plan and the MEP engineering scope before they are locked into the construction documents.

Technology scope gaps close once the technology consultant produces a complete set of Division 27 and Division 28 drawings and specifications that describe every system the project requires, to what performance standard, and with what infrastructure. These deliverables are not typically covered by the MEP engineer's contract, which is why they call for a dedicated technology consultant. Contractors can price that scope accurately because it is fully documented.

 MEP Coordination and Change Order FAQs 

What Is MEP Coordination in Construction?

 MEP coordination is the process of giving a building's mechanical, electrical, and plumbing systems a defined location, pathway, and space so they do not conflict with each other or with the structure. It happens throughout design so that conflicts are resolved on the drawings rather than discovered in the field. 

How Does MEP Coordination Prevent Change Orders?

 Coordinating technology scope with MEP design closes the gaps that create change orders: conduit routes are sized and located for the systems they carry, equipment rooms are sized with technology input, and Division 27 and 28 scope is fully documented.

When those requirements are settled during design development, contractors price a complete scope, and the field conflicts that drive change orders do not appear. 

Why Are Technology Systems a Common Source of Change Orders?

 Technology is usually the last scope to be defined on a project, so it is the last to surface conflicts. When there are no Division 27 drawings, no AV specifications, and no access control design at bid, contractors scope conservatively and rely on the RFI process to fill gaps, and each unresolved gap becomes a potential change order. 

Does an MEP Engineer Handle Technology Scope?

 An MEP engineer coordinates the power, conduit, and mechanical requirements that support technology, but the detailed design of AV, structured cabling, access control, and network systems sits outside a standard MEP contract. Those deliverables call for a dedicated technology consultant who documents the systems and coordinates them with the MEP drawings. 

When Should Technology Coordination Happen on a Building Project?

 The most valuable coordination happens during design development, while conduit routes, equipment room layouts, ceiling pathways, and structural penetrations are still open.

Coordination attempted after construction documents are issued becomes reactive, identifying problems rather than preventing them. 

What Are Division 27 and Division 28 Drawings?

 Division 27 covers communications and low-voltage infrastructure such as structured cabling and the network backbone, while Division 28 covers electronic safety and security systems such as access control and video surveillance.

A technology consultant produces the drawings and specifications for both so the project's technology scope is complete and biddable. 

How Does Early Technology Coordination Protect a Project Budget?

Early coordination keeps change orders tied to genuine owner-driven scope changes rather than avoidable documentation gaps. When technology requirements are defined and coordinated before the project goes to bid, the construction documents go out complete and the budget holds up through construction.

 

Optimize Your Construction Coordination Technology Systems

The most valuable coordination work happens during design development, when the construction documents are being assembled, and the decisions that drive future field conflicts are still open. Conduit routes, equipment room layouts, ceiling pathway strategies, and structural penetration requirements are all established during DD.

Coordination that happens after CDs are issued is reactive. The decisions have been made without technology input, and the technology consultant's role becomes one of identifying problems rather than preventing them. That's still better than no coordination at all – but it produces worse outcomes than coordination done at the right phase.

Scoping technology alongside MEP during DD means the CDs go out to bid complete. Contractors price the entire scope – and change orders that stem from undefined or uncoordinated technology requirements don't happen, because the requirements were defined and coordinated before the project went to bid.

Ready to learn more about how TMC can coordinate technology scope with your design team? Get started today.

Expert Insights

Read our blog for strategic guidance and analysis from TMC’s technology consultants.

How Early Should Low-Voltage Design Start on a Building Project?

Low-voltage design should begin during schematic design – at the same time the architect is establishing the building's ...

What Does a Technology Consultant for Architects Actually Do?

TL;DR A technology consultant for architects is a design-side professional who defines, coordinates, and documents ...

Technology Consultant for Architects: What Systems Do You Need To Coordinate?

Architects are responsible for ensuring that all building systems, including technology systems, are coordinated and ...

Let’s Build What’s Next

Connect with our team to start planning secure, scalable technology systems that support your mission and future growth.

Get Started