Bangladesh Recalls and Field Corrective Action: Where CAPA Fits

1. Key takeaways

In Bangladesh a recall is not a stand-alone action. It is one link in a chain that starts long before the event occurs: recall history for the past 2 years is submitted at registration as the baseline record, systematic post-market surveillance monitors the device thereafter, serious adverse events are reported as vigilance reports within 10 working days, and corrective and preventive action or recall is the disposition step. §5 of the DGDA Medical Device Registration Guideline places post-market surveillance, vigilance reporting and CAPA in the same article, which tells us that DGDA reads a recall as an output of a system rather than as an isolated incident to be managed when it happens.

• The recall decision and the vigilance reporting decision are separate decisions with separate triggers and separate timelines, and they should not be collapsed into one process.
• §5 uses may be applied for CAPA rather than shall, so at the level of the text the CAPA expectation is advisory in tone.
• The mandatory element sits at registration: recall history for the past 2 years is a required part of the file, which creates a combination of a mandatory entry point and an advisory follow-through.
• The provision that actually compels withdrawal is the safeguard clause in §9, under which DGDA shall take all appropriate temporary measures to withdraw, prohibit or restrict marketing.
• A recall enters the dossier for the next renewal, so a decision taken today is still visible to the regulator 5 years later.
• Voluntary recall and compulsory withdrawal are different in character and different in consequence, which is the main argument for acting before the regulator acts.

2. Legal basis

The legal picture is split between an article that describes the system and an article that supplies the enforcement power. The table separates the two, and marks which rows come from the guideline text and which come from registration practice.

The division of labour between the two articles is worth stating plainly. Section 5 describes what a manufacturer is expected to maintain and to do: monitor the device systematically, analyse and report serious adverse events, and apply corrective and preventive action within the quality system. Section 9 describes what the regulator can do when the first set of expectations has not produced a safe outcome on the market. One article is written in the language of system maintenance; the other is written in the language of compulsion. A recall file that only addresses section 5 is a file that has not yet engaged with the provision that gives the regulator its power.

3. Expert insights

Insight one: §5 says may be applied rather than shall, so CAPA is framed as an expectation in the text. The wording is that appropriate corrective and preventive actions may be applied to prevent or reduce the likelihood of recurrence. At the level of the drafting this is advocacy rather than compulsion. But the recall history submitted at registration is a mandatory element, a point covered in article 26 of this series. The two together produce a specific combination: compulsory at the entry gate, advisory after the product is on the market. Companies that read only the advisory half tend to under-invest in the corrective action record, and then discover at renewal that the entry-gate requirement captures everything.

Insight two: the instrument with real force is the safeguard clause in §9. Section 9 provides that where DGDA considers a device may endanger health or safety, it shall take all appropriate temporary measures to withdraw, prohibit or restrict marketing. A voluntary recall by the company and a compulsory withdrawal ordered under §9 are consequences of an entirely different character. A voluntary recall preserves the commercial relationship and keeps the initiative with the manufacturer; a compulsory withdrawal removes that initiative and leaves a regulatory record that follows the product. The same underlying defect can produce either outcome depending on how quickly and how completely the company acted.

Insight three: a recall becomes part of the next renewal file, which is why concealment does not work. Renewal requires the submission of updated documentation, and recall history is a required component of that documentation. This means a recall that occurs today will appear directly in the renewal materials five years from now, and will be used by DGDA as part of its assessment of product safety. That is the reason we do not recommend withholding a recall from the record. A concealed event is not erased by time; it is compared against the record at the next renewal, when the discrepancy is harder to explain than the original event would have been.

Insight four: the chain has four links, and each link has its own evidence requirement. The baseline record at registration establishes what the product’s history looked like on entry. Post-market surveillance establishes that the device is being watched. The vigilance report establishes that a serious event was escalated within the ten working days. The CAPA or recall record establishes that something was done. Each link is evidenced by a different document produced at a different time by a different function, and the weakness we most often find is a file where the first and last links exist but the middle two are thin. A recall is defensible when all four links are present and dated.

Insight five: the wording of §9 covers prohibition and restriction, not only removal. The safeguard clause is not limited to taking a product off the market. It extends to prohibiting marketing and to restricting it, so the range of possible regulatory outcomes is wider than a simple recall, and planning should account for restricted supply rather than treating the choice as binary between full recall and normal trading.

4. Practical recommendations

• Establish a recall decision process that is documented separately from the vigilance reporting process, because the two have different triggers and different timelines.
• First determine whether a vigilance report is required under the 10 working day rule, and only then determine whether a recall is required; reversing the order loses days that cannot be recovered.
• Register the vigilance deadline and the recall timeline separately in the event file, so that progress on one is not mistaken for progress on the other.
• Prepare channel stop-sale notification templates in advance, addressed to every distribution channel, so that the notice goes out on the day the decision is taken rather than after drafting.
• Route all external communication through the local licence holder on a single agreed line, so that hospitals, distributors and the regulator receive the same account.
• Update the recall history file once the event is closed, in the form in which it will be submitted at the next renewal.
• Assess the exposure to a compulsory withdrawal under §9 at the outset, and treat voluntary recall as the preferred route wherever the facts support it.

5. Verification checklist

• □ A recall decision process exists and is kept separate from the vigilance reporting process
• □ The vigilance deadline and the recall timeline are registered separately
• □ Channel stop-sale notification templates are prepared and current
• □ The external line has been unified through the licence holder
• □ The recall history file has been updated after event closure
• □ The risk of a compulsory withdrawal under §9 has been assessed, with voluntary recall preferred
• □ Recall history for the past 2 years is available in the form required at registration and renewal

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