Build Your Project With Confidence Meet Our Engineering Experts
How Engineering Teams Manage Design Changes During Project Development

How Engineering Teams Manage Design Changes During Project Development

Design changes are a normal part of many engineering and construction projects. Client requirements can evolve, site conditions can reveal new information, authorities can request revisions, and coordination between disciplines can uncover issues that require a different design solution.

When changes are handled informally, even a small modification can create conflicts elsewhere in the project. When they are controlled and documented, project teams have a clearer understanding of what changed, why it changed, and what needs to happen next.

What Is Design Change Management?

Design change management is the structured process used to control modifications to an engineering or construction project’s approved design.

It typically involves:

  • Identifying the proposed change.
  • Recording why the change is required.
  • Assessing its technical impact.
  • Evaluating cost and schedule implications.
  • Coordinating affected disciplines.
  • Obtaining the required approvals.
  • Updating drawings, models, and specifications.
  • Communicating the change.
  • Tracking implementation and verification.

A controlled design change has a traceable record. The project team can identify the original requirement, the proposed modification, the reason for the change, the people responsible for reviewing it, and the final approved solution.

Why Do Design Changes Occur During Project Development?

Design changes can originate from many different sources. Some are the result of new information, while others are driven by project requirements, coordination, availability, or regulatory considerations.

Changes in Client Requirements

Client requirements can evolve as a project develops.

Examples include:

  • Changes in space requirements.
  • New operational needs.
  • Changes in building functionality.
  • Revised project priorities.
  • Changes to equipment or user requirements.

A client may initially require a particular layout and later determine that additional space or a different operational arrangement is needed.

Site and Existing-Condition Discoveries

Early designs are sometimes based on surveys, investigations, or existing information that does not reveal every condition.

Further investigation may identify:

  • Unexpected site conditions.
  • Existing structural elements.
  • Unrecorded services.
  • Different site dimensions.
  • Ground conditions that require a revised approach.

When new information becomes available, the engineering team may need to modify the design to reflect actual conditions.

Regulatory or Authority Requirements

Projects may also require design adjustments following authority comments, approvals, or changes to applicable requirements.

Depending on the project and jurisdiction, this can affect areas such as:

  • Building design.
  • Fire and life safety.
  • Accessibility.
  • MEP systems.
  • Structural requirements.
  • Documentation.

The applicable requirements and approval process vary by project, so changes should be assessed against the specific regulatory framework governing the development.

Coordination Issues

Design coordination is another common source of change.

For example:

  • An architectural layout may conflict with structural elements.
  • An MEP system may clash with another service.
  • Equipment may require more space than originally allocated.
  • Maintenance access may not be sufficient.
  • Service routes may need to be adjusted.

A design change introduced to resolve one issue can also affect other disciplines, which is why multidisciplinary coordination is important.

Materials, Equipment, or Supply Constraints

Specified materials or equipment may become unavailable, have extended lead times, or become impractical for procurement or installation.

In these situations, an alternative may need to be assessed.

The replacement should be evaluated for factors such as:

  • Technical performance.
  • Dimensions.
  • Compatibility.
  • Energy performance.
  • Installation requirements.
  • Maintenance.
  • Cost.
  • Availability.

A substitution should therefore be treated as an engineering change rather than simply replacing one product with another.

The Engineering Design Change Management Process

1. Identify and Record the Proposed Change

The first step is to clearly document what needs to change and why.

The change record should establish:

  • What needs to change.
  • Why the change is required.
  • Who requested it.
  • Which part of the project is affected.
  • Relevant drawings or documents.
  • The date of the request.
  • The current design revision.

Creating a traceable record helps prevent verbal instructions or informal modifications from becoming part of the project without proper technical review.

2. Assess the Technical Impact

The next step is to understand what the proposed change could affect.

Depending on its scope, the assessment may consider:

  • Architectural design.
  • Structural systems.
  • MEP systems.
  • Materials.
  • Safety.
  • Building performance.
  • Constructability.
  • Maintenance requirements.

