Engineering Change Order (ECO) for Medical Devices: Complete Process Guide

Why Engineering Change Orders Matter in Medical Devices

Change is constant throughout the lifecycle of a medical device. Materials get substituted, manufacturing processes improve, software updates address bugs, supplier changes force redesigns, and post-market surveillance reveals opportunities for enhancement. Every one of these changes — if not properly controlled — can compromise device safety, trigger regulatory violations, or result in product recalls.

The Engineering Change Order (ECO) is the formal mechanism that ensures every modification to a medical device or its manufacturing process is identified, evaluated, approved, documented, and verified before implementation. Under FDA's Quality Management System Regulation (QMSR), effective February 2, 2026, which incorporates ISO 13485:2016 by reference, design change control is a mandatory requirement — not a suggestion.

This guide covers the complete ECO process from initiation through implementation, with specific focus on regulatory requirements, risk-based decision-making, and practical implementation for medical device manufacturers.

ECO, ECR, and ECN: Understanding the Terminology

The engineering change process involves three distinct document types. While terminology varies across organizations, the most widely used convention in the medical device industry is:

The flow is always: Request → Review & Approval → Implementation → Notification. Some organizations combine the ECO and ECN into a single document. What matters is that every change follows this sequence regardless of what you call each step.

How ECO Relates to Broader Change Control

ECO is a subset of change control that specifically addresses modifications to product design, specifications, drawings, manufacturing processes, and associated documentation. Broader change control under ISO 13485 also covers QMS process changes, supplier changes, and organizational changes. Design changes — managed through ECOs — typically receive the most scrutiny because they can directly affect device safety and regulatory status.

Regulatory Requirements for Design Changes

FDA QMSR (21 CFR Part 820, Effective February 2, 2026)

The QMSR incorporates ISO 13485:2016 by reference. The former 21 CFR 820.30(i) required manufacturers to "establish and maintain procedures for the identification, documentation, validation or where appropriate verification, review, and approval of design changes before their implementation." Under QMSR, this requirement now aligns with ISO 13485 Clause 7.3.9, which states:

"The organization shall document, review, and approve design changes, as appropriate, before implementation. The review of design changes shall include evaluation of the effect of the changes on constituent parts and product already delivered."

Key FDA expectations include:

• Changes must be identified, documented, verified or validated, reviewed, and approved before implementation

• The effect on already-delivered products must be evaluated

• Changes to the device, manufacturing process, or labeling that affect safety or effectiveness may require a new regulatory submission

ISO 13485:2016 Clause 7.3.9

ISO 13485 mentions change control over 30 times throughout the standard. The most relevant clauses:

EU MDR Article 16 and Annex IX

Under the EU Medical Device Regulation (MDR 2017/745), substantial changes to a device may require re-assessment by the Notified Body. Manufacturers must have a documented change control procedure and must notify their Notified Body of changes that affect the device's conformity with the essential safety and performance requirements.

The Complete ECO Process: Step by Step

Step 1: Change Identification and Initiation (ECR)

The process begins when someone identifies a need for change. Common triggers include:

• Customer complaints revealing a design weakness

• CAPA investigations requiring corrective action

• Supplier changes forcing material or component substitution

• Process improvements identified during manufacturing

• Regulatory updates requiring compliance modifications

• Nonconformance management identifying design-related root causes

• Risk management activities revealing unacceptable risk levels

• Post-market surveillance data indicating performance issues

The initiator completes an Engineering Change Request (ECR) that includes:

1. Description of the proposed change — What exactly is being changed and how

2. Rationale — Why the change is needed, with supporting data

3. Affected items — Part numbers, assemblies, documents, specifications

4. Urgency classification — Emergency, expedited, or routine

5. Preliminary risk assessment — Initial evaluation of potential impacts

Step 2: Impact Assessment

A cross-functional team evaluates the proposed change across multiple dimensions:

Step 3: Risk and Regulatory Evaluation

This step is critical and often overlooked or given insufficient attention:

Risk Assessment:

