Bangladesh Vigilance Reports: Ten Working Days From the Date of Knowledge

1. Key takeaways

Bangladesh gives manufacturers and importers 10 working days to file a medical device vigilance report, and the count does not begin on the day the event occurred or on the day a patient or hospital reported it. It begins on the date the incident became known to the manufacturer or the importer. That distinction between the event date and the knowledge date is the single most consequential detail in the provision, and it is also the detail most often lost when the requirement is summarised in secondary material. The rule sits in §5 of the DGDA Medical Device Registration Guideline, and it applies once a Class B, C or D device has been placed on the market.

• The deadline is 10 working days, counted in working days rather than calendar days, so weekends and public holidays do not consume the allowance.
• The trigger is the date the incident is known to the manufacturer or the importer, not the date of the incident itself and not the date of the patient report.
• The obligation is attached to both ends of the supply chain, so the overseas manufacturer and the local licence holder each carry a clock.
• The provision applies to Class B, C and D devices once they are on the Bangladesh market.
• Serious adverse events must be analysed and reported to a designated authority in DGDA as vigilance reports, and the guideline gives no closed list defining seriousness.
• Corrective and preventive action is expected as part of the manufacturer’s quality management system, which is why the same article links reporting to CAPA.

2. Legal basis

The requirement is not spread across several instruments. It is concentrated in a single article of the registration guideline, which is why the wording of that article carries so much weight in practice. The table below sets out each element and the provision it comes from, keeping the guideline language intact so that the trigger and the deadline can be read exactly as drafted.

Two features of the drafting deserve attention before any operational decision is taken. First, the guideline anchors the deadline to knowledge rather than to occurrence, which makes the internal record of when information arrived a regulated document in its own right. Second, the same article carries the post-market surveillance obligation, the reporting obligation and the CAPA expectation, which tells us that DGDA reads these as one continuous system rather than as three separate filings. The practical consequence is that a company cannot treat the ten-day report as an isolated administrative task: the report is one visible output of a monitoring system that the guideline expects to exist whether or not an event has occurred.

3. Expert insights

Insight one: the clock starts at knowledge, and those are the two words most often missed. Chinese-language summaries frequently describe the rule as a deadline of ten working days after the event. The guideline says something different: within 10 working days from the date of incident being known to the manufacturer or importer. For organisations with a long import path and slow information transfer, that difference decides whether a file is compliant. The knowledge date is the point at which the information is recorded internally, not the point at which the hospital submitted it, and not the point at which the distributor forwarded it.

Insight two: the duty sits on the manufacturer or the importer, so both ends need a clock. The provision attaches the obligation to either party rather than designating a single responsible entity. The operational consequence is that the overseas manufacturer and the local licence holder both need a knowledge register, and whichever end learns first starts the countdown from that moment. In our experience the failure mode is not a missing register but two registers that disagree, which is why we recommend that both parties work from a single shared event log with one numbering scheme and one definition of receipt.

Insight three: serious is a threshold word, and the guideline does not supply a definition list. The text states that serious adverse events should be analysed and reported, but it does not attach criteria for determining seriousness. That silence is not permission to interpret generously. Where a case is borderline, the defensible course is to treat it as serious and report within the ten working days, leaving the interpretation to DGDA rather than resolving it internally in favour of a shorter file. A report that DGDA later judges unnecessary is a lesser problem than an unreported event that surfaces during a market visit or a renewal.

Insight four: ten working days and the fifteen calendar days in the GVP are two different regimes. For devices the applicable figure is the 10 working days in §5 of the guideline. The pharmacovigilance guideline, GVP Version 01, sets immediate reporting for serious events and no more than 15 calendar days. Both instruments exist at the same time and they are not interchangeable. Our separate article in this series, article 42, deals with the boundary between the two in detail; the point to carry into a device file is that the device figure governs device reports.

Insight five: the reporting duty and the CAPA duty are drafted together, so the file does not close at submission. Because §5 places CAPA within the quality management system in the same article as the reporting obligation, a submission that ends with the report leaves the obligation partly unmet. What DGDA is positioned to look for later is the trail from the event through the analysis to the action taken and the effectiveness check. Building that trail at the time of the event is straightforward; reconstructing it during a renewal is not.

4. Practical recommendations

• Operate a knowledge-triggered clock: the local licence holder logs any device-related adverse information arriving from a hospital, physician, distributor or patient on the same day, and the ten working day countdown starts from that entry.
• Write the definition of knowledge into the SOP, and make it broad enough to cover information received through complaint channels and social media, because those channels reach the local party before they reach the manufacturer.
• Use one event registration template for the overseas manufacturer and the local licence holder, so that the starting date cannot be disputed between two independently maintained logs.
• Count in working days on a published calendar that reflects Bangladesh public holidays, rather than converting to calendar days and hoping the margin absorbs the difference.
• Escalate borderline cases to serious and report, documenting the reasoning for the escalation decision in the event file.
• Record the CAPA decision against every reported event, including events where the conclusion is that no corrective action is required, so that the trail is complete rather than selective.

5. Verification checklist

• □ An event register exists and records the knowledge date rather than the event date
• □ The overseas manufacturer and the local licence holder share a single template
• □ The SOP defines the channels that constitute knowledge, including complaints and social media
• □ The countdown is calculated in working days, not calendar days
• □ Borderline events have been treated as serious and reported
• □ CAPA measures are recorded for every event already reported
• □ Class B, C and D products are covered by the register, with no product left outside it

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