A change that appears small in one discipline can have significant consequences elsewhere.

For example, moving an internal wall could affect structural elements, HVAC distribution, electrical outlets, lighting, fire protection, and plumbing.

This is why design change impact assessment should consider the wider project rather than only the discipline that initiated the change.

3. Evaluate Cost and Schedule Implications

Before approval, project stakeholders should understand the potential consequences of the change.

The assessment may include:

  • Additional materials.
  • Additional engineering work.
  • Construction costs.
  • Procurement implications.
  • Potential rework.
  • Schedule impact.
  • Impact on existing contracts or activities.

This information allows stakeholders to make informed decisions about whether and how the change should proceed.

4. Coordinate With Other Disciplines

Multidisciplinary coordination is one of the most important parts of the engineering change process.

A change may require updates to:

  • Architecture.
  • Structure.
  • Mechanical systems.
  • Electrical systems.
  • Plumbing.
  • Fire protection.
  • Specialist systems.

The affected disciplines should review the proposed modification before it is finalized.

This helps ensure that solving a problem in one part of the design does not create another problem elsewhere.

5. Obtain the Required Approvals

Once the technical and project impacts have been properly worked through, the proposed change can be moved into whatever approval process the project calls for.

Depending on how the project is structured, the stakeholders involved may include: 

  • Client or project owner.
  • Design consultant.
  • Project manager.
  • Contractor.
  • Relevant authorities, where applicable.

Not every project follows the same approval structure.

The important principle is that changes should receive the appropriate design change approval before they are incorporated into the controlled project information or implemented on site.

6. Update Drawings, Models, and Specifications

After approval, the project information needs to reflect the new design.

Depending on the change, this may include updating:

  • Construction drawings.
  • BIM models.
  • Specifications.
  • Schedules.
  • Engineering calculations.
  • Equipment information.
  • Other affected documentation.

Version control is critical.

If a revised drawing is issued but an outdated version remains in circulation, different project teams may work from conflicting information.

A controlled design revision process helps ensure that the approved information is identifiable and accessible to the people who need it.

7. Communicate the Change

An approved change is only effective if the relevant people know about it.

Communication may need to include:

The communication should make clear:

What changed?

Why did it change?

When does the change take effect?

Clear communication helps reduce the possibility of one project team continuing to work from superseded information.

8. Verify Implementation

Change management does not end when a drawing is revised.

The project team should verify that:

  • The revised design was correctly implemented.
  • Superseded information is no longer being used.
  • Related disciplines have incorporated the change.
  • Site work reflects the approved revision.
  • Relevant documentation has been updated.

This final step closes the loop between design approval and physical implementation.

How BIM Helps Engineering Teams Manage Design Changes

BIM can provide valuable support for construction project coordination and design change management.

A coordinated model can help project teams:

  • Centralize project information.
  • Update multiple building elements.
  • Identify clashes.
  • Coordinate different disciplines.
  • Visualize proposed changes.
  • Review design revisions.
  • Identify potential downstream impacts.

Consider a simple example: moving an internal wall.

The architectural change may appear straightforward, but the wall could affect:

  • Structural elements.
  • HVAC distribution.
  • Electrical outlets.
  • Lighting.
  • Fire systems.
  • Plumbing.
  • Ceiling layouts.

A coordinated BIM model can make these spatial relationships easier to visualize and review before the change reaches construction.

However, BIM is a supporting tool, not a replacement for engineering judgment.

How Design Changes Can Affect Project Cost and Schedule

Poorly managed design changes in construction can create consequences beyond the original modification.

Potential impacts include:

  • Rework.
  • Material waste.
  • Additional engineering hours.
  • Procurement changes.
  • Contractor claims.
  • Construction delays.
  • Coordination problems.
  • Repeated inspections or approvals.

For example, changing the specification of an installed component may require new procurement, removal of the original material, revised installation, and coordination with other trades.

However, it is important not to assume that every change increases cost or delays the project.