• Review and update the device risk analysis (per ISO 14971) to reflect the proposed change

• Evaluate whether the change introduces new hazards or increases the severity or probability of existing harms

• Document the risk evaluation in the ECO record

Regulatory Notification Assessment: For FDA-regulated devices, determine whether the change requires a new 510(k) submission using the decision framework in FDA's guidance "Deciding When to Submit a 510(k) for a Change to an Existing Device":

For EU MDR devices, consult your Notified Body's change notification procedure. Substantial changes typically require prior approval before implementation.

Step 4: Verification and Validation Planning

The ECO must define what verification and/or validation activities are required:

• Design verification: Does the changed device still meet design input requirements?

• Design validation: Does the changed device still meet user needs and intended use?

• Process validation: If the change affects manufacturing, does the updated process consistently produce conforming product?

• Software verification: If the change involves software, have all affected functions been re-tested?

The level of V&V effort should be proportional to the risk and complexity of the change. A minor label correction needs less verification than a material substitution in an implant.

Step 5: Cross-Functional Review and Approval

The ECO is reviewed and approved by a cross-functional team. For medical device companies, this typically includes:

Many organizations use a Change Control Board (CCB) — a standing committee that meets regularly to review and approve ECOs. The CCB structure should be documented in your change control SOP, including quorum requirements and decision authority levels.

Step 6: Implementation

After approval, the change is executed according to the implementation plan defined in the ECO:

1. Update all affected documents — drawings, specifications, work instructions, SOPs

2. Revise the DHF — add change records, updated risk analysis, V&V results

3. Update the DMR — ensure Device Master Record reflects the new revision

4. Disposition existing inventory — scrap, rework, use-as-is with justification, or return to supplier

5. Execute V&V activities — perform planned verification and validation

6. Update training records — ensure affected personnel are trained on the changes

7. Communicate to affected parties — issue ECN to manufacturing, supply chain, distributors

Step 7: Closure and Effectiveness Check

After implementation:

1. Verify completeness — Confirm all action items from the ECO have been completed

2. Review V&V results — Ensure all acceptance criteria were met

3. Update the DHF — File all records associated with the change

4. Effectiveness check — For changes resulting from CAPA, verify the change actually resolved the issue

5. Close the ECO — Document completion with signatures and dates

ECO Process Flow Summary

Change Trigger → ECR Created → Impact Assessment → Risk & Regulatory
Evaluation → V&V Planning → Cross-Functional Review → CCB Approval →
Implementation → V&V Execution → Documentation Update → ECN Issued →
Effectiveness Check → ECO Closure

Documentation Requirements: What Goes in the ECO Record

A complete ECO record should contain:

Common Mistakes and How to Avoid Them

1. Implementing Changes Before Approval

This is the single most common audit finding. Any change to a released design must be approved before implementation — no exceptions. Emergency changes should follow an expedited approval process, not bypass approval entirely.

2. Insufficient Impact Assessment

Treat every change as potentially affecting the entire system. A material change in a non-critical component might affect biocompatibility. A software update in a monitoring function might affect alarm reliability. The cross-functional review exists precisely to catch these cascade effects.

3. Incomplete DHF Updates

The Design History File must reflect the complete design history, including all changes. Each ECO should either be filed in the DHF or referenced from it. Missing change records are a frequent FDA 483 observation.

4. Skipping V&V for "Minor" Changes

The level of verification should be proportional to risk — but some verification is always required. Even a label change should be verified for accuracy. Document the rationale for the V&V approach in the ECO.

5. Ignoring Inventory Disposition

When a design changes, existing inventory (finished goods, work-in-progress, raw materials) must be addressed. Failing to disposition inventory leads to mixing old and new revisions — a direct quality system violation.

Digital ECO Management: eQMS vs. Manual Systems

Electronic systems also support 21 CFR Part 11 compliance for electronic records and signatures, which is critical if your ECO process is fully digital.

ECO Classification by Urgency

Emergency ECOs must still be documented, reviewed, and approved. The difference is the timeline — not the rigor. All emergency ECOs should undergo a retrospective full review within a defined period (typically 5 business days).

