Explainer · Change control · 26 min read
Change Request, Change Order, ECO or Deviation: Which One Do You Need?
CR, CO, ECR, ECO, DCO, eCO, MCO: every company seems to use a different set of letters, and the same letters can mean different things two buildings apart. This guide decodes the names, shows what the regulations actually require, and helps you pick the right change path for what you're changing.
Step 1 · Request
Should we change?
The problem or opportunity, the proposed fix, the impact assessment and a go or no-go decision.
Also called CR, ECR, DCR, MCR
Step 2 · Order
What exactly changes?
The affected items and new revisions, effectivity, stock disposition, implementation tasks and final approval.
Also called CO, ECO, DCO, MCO, ECN
Why the names are so confusing
Here's the part that surprises people: no medical device regulation defines a "change request" or a "change order," and neither does ISO 13485. ISO 13485, which the FDA's Quality Management System Regulation (QMSR) now incorporates by reference, talks about controlling changes to documents, to the design, to processes and to the quality system itself. It never tells you what to call the records.[1][2] The software lifecycle standard IEC 62304 does use the term "change request" for software changes, but it doesn't tell you how to structure your change records either.[3]
So each company invents its own vocabulary, usually borrowed from engineering and manufacturing practice, from a previous employer, or from whatever their PLM or eQMS software calls things. After a merger or two, or once engineering and quality run on different systems, the same acronym can mean two different things in the same company.
An auditor won't care what you call it. They will check three things:
- Your procedures define your terms, so everyone knows which record to use when.
- Every change gets the controls the regulations require for that kind of change: review, verification or validation, approval before implementation, and records.
- Someone assessed the regulatory impact and wrote down the conclusion, including when the answer was "no submission needed."
The acronym decoder
These are the meanings you're most likely to meet. Where an acronym has two common meanings, both are listed, because that's exactly where misunderstandings start. Type to filter.
| Acronym | Most common meaning | Also used for | Step |
|---|---|---|---|
| CR | Change request | — | Request |
| CO | Change order | — | Order |
| ECR | Engineering change request | — | Request |
| ECO | Engineering change order | — | Order |
| ECN | Engineering change notice | Sometimes the order itself; sometimes only the announcement sent out after release | Order or after |
| eCO / eCR | Engineering change order / request | Electronic change order / request: the record in a PLM or eQMS system | Either |
| DCR | Document change request | Design change request | Request |
| DCO | Document change order | Design change order | Order |
| DCN | Document change notice | Design change notice | Order or after |
| MCR / MCO | Manufacturing change request / order | — | Either |
| PCR | Process change request | Product change request | Request |
| PCN | Product or process change notification, usually sent by a supplier | Process change notice (internal) | Input |
| SCR | Supplier change request | Software change request | Request |
| TCO / TCN | Temporary change order / notice | Overlaps with a planned deviation | Temporary |
| CCB | Change control board | Configuration control board | Approval |
| CRB | Change review board | Same role as a CCB under another name | Approval |
| ERB / ECB | Engineering review board / engineering change board | A board for engineering changes only, often alongside a separate quality or document review | Approval |
| CAB | Change advisory board, a term from IT service management | Used for changes to IT and quality system software | Approval |
| MRB | Material review board | Not a change board: it decides what happens to nonconforming material, including concessions | Nonconformance |
| CBE | "Changes being effected": a type of FDA PMA supplement, not an internal record | — | Regulatory |
No match. Your company may use its own term, which is fine as long as your procedure defines it.
Key terms in plain words
- Affected item
- Anything the change touches: a document, drawing, part, bill of materials, software version, label, piece of equipment or supplier.
- Revision
- A numbered or lettered version of an item. A change moves an item from one revision to the next, for example B to C.
- Redline
- A marked-up copy showing exactly what was added, removed or changed.
- Release
- The point at which a new revision is approved for use. Before release it's a draft; after, it's the controlled version.
- Baseline
- The approved, released set of items a change is measured against.
- Where-used
- Every place an item is referenced, such as the assemblies a part goes into or the procedures that cite a form. It shows the ripple effect of a change.
- Impact assessment
- The structured look at everything a change could affect: product, risk, testing, regulatory status, suppliers, stock, training.
- Effectivity
- When the change takes effect: a date, a lot or serial number, or completion of specific tasks.
- Disposition
- What happens to product made to the old revision: use it, rework it, scrap it, return it, or update it in the field.
- Change control board
- The group, usually cross-functional, that reviews and approves significant changes. Also called a change review board (CRB), engineering review board (ERB) or engineering change board (ECB).
Two steps under every name
Strip away the acronyms and almost every change process has the same two steps. Some companies put them in two records, some in one record with two stages, and some skip the request for low-risk changes. What matters is that both questions get answered.
| Change request | Change order | |
|---|---|---|
| Question | Should we make this change? | Exactly what changes, when, and is it ready? |
| Starts from | A problem, complaint, CAPA, audit finding, supplier notice, cost or improvement idea | An approved request, or a low-risk change your procedure allows to go straight to an order |
| Contains | Description and reason, proposed solution, initial impact assessment (product, risk, regulatory, cost, schedule) | Affected items with from and to revisions, redlines, verification or validation evidence, effectivity, stock and work-in-progress disposition, implementation tasks |
| Decision | Approve, reject or defer | Approve the new revisions for release |
| Outcome | Permission to do the work, and a record of why | Released revisions and a record that the change was implemented and closed |
| Can be skipped? | Often, for document-only or low-risk changes, if your procedure says so | No. Something has to authorize the new revisions |
A change notice (ECN, DCN) is the third piece some companies use: the announcement that tells production, suppliers or sites that new revisions are effective. Others build that communication into the order's implementation tasks.
A change, start to finish
Here is the full journey, whatever your records are called. Small changes move through it in days; big ones in months. The stages are the same.
- Initiate
Anyone can raise the need: engineering, production, quality, a supplier notice, a complaint, a CAPA or an audit finding. The request says what the problem or opportunity is, why it matters, and what's proposed. Who: the initiator. Output: a request.
- Assess
The change owner pulls in the right experts to look at everything the change could affect (see the impact assessment below), and estimates effort, cost and timing. Who: the change owner and subject experts. Output: a completed impact assessment.
- Decide
The approvers, or a change control board (CCB, CRB or ERB, depending on the company) for significant changes, approve, reject or defer. Rejected and deferred requests are closed with a reason. Who: the approvers. Output: a decision on record.
- Do the work
Update the designs, documents, software or processes; run the verification, validation or revalidation the assessment called for; collect redlines and evidence on the change order. Who: engineering, manufacturing, quality. Output: new draft revisions and evidence.
- Approve and release
Approvers review the change order (every affected item, the evidence, effectivity and disposition) and sign. Design changes must be approved before they're implemented.[2] Who: the approvers. Output: released revisions.
- Implement
Carry out the implementation tasks: training, tooling, ERP and database updates, supplier notices, regulatory submissions, label changes, stock disposition. The change takes effect according to its effectivity. Who: task owners. Output: completed tasks.
- Verify and close
Check that every task is done, the new revisions are in use, and the design and development file and medical device file reflect the change. Then close the record. Who: the change owner and quality. Output: a closed change.
What the standards actually require
Under the QMSR, US manufacturers follow ISO 13485:2016 directly, with a few FDA additions such as labeling and packaging controls, and design controls apply to Class II, Class III and some Class I devices. So the same clauses drive change control in the US, the EU and most other markets.[1] These are the ones that matter, in plain language:[2]
| Clause | Applies to | What it asks for |
|---|---|---|
| 4.2.4 | Documents | Changes are reviewed and approved by whoever approved the original, or by another function you designate that has the background to judge them. The current revision and the changes are identifiable. |
| 7.3.9 | Design changes | Determine how significant the change is to function, performance, usability, safety and regulatory requirements. Review, verify, validate as appropriate and approve before implementation. Evaluate the effect on parts, product in process or already delivered, risk management, and product realization processes. Keep records. |
| 7.5.6 | Validated processes | Procedures for process validation must cover revalidation, including the criteria that trigger it, and approval of changes to the processes, so process and equipment changes are checked against those criteria. |
| 7.4 | Suppliers and purchased product | Evaluate and re-evaluate suppliers. Where applicable, purchasing information includes a written agreement that the supplier tells you before making changes that could affect the purchased product's ability to meet your purchase requirements. |
| 4.1.4 | QMS processes | Evaluate changes for their impact on the quality management system and on the devices it produces, and control them. |
| 5.4.2 | Quality system planning | Keep the quality system intact while changes are planned and implemented. |
| 8.3.2 | Nonconforming product | Accept nonconforming product by concession only with a justification, an approval and regulatory requirements met, and record who authorized it. |
Two practical consequences. First, a design change can't be approved after the fact: the review, verification and approval come before implementation. Second, the change record isn't the end of the trail. The approved change has to show up in the design and development file, and in the medical device file when it changes the device's specifications, intended use or labeling, or how it's made, installed or serviced.[2]
Change types, side by side
The record may be the same, but the checks inside it depend on what's changing. Open each card for the details.
Document-only
Typos, formatting, clarifying wording, adding a missing step that people already follow.
Typical path: order only (DCO, DCN)
Read more
Controls: review and approval by the original approving function or a designated one; new revision identified; training if the change affects how people do the work.[2]
Watch out for: "document-only" changes that aren't. If the edit changes a specification, an acceptance criterion, a process parameter or a label, it's a design, process or labeling change and needs those controls.
Design
Specifications, components, materials, dimensions, principle of operation, packaging, accessories.
Typical path: request, then order
Read more
Controls: significance determined; review, verification and validation as appropriate, and approval before implementation; effect on parts, work in progress, delivered product, risk management and product realization processes evaluated.[2]
Regulatory: assess against the 510(k), PMA, notified body and other market rules, and check whether the change creates a new version or model that needs a new device identifier.[4][5]
Watch out for: small changes that add up. Several minor changes since the last clearance can together amount to a significant one.[4]
Software
New features, bug fixes, algorithm updates, operating system or library updates, cybersecurity patches.
Typical path: request, then order (often grouped by release)
Read more
Controls: the same design change controls, plus software change control under IEC 62304: analyze each change request, approve it before implementation, run regression testing, and record the software version as an affected item.[3]
Regulatory: FDA has a separate guidance for deciding whether a software change needs a new 510(k).[6] A predetermined change control plan (PCCP) authorized by FDA can cover planned changes without a new submission, as long as each change is consistent with the plan. PCCPs are most developed for AI-enabled software.[7][8]
Watch out for: patches pushed under time pressure. Plan an expedited path in your procedure rather than skipping the record.
Labeling
Labels, instructions for use, warnings, indications, translations, symbols, packaging artwork.
Typical path: request, then order; editorial fixes may go straight to order
Read more
Controls: content review by regulatory and clinical where claims or warnings change; artwork proofing; translations; label inspection at implementation.
Regulatory: indications and warnings carry the most weight. For PMA devices, labeling changes that add or strengthen a warning or instruction for safe use can be put into effect before FDA approval, once FDA acknowledges receipt, as a "Special PMA Supplement — Changes Being Effected."[9] In the EU, a change in critical warnings or contraindications, such as "contains latex," needs a new UDI-DI.[10]
Watch out for: database updates (GUDID, EUDAMED) and every language version, which belong in the implementation tasks.
Manufacturing process
Process parameters, methods, work instructions that change how product is made, sterilization, moving or adding a site.
Typical path: request, then order
Read more
Controls: check your revalidation criteria; update process risk analysis; qualify new equipment; verify first production against the specification.[2]
Regulatory: a manufacturing process change that could significantly affect safety or effectiveness can trigger a new 510(k).[7] For PMA devices, manufacturing changes that affect safety and effectiveness usually go to FDA as a 30-day notice; a new facility, sterilization or packaging change may need a PMA supplement.[9] In Canada, manufacturing process, facility and equipment changes can be significant changes for Class III and IV licences.[11]
Watch out for: a site move treated as a logistics project. It's a process change with validation behind it.
Supplier or material
New supplier, second source, supplier moving its own production, a different material or grade.
Typical path: request, then order; same-specification second sources may go straight to order
Read more
Controls: supplier evaluation and approval; updated purchasing information; verification of the first lots; biocompatibility and other material testing where the material touches patients.[2]
Regulatory: a material change can be a design change in FDA's eyes; its 510(k) guidance has a separate materials flowchart.[4] FDA expects you to analyze supplier-driven material changes even when the material stays within its original specification, and treats changes to a supplier's processing or finishing steps as material changes.[4] In the EU, MDCG 2020-3 gives a new supplier with unchanged specifications as an example of a change that isn't significant for legacy devices.[12]
Watch out for: supplier changes you hear about late. Your purchasing agreement should require advance notice.
Equipment
New or replacement production or test equipment, fixture changes, equipment software updates.
Typical path: order, or request then order if a validated process is affected
Read more
Controls: installation and operational qualification, calibration set-up, maintenance plan, and a revalidation decision for any validated process the equipment runs.[2]
Watch out for: "like-for-like" replacements. Same model, different firmware or settings, can still change the process. Write down why it's equivalent.
QMS process
Procedures, forms, organization changes, new eQMS or ERP software, moving a quality function.
Typical path: order (document change), with an impact assessment for larger changes
Read more
Controls: evaluate the impact on the quality system and on devices; keep the system intact during the transition; train; validate any software used in the quality system.[2]
Regulatory: under the MDR, plans for substantial changes to the quality system must be reported to the notified body before they're made.[13]
The impact assessment, area by area
The impact assessment is the heart of a change. Most problems found later, in audits or in the field, trace back to an area nobody asked about. Go through each one and record the answer, even when it's "not affected."
| Area | Ask | Typical evidence if affected |
|---|---|---|
| Requirements | Does it change any design input, specification or acceptance criterion? | Updated requirements and traceability |
| Risk | Does it add a hazard, change a risk estimate, or weaken or remove a risk control? | Updated risk analysis and risk management file[14] |
| Verification and validation | Which existing test results still hold, and which must be repeated? | Test rationale, new test reports |
| Usability | Does it change what users see, do or are told? | Updated use-related risk analysis; usability evaluation if needed |
| Software and cybersecurity | Does it change code, configuration, interfaces or third-party components? | Regression testing, updated software bill of materials and threat model |
| Biocompatibility and sterility | Does it change a patient-contacting material, a process aid, sterilization or packaging? | Biological evaluation update; sterilization and packaging validation |
| Manufacturing | Does it change a process, parameter, tool, fixture, piece of equipment or site? | Revalidation decision, process risk analysis, first-article inspection |
| Suppliers | Does it change what you buy, from whom, or the specification you buy to? | Supplier approval, updated purchase specifications, supplier notice |
| Labeling | Does it change labels, instructions, claims, warnings or symbols, in any language? | Label review and proofs, translations |
| Regulatory | Does it need a submission, notification or licence amendment in any market? A new device identifier? | Regulatory assessment by market |
| Clinical and post-market | Does it affect clinical evidence, the clinical or performance evaluation, or how you monitor the device in the field? | Evaluation update, post-market surveillance plan update |
| Inventory and field | What happens to stock, work in progress and product already shipped? | Disposition decision; field action assessment |
| Documents and training | Which procedures, forms, work instructions and records change, and who must be trained? | Where-used list, training plan |
| Service and customers | Do service procedures, spare parts or customer communications change? | Service documentation update, customer notice |
ISO 13485 names the core of this list for design changes: the effect on constituent parts, product in process or already delivered, risk management, and product realization processes.[2] The other rows are where experience says changes go wrong.
Change, deviation or concession?
These get blurred more than anything else in change control. The deciding questions are: is it permanent, was it planned, and does the product still meet its requirements?
| Permanent change | Planned deviation | Concession | Nonconformance | |
|---|---|---|---|---|
| What it is | A planned, lasting change to the product, process or documents | A planned, temporary departure from a spec or procedure, limited by time, quantity or lots | A decision to use or release product that doesn't meet a requirement | An unplanned finding that something doesn't meet a requirement |
| Approved | Before implementation | Before it happens | After the fact, on specific product | Recorded when found |
| Product meets requirements? | Yes, the new ones | Not the original spec; the departure is approved in advance, justified and risk-assessed | No, accepted with justification | No, until dispositioned |
| Typical record | CR and CO | Deviation or temporary change order | Disposition on the nonconformance ("use as is") | Nonconformance report |
| ISO 13485 | 4.2.4, 7.3.9, 7.5.6 | Not named in ISO 13485 (ISO 9000:2015, which the QMSR also references, calls it a "deviation permit"); controlled through your procedures and risk management | 8.3.2 | 8.3 |
The regulatory impact check
Every design, labeling, process and material change should end with a documented regulatory assessment, even when the answer is "no submission needed." That written rationale is what an inspector asks for.[4]
United States · 510(k)
A new 510(k) is required when a change could significantly affect safety or effectiveness, for example in design, material, chemical composition, energy source or manufacturing process, or when the intended use changes in a major way.[7]
Read more
FDA's two 2017 guidances walk through the decision with flowcharts: one for general device changes (labeling; technology, engineering and performance; materials; and IVD-specific changes) and one for software changes.[4][6]
Compare the changed device with the version FDA most recently cleared, not with a predicate device as you would for substantial equivalence, and assess changes both one at a time and together. When you conclude no 510(k) is needed, document the change and your rationale.[4]
When a new 510(k) is needed for a well-understood change to your own device, a Special 510(k) is often the faster route.[15] A change that's consistent with an authorized PCCP doesn't need a new 510(k) at all.[7]
United States · PMA
Changes that affect safety or effectiveness need a PMA supplement before they're made, unless FDA allows a different route. Changes that don't affect safety or effectiveness go in the periodic report.[9]
Read more
The regulation lists typical supplement triggers: new indications, labeling changes, a different manufacturing facility, sterilization or packaging changes, design and performance changes, and some shelf life extensions.[9]
There are faster routes. Labeling changes that add or strengthen a warning or instruction for safe use, and quality control or manufacturing changes that add assurance, can be put into effect before approval through a "Changes Being Effected" supplement, once FDA acknowledges receiving it. Manufacturing procedure changes that affect safety and effectiveness can usually go as a 30-day notice; you may distribute 30 days after FDA receives it unless FDA says the notice is inadequate, in which case a 135-day supplement is needed.[9]
United States · UDI and PCCP
A change that creates a new version or model needs a new device identifier, and so does a new device package.[5] A predetermined change control plan lets FDA authorize planned future changes in advance.
Read more
A PCCP has three parts: a description of the planned modifications, the protocol for developing, validating and implementing them, and an impact assessment. FDA's guidance for AI-enabled device software functions is final (first issued December 2024, current version August 2025); its guidance for devices in general was still in draft when we checked in November 2026.[8][16]
Changes made under an authorized PCCP still go through your change control. The plan removes the need for a new submission, not the need for records.
European Union · MDR
Manufacturers must keep series production in conformity and take changes in design or characteristics into account promptly.[17] Where a notified body certified the device, changes that could affect safety and performance or the conditions of use need its approval, and plans for substantial quality system changes must be reported to it.[13] Class I self-certified devices update their own technical documentation and declaration of conformity.
Read more
Under Annex IX, you must tell your notified body about plans for substantial changes to the quality system or the range of devices it covers; approval comes as a supplement to the certificate. Changes to a device whose technical documentation the notified body assessed need its approval if they could affect safety and performance or the conditions prescribed for use; the notified body decides whether a new assessment is needed or a supplement is enough.[13] The IVDR has parallel provisions (Annex IX, Sections 2.4 and 4.11).[18] Article 10(9) also makes changes to harmonised standards or common specifications a reason to revisit conformity.[17]
For legacy devices still on MDD or AIMDD certificates under the MDR transition, a significant change in design or intended purpose ends that status. MDCG 2020-3 explains what counts, and lists examples that don't, such as a new supplier with unchanged specifications or editorial label corrections.[12]
A change that could lead to misidentification, such as a new trade name, version, sterile status or quantity per package, needs a new UDI-DI.[10]
Canada
For Class III and IV devices, a significant change requires a licence amendment before you sell the changed device.[11]
Read more
Health Canada treats a significant change as one that could reasonably be expected to affect safety or effectiveness, including changes to the manufacturing process, facility or equipment, quality control procedures, design and intended use. Changes that aren't significant are still documented in your quality system.[11]
Other licence amendment triggers include changes to the device's class, name or identifier, the manufacturer's name and, for most Class II devices, the medical conditions, purposes or uses the device is marketed for.[11]
Effectivity and disposition, explained
Two questions every change order must answer, and the two most often left vague: when does the new revision take over, and what happens to everything made the old way?
Effectivity options
- On approval. Common for documents and procedures.
- On a date. Gives time for training, tooling or supplier lead time.
- From a lot or serial number. Makes traceability clear: everything from that point on is the new revision.
- When named tasks are complete. For example, after training is done and new labels arrive.
- When old stock runs out. Only when the old revision is still acceptable to use, and the assessment says so.
Disposition options
- Use as is. The old revision is still acceptable; ship or use up existing stock.
- Rework or upgrade. Bring stock or work in progress to the new revision.
- Scrap. The old revision must not be used.
- Return to supplier. For purchased items affected by the change.
- Update in the field. For product already with customers. If the reason is to reduce a risk to health, or to fix a violation that may present one, check whether it's a reportable correction or removal under 21 CFR Part 806 (US) or a field safety corrective action (EU).[19][20]
Decide disposition separately for each place product can be: raw materials, work in progress, finished goods, distributors and the field. "Use up existing stock" is a valid answer only when the impact assessment shows the old revision is still safe and effective.
Which path do I need?
Answer two or three questions to see the usual path and the checks it needs. It's a starting point for your own procedure, not a substitute for it.
1. What's happening?
2. What's changing?
3. Could it affect safety, performance, intended use or regulatory requirements?
What a good change order contains
Whatever you call it, a change order that holds up in an audit answers all of these. Use it as a checklist for your template.
- The reason. A link to the approved request, CAPA or complaint, or the rationale for going straight to an order.
- Every affected item, with from and to revisions. Documents, drawings, parts and bills of materials, software versions, labels, equipment, suppliers.
- What changed in each. Redlines or a clear description, so approvers can see the difference without opening ten files.
- The evidence. Verification, validation or revalidation results, or the rationale for why none were needed.
- The impact assessment. Risk management updates, regulatory conclusion by market, and whether a new device identifier is needed.
- Effectivity. A date, a lot or serial number, or completion of named tasks.
- Disposition of what already exists. Stock, work in progress, product at distributors and in the field: use, rework, scrap or return.
- Implementation tasks with owners. Training, tooling, ERP and database updates, supplier notices, submissions, translations.
- The right approvals. The functions your procedure names for this kind of change, signed before release.
- Closeout. A check that every task is done and that the design and development file and medical device file reflect the change.
Common mistakes, and the fix
For design changes, approval must come before implementation. Build an expedited path for urgent work instead.[2]
"No impact" with no reasoning. Use a structured list like the one above, and record the reason for every "not affected."
The change was fine, but nobody wrote down why no submission was needed. Make the regulatory assessment a required field.
The drawing changed but the work instruction, inspection plan or label didn't. Check where-used before approval.
Nobody can say which units have the change. Name a date, lot or serial number, and decide disposition for every stage.
The same temporary deviation renewed again and again. Convert it to a permanent change or fix the cause.
Many small changes, each assessed alone, that together change the device significantly. Compare against the version last cleared or certified, not just the previous revision.[4]
Released but never verified as implemented. Close only when every task is done and the files are updated.
Common questions
Do we need a change request to fix a typo?
Usually not. Most procedures let document-only corrections go straight to an order, but the corrected document still needs review and approval.[2]
Read more
The test is whether the edit changes any requirement. Fixing "recieve" is editorial. Changing "10 mm" to "1.0 mm" is not, even if someone calls it a typo: it changes a specification, so it needs the controls for a design or process change.
Define in your procedure what counts as editorial, and give examples. That stops the fast path from becoming a loophole.
Can one change order cover several changes?
Yes, if they're related and will be implemented together. Bundling unrelated changes makes review harder and can hold a simple change hostage to a complex one.
Read more
For the regulatory assessment, FDA expects changes to be assessed one at a time and together, against the most recently cleared device. Grouped changes on one order make that combined view easier; scattered changes over several months make it easy to miss.[4]
A common rule of thumb: one order per release or per reason. One request can also spawn several orders, for example a design order and a separate supplier order.
Can a change request exist without a change order?
Yes. Requests that are rejected or deferred never get an order, and that record still matters.
Read more
A rejected request shows that a concern was considered and why it was declined. That's useful in an audit, in a complaint investigation, and the next time someone proposes the same idea.
Close rejected and deferred requests with a reason, rather than leaving them open indefinitely. Old open requests read as an unmanaged backlog.
Who should approve a change?
The functions with the knowledge to judge it, as named in your procedure. For documents, ISO 13485 says the original approving function or a designated function with access to the background.[2]
Read more
Many companies use a change control or change review board for significant changes, with engineering, quality, regulatory, manufacturing and supply chain represented, and a lighter approval matrix for minor ones. Some split it, with an engineering review board for design changes and a separate review for documents or the quality system. A material review board (MRB) is different: it decides the disposition of nonconforming material, not changes.
Scale approvals to risk. Too few approvers misses impacts; too many slows every change and encourages people to work around the system.
What about urgent changes?
Plan an expedited path in your procedure. Speed comes from fewer waiting steps, not from skipping the record or approving afterwards.
Read more
For design changes, ISO 13485 requires review, verification and approval before implementation, so "fix now, paperwork later" doesn't work.[2] A planned deviation can bridge a short gap while the permanent change is processed, if the risk is assessed and the deviation is approved before use.
On the regulatory side, PMA holders have a "Changes Being Effected" route for safety labeling and added quality controls, which can be implemented before FDA approval once FDA acknowledges receipt.[9]
A supplier changed something without telling us. Now what?
Treat it as a nonconformance against your purchasing agreement, assess the product already received, and ask the supplier for a corrective action.
Read more
ISO 13485 expects purchasing information to include, where applicable, an agreement that the supplier notifies you before making changes that could affect the purchased product's ability to meet your purchase requirements.[2] If that clause wasn't in the agreement, add it.
Then evaluate the change as if it had been proposed: does it affect your device, its validation or its regulatory status? If you decide to keep the change, run it through your normal change process.
Do we need formal change control during development?
Design changes need to be controlled throughout, but most companies use a lighter method before the design is first released, then switch to formal change orders once there's a released baseline.
Read more
ISO 13485's design change clause isn't limited to released products.[2] In practice, early design changes are usually controlled through design reviews, version control and updated design records, with the reasoning captured as you go.
Whatever you choose, write it into your procedure: when the switch to formal change orders happens (for example, at design transfer or the first release for production) and how changes before that point are recorded.
Does every change need a regulatory assessment?
Every change to the design, labeling, manufacturing process or materials should get one, even if it takes a single line. Purely editorial document changes usually don't.
Read more
FDA's 510(k) change guidance stresses documenting the decision, especially when you conclude no new 510(k) is needed.[4] The same record then answers your notified body and other regulators.
Assess each market you sell in. A change that needs nothing in one market can need a notification or licence amendment in another.
How long do we keep change records?
At least the lifetime of the device as you define it, and never less than two years from the device's release, unless a regulation requires longer. The EU MDR, for example, requires technical documentation to be kept for at least 10 years after the last device is placed on the market, or 15 years for implantables.[2][21]
Read more
Keep the request, the order, the impact assessment, the evidence and the approvals together, or linked, so the full story of the change can be reconstructed years later.
Rejected and deferred requests are records too.
References
- 21 CFR Part 820, Quality Management System Regulation (QMSR), §§ 820.7 (incorporating ISO 9000:2015 clause 3 and ISO 13485:2016 by reference), 820.10 (including (c), scope of design controls) and 820.45 (labeling and packaging controls), effective 2 February 2026. www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-820
- ISO 13485:2016, Medical devices — Quality management systems — Requirements for regulatory purposes, clauses 4.1.4, 4.2.3, 4.2.4, 4.2.5, 5.4.2, 7.3.9, 7.3.10, 7.4.1, 7.4.2, 7.5.6, 8.3 and 8.3.2. www.iso.org/standard/59752.html
- IEC 62304:2006 with Amendment 1:2015, Medical device software — Software life cycle processes, clauses 6 (software maintenance) and 8 (software configuration management, including change control). webstore.iec.ch/en/publication/22794
- U.S. FDA, Deciding When to Submit a 510(k) for a Change to an Existing Device, final guidance, October 2017. www.fda.gov/regulatory-information/search-fda-guidance-documents/deciding-when-submit-510k-change-existing-device
- 21 CFR 830.50, changes that require use of a new device identifier. www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-830/subpart-B/section-830.50
- U.S. FDA, Deciding When to Submit a 510(k) for a Software Change to an Existing Device, final guidance, October 2017. www.fda.gov/regulatory-information/search-fda-guidance-documents/deciding-when-submit-510k-software-change-existing-device
- 21 CFR 807.81(a)(3) and (b)(1)(ii), when a premarket notification is required for a changed device, and the exception for changes consistent with a PCCP. www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-807/subpart-E/section-807.81
- U.S. FDA, Marketing Submission Recommendations for a Predetermined Change Control Plan for Artificial Intelligence-Enabled Device Software Functions, final guidance, August 2025 (originally issued December 2024). www.fda.gov/regulatory-information/search-fda-guidance-documents/marketing-submission-recommendations-predetermined-change-control-plan-artificial
- 21 CFR 814.39, PMA supplements, including paragraphs (a) supplement triggers, (b) periodic reports, (d) Special PMA Supplement — Changes Being Effected, and (f) 30-day notices. www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-814/subpart-B/section-814.39
- Regulation (EU) 2017/745 (EU MDR), Annex VI, Part C, Section 3.9, changes requiring a new UDI-DI. eur-lex.europa.eu/eli/reg/2017/745/oj
- Health Canada, Medical Devices Regulations (SOR/98-282), section 1 (definition of significant change) and section 34 (licence amendments); and Health Canada, Guidance on how to interpret "significant change" of a medical device, updated 31 March 2026. www.canada.ca/en/health-canada/services/drugs-health-products/medical-devices/application-information/guidance-documents/interpret-significant-change-medical-device.html
- MDCG 2020-3 Rev.1, Guidance on significant changes regarding the transitional provision under Article 120 of the MDR with regard to devices covered by certificates according to MDD or AIMDD, May 2023. health.ec.europa.eu/system/files/2023-09/mdcg_2020-3_en_1.pdf
- Regulation (EU) 2017/745 (EU MDR), Annex IX, Sections 2.4 (changes to the approved quality management system) and 4.10 (changes to the approved device). eur-lex.europa.eu/eli/reg/2017/745/oj
- ISO 14971:2019, Medical devices — Application of risk management to medical devices. www.iso.org/standard/72704.html
- U.S. FDA, The Special 510(k) Program, final guidance, September 2019. www.fda.gov/regulatory-information/search-fda-guidance-documents/special-510k-program
- U.S. FDA, Predetermined Change Control Plans for Medical Devices, draft guidance, August 2024. www.federalregister.gov/documents/2024/08/22/2024-18828/predetermined-change-control-plans-for-medical-devices-draft-guidance-for-industry-and-food-and-drug
- Regulation (EU) 2017/745 (EU MDR), Article 10(9). eur-lex.europa.eu/eli/reg/2017/745/oj
- Regulation (EU) 2017/746 (EU IVDR), Annex IX, Sections 2.4 and 4.11. eur-lex.europa.eu/eli/reg/2017/746/oj
- 21 CFR Part 806, Medical Devices; Reports of Corrections and Removals, § 806.10. www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-806
- Regulation (EU) 2017/745 (EU MDR), Articles 87 and 89, reporting and analysis of serious incidents and field safety corrective actions. eur-lex.europa.eu/eli/reg/2017/745/oj
- Regulation (EU) 2017/745 (EU MDR), Article 10(8), retention of technical documentation. eur-lex.europa.eu/eli/reg/2017/745/oj
Regulations and guidance were checked against primary sources in November 2026. Company names for change records vary; the acronym meanings shown are common usage, not regulatory definitions.