Some changes can:

  • Reduce material costs.
  • Improve constructability.
  • Resolve coordination problems.
  • Reduce future maintenance requirements.
  • Prevent more significant problems later.

The important factor is understanding the change’s potential impact before implementation.

This is why design risk management and structured change control are important components of engineering project management.

Common Design Change Management Challenges

Unclear Change Requests

A change request without sufficient technical information can lead to different interpretations by different project teams.

The request should clearly identify what is changing and the reason behind it.

Poor Communication

One discipline may implement a modification without informing the other teams affected by it.

This can create new coordination problems.

Outdated Drawings

Site teams may accidentally use superseded drawings when document control is not properly maintained.

Uncoordinated Revisions

Updating one drawing without updating related disciplines can create inconsistencies.

Late Changes

Changes introduced after procurement or construction has progressed can have greater consequences because more project activities may already depend on the original design.

Lack of Change Tracking

Without a centralized record, teams may struggle to determine:

  • Which changes have been requested.
  • Which have been approved.
  • Which are still under review.
  • Which revision is currently valid.
  • Whether the approved change has been implemented.

Keeping a structured change register gives everyone involved a clearer picture of where things stand throughout the project.

Best Practices for Managing Engineering Design Changes

Managing design changes well takes two things working together — a structured process and the kind of project discipline that keeps it running consistently.


The practices that tend to make the biggest difference include:

  1. Establish a formal change-control process.
  2. Document every significant design change.
  3. Assess technical, cost, and schedule impacts before approval.
  4. Involve affected disciplines early.
  5. Maintain clear drawing and model version control.
  6. Use BIM for multidisciplinary coordination where appropriate.
  7. Communicate approved changes to all affected stakeholders.
  8. Maintain a centralized change register.
  9. Verify that approved changes have been implemented correctly.
  10. Review recurring changes to identify underlying design or coordination problems.

Change management can therefore provide insight into broader project risks rather than simply recording individual modifications.

Design Change Management vs. Design Review

Design review and change management are closely related, but they serve different purposes.

Design ReviewDesign Change Management
Evaluates the designManages a proposed modification
Identifies potential issuesControls how a change is introduced
Often occurs at defined design milestonesCan occur throughout project development
Focuses on design quality and coordinationFocuses on the change’s impact and implementation
Helps prevent problemsHelps control necessary changes

An effective design review can identify potential issues before they require changes later.

At the same time, not every change can or should be avoided. Projects evolve, and new information becomes available.

How Engineering Consultants Support Design Change Management

A multidisciplinary engineering consultant can help project teams maintain technical control as the design develops.

UGCE can support developers and project owners through:

  • Technical assessment of proposed changes.
  • Architectural and engineering coordination.
  • Design change impact assessment.
  • BIM coordination.
  • Drawing and specification updates.
  • Design reviews.
  • Change documentation.
  • Constructability assessment.
  • Communication between project stakeholders.
  • Technical support during implementation.

The objective is not to prevent every change.

The real purpose is to give project teams a clear handle on why a change is needed, what it touches, how it needs to be coordinated, and how it can be carried out without letting the wider project start to slip.

Conclusion

Engineering design changes are not necessarily a sign of poor project planning.

Client requirements evolve. Site conditions become clearer. Authorities may request revisions. Materials and equipment availability can change. Coordination reviews can uncover issues that require a different solution.

The greater risk is uncontrolled design change.

A structured process allows engineering teams to:

  • Understand why a change is needed.
  • Assess its wider technical impact.
  • Evaluate cost and schedule implications.
  • Coordinate affected disciplines.
  • Obtain the appropriate approvals.
  • Update drawings, models, and specifications.
  • Communicate the revision.
  • Verify implementation.

consultancy, design coordination, BIM coordination, design reviews, and technical project support throughout project development.

Got changes coming up on a project? Reach out to UGCE to talk through how our engineering and design coordination services can help you stay on top of them without losing control of quality, cost, schedule, or technical requirements.

X

Welcome 👋 This is the UGCE team.
?How can we help you

#