ECO vs. Other Change Mechanisms

In practice, complex changes often require multiple change mechanisms. A material substitution might trigger an ECO (design change), a PCN (process change), and a DCR (document updates). The ECO serves as the umbrella document that coordinates all related changes.

Comparison: ECO Process in Medical Devices vs. Other Industries

Building an Effective ECO SOP

Your change control procedure should address:

1. Scope — What types of changes require an ECO vs. a simpler document change

2. Roles and responsibilities — Who initiates, reviews, approves, implements, and closes

3. Classification criteria — How changes are categorized by urgency and impact

4. Impact assessment template — Standardized form for evaluating cross-functional effects

5. Risk assessment requirements — When and how to update risk analysis

6. Regulatory assessment checklist — Decision tree for submission/notification requirements

7. V&V requirements — How to determine appropriate verification and validation

8. Approval authority matrix — Who can approve changes at each classification level

9. Implementation procedures — How changes are executed and communicated

10. Closure criteria — What must be completed before an ECO can be closed

11. Effectiveness monitoring — How to verify the change achieved its intended outcome

12. Metrics and trending — How to track ECO cycle time, volume, and effectiveness

Key Metrics for ECO Process Performance

Frequently Asked Questions

When is an ECO required vs. a simple document revision?

An ECO is required when the change affects device form, fit, function, safety, or effectiveness. Simple document clarifications, administrative updates, or formatting changes that do not affect product quality can use a Document Change Request (DCR). When in doubt, use the ECO process — over-controlling a change is always preferable to under-controlling it.

Does every design change require a new 510(k)?

No. FDA's guidance document "Deciding When to Submit a 510(k) for a Change to an Existing Device" provides a risk-based decision framework. Changes that could significantly affect safety or effectiveness typically require a new 510(k). Minor changes that do not affect the device's substantial equivalence can be documented through your internal change control process without a new submission.

How do ECOs relate to CAPA?

CAPA investigations often identify the need for design or process changes, which are implemented through ECOs. The CAPA record should reference the ECO number, and the ECO should reference back to the CAPA. This linkage provides the traceability that regulators expect.

Can we implement a change before ECO approval in an emergency?

You may implement emergency changes under a documented expedited process, but you must still perform a review and approval — even if compressed. The full ECO documentation must be completed retroactively, typically within 5 business days. Uncontrolled implementation without any review is a regulatory violation.

What happens to existing inventory when a design changes?

Existing inventory must be dispositioned as part of the ECO. Options include: use-as-is (with documented justification), rework to the new specification, scrap, or return to the supplier. The disposition decision must be documented in the ECO record.

How does QMSR affect ECO requirements?

The QMSR, effective February 2, 2026, incorporates ISO 13485:2016 by reference. This means the ISO 13485 Clause 7.3.9 requirements for design change control now have direct regulatory force in the U.S. The core requirements (identify, document, verify/validate, review, approve before implementation) remain consistent with the former 21 CFR 820.30(i), but the ISO framework adds emphasis on evaluating the effect on already-delivered products and maintaining traceability throughout the change lifecycle.

How should we handle ECOs for contract-manufactured devices?

The original equipment manufacturer (OEM) retains design authority and must approve all design changes. Contract manufacturers may initiate ECRs, but the ECO approval must come from the OEM's designated change control authority. The quality agreement between OEM and contract manufacturer should clearly define change control roles, responsibilities, and communication requirements.

What is the relationship between ECOs and configuration management?

ECOs are the primary tool for maintaining configuration control. Each approved ECO defines the new configuration baseline — the updated set of specifications, drawings, and procedures that define the device at that revision level. Configuration management ensures that the current approved configuration is always identifiable and that only the approved configuration is manufactured and distributed.

Do software changes require ECOs?

Yes. Software changes in a medical device (SiMD) or standalone software that is a medical device (SaMD) must go through the same change control process. Software-specific considerations include regression testing, version control, and whether the change affects the device's clinical function (which may trigger a new regulatory submission).