Bangladesh Change Management: Minor Changes, Major Changes and Retesting

1. Key takeaways

The DGDA Medical Device Registration Guideline does not contain a dedicated article on change management. There is no change chapter, no notification form and no defined classification of variations in the text. Practice therefore fills the gap with a two-tier approach: minor changes, such as packaging text or appearance, are handled by way of notification, while changes involving core technical parameters require fresh test or verification evidence. The handling period in practice is about 1 month. Of all the topics in this series, this one has the strongest practical estimate character, and should be read as such.

• The guideline has no change management article, so the classification into minor and major changes is not a regulatory definition but a working convention.
• Minor changes are notified; changes touching core technical parameters require the submission of new test or verification evidence.
• The working assumption for turnaround is about 1 month, and it should be built into project plans as an estimate rather than a guarantee.
• §4.9 allows DGDA to take such other verification measures as it considers necessary, which is the provision that gives the regulator room to ask questions about a change.
• Where a change affects the coverage of the CFS, a supplementary CFS is required, and this test takes precedence over any technical assessment of the change itself.
• An unrecorded change does not disappear; it resurfaces at renewal, when the current documents are submitted again.

2. Legal basis

The legal position is defined as much by what is absent as by what is present. Sections 4 to 9 of the guideline deal with classification, registration requirements, post-market obligations and safeguards, and none of them establishes a change procedure. The table records that absence explicitly, because a file should not cite a provision that does not exist.

Two provisions do the work that a change article would otherwise do. Section 4.9 permits DGDA to adopt verification measures beyond sampling where it considers them necessary, which is broad enough to cover a request for evidence about a modified device. Section 9 provides the safeguard power to withdraw, prohibit or restrict marketing. Between a discretionary power to verify and a power to act on the result, the regulator does not need a change chapter in order to control changes; it needs only to notice that a change has occurred.

3. Expert insights

Insight one: no article does not mean no requirement. The absence of a change chapter is sometimes read as an absence of control, and that reading is the source of most of the difficulty in this area. Section 4.9 on other verification measures and section 9 on safeguards together create a discretionary space in which DGDA can examine a change and act on what it finds. Where the text is silent, the weight shifts towards established practice and towards the judgement of individual officials on the file. That is precisely why change management in Bangladesh has to be handled by asking before acting, rather than by acting and then explaining.

Insight two: the first filter for classifying a change is whether it falls outside CFS coverage. Product codes follow the CFS, a point covered in article 4 of this series. Any change that goes beyond the scope of the CFS list requires a supplementary CFS before anything else happens, and this operates as a single blocking condition that is independent of the technical significance of the change. A change that is technically trivial can still be blocked if it moves the product outside the coverage of the certificate, and a change that is significant may pass this filter and then need evidence at the second. Running the tests in the wrong order wastes the month the process is likely to take.

Insight three: changes and renewal draw on the same documents, so unrecorded changes surface later. Renewal requires the submission of current documentation, including the CE certificate and the packaging materials. A change that was never recorded will therefore be visible at renewal as a discrepancy between what was filed and what is now in use. The discrepancy is more difficult to explain than the change would have been, because it invites a question about what else was not notified. We recommend a change log that records the date, the content and the evidence reference for each change, so that the renewal file can cite the log directly instead of reconstructing history from emails.

Insight four: the one month estimate is a planning figure, not a service standard. Because the period comes from practice rather than from a published timeline, it should be treated the way any practical estimate is treated: as a reasonable basis for scheduling, with contingency, and with the recognition that a file which raises questions will take longer. The risk in using the figure is not that it is wrong on average, but that it is used as a commitment in a launch plan and then becomes the explanation for a missed date. Where a change is commercially critical, confirm the estimate in writing before the timeline is fixed.

Insight five: the two-tier convention is a substitution for a classification rule, so it needs internal definition. Since the guideline does not define what counts as minor, a company has to define it for itself, in writing, before the first change arises. Packaging text and appearance are the examples that practice treats as minor. Everything touching core technical parameters goes the other way. The space between those two poles is where disputes occur, and the way to occupy it is a written internal procedure that names the parameters considered core for each product family.

4. Practical recommendations

• Follow a fixed sequence: first determine whether the change falls outside CFS coverage, then determine whether it touches core technical parameters, and only then decide between notification and supplementary evidence.
• Complete that assessment before the change is implemented, rather than seeking to remedy the position afterwards.
• Define in writing which parameters are treated as core for each product family, so that the minor and major distinction is applied consistently across files and across staff.
• Record every change in a single log with the date, the content and the evidence reference, linked to the same numbering system used for the registration dossier and the renewal documents.
• Reserve about 1 month in the project schedule for handling a change, and confirm the estimate in writing where the change is commercially critical.
• Use one numbering system across the registration dossier, the change log and the renewal file, because in a paper-based market that is the only way to make the documents reconcile five years later.
• Where a change is significant, confirm the approach in writing with DGDA or with the local partner before submission, and mark the confirmation as a practical estimate in the file.

5. Verification checklist

• □ It is confirmed that the guideline contains no dedicated change management article, and the approach is documented as a practical estimate
• □ The CFS coverage test has been applied first, as a blocking condition
• □ Minor changes by notification are distinguished from changes to core technical parameters requiring evidence
• □ About 1 month has been reserved in the schedule for change handling
• □ A change log exists and uses the same numbering as the registration dossier
• □ Written confirmation has been obtained from DGDA or the local partner before a major change, with the practical estimate noted
• □ The internal definition of core technical parameters is documented for each product family

Regulatory information verified as at 27 October 2026.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across South Asia, including Bangladesh. Our team prepares dossiers to DGDA expectations, manages submissions and deficiency responses, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com