ECOs From CAD Changes for Medical Device Manufacturing Engineers

Contents
- What a medical device ECO has to prove (and why the CAD change is where it starts)
- A design change lands on a manufacturing engineer's desk: where the ECO usually breaks
- From CAD diff to ECO: generating the change record in your own template
- Linking the change to requirements, FMEA rows and structural or thermal risk
- Review, DFM feedback and release without leaving the design context
- Feeding the design and development file: redlined history and verification evidence
- What to look for in ECO software for medical device teams, and how to book a Tandem demo
- Start your next ECO from the CAD diff: book a Tandem demo
Engineering change order software for medical device teams should turn the CAD change itself into the ECO, in your own template, already tied to the affected requirements, FMEA rows and change history that feed the design and development file. Anything less leaves a manufacturing engineer retyping what the designer already did.
That is the standard to hold a tool to. Medical device manufacturing engineers feel a late change first: a bracket gets thinner, a housing wall moves, a fixture no longer fits. The ECO is supposed to prove the change was reviewed, assessed and approved before implementation. In practice it is often a form filled in from memory after the CAD work is done.
This post follows one design change from the moment it lands on a manufacturing engineer's desk to the moment it is released. It shows where the ECO breaks in a typical process and what it looks like when the CAD diff drives it. Tandem, the context layer for hardware engineering, sits alongside your QMS and PLM for this. It is not a QMS.
What a medical device ECO has to prove (and why the CAD change is where it starts)
A medical device ECO has to prove that a design change was identified, documented, assessed, verified or validated as appropriate, and approved before it was implemented. That is the substance of 21 CFR 820.30(i), and the regulation does not prescribe a specific ECO form.
Since February 2, 2026, FDA's QMSR incorporates ISO 13485:2016, so the language has moved. Clause 7.3.9 requires documented procedures for controlling design and development changes, an assessment of each change's significance, and an evaluation of its impact on components and the product before implementation. Clause 7.3.10 requires a design and development file for each device type or family, including or referencing change records. The old "design history file" is now the design and development file.
A defensible change record, as applicable, captures the change description and reason, the affected design documents and configurations, the impact assessment on design inputs, intended use, risk and labeling, the verification or validation activities and results, review and approval identities with dates, and the effective date.
Look at what comes first: what changed and why. That is a CAD fact. The geometry before, the geometry after, and the reasoning in between are the raw material of the whole record. If the ECO starts anywhere else, the record is already a reconstruction.
A design change lands on a manufacturing engineer's desk: where the ECO usually breaks
The usual ECO breaks at the handoff between the designer's CAD session and the change form. Picture a hypothetical: a designer increases a wall thickness on a pump housing to resolve a thermal hot spot. The CAD file is saved. A message goes out. The manufacturing engineer opens the new revision and has to work out what actually moved.
Three things tend to go wrong from there.
The diff is manual. Someone compares two revisions by eye, or relies on the designer's description. A secondary feature that shifted gets missed, and the ECO describes a smaller change than the one that shipped.
The links are by memory. Which requirements does this wall touch? Which FMEA rows mention thermal or structural failure of this housing? The answer lives in someone's head or in a spreadsheet nobody updated. The ECO lists what the author remembered.
The template is retyped. Your company has an ECO format your quality team trusts. Every change means copying description, reason, affected items and approvals into it by hand.
None of this is a compliance failure on day one. It becomes one in an audit, when the reviewer asks how you assessed the impact on risk and the honest answer is "we checked the ones we thought of." The same pattern shows up outside medical devices, and the robotics ECO walkthrough describes it from the CAD side.
From CAD diff to ECO: generating the change record in your own template
With Tandem, the change record starts from the captured CAD change instead of a blank form. Tandem's Design Changes view shows a before/after 3D CAD diff with a plain-language summary, plus the requirements and annotations the change touches. Tandem's CAD plugin works inside SolidWorks, Onshape, CATIA, NX and Fusion, so the designer keeps working in the tool they already use.
From that captured change, Tandem generates the ECO, ECN and supporting engineering documentation in your own templates. The format your quality team already approved stays the format. What changes is who types it.
For the housing example, the manufacturing engineer opens the Design Change and sees the geometry difference highlighted in 3D, a summary in plain language, and the list of affected requirements. The description, the reason and the affected items are already populated in the ECO template. The engineer's job becomes checking and judging instead of transcribing.
That matters for the evidence too. When the ECO is generated from the captured change, the description of what changed is not an author's paraphrase. It is tied to the actual before and after geometry.
Linking the change to requirements, FMEA rows and structural or thermal risk
The impact assessment is the part of an ECO that regulators and auditors read most closely, and it depends entirely on links. In Tandem, requirements sit in a parent/child hierarchy, and FMEA and risk tables are trace-linked to those requirements. A CAD change that touches a requirement therefore reaches the risk rows connected to it.
Back to the housing. The thicker wall affects a thermal requirement and a structural requirement. Both link to FMEA rows covering overheating and housing fracture. The change surfaces all four, with the affected requirements and annotations from the CAD diff alongside, so the engineer reviews them instead of hunting for them. Mechanical CAD is where structural and thermal risk is born, so this is where the link has to be live.
Requirements in Tandem are also verified continuously against live attributes from CAD, Excel and Google Sheets, and Nominal telemetry. If the new wall thickness pushes a mass or thermal attribute outside its limit, that shows up as a requirement status. It does not show up as a surprise at verification.
This connects directly to the verification evidence your file must reference. For how that traceability looks across a program, see design verification traceability in medical device programs.
Review, DFM feedback and release without leaving the design context
Review and manufacturability feedback should happen on the geometry that changed, not in a separate email chain. Tandem design reviews run in a browser-based 3D viewer that needs no CAD license, so a quality engineer, supplier or manufacturing engineer can open the change without installing anything. Annotations are placed directly on geometry, with replies, mentions and Slack or Teams notifications.
This is where DFM feedback lands. The manufacturing engineer can mark the thicker wall where it creates a molding or machining problem, directly on the 3D geometry. That comment surfaces inside the designer's CAD tool and links to the related requirements. The designer sees the manufacturability issue in the place they already work, before the ECO is approved and not after the first build. Tandem's agents can also review parts for manufacturability, which helps engineers judge it faster.
Release then follows. Tandem includes its own PDM with check-in/check-out, soft revisions and a release workflow, live for SolidWorks. If you run a PLM such as Teamcenter or 3DEXPERIENCE, Tandem works alongside it: custom integrations are built as part of deployments, pushing and pulling data to and from the PLM. Your approved release still lands where your organization expects it.
Feeding the design and development file: redlined history and verification evidence
The design and development file needs to contain or reference change records and the evidence behind them, and a redlined history makes that easy to show. Tandem keeps a redlined change history on requirements that is usable for FDA audit documentation. Every edit to a requirement is visible as a change, with who and when.
For the housing change, the file can reference a connected set: the CAD diff, the generated ECO, the affected requirements with their redlined history, the linked FMEA rows, the review annotations, and the validation evidence stored in the same system. Per QMSR, those records may live in the file or be referenced from elsewhere, such as change-control records. You point at a connected record instead of assembling one under audit pressure.
Tandem is not your QMS. Your QMS remains the system of record for procedures, approvals and signatures. Tandem is where the engineering context behind each change is captured, so what your QMS references is complete and traceable. The same logic applies to other regulated change records, for example AS9100 design change records in aerospace.
What to look for in ECO software for medical device teams, and how to book a Tandem demo
The best engineering change order software for medical device work starts from the CAD change and ends in a record your file can reference. Buyers searching for ECO software usually meet two categories. One is PLM and change-management suites, where the ECO is a workflow object: request, order, approval, audit trail, bill of materials revision control. That fits enterprise-wide change processes. The other is a tool that sits closer to the design itself. Tandem is in the second group and works alongside your PLM and QMS instead of replacing either.
Use these criteria when you evaluate any option:
Does the ECO originate from the CAD change? Ask to see a before/after diff generate the record, not a form a person fills in.
Does it use your template? Your quality team's approved format should be the output.
Are requirements and FMEA rows linked live? Impact on structural and thermal risk should surface on its own, not be recalled.
Is review done on geometry? Manufacturing and supplier feedback should attach to 3D, without a CAD license.
Is the history redlined? Requirement changes should show who changed what and when.
Does it fit beside your QMS and PLM? Integration with Teamcenter, 3DEXPERIENCE or Jama matters more than another standalone silo.
Is it cloud-based with the deployment you need? Tandem runs on AWS by default with an isolated environment per customer, and on-prem deployment is available.
On ECR versus ECO: the request captures the problem and proposal, the order authorizes and executes the change. In Tandem the captured CAD change feeds both, so the request and the order describe the same geometry.
If you want to see a CAD diff become an ECO in your own template, book a Tandem demo.
Start your next ECO from the CAD diff: book a Tandem demo
An ECO is only as trustworthy as its first line, and the first line is what changed in the model. When the record is generated from the captured CAD diff, tied to requirements and FMEA rows, and carried into a redlined history, the manufacturing engineer reviews instead of reconstructing. Bring one real design change from your current program to a Tandem demo and see it become an ECO in your own template.
Visit Tandem
Tandem is the AI platform for hardware engineering. It connects requirements, system architecture, CAD design changes, design reviews, PDM and validation evidence in one system, so design intent survives every review, change and handoff. It works inside SolidWorks, Onshape, CATIA, NX and Fusion and alongside PLM, Jira, Slack and Teams, for hardware teams building complex products from prototype through production.
Get startedSources
Frequently asked questions
What is engineering change order software?
Engineering change order software manages how a design change is proposed, assessed, approved and released, keeping an audit trail of each step. For medical device teams, the strongest fit generates the ECO from the CAD change and links it to requirements and risk. Tandem does this in your own templates, alongside your QMS and PLM.
What is the difference between an ECR and an ECO?
An engineering change request describes the problem or improvement, alternatives and risks. An engineering change order authorizes and documents the actual change once approved. In Tandem, the captured before/after CAD diff supports both, so the request and the order describe the same geometry and the same affected requirements.
Does an ECO satisfy FDA design change requirements for medical devices?
The regulation does not prescribe an ECO form, but a good change record captures the change, impact assessment, verification or validation, approvals and effective date, and ties to the design and development file. Tandem generates ECOs from CAD changes with linked requirements and redlined history; your QMS remains the system of record.
Can ECO software work alongside an existing PLM or QMS?
Yes. Tandem is not a QMS or a PLM. It runs alongside your existing PLM, with custom integrations for systems like Teamcenter and 3DEXPERIENCE built during deployment, and your QMS stays the system of record.
Related reading
Written by
Tandem
Tandem is the AI platform for hardware engineering. It connects requirements, system architecture, CAD design changes, design reviews, PDM and validation evidence in one system, so design intent survives every review, change and handoff. It works inside SolidWorks, Onshape, CATIA, NX and Fusion and alongside PLM, Jira, Slack and Teams, for hardware teams building complex products from prototype through production.